Redirect checker
Follow a domain from http:// to the page it finally loads: every hop with its status code, plus loops, missing HTTPS upgrades and temporary redirects.
What this tool checks
DNSPeek requests http://your-domain/ and follows each Location header one hop at a time, up to 10 redirects. For every hop you see the URL, the status code, the server IP and how long it took. The chain stops at the first page that does not redirect, at a loop, or at a redirect to a private address, another port or an IP address, which the tool does not follow.
How to read the result
A good chain has one hop: http://example.com/ → https://example.com/ (or to the www version you prefer) with a 301, ending in a 200. Warnings point out a site that stays on plain HTTP, chains longer than two hops and temporary redirects; problems are loops, errors and a final page that answers 4xx or 5xx.
Redirects after a migration
A new server often comes with different www and HTTPS rules. Before switching DNS, open the site on the new server with a preview link: redirects work there too, including between the domain and its www version. The QA report checks redirects across many pages at once.
Frequently asked questions
What is the difference between a 301 and a 302 redirect?
A 301 (or 308) says the page moved permanently, so browsers and search engines remember the new address and transfer rankings to it. A 302 (or 307) says the move is temporary. Use 301 for http to https and for www handling.
How many redirects are too many?
Every hop costs a round trip before the page starts loading. One redirect, from http:// to the final https:// address, is ideal; this tool warns from three. Browsers give up at around 20 and report “too many redirects”.
What causes a redirect loop?
Two rules that send visitors back and forth, typically an HTTPS redirect on the server combined with a CDN or proxy that talks to the server over plain HTTP, or a CMS whose site address disagrees with the server’s www rule.
Why does the check start at http://?
Visitors who type the bare domain, and old links, arrive over plain HTTP. Starting there shows whether they are upgraded to HTTPS and how many hops it takes. After a result you can check the same path from https:// or the www version with one click, and you can enter a path to check an old URL.
Moving a site to a new server?
See the site on the new server before you change DNS: DNSPeek gives you one HTTPS preview link that works on any device and that you can share with your team or client. No hosts file, no VPN.
Create a free preview link