Students & new developers
Build an HTTP status-code explorer
You have probably met 404 Not Found. Every website answers with a code like it. See what each one means, then build your own explorer in one HTML file.
Choose a situation to see what the website answers. Then select any code below to read about it.
Ask a website for something. See what it answers.
asksGET /recipes
200 OKthe website answers
It worked. Here is what you asked for.
- Who fixes it
- Nobody. Nothing is wrong.
- Try again?
- Not needed
- How often you meet it
- Often
1xx Informational The conversation is still going.
2xx Success It worked.
3xx Redirection Look somewhere else.
4xx Client errors The request was wrong.
5xx Server errors The website failed.
Every code in the IANA registry is here, including a few that are reserved, deprecated or obsolete. Each card says which.
| Code | Name | Class | In plain English | Example | Who fixes it | Try again |
|---|---|---|---|---|---|---|
| 100 | Continue | Informational | Go ahead and send the rest of your request. | A program asks before uploading a large file, and the server says to go ahead. | Nobody | Not needed |
| 101 | Switching Protocols | Informational | The server agrees to switch to a different way of talking. | A chat page upgrades its connection to a WebSocket so that messages arrive instantly. | Nobody | Not needed |
| 102 | Processing | Informational | The server has the request and is still working on it. | A file server takes a long time over a big copy and says it has not forgotten you. | Nobody | Not needed |
| 103 | Early Hints | Informational | Here is a head start: begin loading these files while the page is prepared. | A site tells the browser which fonts and styles to fetch before the page itself arrives. | Nobody | Not needed |
| 200 | OK | Success | It worked. Here is what you asked for. | You open a page and it loads. | Nobody | Not needed |
| 201 | Created | Success | It worked, and something new was made. | You post a comment or create an account. | Nobody | Not needed |
| 202 | Accepted | Success | The request was taken in and will be dealt with later. | You ask for a large report and are told it will be emailed when it is ready. | Nobody | Not needed |
| 203 | Non-Authoritative Information | Success | It worked, but a go-between changed the reply on the way. | A proxy rewrites part of a page before passing it on to you. | Nobody | Not needed |
| 204 | No Content | Success | It worked, and there is nothing to send back. | You save a setting and the page stays as it is. | Nobody | Not needed |
| 205 | Reset Content | Success | It worked. Clear the form you just sent. | A data-entry screen empties its boxes, ready for the next record. | Nobody | Not needed |
| 206 | Partial Content | Success | Here is the part you asked for, not the whole thing. | You skip to the middle of a video, or a download carries on from where it stopped. | Nobody | Not needed |
| 207 | Multi-Status | Success | Several things were asked for at once, and each has its own result inside. | A file-sharing program moves ten files and reports on each one. | Nobody | Not needed |
| 208 | Already Reported | Success | These items were already listed earlier in this reply. | A folder that appears twice in a file-server listing is described only once. | Nobody | Not needed |
| 226 | IM Used | Success | Here are only the changes since the copy you already have. | A feed reader receives just the new entries, not the whole feed again. | Nobody | Not needed |
| 300 | Multiple Choices | Redirection | There is more than one version. Pick one. | A document is offered in several formats or languages. | The requester | After choosing one |
| 301 | Moved Permanently | Redirection | This has a new address for good. Use the new one from now on. | A site changes its name and sends old links to the new pages. | The browser | Automatic |
| 302 | Found | Redirection | This is somewhere else for now. Keep using the old address. | After signing in, you are sent back to the page you came from. | The browser | Automatic |
| 303 | See Other | Redirection | Your request was handled. Fetch the result from this other address. | You submit an order form and land on a confirmation page. | The browser | Automatic |
| 304 | Not Modified | Redirection | Nothing has changed. Use the copy you already have. | You revisit a page and the browser reuses the images it saved last time. | Nobody | Not needed |
| 305 | Use Proxy | Redirection | No longer used. It once told the browser to go through a named proxy. | You will not meet it: browsers stopped honoring it for security reasons. | Nobody | No |
| 306 | (Unused) | Redirection | Reserved and no longer used. | It was dropped from an early version of HTTP, and the number is kept empty. | Nobody | No |
| 307 | Temporary Redirect | Redirection | This is somewhere else for now. Repeat exactly the same request there. | A form you submit is passed to another server without losing what you typed. | The browser | Automatic |
| 308 | Permanent Redirect | Redirection | This has moved for good. Repeat exactly the same request at the new address. | An API moves to a new address and uploads keep working. | The browser | Automatic |
| 400 | Bad Request | Client Error | The server could not understand the request. | A form sends a date that is not a date, or the address contains broken characters. | The requester | After fixing the request |
| 401 | Unauthorized | Client Error | You need to sign in, or your sign-in was not accepted. | You open your account page after your session has expired. | The requester | After signing in |
| 402 | Payment Required | Client Error | Reserved for a future way to pay. A few services use it to say that payment is needed. | An API returns it when a subscription has run out. | The requester | After fixing the request |
| 403 | Forbidden | Client Error | The server knows who you are and will not let you in. | You are signed in as a student and try to open the teacher's gradebook. | The requester | No |
| 404 | Not Found | Client Error | Nothing is at this address. | You mistype a web address, or follow a link to a page that was deleted. | The requester | After fixing the request |
| 405 | Method Not Allowed | Client Error | The address exists, but not for what you tried to do to it. | A program tries to delete a page that can only be read. | The requester | After fixing the request |
| 406 | Not Acceptable | Client Error | The server has nothing in a format you said you would accept. | A program insists on XML and the service only produces JSON. | The requester | After fixing the request |
| 407 | Proxy Authentication Required | Client Error | You must sign in to the proxy before it will pass your request on. | An office network asks for your login before letting you onto the web. | The requester | After signing in |
| 408 | Request Timeout | Client Error | The server gave up waiting for you to finish sending. | A weak phone signal stalls an upload halfway. | The requester | Yes |
| 409 | Conflict | Client Error | The request clashes with what is already there. | Two people edit the same document, and the second save is refused. | The requester | After fixing the request |
| 410 | Gone | Client Error | This was here once and has been removed for good. | A shop takes down the page of a discontinued product on purpose. | The requester | No |
| 411 | Length Required | Client Error | The server needs to be told how much data is coming. | A program uploads a file without saying how big it is. | The requester | After fixing the request |
| 412 | Precondition Failed | Client Error | A condition you attached to the request was not true. | You say "save only if nobody else has changed it", and somebody had. | The requester | After fixing the request |
| 413 | Content Too Large | Client Error | What you sent is bigger than the server allows. | You try to upload a 2 GB video where the limit is 100 MB. | The requester | After fixing the request |
| 414 | URI Too Long | Client Error | The address is longer than the server will read. | A search form packs thousands of characters into the address. | The requester | After fixing the request |
| 415 | Unsupported Media Type | Client Error | The server does not accept the kind of file or data you sent. | You upload a spreadsheet where only images are allowed. | The requester | After fixing the request |
| 416 | Range Not Satisfiable | Client Error | You asked for a part that does not exist. | A download tries to carry on from beyond the end of the file. | The requester | After fixing the request |
| 417 | Expectation Failed | Client Error | The server cannot do what the request's Expect header asked. | A program asks for a go-ahead before uploading, and the server does not give go-aheads. | The requester | After fixing the request |
| 418 | I'm a teapot | Client Error | A joke: the server says it is a teapot and cannot brew coffee. | An April Fools' Day specification defined it in 1998, and some sites return it for fun. | Nobody | No |
| 421 | Misdirected Request | Client Error | The request reached a server that is not set up to answer for that site. | A shared connection is reused for a site the server does not host. | The browser | Yes |
| 422 | Unprocessable Content | Client Error | The request was understood, but what it says does not make sense. | A booking form sends an end date that comes before its start date. | The requester | After fixing the request |
| 423 | Locked | Client Error | The item is locked and cannot be changed now. | A colleague has a shared file open for editing. | The requester | Later |
| 424 | Failed Dependency | Client Error | This step failed because an earlier step it relied on failed. | A file cannot be copied because creating its folder failed first. | The requester | After fixing the request |
| 425 | Too Early | Client Error | The server will not act yet on a request that might be a replayed copy. | A request sent in the first instant of a secure connection is asked to wait until the connection is confirmed. | The browser | Yes |
| 426 | Upgrade Required | Client Error | The server will only answer over a different protocol. | A service refuses an old kind of connection and names the one to use. | The requester | After fixing the request |
| 428 | Precondition Required | Client Error | The server insists that the request carries a condition. | An editor must say which version it is changing, so that two people do not overwrite each other. | The requester | After fixing the request |
| 429 | Too Many Requests | Client Error | You have asked too many times in a short while. Slow down. | A program calls a free API a thousand times in a minute. | The requester | Later |
| 431 | Request Header Fields Too Large | Client Error | The extra information sent with the request is too big. | A site's cookies have grown so large that the server rejects every page. | The requester | After fixing the request |
| 451 | Unavailable For Legal Reasons | Client Error | The server is not allowed to show this for legal reasons. | A court orders a page to be blocked in one country. The number is a nod to the novel Fahrenheit 451. | Nobody | No |
| 500 | Internal Server Error | Server Error | Something broke on the server, and it cannot say what. | A bug in the site's code crashes while building your page. | The website | Later |
| 501 | Not Implemented | Server Error | The server does not know how to do that kind of request. | A simple server receives a kind of request it was never built to handle. | The website | No |
| 502 | Bad Gateway | Server Error | A server in the middle got a broken answer from the server behind it. | The site's front door is open, but the application behind it has crashed. | The website | Later |
| 503 | Service Unavailable | Server Error | The server cannot answer right now. It is overloaded or down for maintenance. | Ticket sales open and far too many people arrive at once. | The website | Later |
| 504 | Gateway Timeout | Server Error | A server in the middle waited too long for the server behind it. | A report takes so long to build that the front server stops waiting. | The website | Later |
| 505 | HTTP Version Not Supported | Server Error | The server does not support the version of HTTP the request used. | A very old program talks to a modern server in a version it has dropped. | The requester | After fixing the request |
| 506 | Variant Also Negotiates | Server Error | The server is set up wrongly: its choice between versions loops back on itself. | A misconfigured site cannot decide which language version to send. | The website | No |
| 507 | Insufficient Storage | Server Error | The server has run out of room to store what you sent. | A shared drive is full when you try to save a file. | The website | Later |
| 508 | Loop Detected | Server Error | The server found itself going round in circles and stopped. | Folders on a file server link to each other in a loop. | The website | No |
| 510 | Not Extended | Server Error | Obsolete. The server wanted the request to use an extension that was never widely adopted. | You will not meet it: the experiment it belonged to was retired. | Nobody | No |
| 511 | Network Authentication Required | Server Error | You must sign in to the network before you can reach the web. | Hotel or airport Wi-Fi shows its login page first. | The requester | After signing in |
Make it your own
Build your own version.
The starter is one HTML file with no tools to install. Save it, open it in your browser, and it fetches the complete free list, draws the five bands and opens a card for any code.
Read the starter before you run it
<!doctype html>
<html lang="en">
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>HTTP status-code explorer</title>
<style>
body { max-width: 1000px; margin: 32px auto; padding: 16px; font: 16px system-ui; color: #243b50; }
input, button { font: inherit; padding: 12px; }
input { max-width: 100%; box-sizing: border-box; }
.tiles { display: grid; grid-template-columns: repeat(auto-fill, minmax(125px, 1fr)); gap: 8px; }
.tile { border: 1px solid #aebfcd; border-top: 3px solid #426b90; border-radius: 5px; background: #f3f7fa; text-align: left; cursor: pointer; }
.tile strong, .tile span { display: block; }
.tile strong { font-size: 1.4rem; margin-bottom: 8px; }
.tile span { font-size: .8rem; }
.dimmed { opacity: .35; }
.tile:hover, .tile:focus-visible { opacity: 1; background: #dce9f2; }
.detail { grid-column: 1 / -1; padding: 18px; border: 1px solid #7b95a9; background: #fff; }
.detail button { float: right; }
</style>
<h1>HTTP status-code explorer</h1>
<p>Select a tile to read what it means. ● marks the codes you meet often.</p>
<label>Find a code or phrase <input id="search" type="search"></label>
<p id="status" role="status">Loading codes…</p>
<button id="retry" hidden>Retry</button>
<main id="explorer"></main>
<script type="module">
const explorer = document.querySelector('#explorer');
const search = document.querySelector('#search');
const status = document.querySelector('#status');
const retry = document.querySelector('#retry');
const classes = ['Informational', 'Success', 'Redirection', 'Client errors', 'Server errors'];
let records = [];
let tiles = [];
let selected;
const detail = document.createElement('section');
detail.className = 'detail';
detail.hidden = true;
// Data goes into textContent, never into HTML strings.
function select(tile, record) {
detail.remove();
selected = tile;
const close = document.createElement('button');
close.textContent = 'Close';
close.onclick = () => {
detail.remove();
tile.focus({ preventScroll: true });
};
const heading = document.createElement('h3');
heading.textContent = `${record.Code} · ${record.Name}`;
const meaning = document.createElement('p');
meaning.textContent = record.PlainEnglish;
const example = document.createElement('p');
example.textContent = `For example: ${record.Example}`;
const facts = document.createElement('p');
facts.textContent = `Who fixes it: ${record.WhoFixesIt}. Try again? ${record.TryAgain}.`;
detail.replaceChildren(close, heading, meaning, example, facts);
// Insert after the last tile on this row, including on phones.
const row = [...tile.parentElement.children].filter(item => item.offsetTop === tile.offsetTop);
row.at(-1).after(detail);
detail.hidden = false;
detail.scrollIntoView({ block: 'nearest' });
close.focus({ preventScroll: true });
}
function filter() {
const query = search.value.trim().toLowerCase();
let count = 0;
for (const { tile, record } of tiles) {
const match = [record.Code, record.Name, record.PlainEnglish].join(' ').toLowerCase().includes(query);
tile.classList.toggle('dimmed', !match);
if (match) count++;
}
status.textContent = `${count} of ${records.length} codes${count ? '' : ' · No matches; try another phrase.'}`;
}
async function load() {
retry.hidden = true;
status.textContent = 'Loading codes…';
try {
const response = await fetch('https://mysafeinfo.com/api/data/httpstatuscodes?format=json');
if (!response.ok) throw new Error(`HTTP ${response.status}`);
records = await response.json();
explorer.replaceChildren();
tiles = [];
for (let family = 1; family <= 5; family++) {
const band = document.createElement('section');
const heading = document.createElement('h2');
heading.textContent = `${family}xx · ${classes[family - 1]}`;
const grid = document.createElement('div');
grid.className = 'tiles';
for (const record of records.filter(row => Math.floor(row.Code / 100) === family).sort((a, b) => a.Code - b.Code)) {
const tile = document.createElement('button');
tile.className = 'tile';
const code = document.createElement('strong');
code.textContent = `${record.Code}${record.Seen === 'Often' ? ' ●' : ''}`;
const name = document.createElement('span');
name.textContent = record.Name;
tile.append(code, name);
tile.onclick = () => select(tile, record);
grid.append(tile);
tiles.push({ tile, record });
}
band.append(heading, grid);
explorer.append(band);
}
filter();
} catch {
status.textContent = 'Could not load the codes. Check your connection and try again.';
retry.hidden = false;
}
}
search.addEventListener('input', filter);
retry.addEventListener('click', load);
document.addEventListener('keydown', event => {
if (event.key === 'Escape') {
detail.remove();
selected?.focus({ preventScroll: true });
}
});
load();
</script>
</html>
A project brief you can finish
-
Milestone 1: show the complete list
Load the free JSON, sort by
Code, and show each code with itsNameandPlainEnglish. Keep the data separate from the function that draws it. -
Milestone 2: search and filter
Search the code, name and plain-English meaning together. Add a filter for
WhoFixesIt, keep keyboard focus in the control, and announce the number of matches without moving the page. -
Milestone 3: handle every state
Show loading, a useful message when nothing matches, and a clear error with Retry. Check
response.okbefore reading the JSON: your own explorer will meet these codes too.
Stretch goals
Add your own stage: a row of situations that each show a request and its answer. Add a quiz that names a situation and asks for the code. Add a “copy code” button, or keyboard shortcuts with visible instructions.
Test a search with no matches, an offline request and a small phone. Not every code here is in everyday use: Status marks the reserved, deprecated and obsolete ones. Compare a code with the IANA registry (opens in a new tab) and the specification its card links to.
Questions
Why check response.ok?
A request that completes can still carry an error code. fetch does not fail just because a server answered 404 or 500, so your code has to look.
What should an empty search look like?
Say that nothing matched and suggest clearing the search. Do not show a network error: the list loaded fine.
Who decided what each code means?
The Internet Engineering Task Force publishes the specifications, and the Internet Assigned Numbers Authority keeps the registry of codes. Specification and SpecificationUrl point to the section that defines each one. The plain-English meanings and examples are ours.
Free in full. No Data Pass or API key needed. Opening this guide does not use your API allowance.
What each record contains
Explore the dataset and its sources. These fields are in the complete download.
| Field | How to read it |
|---|---|
Code |
HTTP status number. A listed code is not necessarily a current IANA standard. |
Name |
Short status label. |
Category |
Status family; useful for filters and grouping. |
Description |
Dataset explanation; check IANA and the linked standard for implementation details. |
PlainEnglish |
What the code means, in one sentence written for students. Ours, not the specification’s. |
Example |
An everyday situation that produces the code. |
WhoFixesIt |
Who has to act: Nobody, The browser, The requester (the person or program that sent the request) or The website. |
TryAgain |
Whether repeating the request can help: Not needed, Automatic, Yes, Later, After signing in, After fixing the request, After choosing one, or No. |
Seen |
How often a web user or developer meets it: Often, Sometimes or Rarely. Our judgement. |
Status |
Standard, Reserved, Deprecated, Unused or Obsolete, as the IANA registry and RFC 9110 class it. |
Specification |
The document and section that define the code, as the IANA registry cites it. |
SpecificationUrl |
A link to that section at rfc-editor.org. |
Working with the download? Convert CSV to JSON, or turn a column into a list with the comma separator.
For your next project
More subjects to build with.
HTTP status codes are free in full. The Data Pass covers the rest of the catalog.
The Data Pass includes complete downloads and API access across the catalog.