HTTP Status Code Checker

Search and learn about HTTP status codes. Find meaning, common causes, and fix solutions for any HTTP response code.

HTTP Status Code Checker

Search HTTP status codes by number or keyword to find meaning, causes, and solutions.

Inputs

Use the fields that actually match the tool instead of a generic text editor.

Search HTTP Status Codes

Search tips:

• Enter a code number: 404, 500, 301
• Browse a family: 4xx, 5xx
• Search by name: "not found", "error"
• Search by category: "client", "server"

4Informational

100Continue

101Switching Protocols

102Processing

103Early Hints

5Success

200OK

201Created

202Accepted

204No Content

206Partial Content

6Redirection

301Moved Permanently

302Found

303See Other

304Not Modified

307Temporary Redirect

308Permanent Redirect

28Client Error

400Bad Request

401Unauthorized

402Payment Required

403Forbidden

404Not Found

405Method Not Allowed

406Not Acceptable

407Proxy Authentication Required

408Request Timeout

409Conflict

410Gone

411Length Required

412Precondition Failed

413Payload Too Large

414URI Too Long

415Unsupported Media Type

416Range Not Satisfiable

417Expectation Failed

418I'm a teapot

422Unprocessable Entity

423Locked

424Failed Dependency

425Too Early

426Upgrade Required

428Precondition Required

429Too Many Requests

431Request Header Fields Too Large

451Unavailable For Legal Reasons

11Server Error

500Internal Server Error

501Not Implemented

502Bad Gateway

503Service Unavailable

504Gateway Timeout

505HTTP Version Not Supported

506Variant Also Negotiates

507Insufficient Storage

508Loop Detected

510Not Extended

511Network Authentication Required

Output

54 resultsBrowsing all codes

Informational

Code	Name	Description
100	Continue	The server has received the request headers and the client should proceed to send the request body.
101	Switching Protocols	The requester has asked the server to switch protocols and the server has agreed to do so.
102	Processing	Server has received and is processing the request, but no response is available yet.
103	Early Hints	Used to return some response headers before final HTTP message.

Success

Code	Name	Description
200	OK	The request has succeeded. This is the most common response for successful GET requests.
201	Created	The request has been fulfilled and a new resource has been created.
202	Accepted	The request has been accepted for processing but has not been completed yet.
204	No Content	The server successfully processed the request but is not returning any content.
206	Partial Content	The server is delivering only part of the resource due to a Range header sent by the client.

Redirection

Code	Name	Description
301	Moved Permanently	The resource has been moved to a new URL permanently. All future requests should use the new URL.
302	Found	The resource is temporarily located at a different URL. Future requests should still use the original URL.
303	See Other	The response can be found at another URL using GET method.
304	Not Modified	The resource has not been modified since last request. Client can use cached version.
307	Temporary Redirect	The resource is temporarily at a different URL. The request method must not change.
308	Permanent Redirect	The resource has been permanently moved. All future requests should use the new URL with the same HTTP method.

Client Error

Code	Name	Description
400	Bad Request	The server cannot process the request due to malformed syntax or invalid request framing.
401	Unauthorized	Authentication is required to access this resource. The client must authenticate itself.
402	Payment Required	This status code is reserved for future use or payment-related responses.
403	Forbidden	The server understood the request but refuses to authorize it. Authentication won't help.
404	Not Found	The server cannot find the requested resource. This can be a page, file, or API endpoint.
405	Method Not Allowed	The HTTP method used is not supported for this resource.
406	Not Acceptable	The server cannot produce a response matching the Accept headers.
407	Proxy Authentication Required	Authentication with the proxy is required before proceeding.
408	Request Timeout	The server timed out waiting for the request.
409	Conflict	The request conflicts with the current state of the resource.
410	Gone	The resource has been permanently deleted and will not be available again.
411	Length Required	The server requires the Content-Length header to be specified.
412	Precondition Failed	The server doesn't meet preconditions in the request headers (If-Match, If-None-Match, etc.).
413	Payload Too Large	The request entity is larger than limits defined by the server.
414	URI Too Long	The URI provided is too long for the server to process.
415	Unsupported Media Type	The media format of the request is not supported by the server.
416	Range Not Satisfiable	The range specified in the Range header cannot be fulfilled.
417	Expectation Failed	The Expectation in the request header cannot be met by the server.
418	I'm a teapot	The server refuses to brew coffee because it is, permanently, a teapot.
422	Unprocessable Entity	The server understands the content type but cannot process the contained instructions.
423	Locked	The resource is locked and cannot be accessed.
424	Failed Dependency	The request failed because it depended on another request that failed.
425	Too Early	The server is unwilling to risk processing a request that might be replayed.
426	Upgrade Required	The server refuses to perform the request using the current protocol.
428	Precondition Required	The server requires the request to be conditional.
429	Too Many Requests	The user has sent too many requests in a given amount of time (rate limiting).
431	Request Header Fields Too Large	The server is unwilling to process the request because header fields are too large.
451	Unavailable For Legal Reasons	The server cannot legally provide the resource (censorship, copyright, etc.).

