Bulk HTTP status code checker
Which of your URLs answer 200, which redirect, and which are broken? Paste up to 50 URLs into this free HTTP status checker. I request each one and show its status code, every redirect hop, the final URL and how long it took.
This tool checks once. Indexing Monitoring keeps checking.
It checks on a schedule and alerts you when the result changes. Ask Theo, the AI assistant in the app, to explain any finding.
What it checks
- Requests each URL and follows its redirects one hop at a time, so every status code in the chain stays visible
- Shows the final URL, the number of hops and the time to first byte of each hop
- Flags server errors, client errors, loops, chains of two or more hops and temporary redirects
- Exports the whole table as CSV, ready for a spreadsheet
What it does not
- It runs from a data center as VitalSentinel Free Tools Bot. A site that treats bots differently may answer me differently than it answers you
- It cannot see redirects that run in the browser: JavaScript or a meta refresh
- It checks up to 50 URLs per run, each timed once from one location
- It does not read the page itself, so a soft 404 that answers 200 looks fine here
Questions
What does each HTTP status code class mean?
- 2xx: the page answered. 200 is what you want for any page you link to.
- 3xx: a redirect. 301 and 308 are permanent, 302 and 307 are temporary.
- 4xx: the request failed. 404 is not found, 410 is gone, 403 is forbidden.
- 5xx: the server failed. Google slows its crawling when it sees these.
Why does a URL show 403 here but load in my browser?
A firewall or bot rule is probably blocking requests from data centers or from tools that say they are bots. I always say who I am. Check your firewall logs, and make sure the same rule does not block Googlebot.
How is this different from the redirect checker?
The redirect checker looks at one URL in depth: what each hop changes, the raw Location header and a meta refresh on the final page. This tool checks many URLs at once and shows the outcome of each.
Does Googlebot get the same status codes?
Not always. I fetch as my own bot, not as Googlebot, so a rule that treats Googlebot differently does not show here. Server Log Monitoring reads your access logs and shows the status code every bot got on every URL it requested. Filter it to Googlebot and Verified (any method) to see only hits confirmed against Google's published IP ranges. Its URLs with errors and redirects card lists each URL that got a 4xx, a 5xx or a redirect.
More free tools
Fair use, and how to recognize us
5 per minute · 25 per hour · 100 per day per IP (per /64 for IPv6), plus a per-site limit
Every request these tools make sends this user agent, including the ones that load a page in a real browser. What a run records is set out in our privacy policy.
Mozilla/5.0 (compatible; VitalSentinel Free Tools Bot/1.0; +https://www.vitalsentinel.com/bot)
Stop checking by hand
Core Web Vitals from real users, indexing and robots.txt, uptime and SSL, monitored continuously. Start on the Free plan and add your first domain in under a minute.