WintelGuy.com

URL Redirection Checker

URL:

Enter a valid URL.

About URL Redirection Checker

This URL Redirection Checker is an online tool designed to help users investigate URL redirections. When you input a URL, the tool follows the URL's redirect chain (if any), displaying detailed information about each step.

Enter the URL:

  • Start by entering the URL you wish to check in the input field (e.g., https://example.com). Make sure to include scheme or protocol details, such as "http://" or "https://", in your URL.

Run the Check:

  • Once the URL is entered, press the "Check Redirect" button. The tool will process the URL, follow any redirections, and gather related DNS and SSL details for each step.

View Results:

  • The results will show the following details:
    • URL Info: Lists all URLs in the redirection chain.
    • HTTP Status Code: Displays codes such as 301 (permanent redirect), 302 (temporary redirect), or 200 (successful request), etc. See below for the complete status code list.
    • DNS: Includes the IP addresses and aliases for the domain names.
    • SSL Certificate Info: If the URL is HTTPS, the certificate's common name (CN), subject alternative names (SANs), issuer, and validity period will be displayed.
  • If the URL does not have a redirect, you will see the details about the original URL alone.

The URL Redirection Checker is an essential tool for investigation and validation of URL redirects, DNS resolution, and SSL configuration. By providing comprehensive insights, this tool may be very useful in many scenarios, including:

SEO and User Experience Management:

  • Ensuring a smooth user experience by verifying that your website's URLs redirect efficiently and accurately to the intended destination.
  • Confirming that URLs are optimized for search engines by avoiding long redirect chains or loops.

Website Migration:

  • When migrating a site to a new domain, all previous links must correctly redirect to the new site. This tool helps verify that each step of the process functions properly, ensuring no broken or incorrect redirects.

URL Reputation Investigation:

  • The tool can "reveal" the target URL behind a shortened link helping to reduce the risk of exposure to malicious content.

Quick URL Redirection Overview

What is HTTP Redirection?

HTTP redirection occurs when a server sends a response to a browser or client telling it to request a different URL instead of the one originally entered. The most common types of server-side redirects are:

  • 301 Moved Permanently: A permanent redirect. Search engines will update their index with the new URL.
  • 302 Found (Temporary Redirect): A temporary redirect, meaning that the client should still use the original URL in future requests.
  • 303 See Other: Redirects to a new URL with a GET request (typically after a POST request).
  • 307 Temporary Redirect: Similar to 302, but mandates the method (GET or POST) remains the same during the redirection.
  • 308 Permanent Redirect: Like 301 but ensures the same method is used (GET remains GET, POST remains POST).

How HTTP Redirection Works.

HTTP redirection is triggered by the server when the client requests a URL. The server responds with an HTTP status code such as 301, 302, etc., accompanied by a "Location" header, which contains the URL the client should be redirected to. The browser or HTTP client automatically follows the new URL.

What is HTML Meta Redirection?

HTML meta redirection, also known as client-side redirect, happens when a webpage includes a special <meta> tag with a http-equiv attribute set to "refresh". This tag directs the browser to automatically refresh or load a new page after a specified delay. Here is an example of a meta redirect:

<meta http-equiv="refresh" content="0; url=https://new-url.example.com">

The content attribute specifies the redirect delay (0 seconds), followed by the URL to redirect to. In the example above, the browser will open https://new-url.example.com immediately after the initial page is loaded.

What is Redirection Used For?

  • Changing URLs: If the structure of a site changes, redirects can be used to ensure users and search engines are directed to the correct new URLs.
  • Shortened URLs: URL shortening services (for example, bit.ly) use redirects to make long URLs easier to share.
  • Load Balancing: Sometimes, redirection is used to distribute traffic between multiple servers.
  • Security Enhancements: Websites may use redirects to force users to switch from HTTP to HTTPS, ensuring secure connections.

HTTP Status Codes

Value Description Reference
1xx Informational
100 Continue [RFC9110, Section 15.2.1]
101 Switching Protocols [RFC9110, Section 15.2.2]
102 Processing [RFC2518]
103 Early Hints [RFC8297]
2xx Successful
200 OK [RFC9110, Section 15.3.1]
201 Created [RFC9110, Section 15.3.2]
202 Accepted [RFC9110, Section 15.3.3]
203 Non-Authoritative Information [RFC9110, Section 15.3.4]
204 No Content [RFC9110, Section 15.3.5]
205 Reset Content [RFC9110, Section 15.3.6]
206 Partial Content [RFC9110, Section 15.3.7]
207 Multi-Status [RFC4918]
208 Already Reported [RFC5842]
226 IM Used [RFC3229]
3xx Redirection
300 Multiple Choices [RFC9110, Section 15.4.1]
301 Moved Permanently [RFC9110, Section 15.4.2]
302 Found [RFC9110, Section 15.4.3]
303 See Other [RFC9110, Section 15.4.4]
304 Not Modified [RFC9110, Section 15.4.5]
305 Use Proxy [RFC9110, Section 15.4.6]
306 (Unused) [RFC9110, Section 15.4.7]
307 Temporary Redirect [RFC9110, Section 15.4.8]
308 Permanent Redirect [RFC9110, Section 15.4.9]
4xx Client Error
400 Bad Request [RFC9110, Section 15.5.1]
401 Unauthorized [RFC9110, Section 15.5.2]
402 Payment Required [RFC9110, Section 15.5.3]
403 Forbidden [RFC9110, Section 15.5.4]
404 Not Found [RFC9110, Section 15.5.5]
405 Method Not Allowed [RFC9110, Section 15.5.6]
406 Not Acceptable [RFC9110, Section 15.5.7]
407 Proxy Authentication Required [RFC9110, Section 15.5.8]
408 Request Timeout [RFC9110, Section 15.5.9]
409 Conflict [RFC9110, Section 15.5.10]
410 Gone [RFC9110, Section 15.5.11]
411 Length Required [RFC9110, Section 15.5.12]
412 Precondition Failed [RFC9110, Section 15.5.13]
413 Content Too Large [RFC9110, Section 15.5.14]
414 URI Too Long [RFC9110, Section 15.5.15]
415 Unsupported Media Type [RFC9110, Section 15.5.16]
416 Range Not Satisfiable [RFC9110, Section 15.5.17]
417 Expectation Failed [RFC9110, Section 15.5.18]
418 (Unused) [RFC9110, Section 15.5.19]
421 Misdirected Request [RFC9110, Section 15.5.20]
422 Unprocessable Content [RFC9110, Section 15.5.21]
423 Locked [RFC4918]
424 Failed Dependency [RFC4918]
425 Too Early [RFC8470]
426 Upgrade Required [RFC9110, Section 15.5.22]
428 Precondition Required [RFC6585]
429 Too Many Requests [RFC6585]
431 Request Header Fields Too Large [RFC6585]
451 Unavailable For Legal Reasons [RFC7725]
5xx Server Error
500 Internal Server Error [RFC9110, Section 15.6.1]
501 Not Implemented [RFC9110, Section 15.6.2]
502 Bad Gateway [RFC9110, Section 15.6.3]
503 Service Unavailable [RFC9110, Section 15.6.4]
504 Gateway Timeout [RFC9110, Section 15.6.5]
505 HTTP Version Not Supported [RFC9110, Section 15.6.6]
506 Variant Also Negotiates [RFC2295]
507 Insufficient Storage [RFC4918]
508 Loop Detected [RFC5842]
510 Not Extended (OBSOLETED) [RFC2774]
511 Network Authentication Required [RFC6585]

Links and References