IP Address Type & Privacy Checker

Classify any IPv4/IPv6 address as public/private/loopback/reserved/documentation

Classify any IPv4 or IPv6 address against the IANA special-use registries — RFC 1918 private, RFC 4193 ULA, loopback, link-local, multicast, and documentation ranges. See whether it is globally routable and what it reveals if it leaks. Runs entirely in your browser. It runs free in your browser on Gera Tools, with nothing uploaded.

Last updated Source: Gera Tools

How do I know if an IP is public or private?

Private IPv4 ranges are 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16 (RFC 1918); private IPv6 is fc00::/7 (RFC 4193). Anything outside the reserved ranges is a public, globally routable address. This tool checks all the reserved ranges and tells you which bucket the address falls into.

Every IP address belongs to a special-use category defined by IANA: some are globally routable and can be geolocated, while others are private, loopback, link-local, or reserved and never appear on the public internet. This tool classifies any IPv4 or IPv6 address and explains what it reveals — useful when auditing logs, configuration files, screenshots, or any text that might contain IP addresses you didn’t intend to share.

How it works

The checker inspects the leading bits of the address against the IANA special-use registries:

IPv4 classifications:

RangeClassificationWhat it means
10.0.0.0/8Private (RFC 1918)Internal network, not routable
172.16.0.0/12Private (RFC 1918)Internal network
192.168.0.0/16Private (RFC 1918)Home/office LAN
127.0.0.0/8LoopbackSame machine only
169.254.0.0/16Link-local (APIPA)Auto-assigned when no DHCP; signals a config problem
100.64.0.0/10Carrier-grade NATISP-level private space (RFC 6598)
192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24Documentation (RFC 5737)Examples only; should never appear in live traffic
224.0.0.0/4MulticastRouting protocols and streaming
240.0.0.0/4ReservedNot usable on public internet
Everything elsePublic (globally routable)Unique, can be geolocated

IPv6 classifications:

RangeClassification
::1/128Loopback
fc00::/7Unique-local (RFC 4193) — equivalent to RFC 1918 private
fe80::/10Link-local — scope is a single network segment
ff00::/8Multicast
2001:db8::/32Documentation (RFC 3849) — examples only
2000::/3Global unicast (publicly routable)

Privacy implications by category

Public / globally routable — The address is unique on the internet. Any organization operating the IP range can be identified via WHOIS, and an approximate geolocation (city or region level) is possible via GeoIP databases. Exposing a public IP in a screenshot, URL, config file, or public log reveals your ISP and rough location. If you see an unexpected public IP in a config, it may be a hardcoded production endpoint or a misconfiguration.

Private (RFC 1918) — The same ranges (10.x, 172.16–31.x, 192.168.x) are reused on millions of separate networks behind NAT. A private address is not unique on the internet and cannot be geolocated or contacted from outside your network. Leaking a private address reveals internal topology but not your location.

Link-local / APIPA (169.254.x.x or fe80::/10) — These addresses are auto-assigned when a host cannot reach a DHCP server. Seeing one in a running system almost always indicates a DHCP failure or misconfigured interface.

Documentation ranges — If you see 192.0.2.x, 198.51.100.x, 203.0.113.x (IPv4) or 2001:db8:: (IPv6) in live traffic, something is wrong. These are reserved for documentation examples and examples only and should never appear in production.

What the checker doesn’t do

This tool classifies addresses by the IANA range tables built into the JavaScript — it does not look up the address online. It can tell you whether an address is globally routable, but it cannot tell you which organization owns it, what hostname it resolves to, or what its current geolocation is. For those, use a WHOIS lookup or GeoIP tool after confirming the address is safe to query.