Paste a list of addresses, one per line, and find out which are valid and why the others are not. IPv4, IPv6 and MAC are all recognised, and each line is classified by shape before being judged, so the explanation is about the format it was evidently meant to be. IPv6 compression is handled properly — one double colon at most, standing for at least one group of zeros, with an optional trailing IPv4 quad — and MAC addresses are accepted in colon, hyphen, Cisco dotted or unseparated form, with the first octet decoded to tell you whether the address is globally unique or something a hypervisor invented. One deliberate strictness: an IPv4 octet with a leading zero is refused rather than accepted, because it is genuinely ambiguous and reading it the wrong way is the basis of a known class of security bypass. Nothing is resolved or looked up; this is pure format checking in your browser.
| Kind | Example | Notes |
|---|---|---|
| IPv4 | 192.168.0.1 | Four octets, 0-255, no leading zeros |
| IPv6 full | 2001:0db8::8a2e:0370:7334 | Eight groups of up to four hex digits |
| IPv6 compressed | ::1 | One double colon only |
| IPv4-mapped | ::ffff:192.168.1.1 | Trailing quad is validated too |
| MAC colon | 00:1A:2B:3C:4D:5E | The usual form |
| MAC hyphen | 00-1A-2B-3C-4D-5E | Common on Windows |
| MAC Cisco | 001A.2B3C.4D5E | Three groups of four |
No. It only checks the format. Nothing is resolved, pinged or sent anywhere, so it works offline and reveals nothing about what you are checking.
Because a leading zero is ambiguous. Several C libraries read 010 as octal 8 rather than ten, and the gap between a validator that accepts it one way and a resolver that reads it the other is a known route to SSRF filter bypasses. Refusing it and saying so is safer than silently picking a reading.
By shape. Six pairs of hex digits separated by colons is a MAC; anything else containing a colon is treated as IPv6. They are the one genuinely ambiguous pair, since both use colons.
That bit one of the first octet is set, meaning the address was assigned by software rather than burned into hardware. Virtual machines, containers and randomised Wi-Fi privacy addresses all set it. A globally unique address comes from a manufacturer's allocated block.
All the standard ones: full, compressed with a double colon, IPv4-mapped such as ::ffff:192.168.1.1, and addresses with a zone index. A second double colon is rejected because it would be ambiguous about how many groups each stands for.
Each line is first classified by shape and only then judged, so the reason given is about the format the input was evidently meant to be rather than a generic rejection. That classification has one genuinely awkward case: MAC addresses and IPv6 addresses both use colons, so six pairs of hex digits separated by colons is treated as a MAC and anything else containing a colon as IPv6. IPv4 is validated strictly, and leading zeros are refused rather than accepted. That is deliberate and worth stating: several C libraries interpret a leading zero as octal, so 010 becomes 8, and the discrepancy between a validator that accepts it as ten and a resolver that reads it as eight is the basis of a well-known class of SSRF filter bypass. Refusing the ambiguous form and saying why is more useful than silently choosing one of the two readings. IPv6 validation implements the compression rules properly: at most one double colon, which must stand for at least one group of zeros; eight groups of up to four hex digits otherwise; an optional trailing IPv4 quad occupying the final two groups, itself validated; an optional zone index; and a single leading or trailing colon rejected since it is only legal as part of a double colon. MAC addresses are accepted in colon, hyphen, Cisco dotted and unseparated forms, but mixed separators are refused. For valid MACs the first octet is decoded — bit one marks a locally administered address and bit zero marks multicast — because those tell you whether an address is a real burned-in identifier or something a hypervisor or container runtime made up. Validation is entirely offline: nothing is resolved or looked up.