HTTP
URL redirect checker
Follow redirects, inspect every HTTP hop and find the final URL.
Recent checks
How to use this tool
- A redirect trace is a chronological record of every HTTP response between an entered URL and the final destination. It exposes status codes, Location headers, protocol changes, hostname changes, timing, and loops without relying on browser cache. Start with the externally visible URL, identify the first incorrect response, map that hop to the system that generated it, change one rule, purge relevant caches, and repeat. Keep each public move to one intentional permanent hop whenever possible. In the area of "redirect status codes and method preservation", read the result from the first hop because later responses may only mask an earlier rule. Record source and target, verify the owning layer, compare behavior without cookies and after cache purge. After a change, re-measure the same URL to confirm a shorter, unambiguous, stable path for users and crawlers.
- A redirect trace is a chronological record of every HTTP response between an entered URL and the final destination. It exposes status codes, Location headers, protocol changes, hostname changes, timing, and loops without relying on browser cache. Start with the externally visible URL, identify the first incorrect response, map that hop to the system that generated it, change one rule, purge relevant caches, and repeat. Keep each public move to one intentional permanent hop whenever possible. In the area of "online tracing and reproducible evidence", read the result from the first hop because later responses may only mask an earlier rule. Record source and target, verify the owning layer, compare behavior without cookies and after cache purge. After a change, re-measure the same URL to confirm a shorter, unambiguous, stable path for users and crawlers.
- A redirect trace is a chronological record of every HTTP response between an entered URL and the final destination. It exposes status codes, Location headers, protocol changes, hostname changes, timing, and loops without relying on browser cache. Start with the externally visible URL, identify the first incorrect response, map that hop to the system that generated it, change one rule, purge relevant caches, and repeat. Keep each public move to one intentional permanent hop whenever possible. In the area of "redirect loops and excessive chains", read the result from the first hop because later responses may only mask an earlier rule. Record source and target, verify the owning layer, compare behavior without cookies and after cache purge. After a change, re-measure the same URL to confirm a shorter, unambiguous, stable path for users and crawlers.
- A redirect trace is a chronological record of every HTTP response between an entered URL and the final destination. It exposes status codes, Location headers, protocol changes, hostname changes, timing, and loops without relying on browser cache. Start with the externally visible URL, identify the first incorrect response, map that hop to the system that generated it, change one rule, purge relevant caches, and repeat. Keep each public move to one intentional permanent hop whenever possible. In the area of "HTTP to HTTPS migration", read the result from the first hop because later responses may only mask an earlier rule. Record source and target, verify the owning layer, compare behavior without cookies and after cache purge. After a change, re-measure the same URL to confirm a shorter, unambiguous, stable path for users and crawlers.
- A redirect trace is a chronological record of every HTTP response between an entered URL and the final destination. It exposes status codes, Location headers, protocol changes, hostname changes, timing, and loops without relying on browser cache. Start with the externally visible URL, identify the first incorrect response, map that hop to the system that generated it, change one rule, purge relevant caches, and repeat. Keep each public move to one intentional permanent hop whenever possible. In the area of "SEO canonicals and redirect chains", read the result from the first hop because later responses may only mask an earlier rule. Record source and target, verify the owning layer, compare behavior without cookies and after cache purge. After a change, re-measure the same URL to confirm a shorter, unambiguous, stable path for users and crawlers.
- A redirect trace is a chronological record of every HTTP response between an entered URL and the final destination. It exposes status codes, Location headers, protocol changes, hostname changes, timing, and loops without relying on browser cache. Start with the externally visible URL, identify the first incorrect response, map that hop to the system that generated it, change one rule, purge relevant caches, and repeat. Keep each public move to one intentional permanent hop whenever possible. In the area of "CDN and reverse-proxy debugging", read the result from the first hop because later responses may only mask an earlier rule. Record source and target, verify the owning layer, compare behavior without cookies and after cache purge. After a change, re-measure the same URL to confirm a shorter, unambiguous, stable path for users and crawlers.
What the result shows
The result is split into the signals that matter for this specific check.
| Field | Purpose | Example |
|---|---|---|
| Status code | A redirect trace is a chronological record of every HTTP response between an entered URL and the final destination. It exposes status codes, Location headers, protocol changes, hostname changes, timing, and loops without relying on browser cache. In the area of "redirect status codes and method preservation", read the result from the first hop because later responses may only mask an earlier rule. Record source and target, verify the owning layer, compare behavior without cookies and after cache purge. After a change, re-measure the same URL to confirm a shorter, unambiguous, stable path for users and crawlers. | Enter the exact public URL, including path and query string. |
| Source URL | A redirect trace is a chronological record of every HTTP response between an entered URL and the final destination. It exposes status codes, Location headers, protocol changes, hostname changes, timing, and loops without relying on browser cache. In the area of "online tracing and reproducible evidence", read the result from the first hop because later responses may only mask an earlier rule. Record source and target, verify the owning layer, compare behavior without cookies and after cache purge. After a change, re-measure the same URL to confirm a shorter, unambiguous, stable path for users and crawlers. | Review every hop rather than only the final page. |
| Location target | A redirect trace is a chronological record of every HTTP response between an entered URL and the final destination. It exposes status codes, Location headers, protocol changes, hostname changes, timing, and loops without relying on browser cache. In the area of "redirect loops and excessive chains", read the result from the first hop because later responses may only mask an earlier rule. Record source and target, verify the owning layer, compare behavior without cookies and after cache purge. After a change, re-measure the same URL to confirm a shorter, unambiguous, stable path for users and crawlers. | Compare status, Location, host, protocol, and duration. |
| Final URL | A redirect trace is a chronological record of every HTTP response between an entered URL and the final destination. It exposes status codes, Location headers, protocol changes, hostname changes, timing, and loops without relying on browser cache. In the area of "HTTP to HTTPS migration", read the result from the first hop because later responses may only mask an earlier rule. Record source and target, verify the owning layer, compare behavior without cookies and after cache purge. After a change, re-measure the same URL to confirm a shorter, unambiguous, stable path for users and crawlers. | Fix the earliest unexpected hop at its owning layer. |
| Hop duration | A redirect trace is a chronological record of every HTTP response between an entered URL and the final destination. It exposes status codes, Location headers, protocol changes, hostname changes, timing, and loops without relying on browser cache. In the area of "SEO canonicals and redirect chains", read the result from the first hop because later responses may only mask an earlier rule. Record source and target, verify the owning layer, compare behavior without cookies and after cache purge. After a change, re-measure the same URL to confirm a shorter, unambiguous, stable path for users and crawlers. | Run the trace again from a clean request. |
| Loop warning | A redirect trace is a chronological record of every HTTP response between an entered URL and the final destination. It exposes status codes, Location headers, protocol changes, hostname changes, timing, and loops without relying on browser cache. In the area of "CDN and reverse-proxy debugging", read the result from the first hop because later responses may only mask an earlier rule. Record source and target, verify the owning layer, compare behavior without cookies and after cache purge. After a change, re-measure the same URL to confirm a shorter, unambiguous, stable path for users and crawlers. | Save the result URL with the deployment ticket. |
| Chain length | A redirect trace is a chronological record of every HTTP response between an entered URL and the final destination. It exposes status codes, Location headers, protocol changes, hostname changes, timing, and loops without relying on browser cache. In the area of "redirect status codes and method preservation", read the result from the first hop because later responses may only mask an earlier rule. Record source and target, verify the owning layer, compare behavior without cookies and after cache purge. After a change, re-measure the same URL to confirm a shorter, unambiguous, stable path for users and crawlers. | Enter the exact public URL, including path and query string. |
| Protocol change | A redirect trace is a chronological record of every HTTP response between an entered URL and the final destination. It exposes status codes, Location headers, protocol changes, hostname changes, timing, and loops without relying on browser cache. In the area of "online tracing and reproducible evidence", read the result from the first hop because later responses may only mask an earlier rule. Record source and target, verify the owning layer, compare behavior without cookies and after cache purge. After a change, re-measure the same URL to confirm a shorter, unambiguous, stable path for users and crawlers. | Review every hop rather than only the final page. |
When this check helps
Use the checker during launches, migrations, SEO audits, incident response, CDN changes, and support investigations. A complete chain separates application behavior from edge rules and makes handoffs between developers, operators, and search specialists concrete. In the area of "redirect status codes and method preservation", read the result from the first hop because later responses may only mask an earlier rule. Record source and target, verify the owning layer, compare behavior without cookies and after cache purge. After a change, re-measure the same URL to confirm a shorter, unambiguous, stable path for users and crawlers.
Use the checker during launches, migrations, SEO audits, incident response, CDN changes, and support investigations. A complete chain separates application behavior from edge rules and makes handoffs between developers, operators, and search specialists concrete. In the area of "online tracing and reproducible evidence", read the result from the first hop because later responses may only mask an earlier rule. Record source and target, verify the owning layer, compare behavior without cookies and after cache purge. After a change, re-measure the same URL to confirm a shorter, unambiguous, stable path for users and crawlers.
Use the checker during launches, migrations, SEO audits, incident response, CDN changes, and support investigations. A complete chain separates application behavior from edge rules and makes handoffs between developers, operators, and search specialists concrete. In the area of "redirect loops and excessive chains", read the result from the first hop because later responses may only mask an earlier rule. Record source and target, verify the owning layer, compare behavior without cookies and after cache purge. After a change, re-measure the same URL to confirm a shorter, unambiguous, stable path for users and crawlers.
Use the checker during launches, migrations, SEO audits, incident response, CDN changes, and support investigations. A complete chain separates application behavior from edge rules and makes handoffs between developers, operators, and search specialists concrete. In the area of "HTTP to HTTPS migration", read the result from the first hop because later responses may only mask an earlier rule. Record source and target, verify the owning layer, compare behavior without cookies and after cache purge. After a change, re-measure the same URL to confirm a shorter, unambiguous, stable path for users and crawlers.
Use the checker during launches, migrations, SEO audits, incident response, CDN changes, and support investigations. A complete chain separates application behavior from edge rules and makes handoffs between developers, operators, and search specialists concrete. In the area of "SEO canonicals and redirect chains", read the result from the first hop because later responses may only mask an earlier rule. Record source and target, verify the owning layer, compare behavior without cookies and after cache purge. After a change, re-measure the same URL to confirm a shorter, unambiguous, stable path for users and crawlers.
Use the checker during launches, migrations, SEO audits, incident response, CDN changes, and support investigations. A complete chain separates application behavior from edge rules and makes handoffs between developers, operators, and search specialists concrete. In the area of "CDN and reverse-proxy debugging", read the result from the first hop because later responses may only mask an earlier rule. Record source and target, verify the owning layer, compare behavior without cookies and after cache purge. After a change, re-measure the same URL to confirm a shorter, unambiguous, stable path for users and crawlers.
What to review when results look wrong
If the trace differs from a browser, remove cookies, service workers, extensions, and cached permanent redirects from the comparison. Test the same spelling of host, path, slash, case, and query parameters. Then inspect CDN rules, load balancers, web-server configuration, and application middleware in that order. In the area of "redirect status codes and method preservation", read the result from the first hop because later responses may only mask an earlier rule. Record source and target, verify the owning layer, compare behavior without cookies and after cache purge. After a change, re-measure the same URL to confirm a shorter, unambiguous, stable path for users and crawlers.
If the trace differs from a browser, remove cookies, service workers, extensions, and cached permanent redirects from the comparison. Test the same spelling of host, path, slash, case, and query parameters. Then inspect CDN rules, load balancers, web-server configuration, and application middleware in that order. In the area of "online tracing and reproducible evidence", read the result from the first hop because later responses may only mask an earlier rule. Record source and target, verify the owning layer, compare behavior without cookies and after cache purge. After a change, re-measure the same URL to confirm a shorter, unambiguous, stable path for users and crawlers.
If the trace differs from a browser, remove cookies, service workers, extensions, and cached permanent redirects from the comparison. Test the same spelling of host, path, slash, case, and query parameters. Then inspect CDN rules, load balancers, web-server configuration, and application middleware in that order. In the area of "redirect loops and excessive chains", read the result from the first hop because later responses may only mask an earlier rule. Record source and target, verify the owning layer, compare behavior without cookies and after cache purge. After a change, re-measure the same URL to confirm a shorter, unambiguous, stable path for users and crawlers.
If the trace differs from a browser, remove cookies, service workers, extensions, and cached permanent redirects from the comparison. Test the same spelling of host, path, slash, case, and query parameters. Then inspect CDN rules, load balancers, web-server configuration, and application middleware in that order. In the area of "HTTP to HTTPS migration", read the result from the first hop because later responses may only mask an earlier rule. Record source and target, verify the owning layer, compare behavior without cookies and after cache purge. After a change, re-measure the same URL to confirm a shorter, unambiguous, stable path for users and crawlers.
If the trace differs from a browser, remove cookies, service workers, extensions, and cached permanent redirects from the comparison. Test the same spelling of host, path, slash, case, and query parameters. Then inspect CDN rules, load balancers, web-server configuration, and application middleware in that order. In the area of "SEO canonicals and redirect chains", read the result from the first hop because later responses may only mask an earlier rule. Record source and target, verify the owning layer, compare behavior without cookies and after cache purge. After a change, re-measure the same URL to confirm a shorter, unambiguous, stable path for users and crawlers.
If the trace differs from a browser, remove cookies, service workers, extensions, and cached permanent redirects from the comparison. Test the same spelling of host, path, slash, case, and query parameters. Then inspect CDN rules, load balancers, web-server configuration, and application middleware in that order. In the area of "CDN and reverse-proxy debugging", read the result from the first hop because later responses may only mask an earlier rule. Record source and target, verify the owning layer, compare behavior without cookies and after cache purge. After a change, re-measure the same URL to confirm a shorter, unambiguous, stable path for users and crawlers.
How to interpret the result
A redirect trace is a chronological record of every HTTP response between an entered URL and the final destination. It exposes status codes, Location headers, protocol changes, hostname changes, timing, and loops without relying on browser cache. In the area of "redirect status codes and method preservation", read the result from the first hop because later responses may only mask an earlier rule. Record source and target, verify the owning layer, compare behavior without cookies and after cache purge. After a change, re-measure the same URL to confirm a shorter, unambiguous, stable path for users and crawlers.
A redirect trace is a chronological record of every HTTP response between an entered URL and the final destination. It exposes status codes, Location headers, protocol changes, hostname changes, timing, and loops without relying on browser cache. In the area of "online tracing and reproducible evidence", read the result from the first hop because later responses may only mask an earlier rule. Record source and target, verify the owning layer, compare behavior without cookies and after cache purge. After a change, re-measure the same URL to confirm a shorter, unambiguous, stable path for users and crawlers.
A redirect trace is a chronological record of every HTTP response between an entered URL and the final destination. It exposes status codes, Location headers, protocol changes, hostname changes, timing, and loops without relying on browser cache. In the area of "redirect loops and excessive chains", read the result from the first hop because later responses may only mask an earlier rule. Record source and target, verify the owning layer, compare behavior without cookies and after cache purge. After a change, re-measure the same URL to confirm a shorter, unambiguous, stable path for users and crawlers.
A redirect trace is a chronological record of every HTTP response between an entered URL and the final destination. It exposes status codes, Location headers, protocol changes, hostname changes, timing, and loops without relying on browser cache. In the area of "HTTP to HTTPS migration", read the result from the first hop because later responses may only mask an earlier rule. Record source and target, verify the owning layer, compare behavior without cookies and after cache purge. After a change, re-measure the same URL to confirm a shorter, unambiguous, stable path for users and crawlers.
A redirect trace is a chronological record of every HTTP response between an entered URL and the final destination. It exposes status codes, Location headers, protocol changes, hostname changes, timing, and loops without relying on browser cache. In the area of "SEO canonicals and redirect chains", read the result from the first hop because later responses may only mask an earlier rule. Record source and target, verify the owning layer, compare behavior without cookies and after cache purge. After a change, re-measure the same URL to confirm a shorter, unambiguous, stable path for users and crawlers.
A redirect trace is a chronological record of every HTTP response between an entered URL and the final destination. It exposes status codes, Location headers, protocol changes, hostname changes, timing, and loops without relying on browser cache. In the area of "CDN and reverse-proxy debugging", read the result from the first hop because later responses may only mask an earlier rule. Record source and target, verify the owning layer, compare behavior without cookies and after cache purge. After a change, re-measure the same URL to confirm a shorter, unambiguous, stable path for users and crawlers.
Recommended workflow
- Enter the exact public URL, including path and query string.
- Review every hop rather than only the final page.
- Compare status, Location, host, protocol, and duration.
- Fix the earliest unexpected hop at its owning layer.
- Run the trace again from a clean request.
- Save the result URL with the deployment ticket.
Tool vs manual checks
curl -I is useful for one response, while curl -L adds following behavior but still needs careful verbose output to explain each transition. Browser developer tools are valuable for client state, yet cached redirects and extensions can distort evidence. DN01 provides a clean, shareable server-side trace. In the area of "redirect status codes and method preservation", read the result from the first hop because later responses may only mask an earlier rule. Record source and target, verify the owning layer, compare behavior without cookies and after cache purge. After a change, re-measure the same URL to confirm a shorter, unambiguous, stable path for users and crawlers.
curl -I is useful for one response, while curl -L adds following behavior but still needs careful verbose output to explain each transition. Browser developer tools are valuable for client state, yet cached redirects and extensions can distort evidence. DN01 provides a clean, shareable server-side trace. In the area of "online tracing and reproducible evidence", read the result from the first hop because later responses may only mask an earlier rule. Record source and target, verify the owning layer, compare behavior without cookies and after cache purge. After a change, re-measure the same URL to confirm a shorter, unambiguous, stable path for users and crawlers.
curl -I is useful for one response, while curl -L adds following behavior but still needs careful verbose output to explain each transition. Browser developer tools are valuable for client state, yet cached redirects and extensions can distort evidence. DN01 provides a clean, shareable server-side trace. In the area of "redirect loops and excessive chains", read the result from the first hop because later responses may only mask an earlier rule. Record source and target, verify the owning layer, compare behavior without cookies and after cache purge. After a change, re-measure the same URL to confirm a shorter, unambiguous, stable path for users and crawlers.
curl -I is useful for one response, while curl -L adds following behavior but still needs careful verbose output to explain each transition. Browser developer tools are valuable for client state, yet cached redirects and extensions can distort evidence. DN01 provides a clean, shareable server-side trace. In the area of "HTTP to HTTPS migration", read the result from the first hop because later responses may only mask an earlier rule. Record source and target, verify the owning layer, compare behavior without cookies and after cache purge. After a change, re-measure the same URL to confirm a shorter, unambiguous, stable path for users and crawlers.
curl -I is useful for one response, while curl -L adds following behavior but still needs careful verbose output to explain each transition. Browser developer tools are valuable for client state, yet cached redirects and extensions can distort evidence. DN01 provides a clean, shareable server-side trace. In the area of "SEO canonicals and redirect chains", read the result from the first hop because later responses may only mask an earlier rule. Record source and target, verify the owning layer, compare behavior without cookies and after cache purge. After a change, re-measure the same URL to confirm a shorter, unambiguous, stable path for users and crawlers.
curl -I is useful for one response, while curl -L adds following behavior but still needs careful verbose output to explain each transition. Browser developer tools are valuable for client state, yet cached redirects and extensions can distort evidence. DN01 provides a clean, shareable server-side trace. In the area of "CDN and reverse-proxy debugging", read the result from the first hop because later responses may only mask an earlier rule. Record source and target, verify the owning layer, compare behavior without cookies and after cache purge. After a change, re-measure the same URL to confirm a shorter, unambiguous, stable path for users and crawlers.
Why use DN01
- Public server-side request
- Ordered hop evidence
- Loop and chain warnings
- HTTP and HTTPS visibility
- SEO migration support
- Shareable diagnostic result
FAQ
Redirect checker FAQ
Status codes, complete traces, loops, HTTPS migrations, SEO chains and proxy behavior.
Which redirect codes does DN01 show?
The trace shows 301, 302, 303, 307 and 308 responses with Location targets and method implications. redirect codes guide
How do I trace a redirect chain online?
Enter the exact public URL and read every hop from the first response through the final destination.
How can I find a redirect loop?
A repeated URL or alternating pair indicates a loop; inspect the earliest rule shared by the repeated hops.
How should HTTP move to HTTPS?
Use one permanent hop to the canonical HTTPS URL and avoid separate protocol, host and slash transitions.
Do redirect chains hurt SEO?
Long chains waste crawl time, dilute operational clarity and delay users; link directly to the final canonical URL.
Why can CDN redirects differ from origin redirects?
CDN, load balancer, web server and application rules can each emit redirects, so identify the first unexpected hop.