HTTP status checker
See exactly what a URL answers — including each redirect — like a search engine sees it.

How to use the hTTP status checker
- Enter a URL.
- Press Check.
- Review the status of every hop and the final page.
When it's useful
- Confirming an old URL redirects with 301
- Finding redirect chains
- Checking a page isn't returning 404 or 500
Limits to know
- Only public pages can be checked. Pages behind a login, on private networks or that block automated visits can't be read.
- Follows up to 4 redirects. Response time is measured from our server, so it differs from your own connection.
Your privacy
When you check a URL, our server fetches that public page once and shows you the result. Nothing is saved. Pasted HTML or files are checked only in your browser.
What goes in and what comes out
- Input:
- Any public URL.
- Output:
- The status code and timing of each redirect hop, plus key response headers.
Questions
Is the page I check stored?
No. Our server fetches the public page once to read it, then the result is shown only to you. Nothing is saved.
What's the difference between 301 and 302?
301 means the page moved permanently; 302 and 307 mean a temporary move.