HTTP status codes, error identifiers, and code ranges appear in every incident review, code walkthrough, and support ticket. Saying them clearly and naturally marks you as fluent in developer English.
0 / 5 completed
1 / 5
A user reports a bug: "I'm getting HTTP 404 when I visit the page." How is HTTP 404 said aloud?
HTTP 404 — "four oh four" or "HTTP error four hundred and four":
HTTP status codes have two natural spoken patterns depending on context:
"four oh four" — each digit individually, zero said as "oh". Most common in developer conversations: "Getting a four oh four", "the four oh four page"
"four hundred and four" — the full number. More formal: "HTTP error four hundred and four"
"four hundred four" — American English skips "and": "HTTP four hundred four"
Status code pronunciation guide:
Code
Common spoken form
Name
200
"two hundred" or "two oh oh"
OK
404
"four oh four"
Not Found
500
"five hundred" or "five oh oh"
Internal Server Error
401
"four oh one"
Unauthorised
503
"five oh three"
Service Unavailable
Note on "HTTP": Usually spelled out — "H-T-T-P" /eɪtʃ tiː tiː piː/ — but in fast conversation many developers just say "the status code" without spelling HTTP.
2 / 5
A developer explains an error: "We're seeing a lot of 500 errors in production." When talking about HTTP error classes, how are 5xx errors described?
5xx errors — "five-ex-ex" or "five-hundred-class" or just "server errors":
When talking about a class of HTTP errors, developers use several conventions:
5xx — "five-ex-ex" — Server errors (500, 502, 503, 504)
3 / 5
An architect says: "In our error handling, we map every ORA-00904 to a user-friendly message." How would you say the Oracle error code ORA-00904 aloud?
ORA-00904 — "O-R-A zero-zero-nine-oh-four" or "ORA dash zero-zero-nine-oh-four":
Error codes with alphanumeric identifiers are read character by character, with a few conventions:
Letters are spelled out individually: "O-R-A"
The hyphen/dash is usually said as "dash" or "hyphen", or sometimes omitted in fast speech
Digit groups: leading zeros are often retained to avoid ambiguity: "zero-zero-nine-oh-four" not just "nine oh four"
Zero in error codes is commonly said as "oh" or "zero" — both are fine
Other common error code formats:
Code
How to say it
E1000
"E one thousand" or "E ten-zero-zero"
ERR_CONNECTION_REFUSED
"error connection refused" (read as words)
SQLSTATE 42000
"SQL state four-two-zero-zero-zero"
4 / 5
A developer explains: "The error occurs when the response body exceeds 413 — Payload Too Large." How is the HTTP status code 413 most naturally said?
413 — "four thirteen", "four one three", or "four hundred and thirteen" — all used:
Three-digit HTTP status codes have flexible spoken forms:
Form
Example
Register
"four thirteen"
"Getting a four thirteen"
Most natural / conversational
"four one three"
"Error four one three"
Technical / precise
"four hundred and thirteen"
"HTTP four hundred and thirteen"
Formal / presentation
Practical advice: In a fast standup, "four thirteen" is the most natural English form. In a written incident report, "HTTP 413 Payload Too Large" is clearest. In a presentation, spell it out fully.
More status codes and their most natural spoken forms:
200 — "two hundred" (not "two oh oh")
201 — "two oh one" or "two hundred and one"
302 — "three oh two" (redirect)
422 — "four twenty-two" or "four two two" (Unprocessable Entity)
502 — "five oh two" (Bad Gateway)
5 / 5
In a code review comment, a developer writes: "If the status is not 2xx, throw an error." In a spoken code walkthrough, how is this condition described?
2xx in speech — "two-ex-ex" or "in the two-hundreds":
When speaking code comments or logic aloud, there are natural ways to express wildcard/range notation:
"two-ex-ex" — direct reading of the notation, using "ex" for each x
"in the two-hundreds" — natural English: "any status in the two-hundreds means success"
"a successful status code" — semantic paraphrase, most audience-friendly
"not two-ex-ex" — shorthand for "not in the 200–299 range"
Wildcards and ranges in spoken code:
Written
Spoken options
2xx
"two-ex-ex", "in the two-hundreds", "success codes"
In a code walkthrough context: "If the status code is not in the two-hundreds" is the clearest and most natural for a mixed technical and non-technical audience.
What will I practice in "Reading Error Codes and Status Codes Aloud — Pronunciation Practice"?
This is a Beginner pronunciation exercise with 5 questions focused on the correct pronunciation, stress, and sounds of numbers metrics used in IT.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to complete with no account, sign-up, or paywall.
How many questions are in this exercise?
This exercise has 5 questions. A progress bar at the top tracks how many you've answered, and each question gives immediate feedback with an explanation.
Do I need audio or a microphone for this exercise?
No — this is a multiple-choice recognition exercise. It tests whether you can identify correct stress, sounds, and pronunciation patterns, not whether you can record your own speech.
Can I retry the exercise if I get questions wrong?
Yes — use the "Try again" button on the results screen to reset your answers and go through all the questions again. There is no limit on attempts.
Is my progress saved?
Your answers and score for the current session are tracked in the browser as you go. No account or login is needed.
What if I don't understand why an answer is correct?
Read the explanation shown after you answer each question — it breaks down the correct pronunciation in plain English. You can also check the site Glossary for related terms.
Who is this exercise for?
It's designed for non-native English speakers in IT roles who want to sound clearer saying numbers metrics in meetings, code reviews, and interviews.
Where can I find more Numbers Metrics pronunciation exercises?
See the Numbers Metrics section for related exercises, or browse the main Pronunciation hub for other subcategories.
Can this help me prepare for a technical interview?
Yes — clear pronunciation of technical terms matters in interviews. Pair this exercise with our dedicated Interview Preparation section for role-specific practice.