HTTP Status Checker

Check the HTTP status code of up to 100 URLs: 200, 301, 404, 500 and more, with what each means for SEO and a searchable list of every status code.

URLs (one per line, up to 100)

https:// is added when you leave it out.

Check as

Firewalls sometimes answer browsers and Googlebot differently.

Each URL's status code appears here with what it means, where redirects end and how long the server took.

HTTP status codes

Code	Meaning	SEO
100 Continue	The server got the request headers; the client can send the body.
101 Switching Protocols	The server is switching protocols as asked, for example to WebSocket.
103 Early Hints	Preliminary headers (such as Link preloads) sent before the final response.
200 OK	The request succeeded and the page or data is in the response.	The page can be indexed (unless noindex or a canonical says otherwise).
201 Created	The request succeeded and created a new resource (APIs).
202 Accepted	The request was accepted for processing, which has not finished yet.
203 Non-Authoritative Information	Success, but a proxy changed the response.
204 No Content	Success with no body to return.	Google treats it like a page with no content (soft 404).
206 Partial Content	Part of the file was returned, for a Range request (video, resumable downloads).
301 Moved Permanently	The page has a new permanent address, given in the Location header.	Google moves ranking signals to the new URL and indexes that one. Use it for permanent moves.
302 Found	The page is temporarily at another address.	Google keeps the old URL indexed at first; a 302 left in place for a long time is treated like a 301.
303 See Other	Go to another URL with GET, typically after a form was submitted.
304 Not Modified	The cached copy is still valid; no body is sent.	Saves crawl budget: Googlebot reuses its copy.
307 Temporary Redirect	Temporarily at another address; the method and body must not change. Browsers also show 307 for HSTS upgrades to https.	Treated like a 302.
308 Permanent Redirect	Permanently at another address; the method and body must not change.	Treated like a 301.
400 Bad Request	The server cannot process the request because it is malformed.
401 Unauthorized	Authentication is required or has failed (missing or wrong credentials).	The page is not indexed.
403 Forbidden	The server understood the request but refuses it. Firewalls and bot protection often send it.	Not indexed; if your firewall sends it to Googlebot, pages drop out of search.
404 Not Found	Nothing exists at this URL.	Removed from the index over time. Normal for pages that never existed; fix internal links pointing to it.
405 Method Not Allowed	The URL exists but does not accept this method (for example HEAD or POST).
406 Not Acceptable	No version of the resource matches the Accept headers.
408 Request Timeout	The client took too long to send the request.
409 Conflict	The request conflicts with the current state of the resource.
410 Gone	The page was removed on purpose and will not come back.	Removed from the index a little faster than a 404.
411 Length Required	The request needs a Content-Length header.
412 Precondition Failed	A condition in the request headers (If-Match) was not met.
413 Content Too Large	The request body is larger than the server accepts (uploads).
414 URI Too Long	The URL is longer than the server will handle.
415 Unsupported Media Type	The body is in a format the server does not accept.
416 Range Not Satisfiable	The requested byte range is outside the file.
418 I'm a teapot	An April Fools joke from RFC 2324; some sites send it to block bots.
421 Misdirected Request	The request reached a server that cannot answer for this host.
422 Unprocessable Content	The body is well formed but its data is invalid (API validation errors).
425 Too Early	The server will not process a request that might be replayed (TLS early data).
426 Upgrade Required	The client must switch to another protocol.
428 Precondition Required	The server requires a conditional request.
429 Too Many Requests	Rate limited: too many requests in a given time. A Retry-After header may say when to try again.	Googlebot slows down crawling; long periods can drop pages.
431 Request Header Fields Too Large	The request headers (often cookies) are too large.
451 Unavailable For Legal Reasons	Blocked for legal reasons, such as a court order or regional law.
499 Client Closed Request (nginx)	The client disconnected before the server answered.
500 Internal Server Error	Something went wrong on the server, such as a crash in the application.	Googlebot slows down; pages that keep failing are dropped.
501 Not Implemented	The server does not support the method.
502 Bad Gateway	A proxy or load balancer got an invalid answer from the server behind it.	Treated like other 5xx errors.
503 Service Unavailable	Temporarily overloaded or down for maintenance.	The right code for planned maintenance (with Retry-After); Google keeps the page if the outage is short.
504 Gateway Timeout	A proxy did not get an answer from the server behind it in time.
505 HTTP Version Not Supported	The server does not support the HTTP version of the request.
507 Insufficient Storage	The server cannot store what is needed to complete the request.
508 Loop Detected	The server found an infinite loop while processing the request.
511 Network Authentication Required	You must sign in to the network first (captive portal Wi-Fi).
520 Web Server Returned an Unknown Error (Cloudflare)	The origin server sent an empty or unexpected response to Cloudflare.
521 Web Server Is Down (Cloudflare)	The origin server refused Cloudflare's connection.
522 Connection Timed Out (Cloudflare)	Cloudflare could not connect to the origin server in time.
523 Origin Is Unreachable (Cloudflare)	Cloudflare cannot reach the origin (DNS or routing problem).
524 A Timeout Occurred (Cloudflare)	The origin accepted the connection but took over 100 seconds to answer.
525 SSL Handshake Failed (Cloudflare)	Cloudflare could not complete a TLS handshake with the origin.
526 Invalid SSL Certificate (Cloudflare)	The origin's certificate is not valid for Cloudflare's strict SSL mode.

