IP Address Validator

How to use

1. 1Pick Single address to validate one IPv4 or IPv6 value at a time, or Batch validate to paste a list (one address per line).
2. 2Type or paste the address into the input box. IPv4 uses four dotted octets (192.168.1.1), IPv6 uses colon-separated hex groups (2001:db8::1), and bracketed URL forms like [2001:db8::1] are unwrapped for you.
3. 3Read the verdict at the top of the result panel. A valid address is labelled with the detected version, the canonical form, every equivalent representation, and a per-octet or per-group breakdown.
4. 4Check the classification chips for every reserved-range label the address touches (private, loopback, link-local, multicast, documentation, IPv6 unique local, and so on) along with the matching RFC note.
5. 5If the address is invalid, read the reason line below the verdict to fix the input. In batch mode, the line-by-line table shows the status and reason for every entry and the Copy valid and Copy invalid buttons split the cleaned and rejected lists.

About this tool

IP Address Validator confirms whether an IPv4 or IPv6 address is well-formed and surfaces every piece of information a network engineer, security analyst, or developer typically needs about a single address: the version, the canonical form, every equivalent representation, and the reserved-range classifications that decide whether the address is routable on the public internet. IPv4 is parsed under the RFC 791 grammar (four dotted decimal octets in the 0-255 range, leading zeros rejected because some legacy parsers treat them as octal), with plain 32-bit integer inputs accepted as an alternate form and normalized back to the dotted view. IPv6 is parsed under RFC 4291 with RFC 5952 canonicalization: any combination of the eight 16-bit hex groups, at most one :: compression token, optional embedded IPv4 tail like ::ffff:192.168.1.1, an optional zone identifier separated by % (or URL-encoded %25), and bracketed URL syntax like [2001:db8::1] is unwrapped automatically. Successful results include the canonical compressed form, the fully expanded form, the 32-character hex form, the decimal integer for database storage, an IPv4-mapped IPv6 form for IPv4 inputs, and the ip6.arpa or in-addr.arpa reverse-DNS name for PTR record lookups. The classification panel labels the address with every reserved range it touches: private (RFC 1918 for IPv4, RFC 4193 unique local for IPv6), loopback (127.0.0.0/8 and ::1), link-local (169.254.0.0/16 and fe80::/10), carrier-grade NAT (100.64.0.0/10), multicast (224.0.0.0/4 and ff00::/8), broadcast (255.255.255.255), documentation (RFC 5737 TEST-NETs and RFC 3849 2001:db8::/32), benchmarking (198.18.0.0/15), reserved Class E (240.0.0.0/4), deprecated 6to4 relay anycast, the NAT64 well-known prefix, the IPv6 Teredo and discard ranges, IPv4-mapped IPv6, and the global unicast 2000::/3 block. A failure result names the offending segment, so a typo or a wrong-length octet is fixed without re-running. Batch validate mode takes a list of addresses (one per line) from logs, allowlists, or firewall configurations and shows pass and fail counts, a per-line status table with the reason on failure, and Copy buttons for the valid and invalid splits so the cleaned list pastes straight back into a config. Useful for vetting firewall rules, allow and deny lists, log lines, IOCs, security alerts, IPAM records, container network manifests, and any place where IP addresses arrive as text and need to be confirmed before they ship to production. All parsing runs locally in your browser. No address, no log line, and no allowlist is ever sent off your device.

Free to use. Works in your browser. No signup, no login.