RFC 1918 private address
What is RFC 1918 private address?
RFC 1918 reserves three IPv4 blocks -- 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16 -- for private networks, never routed on the public internet without NAT rewriting the source address at the boundary. AdminKit's subnet tooling helps confirm whether a given address actually falls inside one of these reserved ranges.
By AdminKit team, Netbase JSC · Updated
RFC 1918 reserves three blocks of IPv4 address space — 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16 — for use inside private networks, never to be routed on the public internet. ARIN’s page on IPv4 private address space and filtering points out that only part of the 172 and 192 ranges is private, so filters that block these blocks need to use the exact prefixes rather than whole first octets. Any organization or home network can reuse these same addresses internally without coordinating with anyone else — the same three ranges Microsoft’s own TCP/IP addressing documentation lists for private networks — which is what makes NAT (network address translation) necessary at the boundary: a router rewrites a private source address to its one public address before traffic leaves the network, then reverses the mapping for replies. Seeing one of these ranges as a device’s own address is normal and expected behind a home router or office firewall. Seeing one show up where a public-facing address is expected instead usually signals a misconfigured NAT, proxy, or double-NAT setup rather than a real internet-reachable host. IPv6 has a conceptually similar private range of its own, the ULA, though each network generates its own block locally instead of drawing from one globally reserved registry entry the way RFC 1918 works. RFC 1918 space is one recognized category of reserved addressing, listed alongside the other reserved IPv4 blocks in IANA’s special-purpose address registry; traffic claiming to come from unallocated or otherwise reserved space that isn’t a legitimate private range is typically filtered on sight as a bogon address instead.
To check whether one specific address actually falls inside one of these three ranges (or another IANA special-use category entirely), paste it into AdminKit’s IP info tool, which classifies a single address offline with no DNS lookups. For the full picture, including look-alike ranges such as 100.64.0.0/10 and how to pick a private range for a new network, read private IP address ranges (RFC 1918) explained.
RFC 1918 private address is part of AdminKit’s IP & network cluster; the full AdminKit glossary lists other related terms.
Frequently asked questions
What three address blocks does RFC 1918 reserve?
10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16 -- any organization or home network can reuse these internally without coordinating with anyone else, since they're never routed on the public internet.
Why does seeing an RFC 1918 address matter for diagnosing a network problem?
Seeing one as a device's own address behind a home router or office firewall is normal, but seeing one show up where a public-facing address is expected usually signals a misconfigured NAT, proxy, or double-NAT setup.
How does IPv6 handle private addressing compared to RFC 1918?
IPv6 has a conceptually similar private range, the ULA, though each network generates its own block locally instead of drawing from one globally reserved registry entry the way RFC 1918 works.
What happens to traffic claiming to come from RFC 1918 space on the public internet?
RFC 1918 space is one recognized category of reserved addressing in IANA's special-purpose address registry; traffic from unallocated or reserved space that isn't a legitimate private range is typically filtered on sight as a bogon address.