# status.forsale

> Explore HTTP status codes, understand their meanings and find a code that fits your company. status.forsale is an independent reference and advertising project.

This is an independent project, not an IANA or IETF service. Advert placements are published after confirmed payment and remain until another advertiser takes the code, subject to the terms of use. An advert buys no ownership of an HTTP standard. Technical definitions and sponsor advertising are separate.

Reference review: 2026-09-05. This date describes the reference, not the current advert. The catalogue covers the 60 codes offered on the site, not every registered or experimental status.

## Pages

- [Homepage](https://status.forsale/): Explore companies and available advertising spaces.
- [HTTP status code reference](https://status.forsale/codes): All 60 code pages, grouped by HTTP response class.
- [About, rules and sources](https://status.forsale/about): Project identity, claim rules and reference sources.
- [Privacy policy](https://status.forsale/privacy): Information handled by the service, why it is used, retention and privacy rights.
- [Cookie policy](https://status.forsale/cookies): Essential browser storage and optional analytics, enabled only with consent.
- [Terms of use](https://status.forsale/terms): Claims, submitted content and takeover rules.
- [Legal notice](https://status.forsale/legal): Operator and contact information.
- [Full Markdown reference](https://status.forsale/llms-full.txt): Definitions and specification links from the same data as the website.

## Interpretation

- The canonical reference URL for a code is /codes/{code}. These pages return HTTP 200 when the code exists, including /codes/404.
- /responses/{code} is a diagnostic endpoint that intentionally returns the requested HTTP status. It is not the canonical reference page. 1xx cannot be sent as final responses here; 204, 205 and 304 have no response body.
- Consult a code's HTML page for its current company advert. This document deliberately does not snapshot sponsors, prices, takeovers or availability.
- Use the linked RFC for normative HTTP semantics. The IANA registry is at https://www.iana.org/assignments/http-status-codes.
- The 418 teapot entry follows the joke in RFC 2324; the current registry marks 418 as unused.

## Questions about the site

### What is status.forsale?

An independent HTTP status code reference and advertising project. Each code has a page explaining its meaning, plus one space for a company’s advert. It is not affiliated with IANA or the IETF.

### Am I buying an HTTP status code?

No. A claim is for advertising space on this website. HTTP standards remain independent; placing an advert does not give a company ownership of a status code or change how it works.

### Does the site take real payments?

Yes. A claim opens a secure hosted checkout, and the advert is published only after the payment provider confirms payment. Card details are entered with the payment provider and are not stored by status.forsale.

### How do claims and takeovers work?

An available code starts at $10. Each takeover raises the total by $5 in US dollars. A spot stays until another company takes it; there is no guaranteed duration or traffic.

### How does previous claim credit count?

Previous confirmed payments count only for the same verified buyer, company domain and code. For example: claim at $10, get overtaken at $15, and reclaim at $20 by paying another $10. Credit is applied only to a future eligible claim and has no cash value.

### Do sponsors get equal visibility?

Sponsored cards receive a fresh random order each visit, independent of spend. That gives each spot the same chance of a position; it does not guarantee equal measured impressions or clicks.

### Where do the HTTP definitions come from?

The reference summaries are checked against the IANA HTTP status code registry and the RFC linked on each code page. The catalogue covers the 60 codes offered here, rather than every registered or experimental status. Sponsor advertising and company-fit suggestions are separate from the technical definitions.

## 1xx Informational

Informational responses describe progress before the final response.

### 100 Continue

URL: https://status.forsale/codes/100

The request headers were received; the client can continue sending the request body.

Specification: [RFC 9110, section 15.2.1](https://www.rfc-editor.org/rfc/rfc9110.html#section-15.2.1)

Company-fit suggestion (advertising wordplay): For upload tools that keep things moving.

### 101 Switching Protocols

URL: https://status.forsale/codes/101

The server is switching protocols as requested by the client.

Specification: [RFC 9110, section 15.2.2](https://www.rfc-editor.org/rfc/rfc9110.html#section-15.2.2)

Company-fit suggestion (advertising wordplay): For real-time chat and streaming platforms.

### 102 Processing

URL: https://status.forsale/codes/102

The server has received the request and is still processing it.

102 comes from the older WebDAV specification RFC 2518. It is retained here as a reference code; support varies.

Specification: [RFC 2518, section 10.1](https://www.rfc-editor.org/rfc/rfc2518.html#section-10.1)

Company-fit suggestion (advertising wordplay): For background jobs and workflow automation.

### 103 Early Hints

URL: https://status.forsale/codes/103

Early response headers hint at resources while the final response is prepared.

Specification: [RFC 8297, section 2](https://www.rfc-editor.org/rfc/rfc8297.html#section-2)

Company-fit suggestion (advertising wordplay): For faster websites and smarter preloading.

## 2xx Success

Success responses describe how the server handled a request.

### 200 OK

URL: https://status.forsale/codes/200

The request succeeded. Everything is working as it should.

Specification: [RFC 9110, section 15.3.1](https://www.rfc-editor.org/rfc/rfc9110.html#section-15.3.1)

Company-fit suggestion (advertising wordplay): For uptime monitoring and reliable hosting.

### 201 Created

URL: https://status.forsale/codes/201

The request succeeded and a new resource was created.

Specification: [RFC 9110, section 15.3.2](https://www.rfc-editor.org/rfc/rfc9110.html#section-15.3.2)

Company-fit suggestion (advertising wordplay): For website builders and creative tools.

### 202 Accepted

URL: https://status.forsale/codes/202

The request has been accepted for processing, which is not yet complete.

Specification: [RFC 9110, section 15.3.3](https://www.rfc-editor.org/rfc/rfc9110.html#section-15.3.3)

Company-fit suggestion (advertising wordplay): For job queues and asynchronous workflows.

### 203 Non-Authoritative Information

URL: https://status.forsale/codes/203

A proxy modified the origin server’s successful response.

Specification: [RFC 9110, section 15.3.4](https://www.rfc-editor.org/rfc/rfc9110.html#section-15.3.4)

Company-fit suggestion (advertising wordplay): For content proxies and data transformation.

### 204 No Content

URL: https://status.forsale/codes/204

The request succeeded, but there is no response content to send.

A 204 response has no body. Read any relevant result information from its headers.

Specification: [RFC 9110, section 15.3.5](https://www.rfc-editor.org/rfc/rfc9110.html#section-15.3.5)

Company-fit suggestion (advertising wordplay): For minimalist tools that clear the clutter.

### 205 Reset Content

URL: https://status.forsale/codes/205

The request succeeded; reset the input view for another submission.

A 205 response has no body. Its meaning asks the client to reset the document view used to send the request.

Specification: [RFC 9110, section 15.3.6](https://www.rfc-editor.org/rfc/rfc9110.html#section-15.3.6)

Company-fit suggestion (advertising wordplay): For form builders and fresh starts.

### 206 Partial Content

URL: https://status.forsale/codes/206

The response supplies the requested portion of a representation.

Specification: [RFC 9110, section 15.3.7](https://www.rfc-editor.org/rfc/rfc9110.html#section-15.3.7)

Company-fit suggestion (advertising wordplay): For video streaming and resumable downloads.

### 207 Multi-Status

URL: https://status.forsale/codes/207

A WebDAV response contains separate results for multiple resources or operations.

Specification: [RFC 4918, section 13](https://www.rfc-editor.org/rfc/rfc4918.html#section-13)

Company-fit suggestion (advertising wordplay): For batch operations and file management.

### 208 Already Reported

URL: https://status.forsale/codes/208

A WebDAV binding was already listed, avoiding repeated enumeration.

Specification: [RFC 5842, section 7.1](https://www.rfc-editor.org/rfc/rfc5842.html#section-7.1)

Company-fit suggestion (advertising wordplay): For tools that eliminate duplicate work.

### 226 IM Used

URL: https://status.forsale/codes/226

The response represents the result of instance manipulations applied to a resource, such as delta encoding.

Specification: [RFC 3229, section 10.4.1](https://www.rfc-editor.org/rfc/rfc3229.html#section-10.4.1)

Company-fit suggestion (advertising wordplay): For efficient syncing and smaller updates.

## 3xx Redirection

Redirection responses indicate another step or reuse of a cached representation.

### 300 Multiple Choices

URL: https://status.forsale/codes/300

There is more than one possible response to this request.

Specification: [RFC 9110, section 15.4.1](https://www.rfc-editor.org/rfc/rfc9110.html#section-15.4.1)

Company-fit suggestion (advertising wordplay): For comparison tools and recommendation engines.

### 301 Moved Permanently

URL: https://status.forsale/codes/301

This resource has moved to a new, permanent address.

Specification: [RFC 9110, section 15.4.2](https://www.rfc-editor.org/rfc/rfc9110.html#section-15.4.2)

Company-fit suggestion (advertising wordplay): For website migrations and moving services.

### 302 Found

URL: https://status.forsale/codes/302

The resource is temporarily available at a different address.

Specification: [RFC 9110, section 15.4.3](https://www.rfc-editor.org/rfc/rfc9110.html#section-15.4.3)

Company-fit suggestion (advertising wordplay): For short links and flexible redirects.

### 303 See Other

URL: https://status.forsale/codes/303

Retrieve the result from the URL in the Location header.

Specification: [RFC 9110, section 15.4.4](https://www.rfc-editor.org/rfc/rfc9110.html#section-15.4.4)

Company-fit suggestion (advertising wordplay): For discovery tools that point somewhere new.

### 304 Not Modified

URL: https://status.forsale/codes/304

The cached version is still current. No download needed.

304 is a cache validation result, not a redirect to a new URL. It has no response body.

Specification: [RFC 9110, section 15.4.5](https://www.rfc-editor.org/rfc/rfc9110.html#section-15.4.5)

Company-fit suggestion (advertising wordplay): For caching tools that skip needless downloads.

### 307 Temporary Redirect

URL: https://status.forsale/codes/307

Repeat the request elsewhere temporarily, preserving its method.

Specification: [RFC 9110, section 15.4.8](https://www.rfc-editor.org/rfc/rfc9110.html#section-15.4.8)

Company-fit suggestion (advertising wordplay): For traffic routing and temporary detours.

### 308 Permanent Redirect

URL: https://status.forsale/codes/308

Repeat the request at its permanent URL, preserving its method.

Specification: [RFC 9110, section 15.4.9](https://www.rfc-editor.org/rfc/rfc9110.html#section-15.4.9)

Company-fit suggestion (advertising wordplay): For permanent migrations that preserve requests.

## 4xx Client error

Client error responses explain why a request could not be fulfilled.

### 400 Bad Request

URL: https://status.forsale/codes/400

The server cannot process the request because of a client error.

Specification: [RFC 9110, section 15.5.1](https://www.rfc-editor.org/rfc/rfc9110.html#section-15.5.1)

Company-fit suggestion (advertising wordplay): For API testing and request validation.

### 401 Unauthorized

URL: https://status.forsale/codes/401

The request needs valid authentication credentials.

Specification: [RFC 9110, section 15.5.2](https://www.rfc-editor.org/rfc/rfc9110.html#section-15.5.2)

Company-fit suggestion (advertising wordplay): For login tools and identity verification.

### 402 Payment Required

URL: https://status.forsale/codes/402

Reserved for future use; often associated with payment requirements.

402 is reserved in the HTTP standard. An API that uses it for payments defines its own application-specific behaviour.

Specification: [RFC 9110, section 15.5.3](https://www.rfc-editor.org/rfc/rfc9110.html#section-15.5.3)

Company-fit suggestion (advertising wordplay): For payments, billing and getting paid.

### 403 Forbidden

URL: https://status.forsale/codes/403

The server understands the request but refuses to fulfil it.

Specification: [RFC 9110, section 15.5.4](https://www.rfc-editor.org/rfc/rfc9110.html#section-15.5.4)

Company-fit suggestion (advertising wordplay): For access control and security platforms.

### 404 Not Found

URL: https://status.forsale/codes/404

The server could not find the requested resource.

Specification: [RFC 9110, section 15.5.5](https://www.rfc-editor.org/rfc/rfc9110.html#section-15.5.5)

Company-fit suggestion (advertising wordplay): For search tools that find what’s missing.

### 405 Method Not Allowed

URL: https://status.forsale/codes/405

The resource does not support this request method.

Specification: [RFC 9110, section 15.5.6](https://www.rfc-editor.org/rfc/rfc9110.html#section-15.5.6)

Company-fit suggestion (advertising wordplay): For API gateways and method validation.

### 406 Not Acceptable

URL: https://status.forsale/codes/406

No available representation matches the requested content negotiation preferences.

Specification: [RFC 9110, section 15.5.7](https://www.rfc-editor.org/rfc/rfc9110.html#section-15.5.7)

Company-fit suggestion (advertising wordplay): For content negotiation and format conversion.

### 407 Proxy Authentication Required

URL: https://status.forsale/codes/407

The proxy requires authentication before forwarding the request.

Specification: [RFC 9110, section 15.5.8](https://www.rfc-editor.org/rfc/rfc9110.html#section-15.5.8)

Company-fit suggestion (advertising wordplay): For secure proxies and authenticated access.

### 408 Request Timeout

URL: https://status.forsale/codes/408

The server timed out while waiting for the complete request.

Specification: [RFC 9110, section 15.5.9](https://www.rfc-editor.org/rfc/rfc9110.html#section-15.5.9)

Company-fit suggestion (advertising wordplay): For faster uploads and reliable connections.

### 409 Conflict

URL: https://status.forsale/codes/409

The request conflicts with the current state of the resource.

Specification: [RFC 9110, section 15.5.10](https://www.rfc-editor.org/rfc/rfc9110.html#section-15.5.10)

Company-fit suggestion (advertising wordplay): For version control and conflict resolution.

### 410 Gone

URL: https://status.forsale/codes/410

The resource is no longer available, likely permanently.

Specification: [RFC 9110, section 15.5.11](https://www.rfc-editor.org/rfc/rfc9110.html#section-15.5.11)

Company-fit suggestion (advertising wordplay): For data deletion and digital decluttering.

### 411 Length Required

URL: https://status.forsale/codes/411

The server requires a Content-Length header.

Specification: [RFC 9110, section 15.5.12](https://www.rfc-editor.org/rfc/rfc9110.html#section-15.5.12)

Company-fit suggestion (advertising wordplay): For upload validation and request inspection.

### 412 Precondition Failed

URL: https://status.forsale/codes/412

A condition in the request headers evaluated to false.

Specification: [RFC 9110, section 15.5.13](https://www.rfc-editor.org/rfc/rfc9110.html#section-15.5.13)

Company-fit suggestion (advertising wordplay): For version checks and safer updates.

### 413 Content Too Large

URL: https://status.forsale/codes/413

The request content exceeds the server’s accepted size.

Specification: [RFC 9110, section 15.5.14](https://www.rfc-editor.org/rfc/rfc9110.html#section-15.5.14)

Company-fit suggestion (advertising wordplay): For file compression and large-file transfers.

### 414 URI Too Long

URL: https://status.forsale/codes/414

The request URI exceeds the server’s accepted length.

Specification: [RFC 9110, section 15.5.15](https://www.rfc-editor.org/rfc/rfc9110.html#section-15.5.15)

Company-fit suggestion (advertising wordplay): For URL shorteners and cleaner links.

### 415 Unsupported Media Type

URL: https://status.forsale/codes/415

The request’s media type or encoding is unsupported.

Specification: [RFC 9110, section 15.5.16](https://www.rfc-editor.org/rfc/rfc9110.html#section-15.5.16)

Company-fit suggestion (advertising wordplay): For media conversion and format compatibility.

### 416 Range Not Satisfiable

URL: https://status.forsale/codes/416

The server cannot satisfy the requested range.

Specification: [RFC 9110, section 15.5.17](https://www.rfc-editor.org/rfc/rfc9110.html#section-15.5.17)

Company-fit suggestion (advertising wordplay): For download tools and media delivery.

### 417 Expectation Failed

URL: https://status.forsale/codes/417

The server cannot meet the request’s Expect header requirements.

Specification: [RFC 9110, section 15.5.18](https://www.rfc-editor.org/rfc/rfc9110.html#section-15.5.18)

Company-fit suggestion (advertising wordplay): For API diagnostics and compatibility testing.

### 418 I'm a teapot

URL: https://status.forsale/codes/418

The beloved teapot response from RFC 2324. A playful addition; IANA marks 418 as unused.

“I’m a teapot” is the joke response from RFC 2324. The current IANA registry and RFC 9110 mark 418 as unused.

Specification: [RFC 2324, section 2.3.2](https://www.rfc-editor.org/rfc/rfc2324.html#section-2.3.2)

Company-fit suggestion (advertising wordplay): For tea brands and a better brew.

### 421 Misdirected Request

URL: https://status.forsale/codes/421

The request reached a server unable to answer for that origin.

Specification: [RFC 9110, section 15.5.20](https://www.rfc-editor.org/rfc/rfc9110.html#section-15.5.20)

Company-fit suggestion (advertising wordplay): For DNS tools and smarter request routing.

### 422 Unprocessable Content

URL: https://status.forsale/codes/422

The content syntax is understood, but its instructions cannot be processed.

Specification: [RFC 9110, section 15.5.21](https://www.rfc-editor.org/rfc/rfc9110.html#section-15.5.21)

Company-fit suggestion (advertising wordplay): For data validation and better forms.

### 423 Locked

URL: https://status.forsale/codes/423

A WebDAV resource is locked, preventing the requested operation.

Specification: [RFC 4918, section 11.3](https://www.rfc-editor.org/rfc/rfc4918.html#section-11.3)

Company-fit suggestion (advertising wordplay): For file locking and document collaboration.

### 424 Failed Dependency

URL: https://status.forsale/codes/424

A WebDAV operation failed because another operation it depended on failed.

Specification: [RFC 4918, section 11.4](https://www.rfc-editor.org/rfc/rfc4918.html#section-11.4)

Company-fit suggestion (advertising wordplay): For dependency monitoring and workflow recovery.

### 425 Too Early

URL: https://status.forsale/codes/425

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

Specification: [RFC 8470, section 5.2](https://www.rfc-editor.org/rfc/rfc8470.html#section-5.2)

Company-fit suggestion (advertising wordplay): For replay protection and safer requests.

### 426 Upgrade Required

URL: https://status.forsale/codes/426

The server requires a different protocol to fulfil the request.

Specification: [RFC 9110, section 15.5.22](https://www.rfc-editor.org/rfc/rfc9110.html#section-15.5.22)

Company-fit suggestion (advertising wordplay): For software upgrades and modern protocols.

### 428 Precondition Required

URL: https://status.forsale/codes/428

The server requires a conditional request, often to avoid conflicting updates.

Specification: [RFC 6585, section 3](https://www.rfc-editor.org/rfc/rfc6585.html#section-3)

Company-fit suggestion (advertising wordplay): For concurrency control and safer editing.

### 429 Too Many Requests

URL: https://status.forsale/codes/429

Too many requests have arrived in a given amount of time.

Specification: [RFC 6585, section 4](https://www.rfc-editor.org/rfc/rfc6585.html#section-4)

Company-fit suggestion (advertising wordplay): For rate limiting and traffic management.

### 431 Request Header Fields Too Large

URL: https://status.forsale/codes/431

The request headers are too large, individually or together.

Specification: [RFC 6585, section 5](https://www.rfc-editor.org/rfc/rfc6585.html#section-5)

Company-fit suggestion (advertising wordplay): For cookie management and leaner requests.

### 451 Unavailable For Legal Reasons

URL: https://status.forsale/codes/451

The resource is unavailable due to a legal demand.

Specification: [RFC 7725, section 3](https://www.rfc-editor.org/rfc/rfc7725.html#section-3)

Company-fit suggestion (advertising wordplay): For legal services and digital rights.

## 5xx Server error

Server error responses describe failures in the server or its upstream services.

### 500 Internal Server Error

URL: https://status.forsale/codes/500

An unexpected server condition prevented the request from being fulfilled.

Specification: [RFC 9110, section 15.6.1](https://www.rfc-editor.org/rfc/rfc9110.html#section-15.6.1)

Company-fit suggestion (advertising wordplay): For error tracking and debugging tools.

### 501 Not Implemented

URL: https://status.forsale/codes/501

The server does not implement the requested functionality.

Specification: [RFC 9110, section 15.6.2](https://www.rfc-editor.org/rfc/rfc9110.html#section-15.6.2)

Company-fit suggestion (advertising wordplay): For development teams building missing features.

### 502 Bad Gateway

URL: https://status.forsale/codes/502

A gateway received an invalid response from an upstream server.

Specification: [RFC 9110, section 15.6.3](https://www.rfc-editor.org/rfc/rfc9110.html#section-15.6.3)

Company-fit suggestion (advertising wordplay): For API monitoring and reliable gateways.

### 503 Service Unavailable

URL: https://status.forsale/codes/503

The server is temporarily unable to handle the request.

Specification: [RFC 9110, section 15.6.4](https://www.rfc-editor.org/rfc/rfc9110.html#section-15.6.4)

Company-fit suggestion (advertising wordplay): For incident response and service recovery.

### 504 Gateway Timeout

URL: https://status.forsale/codes/504

A gateway did not receive a timely response from an upstream server.

Specification: [RFC 9110, section 15.6.5](https://www.rfc-editor.org/rfc/rfc9110.html#section-15.6.5)

Company-fit suggestion (advertising wordplay): For performance monitoring and faster APIs.

### 505 HTTP Version Not Supported

URL: https://status.forsale/codes/505

The server does not support this HTTP protocol version.

Specification: [RFC 9110, section 15.6.6](https://www.rfc-editor.org/rfc/rfc9110.html#section-15.6.6)

Company-fit suggestion (advertising wordplay): For protocol testing and server modernisation.

### 506 Variant Also Negotiates

URL: https://status.forsale/codes/506

A server configuration error creates a circular reference during content negotiation.

Specification: [RFC 2295, section 8.1](https://www.rfc-editor.org/rfc/rfc2295.html#section-8.1)

Company-fit suggestion (advertising wordplay): For server configuration and content negotiation.

### 507 Insufficient Storage

URL: https://status.forsale/codes/507

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

Specification: [RFC 4918, section 11.5](https://www.rfc-editor.org/rfc/rfc4918.html#section-11.5)

Company-fit suggestion (advertising wordplay): For cloud storage and more room to grow.

### 508 Loop Detected

URL: https://status.forsale/codes/508

A WebDAV operation stopped because the server detected an infinite loop.

Specification: [RFC 5842, section 7.2](https://www.rfc-editor.org/rfc/rfc5842.html#section-7.2)

Company-fit suggestion (advertising wordplay): For tracing tools that catch endless loops.

### 511 Network Authentication Required

URL: https://status.forsale/codes/511

Network access requires authentication, such as signing in through a captive portal.

511 concerns network access authentication. It is different from an application requesting login with 401.

Specification: [RFC 6585, section 6](https://www.rfc-editor.org/rfc/rfc6585.html#section-6)

Company-fit suggestion (advertising wordplay): For Wi-Fi access and network authentication.