404 or 410?
404 Not Found means nothing is at the URL; 410 Gone means it was removed on purpose and won't come back, which tells search engines to drop it sooner.
Look up what any HTTP status code means, from 100 Continue to 511, in plain English.
For example 404, 5xx or “too many”
47 codes
ContinueInformational
The server got the request headers; the client can send the body.
Switching ProtocolsInformational
The server is switching protocols, for example to WebSocket.
Early HintsInformational
Headers sent early so the browser can start preloading resources.
OKSuccess
The request succeeded.
CreatedSuccess
The request succeeded and a new resource was created.
AcceptedSuccess
The request was accepted for processing, which hasn't finished yet.
No ContentSuccess
The request succeeded and there is nothing to send back.
Partial ContentSuccess
Only part of the resource is sent, as asked for with a Range header.
Moved PermanentlyRedirection
The resource has a new permanent URL; search engines pass ranking to it.
FoundRedirection
The resource is temporarily at another URL.
See OtherRedirection
Fetch the result from another URL with GET, for example after a form is sent.
Not ModifiedRedirection
The cached copy is still up to date; nothing is sent again.
Temporary RedirectRedirection
Temporarily at another URL; the method and body must not change.
Permanent RedirectRedirection
Permanently at another URL; the method and body must not change.
Bad RequestClient error
The server can't process the request because it is malformed.
UnauthorizedClient error
Authentication is needed, or the credentials given are wrong.
Payment RequiredClient error
Reserved; some services use it when a payment or plan is needed.
ForbiddenClient error
The server understood the request but refuses it, even with login.
Not FoundClient error
Nothing exists at this URL.
Method Not AllowedClient error
This URL doesn't accept that method, such as POST.
Not AcceptableClient error
No version of the resource matches the Accept headers.
Request TimeoutClient error
The client took too long to send the request.
ConflictClient error
The request conflicts with the current state, such as an edit conflict.
GoneClient error
The resource was removed on purpose and won't come back.
Length RequiredClient error
The request needs a Content-Length header.
Precondition FailedClient error
A condition in the request headers (such as If-Match) is false.
Content Too LargeClient error
The request body is larger than the server accepts.
URI Too LongClient error
The URL is longer than the server accepts.
Unsupported Media TypeClient error
The server doesn't accept the body's format (Content-Type).
Range Not SatisfiableClient error
The requested byte range is outside the file.
I'm a teapotClient error
An April Fools' joke from RFC 2324; not a real error.
Unprocessable ContentClient error
The request is well-formed but has invalid data, such as a form error.
Too EarlyClient error
The server won't risk processing a request that might be replayed.
Upgrade RequiredClient error
The client must switch to another protocol, such as TLS.
Precondition RequiredClient error
The request must be conditional, to prevent lost updates.
Too Many RequestsClient error
Rate limit reached; wait before trying again (see Retry-After).
Request Header Fields Too LargeClient error
The headers, often cookies, are too large.
Unavailable For Legal ReasonsClient error
Blocked for legal reasons, such as a court order.
Internal Server ErrorServer error
Something went wrong on the server; the request may be fine.
Not ImplementedServer error
The server doesn't support the feature needed.
Bad GatewayServer error
A proxy or CDN got an invalid response from the server behind it.
Service UnavailableServer error
The server is overloaded or down for maintenance; try again later.
Gateway TimeoutServer error
A proxy or CDN gave up waiting for the server behind it.
HTTP Version Not SupportedServer error
The server doesn't support the HTTP version used.
Insufficient StorageServer error
The server can't store what is needed to finish the request.
Loop DetectedServer error
The server found an infinite loop while processing the request.
Network Authentication RequiredServer error
Log in to the network first, as on hotel Wi-Fi.
Runs in your browser — nothing you enter is sent to a server.
Type a status code, the first digits of one, a class such as 4xx, or words like "too many". Each code is listed with its official name from the IANA registry and a plain-English explanation.
The first digit gives the class:
404 Not Found means nothing is at the URL; 410 Gone means it was removed on purpose and won't come back, which tells search engines to drop it sooner.
Both are permanent redirects. 308 also requires the method and body to stay the same, so a POST stays a POST.
Too Many Requests: a rate limit was reached. Wait before trying again; the Retry-After header often says how long.
401 means you aren't logged in (or the credentials are wrong). 403 means you are known but not allowed.
It's an April Fools' joke from 1998 (RFC 2324, "I'm a teapot") that stayed reserved because so many servers use it for fun.
Split a URL into scheme, host, port, path, query parameters and fragment.
Developer Tools
Create a robots.txt file that blocks paths, allows exceptions, lists sitemaps and can block AI training crawlers.
SEO Tools
Find the MIME type for a file extension, or the extensions for a MIME type.
Developer Tools