Validate and inspect IPv4 and IPv6 addresses, with the special ranges named and the formatting rules that trip up string comparison explained.
Waiting for an address
One per line. IPv4 and IPv6 are both read.
Waiting for an address
One per line. IPv4 and IPv6 are both read.
IP Address Inspector runs entirely on your device — nothing is uploaded, and no host is contacted.
You’re on the Free plan. Compare plans
Address validation is where homegrown regexes go to die, and the failure is usually silent. `192.168.001.1` looks fine and is not a valid dotted-quad; worse, some C library functions read a leading zero as octal, so the same string can mean two different addresses in two parts of one system.
IPv6 has the opposite problem: one address has many spellings. `2001:db8::1`, `2001:0db8:0000:0000:0000:0000:0000:0001` and `2001:DB8::1` are the same address, and comparing them as strings says they are not. The canonical form — RFC 5952, lower case, longest zero run compressed, exactly one `::` — is what makes comparison work, and it is shown for every address.
Special ranges are named rather than merely flagged. Loopback, link-local, private, carrier-grade NAT, documentation, multicast and unique local each mean something different for whether an address should appear where you found it. An address from the documentation range in production configuration is a copied example nobody replaced.
IPv4-mapped IPv6 addresses — `::ffff:192.168.1.1` — are identified for what they are, because a dual-stack socket reports them and code that checks for a private range in IPv4 form will not see one.
Nothing is contacted. This reads the address as text, so it cannot tell you whether anything answers there.
A dotted-quad octet has no leading zeros. Beyond being invalid, it is ambiguous: some C library functions read a leading zero as octal, so `010` becomes 8 — meaning one string can resolve to two different addresses in one system.
Because one address has many spellings. Case, leading zeros and where `::` sits all vary. Compare the canonical RFC 5952 form, or compare the parsed bytes — never the strings as typed.
An IPv4-mapped IPv6 address, which is how a dual-stack socket reports an IPv4 client. Code that checks for private ranges in IPv4 form will not recognise it, which is a quiet way for an access check to fail open.
10.0.0.0/8, 172.16.0.0/12 and 192.168.0.0/16 for IPv4, and fc00::/7 for IPv6. 100.64.0.0/10 is carrier-grade NAT — not private, not reachable from the internet, and a frequent surprise.
No. Nothing is contacted. This validates and explains the format; reachability needs an actual network request.