What are the private IP address ranges in RFC 1918?
RFC 1918 reserves three IPv4 blocks for private networks: 10.0.0.0/8, 172.16.0.0/12 and 192.168.0.0/16. Anyone can use them inside a home, office or cloud network without asking a registry, but they are never routed on the public internet. AdminKit's free IP-in-CIDR tool tells you whether an address is in one.
By AdminKit team, Netbase JSC · Updated
Key takeaways
- RFC 1918 reserves three IPv4 blocks for private networks:
10.0.0.0/8,172.16.0.0/12and192.168.0.0/16. - They can be reused by anyone, so they have no meaning outside the network that uses them. Routers on the internet are expected to filter them, and NAT translates them to a public address on the way out.
172.16.0.0/12ends at172.31.255.255. Addresses just outside it, such as172.32.0.1, are public.100.64.0.0/10(carrier-grade NAT),169.254.0.0/16(link-local) and127.0.0.0/8(loopback) are special-purpose too, but they are not RFC 1918 space.- AdminKit’s free IP-in-CIDR tool checks an address against any ranges you paste and names the special-use category, in your browser.
What are the three private IPv4 ranges?
Section 3 of RFC 1918, published in 1996, lists three blocks that IANA reserved “for private internets”:
| Block | First address | Last address | Total addresses | RFC 1918 name |
|---|---|---|---|---|
10.0.0.0/8 | 10.0.0.0 | 10.255.255.255 | 16,777,216 | 24-bit block |
172.16.0.0/12 | 172.16.0.0 | 172.31.255.255 | 1,048,576 | 20-bit block |
192.168.0.0/16 | 192.168.0.0 | 192.168.255.255 | 65,536 | 16-bit block |
The totals are 2 raised to the number of host bits: 24, 20 and 16. The RFC notes that in the old classful terms the first block is one class A network, the second is 16 class B networks and the third is 256 class C networks.
Any organization can use these addresses “without any coordination with IANA or an Internet registry”. That is why many home routers hand out a 192.168.x.x address, and why cloud providers recommend these blocks for virtual networks.
To see the network, broadcast address and usable hosts inside any slice of these blocks, use AdminKit’s subnet calculator. Subnet and CIDR basics explains what a prefix such as /12 means.
Why does 172.16.0.0/12 confuse people?
The first and last blocks line up with whole octets: everything starting 10. and everything starting 192.168. is private. The middle block does not. A /12 prefix fixes the first 12 bits, which is all 8 bits of the first octet and only the top 4 bits of the second:
172 = 10101100
16 to 31 = 0001xxxx
So the second octet can only be 16 to 31. 172.15.255.255 and 172.32.0.0 sit on either side of the private block and are both public.
ARIN’s page on IPv4 private address space and filtering warns about exactly this: only a portion of the “172” and “192” ranges is private, and the remaining addresses are routable on the internet. ARIN began allocating “172” space to internet service, wireless and content providers in August 2012, and notes reports of operators blocking the whole 172.0.0.0/8 range, which leaves some legitimate users unable to reach those sites. Firewall rules and bogon filters should list the exact prefixes, never “172.x.x.x”.
| Address | Inside a private range? |
|---|---|
10.255.255.255 | Yes, last address of 10.0.0.0/8 |
172.15.255.255 | No, public |
172.31.0.1 | Yes, inside 172.16.0.0/12 |
172.32.0.1 | No, public |
192.169.0.1 | No, public |
100.64.0.1 | No, CGNAT shared space (RFC 6598) |
Why can’t private addresses be reached from the internet?
Because thousands of networks use the same private addresses at once, an address such as 10.0.0.5 does not identify one host on the internet. RFC 1918 states that “private addresses have no global meaning”, so:
- Routing information about private networks shall not be passed between enterprises, and packets with private source or destination addresses should not be forwarded across those links.
- Internet service providers are expected to filter routes for private networks.
- References to private addresses, such as DNS records, should stay inside the enterprise.
A device with a private address reaches the internet through network address translation (NAT). Your router rewrites the private source address to its own public address on the way out and keeps a table to send replies back. That is why AdminKit’s My IP tool shows a different address from the one your laptop reports: it sees the public address after NAT.
Private addressing is not a security control on its own. It keeps hosts from being addressed directly from the internet, but a port forward, a VPN or a compromised device inside the network still reaches them.
Which ranges look private but are not RFC 1918?
Several other IPv4 and IPv6 blocks are reserved for special purposes. RFC 6890 collects them into IANA’s special-purpose address registries. Cloud providers list the same blocks when they say which ranges a subnet may use, for example Google Cloud’s valid IPv4 subnet ranges.
| Block | Purpose | Defined in | RFC 1918? |
|---|---|---|---|
100.64.0.0/10 | Shared Address Space for carrier-grade NAT | RFC 6598 | No |
169.254.0.0/16 | IPv4 link-local, self-assigned when DHCP fails | RFC 3927 | No |
127.0.0.0/8 | Loopback, the host itself | RFC 1122 | No |
192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24 | Documentation examples only | RFC 5737 | No |
198.18.0.0/15 | Network benchmark testing | RFC 2544 | No |
fc00::/7 (in practice fd00::/8) | IPv6 Unique Local Addresses | RFC 4193 | No, but the closest IPv6 equivalent |
100.64.0.0/10 causes the most confusion. RFC 6598 says this Shared Address Space “is distinct from RFC 1918 private address space because it is intended for use on Service Provider networks”. If your router’s WAN address is in it, your ISP is putting you behind carrier-grade NAT. What is CGNAT explains what that breaks, and the CGNAT glossary entry gives the short version.
For IPv6, see the ULA glossary entry. RFC 4193 adds a pseudo-random 40-bit Global ID to each ULA prefix, so two networks that pick ULA prefixes independently are unlikely to clash later.
How do you check whether an IP address is private?
Paste the address into AdminKit’s IP-in-CIDR tool, with the three RFC 1918 blocks as the ranges:
10.0.0.0/8
172.16.0.0/12
192.168.0.0/16
The tool reports “Contained” or “Not contained” for each range, shows the normalized network it tested, and labels the category, for example “Private use (RFC 1918)”. If you add 100.64.0.0/10 as a fourth line, it also tells you whether the address is CGNAT space. Everything is calculated in your browser and nothing is sent to a server.
For a quick check by eye:
- Starts with
10.: private. - Starts with
192.168.: private. - Starts with
172.and the second number is 16 to 31: private. Any other second number: public. - Starts with
100.and the second number is 64 to 127: CGNAT shared space, not RFC 1918.
How do you choose a private range for a new network?
Any of the three blocks works technically. The choice matters later, when networks have to connect. Cloud providers recommend RFC 1918 space too: the Amazon VPC User Guide recommends a CIDR block “from the private IPv4 address ranges as specified in RFC 1918”, and the Azure Virtual Network FAQ recommends the same three ranges, and also allows 100.64.0.0/10, which Azure treats as private.
Practical rules:
| Situation | Suggested approach | Why |
|---|---|---|
| Home or small office | A /24 from 192.168.0.0/16 that is not your router’s default | Avoids a clash when you connect over VPN from another home network on the same default |
| Office that will use site-to-site VPN | A distinct /24 or /16 per site from 10.0.0.0/8 | Each site’s range must be unique for routing between sites to work |
| Cloud VPC or virtual network | A block from 10.0.0.0/8 or 172.16.0.0/12 that no on-premises or other cloud network uses | Peering and VPN connections need non-overlapping ranges |
| Anything that runs AWS services or containers | Avoid 172.17.0.0/16 | AWS documents that some of its services use this range and can conflict with a VPC that uses it |
Size each subnet with room to spare, because cloud platforms keep some addresses for themselves. The Azure Virtual Network FAQ states that Azure reserves the first four addresses and the last address in every subnet, five in total. In a 192.168.1.0/24 subnet that leaves 251 addresses for your own resources, not the 254 a plain subnet calculation gives. Other providers document their own reserved addresses, so check before you cut a block into small subnets. AdminKit’s subnet calculator shows the plain usable host count for any prefix. Subtract your platform’s reserved addresses from that count.
RFC 1918 itself names the long-term cost: “companies tend to merge”, and two private networks that were set up separately may then contain duplicate addresses that have to be renumbered. A short written plan of which range each site and cloud network uses avoids most of that. Using a subnet calculator to plan a VLAN or multi-subnet network walks through splitting one block into subnets.
What does a private address in the wrong place tell you?
- Your router’s WAN address is private. There is another NAT in front of it: the ISP’s carrier-grade NAT if it is in
100.64.0.0/10, or a second router or modem in NAT mode if it is RFC 1918 space. Inbound port forwarding will not work until that is resolved. - A public DNS record returns a private address. Internal hostnames are leaking into public DNS. RFC 1918 asks that such references stay inside the enterprise. Visitors outside your network cannot reach that address.
- A log or email header shows a private source address. It was added by a device inside some network, often a proxy or internal mail relay. It cannot be traced on the internet, so look at the next public hop instead. The bogon address glossary entry covers why packets from private or unallocated space arriving from the internet are dropped.
Check an address against the private ranges now: it is free, needs no account and runs entirely in your browser. For the one-paragraph definition, see the RFC 1918 glossary entry. This guide is part of AdminKit’s IP and network cluster.
This guide is general information, not a security audit of your specific network — see our disclaimer for what AdminKit's guidance does and does not commit to.
Frequently asked questions
What are the three private IPv4 address ranges?
RFC 1918 reserves 10.0.0.0 to 10.255.255.255 (10.0.0.0/8), 172.16.0.0 to 172.31.255.255 (172.16.0.0/12) and 192.168.0.0 to 192.168.255.255 (192.168.0.0/16). Any organization can use them internally without coordination with IANA or a regional internet registry.
Is 172.32.0.1 a private IP address?
No. The private block 172.16.0.0/12 covers only 172.16.0.0 to 172.31.255.255. Addresses from 172.32.0.0 upward, and from 172.0.0.0 to 172.15.255.255, are ordinary public address space. Paste the address and 172.16.0.0/12 into AdminKit's IP-in-CIDR tool to check.
Is 100.64.0.0/10 a private range?
Not in the RFC 1918 sense. RFC 6598 reserves 100.64.0.0/10 as Shared Address Space for carrier-grade NAT, meant for use on service provider networks between the provider's NAT and customer routers. It is not routed on the internet either, but it should not be used as a replacement for RFC 1918 space in your own LAN unless your platform documents it, as Azure does for virtual networks.
Why does my router show a private WAN IP address?
Your router is behind another NAT. If the WAN address is in 100.64.0.0/10, your ISP is using carrier-grade NAT. If it is an RFC 1918 address, there is usually another router or modem in NAT mode in front of yours (double NAT). Compare it with the public address AdminKit's My IP tool shows.
Can two networks use the same private range?
Yes, as long as they never need to route to each other directly. Problems start when they do: a site-to-site VPN, a cloud network peering or a company merger. RFC 1918 itself notes that merged private networks may end up with duplicate addresses that need renumbering, so pick distinct ranges for networks that may ever be connected.
What is the IPv6 equivalent of RFC 1918?
Unique Local Addresses (ULA) from RFC 4193, in fc00::/7. In practice they use fd00::/8 with a pseudo-random 40-bit Global ID, which makes it unlikely that two separately created ULA networks overlap when they are later connected.
Sources
- RFC 1918 — Address Allocation for Private Internets
- RFC 6598 — IANA-Reserved IPv4 Prefix for Shared Address Space
- RFC 6890 — Special-Purpose IP Address Registries
- RFC 4193 — Unique Local IPv6 Unicast Addresses
- ARIN — IPv4 Private Address Space and Filtering
- Amazon VPC User Guide — VPC CIDR blocks
- Microsoft Learn — Azure Virtual Network FAQ
- Google Cloud — Subnets (valid IPv4 ranges)
Want AdminKit to watch this for you?
Free checks tell you the state today. Protective DNS and monitoring tell you when it changes.
Talk to an expert
Huy Nguyen (David), Founder & CEO, Netbase JSC
Ask whether this fix applies to your setup, or get a second pair of eyes on your DNS and mail records.