IPs, Ports & Hex

192.168.0.1 = "one-ninety-two dot one-sixty-eight dot zero dot one":

An IPv4 address has four octets separated by dots. The separator is read as "dot" (not "point" — that is reserved for decimals and versions), and each octet is read as a normal number.

• "one-ninety-two dot one-sixty-eight dot zero dot one" — natural and clear.
• Digit-by-digit ("one nine two...") is also acceptable when accuracy is critical, e.g. over a noisy phone line.

Why "dot" and not "point"? Convention: addresses, hostnames and file extensions use "dot" (as in "example dot com"); decimal numbers use "point". So 192.168.0.1 is dots, but 3.14 is "three point one four".

Never merge octets: each is 0–255 and independent, so you never say "one hundred ninety-two point one hundred sixty-eight". Reading it as one giant number is always wrong.

:8080 = "port eight thousand (and) eighty" or "eighty-eighty":

The leading colon means "port", and is usually spoken as the word "port" rather than "colon". The number 8080 is read as a whole number.

• "port eight thousand and eighty" — fully correct.
• "port eighty-eighty" — extremely common shorthand, grouping the digits in pairs (80-80).

Common port readings:

• 80 → "port eighty" (HTTP)
• 443 → "port four-four-three" or "four hundred and forty-three" (HTTPS)
• 8080 → "port eighty-eighty"
• 3000 → "port three thousand"
• 5432 → "port fifty-four thirty-two" (Postgres)

Note: reading it digit-by-digit ("eight-oh-eight-oh") is heard but less idiomatic than the paired "eighty-eighty". There is no decimal point, so "eight point zero eight zero" is wrong.

0x1F = "zero-ex one-F" (hex 1F) = 31 decimal:

The 0x prefix marks a hexadecimal number and is read "zero-ex" (or you simply say "hex"). Each hex digit is then read by name: 1 is "one", and F is the letter "eff".

• "zero-ex one-eff" or "hex one-F" — both fine.
• Value: 1F₃₆ = (1 × 16) + 15 = 31. The digit F equals 15.

Hex letter pronunciations (A–F):

• A = "ay", B = "bee", C = "see", D = "dee", E = "ee", F = "eff"
• 0xFF → "zero-ex eff-eff" = 255
• 0xDEAD → sometimes spoken as the word "dead"; 0xCAFE as "caff" / "cafe"

Wrong options: there is no decimal point (so not 1.5 or 16), and you do not use the NATO alphabet ("foxtrot") for hex digits in normal speech.

/24 = "slash twenty-four" — a CIDR prefix length:

In CIDR notation (Classless Inter-Domain Routing), the number after the slash is how many bits of the 32-bit address are the network prefix. The slash IS spoken — "slash twenty-four".

• /24 = 24 network bits, leaving 8 host bits = 2⁸ = 256 addresses (254 usable hosts).
• It corresponds to the subnet mask 255.255.255.0.

Common prefixes (say "slash N"):

• /8 → "slash eight" — 16,777,216 addresses (a "slash eight")
• /16 → "slash sixteen" — 65,536 addresses
• /24 → "slash twenty-four" — 256 addresses
• /32 → "slash thirty-two" — a single host

Wrong readings: it is not division, not "out of", and not a VLAN id. Engineers literally say "we allocated a slash twenty-four to that VPC."

#FF5733 = "hex F-F-five-seven-three-three" (or "hash F F 5 7 3 3"):

A CSS colour is a 6-digit hexadecimal value. The # is read as "hash" (British) or "pound"/"number sign" (US), or skipped by just saying "hex". Each of the six characters is then read individually.

• "hex eff-eff-five-seven-three-three" — clearest for dictation.
• It splits into RGB pairs: FF = red 255, 57 = green 87, 33 = blue 51 — a vivid orange.

Reading colour hex by pairs: "eff-eff, five-seven, three-three" groups the red/green/blue bytes, which helps the listener reconstruct the value.

Special cases:

• #FFFFFF → "hex all effs" / "triple-eff" — white
• #000000 → "all zeros" — black
• Shorthand #F53 expands to #FF5533.

Wrong: never read it as one giant decimal, and avoid "hashtag" (that is social-media usage). The digits are not "fifty-five" etc. — read each character.