Check HTTP Status Codes in Bulk

An HTTP status code is a 3-digit number a server returns with every response so the client knows what happened. The first digit groups them: 1xx informational, 2xx success, 3xx redirection, 4xx client error, 5xx server error.

The most common ones in day-to-day SEO and ops are 200 (OK), 301 (permanent redirect), 302 (temporary redirect), 404 (not found), 410 (gone), 500 (server error), and 503 (service unavailable).

Paste up to 100 URLs (one per line) into the input above and press Check status codes. The tool fetches each URL with a real GET request, follows up to 10 redirect hops, and returns both the initial status code (what the URL itself returns) and the final status code (what you land on after following all redirects).

You can export everything to CSV when it's done.

Yes. The tool follows up to 10 HTTP-level redirect hops per URL and shows you the full chain — both the initial code (e.g. 301) and the final code after following the chain (e.g. 200, 404, or 0 if it errored).

Click any row to see every hop with its status code, URL, and response time. If you want only the first response without following the chain, look at the Initial column.

200 OK is the standard success response: the server received the request, processed it, and is returning the requested resource. For SEO, a 200 is what you want for every page you intend to be indexed.

If a page that should return 200 starts returning anything else (a redirect, a 404, or a 5xx), search engines will eventually drop it from the index.

Both are redirects, both pass PageRank — Google confirmed in 2016 that all 30x codes pass PageRank equally. The difference is canonicalization:

301 is permanent and tells search engines the new URL replaces the old one in the index. 302 is temporary — Google follows it but keeps the original URL indexed.

Use 301 for migrations and renames; use 302 for A/B tests, maintenance pages, and short-lived redirects.

Both mean the page isn't there, but they say different things. 404 Not Found means the page is missing — possibly temporarily, possibly an error. 410 Gone is more definitive: this page is permanently removed and there's nothing to redirect to.

For SEO, 410 helps search engines deindex a page faster than 404. Use 410 for products you've discontinued, expired campaigns, and intentionally removed pages.

4xx codes mean the client (browser, bot, your tool) made a request the server couldn't fulfill — most commonly 404 (page doesn't exist), 403 (forbidden), or 401 (auth required).

5xx codes mean the server itself failed — 500 (generic error), 502 (bad gateway, often a backend service is down), 503 (service unavailable, usually maintenance or overload), 504 (gateway timeout).

4xx is your problem to fix in URLs or routing; 5xx is your problem to fix in the application or infrastructure.

Your URLs are sent only to Wygard's own thin CORS proxy (a single PHP script that fetches the URL on your behalf, because browsers can't read HTTP status codes from cross-origin responses directly). The proxy doesn't log, store, or forward anything — it returns the response straight to your browser, which orchestrates the rest.

No analytics on what you check, no third-party trackers on this tool.

100 URLs × up to 10 hops each = up to 1000 HTTP requests through a shared proxy. Beyond that we'd start hammering target servers and our own infrastructure. The tool runs 5 URLs in parallel, but URLs from the same domain are queued sequentially with a small delay — to be polite to the target server.

If you need to monitor status codes for more than 100 URLs continuously, that's exactly what Wygard is built for.