Server Error

Code	Name	Description
500	Internal Server Error	The server encountered an unexpected condition that prevented it from fulfilling the request.
501	Not Implemented	The server does not support the functionality required to fulfill the request.
502	Bad Gateway	The server, while acting as a gateway or proxy, received an invalid response from an upstream server.
503	Service Unavailable	The server is not ready to handle the request, often due to maintenance or overload.
504	Gateway Timeout	The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server.
505	HTTP Version Not Supported	The HTTP version used in the request is not supported by the server.
506	Variant Also Negotiates	The server has an internal configuration error with content negotiation.
507	Insufficient Storage	The server cannot store the representation needed to complete the request.
508	Loop Detected	The server detected an infinite loop in the request processing.
510	Not Extended	Further extensions to the request are required for the server to fulfill it.
511	Network Authentication Required	The client needs to authenticate to gain network access.

Loading tool...

What is HTTP Status Code Checker

Written by Giorgos Kostas. Last reviewed: April 18, 2026

HTTP Status Code Checker is an online tool that helps you check HTTP Status Code.

It checks hTTP Status Code against known rules and surfaces any issues before the content reaches production.

Why use it

Work through hTTP Status Code faster with a focused browser-based workflow.
Review hTTP Status Code input and output without switching between extra tools.
Catch hTTP Status Code issues earlier while the data or content is still in front of you.
Keep hTTP Status Code results easy to copy back into your project or process.

Example (before/after)

HTTP Status Code input

Start with the hTTP Status Code input you want to process in HTTP Status Code Checker.

HTTP Status Code output

Get a hTTP Status Code result from HTTP Status Code Checker that is ready to review, copy, and reuse in the next step of your workflow.

Common errors

Unsupported input

The tool may reject input that does not match the expected content, structure, or file type.

Fix: Confirm the tool input requirements and paste the correct type of data.

Incomplete values

Missing fields or partial content can block processing or produce weak results.

Fix: Provide the full required input before running the tool.

Copying placeholder content

Sample or placeholder values can lead to output that looks valid but is not ready for real use.

Fix: Replace placeholders with your actual values before relying on the result.

FAQ

Does HTTP Status Code Checker use the same rules as Googlebot?

HTTP Status Code Checker follows the publicly documented behavior of Googlebot, Bingbot, and other major crawlers — robots.txt disallow rules, meta robots tags, canonical URLs, and HTTP status handling all match the official specs. Edge cases that vary between crawlers are called out in the output.

How many URLs can HTTP Status Code Checker check per request?

HTTP Status Code Checker checks up to 100 URLs per batch so the request completes in under a minute and doesn't hammer third-party servers. For larger sweeps, run the tool in a loop from a script.

Does HTTP Status Code Checker handle JavaScript-rendered pages?

HTTP Status Code Checker fetches the raw HTML served to a crawler, which is what search engines index for the first pass. If your site relies on client-side rendering, the tool shows you exactly what Googlebot's initial render sees before it runs JavaScript.

What User-Agent does HTTP Status Code Checker send?

HTTP Status Code Checker sends a User-Agent string that identifies itself honestly (DevFox bot) rather than impersonating Googlebot — spoofing UAs can get a site's access flagged. If a page blocks non-browser UAs, you'll see the block clearly reflected in the output.

Can HTTP Status Code Checker check password-protected pages?

No. HTTP Status Code Checker only makes anonymous public requests — it can't log in or carry session cookies. For auth-protected pages, use a headless browser in your own environment.

Related tools

Continue the workflow with related tools for hTTP Status Code, adjacent input and output steps, or other utilities in the same category. You can also browse the full SEO & Web Tools category for more options.

Broken Link Checker

Check URLs for broken links

Reading Level Checker

Check reading ease, grade level, sentence length, and complexity for blog posts, emails, docs, and landing page copy.

URL Slug Length and Readability Checker

Check slug length, stop words, readability, and URL cleanliness for SEO-friendly article, category, and landing page paths.

URL Inspector

Inspect status, headers, redirects, and canonical hints for a URL

Favicon Checker From URL

Inspect favicon, apple-touch-icon, and manifest links from a live page

Curl to PHP

Convert curl commands to PHP code

Accessibility Label Helper

Scan pasted HTML for missing alt text, labels, and aria attributes in common interactive elements

