Network and API

HTTP status codes directory

The reference helps you quickly understand what server response code means and how it affects APIs, SEO, caching, redirects, and custom scripting.

FreeNo registrationOnline in browser
100

Continue

The server has received the headers and is waiting for the request to continue.

101

Switching Protocols

The server switches the protocol at the request of the client.

200

OK

The request was successfully processed and the server returned the expected response.

201

Created

The resource was successfully created. Often found in POST APIs.

202

Accepted

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

204

No Content

Success without a response body. Useful for delete/update scripts.

301

Moved Permanently

Permanent redirect. Important for SEO and URL transfer.

302

Found

Temporary redirect. Doesn't transmit signals the same way as 301.

304

Not Modified

The content has not changed. Used in caching.

307

Temporary Redirect

Temporary redirect without changing the request method.

308

Permanent Redirect

Permanent redirect without changing the request method.

400

Bad Request

The request is formed incorrectly: there is an error in the parameters or structure.

401

Unauthorized

Requires authentication or access token.

403

Forbidden

Access is denied even if the user is authorized.

404

Not Found

Resource not found. Critical for SEO and UX if the code is shared frequently.

405

Method Not Allowed

The route exists, but the request method is not allowed.

409

Conflict

State conflict. Often when re-creating an entity.

410

Gone

The resource has been permanently deleted and will no longer be available.

418

I'm a teapot

A humorous status from the RFC, but sometimes found in tests and demos.

422

Unprocessable Entity

The syntax is correct, but the data is not validated.

429

Too Many Requests

Rate limit triggered. Important for APIs, parsers and integrations.

500

Internal Server Error

Internal application or server error.

502

Bad Gateway

Problem between proxy/gateway and upstream service.

503

Service Unavailable

The service is temporarily unavailable: overload, maintenance or emergency.

504

Gateway Timeout

The intermediate server did not wait for the upstream response.

What the tool can do

  • Search by status code or name.
  • Division into groups 1xx–5xx.
  • An explanation of the cases in which the code occurs.

How to use

  1. Enter the code or part of the status name.
  2. Open the desired card from the list.
  3. Use explanation for debug or documentation.

Where is this service useful?

Debugging APIs and web applications.
Checking SEO redirects and 404 pages.
Preparation of documentation and technical specifications.

FAQ

Why are HTTP statuses important for SEO?

Search engines rely on response codes. Errors 404, 5xx and incorrect redirects directly affect indexing and crawl quality.

Why know the difference between 301 and 302?

Because permanent and temporary redirects have different effects on indexing, signaling, and caching.

Related tools

All instruments
NBM-IT

Need a tool for your process?

We can make a custom calculator, validator, integration helper or audit panel for your data, CRM and internal scripts.