Server & Network
HTTP Status Check
Check the HTTP status codes of up to 100 addresses at once – ideal after a relaunch or for a list from your sitemap. With redirect targets, response time, file type, CSV export and a glossary of all important status codes.
- Processed on the server – Privacy
- No sign-up
- Free
Check addresses
You can also paste a complete sitemap.xml – the addresses are extracted automatically.
Status code glossary
Result
| Status | Address | Response | Type | Size |
|---|
Guide
How it works
- Paste addresses
One address per line – full URLs or just domain and path. You can also paste the content of a sitemap.xml; duplicate addresses are removed automatically.
- Check
With “Follow redirects” you also see where a redirect ends. Without this option, the tool only shows the first response of each address. Ctrl+Enter also starts the check.
- Evaluate
The filters at the top show all redirects, error pages or server errors with one click. Notes below an address point to chains, temporary redirects or slow responses.
- Keep working
“Copy problems” puts all addresses without 200 on the clipboard, “CSV” downloads the complete result for Excel. Clicking a status code explains it in the glossary.
FAQ
Frequently asked questions
Which status codes are good for SEO?
200 for pages that should be found, 301 (or 308) for pages that have moved permanently and 410 for pages that no longer exist without replacement. Temporary redirects (302, 307) are only meant for a short time; server errors (5xx) should never occur permanently.
What is the difference between 404 and 410?
Both mean “not there”. 410 explicitly says that the page was removed intentionally and permanently – search engines then usually remove it from the index faster.
Why does the tool show 403 or 429 although the page works in the browser?
Some websites block automated requests with bot protection or throttle many requests in a short time. The tool fetches the pages from my server, not from your browser.
What does the response time mean?
The time to the first byte of the response (time to first byte), measured from my server in Germany. It shows how quickly the server reacts – not how quickly the whole page loads in the browser.
Why are redirect chains highlighted?
Every additional redirect costs loading time, and search engines only follow a limited number. It is better for every old address to redirect directly to the final target. You can examine individual chains in more detail with the Redirect Checker.
How many addresses can I check?
Up to 100 at once. Simply split longer lists. To avoid overloading the server, the number of requests per minute is limited – with very large lists, the tool pauses briefly.