• Network & DNS
Trace all HTTP redirects for any URL. View status codes (301, 302, 307, 308), final destination, and detect redirect loops or HTTP→HTTPS downgrades.
Trace the full redirect chain for any URL. Detect redirect loops, mixed-content downgrades, and unnecessary hops.
Enter the exact URL to trace — path, query, and hash are not stripped.
• About this tool
A redirect checker follows every Location hop for a URL and shows each HTTP status code and destination so you can see where a link goes before you click it — including shortened and tracked URLs.
| What this checks |
|---|
| Full redirect chain with status codes |
| 301 / 302 / 307 / 308 detection |
| Redirect loop detection |
| Final destination host check |
• How to
Paste the URL
Enter the full URL, including https:// when you have it.
Run the trace
Start the check and wait for each hop to resolve.
Read each hop
Note status code, Location target, and whether the scheme stays on HTTPS.
Confirm the final host
Verify the last URL is the domain you expect — not an open-redirect sink.
Each row is one HTTP response that issued a redirect. Status tells you permanent vs temporary; Location is where the client is told to go next. The last non-redirect response is your final destination.
Permanent codes (301, 308) signal lasting moves for SEO and caches. Temporary codes (302, 307) keep the original URL indexed. 307/308 preserve the HTTP method; classic 301/302 historically may convert POST to GET depending on the client.
| Code | Permanent? | Method preserved? | Typical use |
|---|---|---|---|
| 301 | Yes | Often not | Canonical host / path moves |
| 302 | No | Often not | Campaigns, short-lived routes |
| 307 | No | Yes | Safer temporary redirects |
| 308 | Yes | Yes | Permanent moves keeping method |
A loop exists when hop N eventually points back to an earlier hop. Flatten the chain so A → B once. Check CDN rules, WordPress siteurl, and HSTS/preload interactions when http and https bounce forever.
Each hop adds latency. Search engines tolerate a few hops but prefer a single 301 to the canonical URL. Long chains also confuse analytics and break some security scanners mid-path.
Paste bit.ly-style or UTM-wrapped links to see the real landing host before you click. Useful for phishing review and vendor link audits.
Open redirects that allow attacker-controlled destinations are phishing and sometimes SSRF pivots. After a free check, run a proof-backed AI VAPT on domains you own to confirm impact.
• FAQ
301 is a permanent redirect — search engines transfer link equity. 302 is temporary — search engines do not transfer link equity and may keep the original URL indexed.
A redirect loop occurs when URLs redirect to each other cyclically. Browsers abort after a fixed number of hops (usually 10) and display an error.
Each hop adds latency (~100–200ms). Google recommends fewer than 5 hops per URL chain for SEO.
A 301 redirect from http:// to https:// ensures all traffic is encrypted. It should be combined with HSTS to prevent SSL-stripping.
Paste the link into this redirect checker and read the final destination hostname in the last hop.
The tool follows Location headers until a non-redirect response. The last URL is where a browser would land.
Point staging or a temporary path at the new location, run this checker, confirm a single 301 to HTTPS, then cut over DNS or the reverse proxy.
Paste the short URL here. The checker expands the chain without loading page content in your browser session the way a click would.
Next step
This free check is point-in-time. PandaONE maps the full surface, then runs proof-backed AI testing on domains you verify.
• Related
HTTP Security Headers Checker
Audit the HTTP security headers of any website. Score CSP, HSTS, X-Frame-Options, and more.
Robots.txt Analyzer
Fetch and parse any website's robots.txt file. See allowed/disallowed paths, crawl delays, and sitemap references.
SSL Certificate Checker
Inspect the SSL/TLS certificate for any domain. Check validity, expiry, issuer, and certificate chain.
• automated security
PandaONE runs autonomous agents against your app, validates findings with proof, and opens fixes as pull requests.
Scan your domain