Private vs Public IP Checker
Enter any IPv4 address to find out if it belongs to a private range, a public range, or a special-purpose block. The checker validates the IP format and classifies the address according to IANA standards.
Reviewed by the ToolNestr Editorial Team — July 2026
Check an IP address
Private vs public IP classification
The IPv4 address space is divided into public and private ranges by the Internet Assigned Numbers Authority (IANA). Private IP addresses are defined in RFC 1918 and are reserved for use within private networks. These addresses are not globally unique — the same private IP can be used by millions of networks around the world. Public IP addresses are globally unique and are assigned to organizations and individuals by Regional Internet Registries (RIRs) through ISPs.
The classification is determined entirely by the address range, specifically the first octet (for 10.x.x.x and 192.168.x.x) or the first two octets (for 172.16.x.x through 172.31.x.x). The checker also identifies special-purpose addresses such as loopback (127.0.0.0/8, RFC 1122), link-local (169.254.0.0/16, RFC 3927), carrier-grade NAT (100.64.0.0/10, RFC 6598), and multicast (224.0.0.0/4, RFC 5771). Each of these ranges has different routing properties and use cases.
Understanding the difference between private and public IPs is fundamental to network design. Private IPs enable the reuse of address space across different organizations, which has been critical in slowing IPv4 exhaustion. NAT gateways at the network boundary translate private IPs to public IPs for internet access, allowing thousands of devices to share a single public IP address through port multiplexing. Without private IP addressing and NAT, the IPv4 address space would have been exhausted years earlier than it was.
RFC 1918 private address blocks
RFC 1918 defines three blocks of IPv4 address space reserved for private internets. The largest is 10.0.0.0/8, which provides over 16 million addresses and is typically used by large corporations, government agencies, and cloud providers for their internal networks. Amazon Web Services (AWS), Microsoft Azure, and Google Cloud all use 10.0.0.0/8 as the default range for their Virtual Private Cloud (VPC) networks, allowing customers to create subnets of any size within this massive block.
The 172.16.0.0/12 block (172.16.0.0 to 172.31.255.255) provides approximately 1 million addresses. This range is particularly common in medium-sized organizations and educational institutions. Note that only 172.16.0.0 through 172.31.255.255 are private — addresses like 172.32.0.0 and above are public. This truncated range often causes confusion, as people mistakenly assume all 172.x.x.x addresses are private.
The 192.168.0.0/16 block (192.168.0.0 to 192.168.255.255) is the most widely recognized private range, used in virtually every consumer router. Most home networks use 192.168.0.0/24 or 192.168.1.0/24, providing 254 usable addresses for household devices. This range is also commonly used in small office networks, IoT deployments, and test labs due to its simplicity and universal support across networking equipment.
Special-purpose address ranges
Loopback — 127.0.0.0/8 (RFC 1122)
The loopback address range is reserved for local testing and inter-process communication on a host machine. The most commonly used address is 127.0.0.1 (localhost). Packets addressed to 127.x.x.x never leave the host.
Link-Local — 169.254.0.0/16 (RFC 3927)
Link-local addresses are automatically assigned when a device fails to obtain an IP from DHCP. This Auto-Configuration (APIPA) mechanism ensures that devices on the same subnet can still communicate even without a DHCP server. These addresses are not routable.
Carrier-Grade NAT — 100.64.0.0/10 (RFC 6598)
This shared address space is used by ISPs for CGNAT deployments. It allows ISPs to multiplex thousands of customers behind a single public IP, conserving IPv4 addresses. Addresses in this range are not private but are also not globally routable.
Multicast — 224.0.0.0/4 (RFC 5771)
Multicast addresses are used for one-to-many communication. Common multicast addresses include 224.0.0.1 (all hosts on a subnet), 224.0.0.2 (all routers), and 224.0.0.5/6 (OSPF). Multicast routing requires IGMP and PIM protocols.
Reserved — 240.0.0.0/4 (RFC 1112)
The Class E range (240.0.0.0 to 255.255.255.255) is reserved for future use. 255.255.255.255 is the limited broadcast address used for DHCP discovery and other local broadcast traffic.
Why IP classification matters
Knowing whether an IP is private or public is critical for network troubleshooting, security configuration, and compliance audits. When a device cannot reach the internet, the first check is whether it has a valid public IP or is correctly configured for NAT. Private IPs in public-facing configurations create security risks and routing problems, while accidental public IP assignment to internal devices wastes scarce public address space.
Firewall rules and access control lists frequently use IP classification to determine policy. Traffic from private IPs destined for the internet is typically allowed through NAT, while traffic from public IPs destined for internal private IPs is blocked at the perimeter unless it matches an allowlisted exception. Understanding these boundaries helps network engineers design secure, correctly routed network topologies that comply with organizational security policies and regulatory requirements.
Limitations
This tool classifies IPv4 addresses only. IPv6 has its own private addressing concept (Unique Local Addresses, or ULAs, defined in RFC 4193, using the fd00::/8 prefix). The checker identifies standard RFC 1918 private ranges, RFC 6598 CGNAT, RFC 3927 link-local, and several other special-purpose blocks recognized by IANA. It does not validate whether an IP is actually assigned or in use — it only checks the address range against published standards. For real-time availability checks, use a ping or WHOIS lookup tool.
Frequently asked questions
What is a private IP address?
A private IP address is an address that is not routable on the public internet. Defined in RFC 1918, private ranges include 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16. These addresses are used within local networks and must be translated to a public IP via NAT to access the internet.
What is a public IP address?
A public IP address is globally unique and routable on the internet. These addresses are assigned by IANA to Regional Internet Registries (RIRs), then to ISPs, and finally to end users. Any device with a public IP can be reached from anywhere on the internet.
What is the 10.0.0.0/8 range?
The 10.0.0.0/8 range spans from 10.0.0.0 to 10.255.255.255, providing 16,777,216 addresses. It is the largest private address block defined in RFC 1918 and is commonly used by large organizations and cloud providers for internal networking.
What are the 172.16.0.0/12 private addresses?
The 172.16.0.0/12 range spans from 172.16.0.0 to 172.31.255.255, providing 1,048,576 addresses. Despite being in the 172.x.x.x range, only 172.16.0.0 to 172.31.255.255 are private — addresses like 172.32.0.0 are public. This truncated range is a common point of confusion.
What is 192.168.0.0/16?
The 192.168.0.0/16 range spans from 192.168.0.0 to 192.168.255.255, providing 65,536 addresses. This is the most common private address range used in home routers, small offices, and consumer devices. Most home networks use a subset like 192.168.1.0/24 or 192.168.0.0/24.
What is link-local addressing?
The 169.254.0.0/16 range is reserved for link-local addressing (RFC 3927). These addresses are automatically assigned by devices when no DHCP server is available, using APIPA (Automatic Private IP Addressing). They are only valid on a single network segment and are not routable.
What is carrier-grade NAT (CGNAT)?
CGNAT uses the 100.64.0.0/10 range (RFC 6598) for sharing a single public IP among multiple customers. ISPs use CGNAT to conserve IPv4 addresses. Addresses in this range are not private but are also not globally routable — they are shared address space.
Can I use private IP addresses on the internet?
No — private IP addresses are filtered by ISPs and cannot route on the public internet. If a device with a private IP tries to access the internet, the router performs NAT (Network Address Translation) to replace the private source IP with the router public IP before forwarding the packet.