Domain Name Search

Check domain availability across .com, .net, .org, .io, and .dev with a free RDAP-based search tool for quick naming research.

Email Subject Line Tester

Score email subject lines for length, spam risk, readability, and click potential

Read Time Calculator

Calculate reading time, word count, and text stats for articles, emails, and landing pages

Google SERP Preview

Preview how your page appears in Google search results

HTTP Header Inspector

Paste response headers to audit HSTS, CSP, CORS, X-Powered-By disclosure, and Set-Cookie flags

Code

Name

Description

Action

100

Continue

The server has received the request headers and the client should proceed to send the request body.

101

Switching Protocols

The requester has asked the server to switch protocols and the server has agreed to do so.

102

Processing

Server has received and is processing the request, but no response is available yet.

103

Early Hints

Used to return some response headers before final HTTP message.

Code

Name

Description

Action

200

The request has succeeded. This is the most common response for successful GET requests.

201

Created

The request has been fulfilled and a new resource has been created.

202

Accepted

The request has been accepted for processing but has not been completed yet.

204

No Content

The server successfully processed the request but is not returning any content.

206

Partial Content

The server is delivering only part of the resource due to a Range header sent by the client.

Code

Name

Description

Action

301

Moved Permanently

The resource has been moved to a new URL permanently. All future requests should use the new URL.

302

Found

The resource is temporarily located at a different URL. Future requests should still use the original URL.

303

See Other

The response can be found at another URL using GET method.

304

Not Modified

The resource has not been modified since last request. Client can use cached version.

307

Temporary Redirect

The resource is temporarily at a different URL. The request method must not change.

308

Permanent Redirect

The resource has been permanently moved. All future requests should use the new URL with the same HTTP method.

Code

Name

Description

Action

400

Bad Request

The server cannot process the request due to malformed syntax or invalid request framing.

401

Unauthorized

Authentication is required to access this resource. The client must authenticate itself.

402

Payment Required

This status code is reserved for future use or payment-related responses.

403

Forbidden

The server understood the request but refuses to authorize it. Authentication won't help.

404

Not Found

The server cannot find the requested resource. This can be a page, file, or API endpoint.

405

Method Not Allowed

The HTTP method used is not supported for this resource.

406

Not Acceptable

The server cannot produce a response matching the Accept headers.

407

Proxy Authentication Required

Authentication with the proxy is required before proceeding.

408

Request Timeout

The server timed out waiting for the request.

409

Conflict

The request conflicts with the current state of the resource.

410

Gone

The resource has been permanently deleted and will not be available again.

411

Length Required

The server requires the Content-Length header to be specified.

412

Precondition Failed

The server doesn't meet preconditions in the request headers (If-Match, If-None-Match, etc.).

413

Payload Too Large

The request entity is larger than limits defined by the server.

414

URI Too Long

The URI provided is too long for the server to process.

415

Unsupported Media Type

The media format of the request is not supported by the server.

416

Range Not Satisfiable

The range specified in the Range header cannot be fulfilled.

417

Expectation Failed

The Expectation in the request header cannot be met by the server.

418

I'm a teapot

The server refuses to brew coffee because it is, permanently, a teapot.

422

Unprocessable Entity

The server understands the content type but cannot process the contained instructions.

423

Locked

The resource is locked and cannot be accessed.

424

Failed Dependency

The request failed because it depended on another request that failed.

425

Too Early

The server is unwilling to risk processing a request that might be replayed.

426

Upgrade Required

The server refuses to perform the request using the current protocol.

428

Precondition Required

The server requires the request to be conditional.

429

Too Many Requests

The user has sent too many requests in a given amount of time (rate limiting).

431

Request Header Fields Too Large

The server is unwilling to process the request because header fields are too large.

451

Unavailable For Legal Reasons

The server cannot legally provide the resource (censorship, copyright, etc.).

Code

Name

Description

Action

500

Internal Server Error

The server encountered an unexpected condition that prevented it from fulfilling the request.

501

Not Implemented

The server does not support the functionality required to fulfill the request.

502

Bad Gateway

The server, while acting as a gateway or proxy, received an invalid response from an upstream server.

503

Service Unavailable

The server is not ready to handle the request, often due to maintenance or overload.

504

Gateway Timeout

The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server.

505

HTTP Version Not Supported

The HTTP version used in the request is not supported by the server.

506

Variant Also Negotiates

The server has an internal configuration error with content negotiation.

507

Insufficient Storage

The server cannot store the representation needed to complete the request.

508

Loop Detected

The server detected an infinite loop in the request processing.

510

Not Extended

Further extensions to the request are required for the server to fulfill it.

511

Network Authentication Required

The client needs to authenticate to gain network access.