- 10.0.0.0/8, 172.16.0.0/12 and 192.168.0.0/16 are private (RFC 1918).
- 100.64.0.0/10 is shared space for carrier-grade NAT (RFC 6598).
- Private addresses are not routed on the public internet.
- Pick an unusual range to avoid clashes with home networks over VPN.
Turn any start and end address into the fewest CIDR blocks
The three RFC 1918 ranges
RFC 1918, from 1996, reserves three blocks for use inside private networks. Anyone may use them without asking a registry, and routers on the public internet drop them.
| Range | CIDR | Addresses | Old class equivalent |
|---|---|---|---|
| 10.0.0.0 to 10.255.255.255 | 10.0.0.0/8 | 16,777,216 | One class A |
| 172.16.0.0 to 172.31.255.255 | 172.16.0.0/12 | 1,048,576 | 16 class B |
| 192.168.0.0 to 192.168.255.255 | 192.168.0.0/16 | 65,536 | 256 class C |
Carrier-grade NAT: 100.64.0.0/10
RFC 6598 set aside 100.64.0.0/10 (100.64.0.0 to 100.127.255.255, 4,194,304 addresses) for internet providers that put customers behind a second layer of NAT. It exists so that providers do not have to use RFC 1918 space, which would clash with the customer's own network.
You will see it on mobile networks and some broadband connections, and some overlay VPNs use it inside their own networks. Treat it as not yours to use on a corporate LAN.
Other special ranges
| Range | Purpose | Defined in |
|---|---|---|
| 127.0.0.0/8 | Loopback, never leaves the host | RFC 1122 |
| 169.254.0.0/16 | Link-local, self-assigned when DHCP fails | RFC 3927 |
| 192.0.2.0/24 | Documentation (TEST-NET-1) | RFC 5737 |
| 198.51.100.0/24 | Documentation (TEST-NET-2) | RFC 5737 |
| 203.0.113.0/24 | Documentation (TEST-NET-3) | RFC 5737 |
| 198.18.0.0/15 | Network benchmarking | RFC 2544 |
| 224.0.0.0/4 | Multicast | RFC 5771 |
| 240.0.0.0/4 | Reserved | RFC 1112 |
The IPv4 calculator labels every address with its range, so you can paste an address and see straight away whether it is private, shared, reserved or public.
Choosing a range that will not clash
Address clashes show up when two networks join: a VPN from a home network, a merger, or a link to a partner. Most home routers use 192.168.0.0/24 or 192.168.1.0/24, and many use 10.0.0.0/24. If your office uses the same range, remote users cannot reach it over VPN.
- Avoid the defaults. Skip 192.168.0.x, 192.168.1.x and 10.0.0.x for anything people will reach remotely.
- Pick a random second octet in 10/8. Something like 10.137.0.0/16 is unlikely to match anyone else.
- Plan the whole block. Reserve a /16 per site and carve it with the subnet planner, so sites summarise cleanly.
- Check overlaps before you build. The overlap checker tells you if two ranges collide.
Private ranges in the cloud
Cloud VPCs and VNets use the same RFC 1918 ranges, so the clash rules matter even more. A VPC peered with another VPC, or connected back to the office, must not overlap with either. AWS allows VPC blocks between /16 and /28, and many teams give each environment its own /16 from 10/8. See cloud reserved IPs for how subnets inside a VPC are sized.
The IPv6 equivalent
IPv6 has unique local addresses, fd00::/8 in practice, defined in RFC 4193. Instead of everyone sharing the same few ranges, each network picks a random 40-bit ID, so clashes are very unlikely. Generate one with the ULA generator.
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 5737: IPv4 Address Blocks Reserved for Documentation
- IANA IPv4 Special-Purpose Address Registry