# What does the HTTP 403 status code mean?

> HTTP 403 Forbidden means the server understood the request but refuses to fulfill it, as defined in RFC 9110, the HTTP Semantics standard.

*Under the HTTP standard, a client should not automatically repeat the request with the same credentials, and a server may answer 404 instead to hide that a forbidden page exists.*

- Type: Explainer
- Section: Tech
- By: Tech Desk
- Published: 2026-11-12T11:39:04-05:00
- Updated: 2026-11-12T11:39:04-05:00
- Checked: 2026-11-12T11:38:00-05:00
- URL: https://factsdesk.com/tech/what-does-the-http-403-status-code-mean/

## Key facts

- Under RFC 9110, the HTTP 403 (Forbidden) status code means the server understood the request but refuses to fulfill it. Source: [RFC Editor](https://www.rfc-editor.org/rfc/rfc9110.html). Confirmed 2026-11-12T11:38:00-05:00. Cite: https://factsdesk.com/tech/what-does-the-http-403-status-code-mean/#under-rfc-9110-the-http-403-forbidden-status-code-means-the
- RFC 9110 says that if credentials were sent with a request that gets a 403, the server considers them insufficient, and the client should not automatically repeat the request with the same credentials. Source: [RFC Editor](https://www.rfc-editor.org/rfc/rfc9110.html). Confirmed 2026-11-12T11:38:00-05:00. Cite: https://factsdesk.com/tech/what-does-the-http-403-status-code-mean/#rfc-9110-says-that-if-credentials-were-sent-with-a-request
- RFC 9110 allows a server that wants to hide that a forbidden resource exists to answer with 404 (Not Found) instead of 403. Source: [RFC Editor](https://www.rfc-editor.org/rfc/rfc9110.html). Confirmed 2026-11-12T11:38:00-05:00. Cite: https://factsdesk.com/tech/what-does-the-http-403-status-code-mean/#rfc-9110-allows-a-server-that-wants-to-hide-that-a-forbidden
- The IANA HTTP Status Code Registry lists 403 as Forbidden, with RFC 9110, Section 15.5.4, as its reference. Source: [Internet Assigned Numbers Authority (IANA)](https://www.iana.org/assignments/http-status-codes). Confirmed 2026-11-12T11:38:00-05:00. Cite: https://factsdesk.com/tech/what-does-the-http-403-status-code-mean/#the-iana-http-status-code-registry-lists-403-as-forbidden
- RFC 9110, HTTP Semantics, is an IETF Internet Standard published in June 2022 and also known as STD 97. Source: [IETF Datatracker](https://datatracker.ietf.org/doc/rfc9110/). Confirmed 2026-11-12T11:38:00-05:00. Cite: https://factsdesk.com/tech/what-does-the-http-403-status-code-mean/#rfc-9110-http-semantics-is-an-ietf-internet-standard

The HTTP 403 status code, named Forbidden, means that the server understood the request but refuses to fulfill it, according to [RFC 9110](https://www.rfc-editor.org/rfc/rfc9110.html), the document that defines HTTP Semantics. A server that wants to say publicly why the request was forbidden can describe the reason in the response content, [the standard says](https://www.rfc-editor.org/rfc/rfc9110.html).

## What the standard says

Section 15.5.4 of [RFC 9110](https://www.rfc-editor.org/rfc/rfc9110.html) defines the code in these words: "The 403 (Forbidden) status code indicates that the server understood the request but refuses to fulfill it."

The [IANA HTTP Status Code Registry](https://www.iana.org/assignments/http-status-codes), which is maintained by IANA and registers status code numbers, records 403 as Forbidden with RFC 9110, Section 15.5.4, as its reference. The same registry describes the 4xx class, to which 403 belongs, as "Client Error - The request contains bad syntax or cannot be fulfilled".

[RFC 9110](https://www.rfc-editor.org/rfc/rfc9110.html) says that a server sending any 4xx response, except to a HEAD request, should send a representation explaining the error and whether it is a temporary or permanent condition, and that user agents should display that representation to the user.

## Does logging in again fix a 403?

[RFC 9110](https://www.rfc-editor.org/rfc/rfc9110.html) says that if authentication credentials were provided in the request, the server considers them insufficient to grant access, and the client should not automatically repeat the request with the same credentials. The client may repeat the request with new or different credentials, but the standard adds that a request "might be forbidden for reasons unrelated to the credentials."

## How 403 differs from 401

The two codes answer different problems. Under [RFC 9110](https://www.rfc-editor.org/rfc/rfc9110.html), 401 (Unauthorized) means the request has not been applied because it lacks valid authentication credentials for the target resource, and a server sending 401 must include a WWW-Authenticate header field with at least one challenge. The same document says that a server that receives valid credentials that are not adequate to gain access ought to respond with 403 (Forbidden).

| Code | Name | When the standard uses it |
| --- | --- | --- |
| 401 | Unauthorized | Request lacks valid authentication credentials |
| 403 | Forbidden | The request is understood but refused |
| 404 | Not Found | No current representation, or the server will not disclose one exists |

The table follows the definitions in [RFC 9110](https://www.rfc-editor.org/rfc/rfc9110.html), Sections 15.5.2, 15.5.4 and 15.5.5.

## Why a forbidden page can show 404 instead

[RFC 9110](https://www.rfc-editor.org/rfc/rfc9110.html) allows an origin server that wishes to hide the current existence of a forbidden target resource to respond with 404 (Not Found) instead of 403. The standard's definition of 404 covers this case, saying the code means the origin server did not find a current representation for the target resource "or is not willing to disclose that one exists."

## Which document defines HTTP status codes

RFC 9110, HTTP Semantics, is an Internet Standard of the Internet Engineering Task Force published in June 2022, and it is also known as STD 97, [the IETF Datatracker shows](https://datatracker.ietf.org/doc/rfc9110/). It obsoletes earlier documents including RFC 7231 and RFC 7235, according to the [Datatracker](https://datatracker.ietf.org/doc/rfc9110/) record.

## Sources

1. [RFC 9110: HTTP Semantics](https://www.rfc-editor.org/rfc/rfc9110.html), RFC Editor, 2022-06 (primary source)
2. [Hypertext Transfer Protocol (HTTP) Status Code Registry](https://www.iana.org/assignments/http-status-codes), Internet Assigned Numbers Authority (IANA), 2025-09-15 (primary source)
3. [RFC 9110: HTTP Semantics](https://datatracker.ietf.org/doc/rfc9110/), IETF Datatracker, 2026-05-20 (primary source)

## Asked next

- [What does the HTTP 301 status code mean?](https://factsdesk.com/tech/what-does-the-http-301-status-code-mean/): HTTP 301 means Moved Permanently: the resource has a new permanent URI, and future references to it ought to use the new address, under RFC 9110.
- [What does the HTTP 400 status code mean?](https://factsdesk.com/tech/what-does-the-http-400-status-code-mean/): HTTP 400 Bad Request means the server cannot or will not process a request because of something it perceives to be a client error, under RFC 9110.
- [What does the HTTP 401 status code mean?](https://factsdesk.com/tech/what-does-the-http-401-status-code-mean/): The HTTP 401 Unauthorized status code means a request was not applied because it lacks valid authentication credentials for the target resource.
- [What does the HTTP 404 status code mean?](https://factsdesk.com/tech/what-does-the-http-404-status-code-mean/): HTTP 404 Not Found means the server did not find a current representation for the target resource or is not willing to disclose that one exists.
- [What does the HTTP 500 status code mean?](https://factsdesk.com/tech/what-does-the-http-500-status-code-mean/): HTTP 500 Internal Server Error means the server encountered an unexpected condition that prevented it from fulfilling the request, under RFC 9110.
- [What does the HTTP 429 status code mean?](https://factsdesk.com/tech/what-does-the-http-429-status-code-mean/): HTTP 429 Too Many Requests means the user has sent too many requests in a given amount of time, which RFC 6585 calls rate limiting.
