HTTP Status Codes & Common Ports Reference

Quick reference for HTTP status codes, common ports and MIME types with keyword filtering and one-click copy. All data ships with the page.

1xx Informational

Continue

Headers received, client should continue sending the body

Switching Protocols

Protocol switch, typically a successful WebSocket handshake

Processing

Server received the request and is still processing it

Early Hints

Early hints so the client can preload resources

2xx Success

OK

Request succeeded and the response body contains the result

Created

Resource created, usually with a Location header

Accepted

Request accepted but not finished, common for async jobs

Non-Authoritative Information

Metadata comes from a cached copy rather than the origin

No Content

Success with no response body, common for DELETE

Reset Content

Client should reset the document view

Partial Content

Partial content for range requests, resume and video chunks

Multi-Status

Multiple statuses for batch operations, body lists details

Already Reported

Avoids repeated enumeration of the same members

IM Used

Server fulfilled the request with delta encoding

3xx Redirection

Multiple Choices

Multiple representations exist, client must choose

Moved Permanently

Resource moved permanently, search engines update the index

Found

Temporary redirect, later requests still use the original URL

See Other

Fetch the result from another URL using GET

Not Modified

Cache is still valid, no need to resend the body

Use Proxy

Resource must be accessed via a proxy (deprecated)

Temporary Redirect

Temporary redirect that preserves method and body

Permanent Redirect

Permanent redirect that preserves method and body

4xx Client Error

Bad Request

Malformed request syntax or invalid parameters

Unauthorized

Not authenticated, retry with valid credentials

Payment Required

Reserved code, often used for paid API limits

Forbidden

Authenticated but not allowed to access the resource

Not Found

Resource not found or no route matched

Method Not Allowed

Method not allowed, the Allow header lists valid methods

Not Acceptable

Cannot produce a representation matching the Accept header

Proxy Authentication Required

Proxy authentication is required first

Request Timeout

Server timed out waiting for the request

Conflict

Conflicts with the current state, such as duplicate creation

Gone

Resource permanently deleted with no forwarding address

Length Required

Content-Length header is required

Precondition Failed

A precondition in the request headers failed

Payload Too Large

Request body exceeds the server limit

URI Too Long

Request URL is too long, send data in the body instead

Unsupported Media Type

The Content-Type is not supported

Range Not Satisfiable

The requested byte range is invalid

Expectation Failed

The Expect header cannot be satisfied

I'm a teapot

April Fools code, often used in rate-limit demos

Misdirected Request

Request was sent to a server unable to respond

Unprocessable Entity

Syntax is valid but semantic validation failed

Locked

Resource is locked, common in WebDAV

Failed Dependency

Failed because a previous request failed

Too Early

Request arrived too early and may be replayed

Upgrade Required

Client must upgrade to another protocol such as TLS

Precondition Required

Request must be conditional to avoid lost updates

Too Many Requests

Rate limited, back off according to Retry-After

Request Header Fields Too Large

Request headers too large, often from cookie bloat

Unavailable For Legal Reasons

Unavailable for legal reasons

Client Closed Request

Nginx extension: the client closed the connection

5xx Server Error

Internal Server Error

Unhandled server error, check the service logs

Not Implemented

The server does not support the request method

Bad Gateway

Gateway received an invalid upstream response

Service Unavailable

Service unavailable, possibly overloaded or in maintenance

Gateway Timeout

Gateway timed out waiting for the upstream

HTTP Version Not Supported

The HTTP version is not supported

Variant Also Negotiates

Content negotiation configuration is circular

Insufficient Storage

Insufficient storage, common in WebDAV

Loop Detected

Infinite loop detected, common in WebDAV traversal

Not Extended

Further extensions to the request are required

Network Authentication Required

Network authentication required, such as a WiFi portal

Web Server Returned an Unknown Error

Cloudflare extension: origin returned an unknown error

Web Server Is Down

Cloudflare extension: the origin server is down

Reference data is bundled with the page, so lookups never trigger network requests.

About This Tool

This reference gathers HTTP status codes from 1xx to 5xx, common service ports and MIME types on one page. Filter by keyword and click any code or type to copy it, without switching between multiple documents.

All data ships with the page, so lookups never trigger network requests and no account is required. Use it to triage production errors, decide whether a 502 comes from the gateway or the origin, or pick the right status code during API design.

Key Features

Three references in one

Status codes, ports and MIME types live in separate tabs, no need to open three sites.

Instant filtering

Type 502, redis or .xlsx to jump straight to the entry; both names and descriptions match.

One-click copy

Click a code or port to copy it into a ticket or chat message.

Fully local

The dataset loads with the page, works offline and never sends your query anywhere.

When to Use It

Incident triage

Quickly confirm what 502, 504 or 499 mean and where the failure most likely sits.

API design reviews

Choose meaningful status codes instead of returning 200 for every outcome.

Deployment checks

Verify port usage and pick the right MIME type for upload endpoints.

How to Use It

  1. 1Open the HTTP Status, Common Ports or MIME Types tab.
  2. 2Type a status code, service name, port or file extension in the search box.
  3. 3Click the code or type to copy it to the clipboard.

Frequently Asked Questions

What is the difference between 502 and 504?

502 means the gateway received an invalid response from upstream, often because the backend process is down. 504 means the gateway timed out waiting for upstream, often due to slow processing or network issues.

Are these port numbers fixed?

They are the conventional IANA defaults. Real deployments may differ, so always check the actual listening port and firewall rules when debugging.

Why does one extension appear with multiple MIME types?

Some extensions are ambiguous. For example .ts can be TypeScript source or an MPEG transport stream, so pick the type based on the actual content.

Other Tools

CodeSwordsman

100+ technical tools with browser-local processing — your data never leaves your device. Official Microsoft Store desktop apps: free, ad-free, offline.

Completely Free

© 2026 CodeSwordsman All Rights Reserved

Service Terms | Privacy Policy | Help | Version Updates | About Us

This website uses cookies to ensure you get the best experience on our website. Privacy Policy.