Check URL redirects and redirect chains.
Redirect Checker follows a URL through every redirect and lists each hop with its real HTTP status code (301, 302, 307, 308) and destination, ending at the final URL. It warns about redirect chains, loops and temporary redirects that should be permanent. The requests come from our server, so it works for any public site.
Made for it and developers. Typical uses:
It follows up to 10 redirects from a single location, and reads HTTP redirects only. Redirects done by JavaScript or a meta refresh tag inside the page are not followed. Only public http and https addresses can be checked.
Accuracy: Results reflect what the lookup returns at the moment you run it. Records and locations can change or differ between networks.
Syntax and format checks find broken markup, bad JSON and mistyped numbers, but not meaning, business rules, email deliverability or whether a URL is alive.
Three small technical SEO pieces that are easy to get wrong: what robots.txt, XML sitemaps and canonical tags each control, common mistakes, and how to test them.
A step-by-step way to find out why a site is down or misbehaving: check DNS records, then the HTTP status code and redirect chain, then domain expiry and your own IP.
Explore more in Network Tools, read the guides and articles, or see how we test our tools.
Check website status and HTTP response codes.
Best for confirming whether a website outage is real or a problem on your end
Look up DNS records for any domain.
Best for verifying MX records are set up correctly after configuring email
Find your public IP address and location details.
Best for verifying a VPN or proxy is actually masking your IP
Check domain registration details.
Best for checking when a domain is due to expire before it lapses
Find geographic location of IP addresses.
Best for investigating the origin of suspicious website traffic
Parse user agent strings to identify browser, OS, device, and version.
Best for decoding a user agent string from server logs to see which browser is causing errors