HTTP 200 OK

Success code, RFC 9110, section 15.3.1

What it means

The request worked and the answer is in the response. For GET it holds the page or file you asked for; for POST it usually describes the result.

A real response

This is the request and the answer our test server gave when we asked it to return 200.

GET /c/200 HTTP/1.1
Host: example.com

HTTP/1.1 200 OK
Date: Sat, 14 Nov 2026 10:00:00 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 11

<p>demo</p>

If you run the site

This is the normal success code. If you want to tell clients that the request worked but there is nothing to send back, 204 is more exact. A frequent error is returning 200 with an error message in the body: tools that watch status codes then think everything is fine.

If you are a visitor

Nothing to fix. If the page looks wrong, the problem is in the page, not in the connection.

A common mistake

Returning 200 for a page that does not exist (a "soft 404"). Search engines treat these as errors and may stop trusting the site. Send a real 404.

Registered in the IANA HTTP Status Code Registry as OK, defined in RFC 9110, section 15.3.1.

This is an independent guide. It is not connected with the IETF, IANA, any browser maker or any company named here. Meanings were checked against the RFC texts on 14 November 2026. Responses shown were recorded on 14 November 2026 from a small test server on the author's own computer.