Back

Networking

Private IP Ranges Explained

Learn which IPv4 and IPv6 ranges are reserved for private networks, why they are not publicly routable, and how to check an address locally.

Published: Sep 16, 20253 min read

Quick answer: Private IP addresses are reserved for internal networks. They are not routed across the public internet, so homes, offices, and cloud networks can reuse the same address space independently.

The three IPv4 ranges come from RFC 1918. IPv6 has a comparable internal-use range called Unique Local Addresses (ULA), defined by RFC 4193.

The private ranges at a glance

10.0.0.0/8

The largest private IPv4 block. It is common in large organisations, campus networks, and multi-site environments where many subnets are needed.

RFC 191810.0.0.0/8IPV4Private
Range Start
10.0.0.0
Range End
10.255.255.255
Address Count
16,777,216
Prefix
/8

Open RFC reference

172.16.0.0/12

This range covers 172.16.0.0 through 172.31.255.255. It is often used for VPN pools and cloud VPCs because it provides a useful middle ground between address capacity and avoiding common home-network defaults.

RFC 1918172.16.0.0/12IPV4Private
Range Start
172.16.0.0
Range End
172.31.255.255
Address Count
1,048,576
Prefix
/12

Open RFC reference

192.168.0.0/16

The familiar choice for home routers and small office networks. A router will often assign addresses from 192.168.0.0/24 or 192.168.1.0/24 to devices on the local network.

RFC 1918192.168.0.0/16IPV4Private
Range Start
192.168.0.0
Range End
192.168.255.255
Address Count
65,536
Prefix
/16

Open RFC reference

fc00::/7

IPv6 Unique Local Addresses cover fc00::/7; in practice, locally assigned addresses normally begin with fd. Like private IPv4 ranges, they are intended for internal use and are not globally routed.

RFC 4193fc00::/7IPV6Private
Range Start
fc00::
Range End
fdff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
Address Count
2,658,455,991,569,831,745,807,614,120,560,689,152
Prefix
/7

Open RFC reference

Why private addresses are useful

  • They can be reused: Your 192.168.1.10 can exist in millions of unrelated networks without conflict.
  • They reduce public IPv4 demand: NAT lets many internal devices share a smaller number of public addresses.
  • They help separate internal services: Private addressing is useful for printers, databases, internal dashboards, and service-to-service traffic.

Private does not mean secure by itself. A private address should still be protected with sensible access controls, network segmentation, and authentication. Learn more about NAT and the difference between an intranet and the internet.

Check an IP address

Private IP checker

Use this free online private IP checker to identify whether an IPv4 or IPv6 address belongs to an RFC 1918 private range or an IPv6 Unique Local Address range. Paste an address into the field, select Check address, and read the result to see whether it is private, public, or special-use, plus the matching CIDR range when applicable. The check runs locally in your browser, so the address is not sent to IPlyte.

Try an example:

Private IP FAQ

Can a private IP address access the internet?
Yes. A router or gateway usually uses NAT to translate the private source address to a public address for outbound traffic. Direct inbound access normally needs an explicit setup such as port forwarding, a VPN, or a reverse proxy.
Is 172.32.0.1 a private IP address?
No. Only 172.16.0.0 through 172.31.255.255 are private. The broader 172.0.0.0/8 block is not entirely private.
Does a private IP address hide my identity?
Not by itself. It prevents the address from being globally routed, but services, routers, and network administrators can still log and identify activity within their own networks.