Public / Private IP Checker
Check whether an IP is private, loopback or a reserved range.
Not every IPv4 address is reachable on the internet. Some ranges are reserved for special use — private networks, loopback, link-local, documentation — and are never routed on the public internet. This tool tells you which range an IP belongs to, whether it is internet-routable, and the RFC behind it.
Use it to tell whether an IP in your server logs is an internal address or an external visitor, or while reviewing firewall and proxy settings. If the IP is an external visitor, dig deeper with the IP Geolocation or IP ASN Lookup tools.
| Classification | Private IP (RFC 1918) |
|---|---|
| Internet routable | No (special/private range) |
| Matched range | 192.168.0.0/16 |
| Reference | RFC 1918 |
Key special ranges
- Private (RFC 1918): 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16 — internal only.
- Loopback: 127.0.0.0/8 — the host itself (localhost).
- Link-local: 169.254.0.0/16 — auto-assigned when DHCP fails (APIPA).
- CGNAT: 100.64.0.0/10 — carrier shared NAT range.
- Documentation: 192.0.2.0/24 and others — examples only, not routable.
Seeing 169.254.x.x?
If a device has this address, it failed to get an IP from DHCP — a common cause of "no internet" issues.
Full special-range reference (the 16 rules this tool checks)
The tool tests these ranges using longest-prefix match (narrowest range wins). If an address matches none of them, it is classified as public. The Matched range and Referencevalues appear verbatim on the result card.
| Range (CIDR) | Classification | Reference | Routable |
|---|---|---|---|
0.0.0.0/8 | This network (source only) | RFC 1122 | No |
10.0.0.0/8 | Private (class A) | RFC 1918 | No |
100.64.0.0/10 | CGNAT | RFC 6598 | No |
127.0.0.0/8 | Loopback | RFC 1122 | No |
169.254.0.0/16 | Link-local (APIPA) | RFC 3927 | No |
172.16.0.0/12 | Private (class B) | RFC 1918 | No |
192.0.0.0/24 | IETF protocol assignments | RFC 6890 | No |
192.0.2.0/24 | Documentation TEST-NET-1 | RFC 5737 | No |
192.88.99.0/24 | 6to4 relay anycast (deprecated) | RFC 7526 | No |
192.168.0.0/16 | Private (class C) | RFC 1918 | No |
198.18.0.0/15 | Network benchmark | RFC 2544 | No |
198.51.100.0/24 | Documentation TEST-NET-2 | RFC 5737 | No |
203.0.113.0/24 | Documentation TEST-NET-3 | RFC 5737 | No |
224.0.0.0/4 | Multicast | RFC 5771 | No |
240.0.0.0/4 | Reserved (future use) | RFC 1112 | No |
255.255.255.255/32 | Limited broadcast | RFC 919 | No |
Example: how 100.64.10.5 is classified
It looks like an ordinary private IP with no external ASN, but it is actually a carrier shared-NAT address. Here is how the tool decides:
- Input
100.64.10.5→ 32-bit integer1681915397. - AND with the
100.64.0.0/10mask (top 10 bits) → same base value. Match. - Classification = CGNAT, matched range =
100.64.0.0/10, reference =RFC 6598, internet routable = No. - The status shows as warn, alongside private/loopback/link-local — while multicast, reserved, and documentation show as danger.
Common pitfall
- Do not assume 10.x.x.x always means "our corporate LAN." The same private range is reused by countless orgs, VPNs, and container networks, so the IP alone never tells you which network it belongs to.
- It is easy to mistake
100.64.x.xfor RFC 1918 private space, but it is RFC 6598 CGNAT — an address the carrier hands to subscribers, not your own internal LAN. - An address not being in a special range does not mean it is reachable from outside. Being public is independent of firewall, NAT, and open-port status.
Frequently asked questions
Can a private IP be reached directly from the internet?
Is seeing a CGNAT range (100.64.x.x) a problem?
Does it classify IPv6?
Is only 172.16–172.31 private, while 172.32 is public?
Is the IP I enter sent to a server?
Related guides
- Public vs Private IP: The Difference and How to CheckWhat separates public and private IPs, how NAT and port forwarding relate, and how to check yours.