Something not working, or missing a feature? Send feedback

About the HTTP Status Checker

HTTP Status Checker requests up to 100 URLs and shows the status code each one returns, such as 200 OK, 301 Moved Permanently, 404 Not Found or 503 Service Unavailable, with what it means and how Google treats it. Redirects show where they end. A searchable list explains every standard code plus Cloudflare's 52x errors.

Our server requests the URLs you enter, like a crawler: it reads the response without running the page's scripts, and the analysis runs in your browser. The URLs and results are not stored.

How to use the HTTP Status Checker

Paste URLs, one per line (https:// is added if missing).
Choose whether to check as a browser, an iPhone or Googlebot.
Click Check and read each code, its meaning and the final URL of redirects.
Copy the results as CSV, or search the status code list below.

Works well with the HTTP Status Checker

Redirect Checker: see every hop and header of a redirect chain.
Broken Link Checker: find links on a page that return errors.
Site Audit Tool: check status codes across a whole site.

Frequently asked questions

What is the difference between a 301 and a 302?

A 301 says the page moved for good: Google indexes the new URL and passes its ranking signals there. A 302 is temporary, so Google keeps the old URL at first. Use 301 (or 308) for permanent moves.

Should a deleted page return 404 or 410?

Both remove it from search over time; 410 Gone is a slightly stronger signal that it will not return. Redirect it with a 301 instead if a close replacement exists.

Why does my site return 403 here but work in my browser?

Firewalls and bot protection (Cloudflare, Wordfence) often block requests from servers or unfamiliar user agents. Try "Check as" Chrome. If Googlebot gets a 403, your pages can drop out of Google.

Which requests does the checker send?

A HEAD request, repeated with GET if the server rejects HEAD, from Devtoolry's server. Redirects are followed one hop at a time, up to 10.

Code

Meaning

SEO

100 Continue

The server got the request headers; the client can send the body.

101 Switching Protocols

The server is switching protocols as asked, for example to WebSocket.

103 Early Hints

Preliminary headers (such as Link preloads) sent before the final response.

200 OK

The request succeeded and the page or data is in the response.

The page can be indexed (unless noindex or a canonical says otherwise).

201 Created

The request succeeded and created a new resource (APIs).

202 Accepted

The request was accepted for processing, which has not finished yet.

203 Non-Authoritative Information

Success, but a proxy changed the response.

204 No Content

Success with no body to return.

Google treats it like a page with no content (soft 404).

206 Partial Content

Part of the file was returned, for a Range request (video, resumable downloads).

301 Moved Permanently

The page has a new permanent address, given in the Location header.

Google moves ranking signals to the new URL and indexes that one. Use it for permanent moves.

302 Found

The page is temporarily at another address.

Google keeps the old URL indexed at first; a 302 left in place for a long time is treated like a 301.

303 See Other

Go to another URL with GET, typically after a form was submitted.

304 Not Modified

The cached copy is still valid; no body is sent.

Saves crawl budget: Googlebot reuses its copy.

307 Temporary Redirect

Temporarily at another address; the method and body must not change. Browsers also show 307 for HSTS upgrades to https.

Treated like a 302.

308 Permanent Redirect

Permanently at another address; the method and body must not change.

Treated like a 301.

400 Bad Request

The server cannot process the request because it is malformed.

401 Unauthorized

Authentication is required or has failed (missing or wrong credentials).

The page is not indexed.

403 Forbidden

The server understood the request but refuses it. Firewalls and bot protection often send it.

Not indexed; if your firewall sends it to Googlebot, pages drop out of search.

404 Not Found

Nothing exists at this URL.

Removed from the index over time. Normal for pages that never existed; fix internal links pointing to it.

405 Method Not Allowed

The URL exists but does not accept this method (for example HEAD or POST).

406 Not Acceptable

No version of the resource matches the Accept headers.

408 Request Timeout

The client took too long to send the request.

409 Conflict

The request conflicts with the current state of the resource.

410 Gone

The page was removed on purpose and will not come back.

Removed from the index a little faster than a 404.

411 Length Required

The request needs a Content-Length header.

412 Precondition Failed

A condition in the request headers (If-Match) was not met.

413 Content Too Large

The request body is larger than the server accepts (uploads).

414 URI Too Long

The URL is longer than the server will handle.

415 Unsupported Media Type

The body is in a format the server does not accept.

416 Range Not Satisfiable

The requested byte range is outside the file.

418 I'm a teapot

An April Fools joke from RFC 2324; some sites send it to block bots.

421 Misdirected Request

The request reached a server that cannot answer for this host.

422 Unprocessable Content

The body is well formed but its data is invalid (API validation errors).

425 Too Early

The server will not process a request that might be replayed (TLS early data).

426 Upgrade Required

The client must switch to another protocol.

428 Precondition Required

The server requires a conditional request.

429 Too Many Requests

Rate limited: too many requests in a given time. A Retry-After header may say when to try again.

Googlebot slows down crawling; long periods can drop pages.

431 Request Header Fields Too Large

The request headers (often cookies) are too large.

451 Unavailable For Legal Reasons

Blocked for legal reasons, such as a court order or regional law.

499 Client Closed Request (nginx)

The client disconnected before the server answered.

500 Internal Server Error

Something went wrong on the server, such as a crash in the application.

Googlebot slows down; pages that keep failing are dropped.

501 Not Implemented

The server does not support the method.

502 Bad Gateway

A proxy or load balancer got an invalid answer from the server behind it.

Treated like other 5xx errors.

503 Service Unavailable

Temporarily overloaded or down for maintenance.

The right code for planned maintenance (with Retry-After); Google keeps the page if the outage is short.

504 Gateway Timeout

A proxy did not get an answer from the server behind it in time.

505 HTTP Version Not Supported

The server does not support the HTTP version of the request.

507 Insufficient Storage

The server cannot store what is needed to complete the request.

508 Loop Detected

The server found an infinite loop while processing the request.

511 Network Authentication Required

You must sign in to the network first (captive portal Wi-Fi).

520 Web Server Returned an Unknown Error (Cloudflare)

The origin server sent an empty or unexpected response to Cloudflare.

521 Web Server Is Down (Cloudflare)

The origin server refused Cloudflare's connection.

522 Connection Timed Out (Cloudflare)

Cloudflare could not connect to the origin server in time.

523 Origin Is Unreachable (Cloudflare)

Cloudflare cannot reach the origin (DNS or routing problem).

524 A Timeout Occurred (Cloudflare)

The origin accepted the connection but took over 100 seconds to answer.

525 SSL Handshake Failed (Cloudflare)

Cloudflare could not complete a TLS handshake with the origin.

526 Invalid SSL Certificate (Cloudflare)

The origin's certificate is not valid for Cloudflare's strict SSL mode.

HTTP Status Checker

HTTP status codes

About the HTTP Status Checker

How to use the HTTP Status Checker

Works well with the HTTP Status Checker

Frequently asked questions

Website SEO Checker

Broken Link Checker

Redirect Checker

AdSense Readiness Checker

Site Audit Tool

Page Speed Checker

HTTP status codes

HTTP Status Checker

HTTP status codes

About the HTTP Status Checker

How to use the HTTP Status Checker

Works well with the HTTP Status Checker

Frequently asked questions

Related tools

Website SEO Checker

Broken Link Checker

Redirect Checker

AdSense Readiness Checker

Site Audit Tool

Page Speed Checker

HTTP status codes