Group | Hex | Decimal |
---|---|---|
{{ i + 1 }} | {{ g }} | {{ parseInt(g,16) }} |
Internet Protocol version 6 (IPv6) replaces the limited 32-bit address space of IPv4 with 128 bits, preventing exhaustion while supporting hierarchical routing, multicast, and autoconfiguration. Each address is written as eight 16-bit hexadecimal groups separated by colons, balancing human readability with immense numerical scale that complicates everyday inspection and error avoidance.
This client-side tool accepts a single IPv6 string, verifies structural correctness under RFC 5952 guidelines, expands suppressed zeros, recompresses the longest contiguous zero block, detects standard prefix categories, separates network and interface identifiers, and renders a 128-bit binary view, all through an in-browser reactive engine that never stores or transmits data.
During outage triage you can paste an address captured from packet traces, instantly verify validity, copy the uniformly compressed value into automation playbooks, or document loopback and link-local scopes in tickets. Typos spread rapidly through configuration management systems; always validate every quartet before committing device or firewall changes to shared repositories.
IPv6 encodes host and network information in 128-bit unsigned integers expressed as hexadecimal quartets. Leading zeros within each quartet may be omitted, and a single contiguous run of zero quartets may be compressed to a double colon. These conventions drastically shorten everyday addresses but make textual variants non-unique, so reliable tooling must consistently expand, validate, recompress, and classify values to compare prefixes, generate reverse-DNS records, or derive interface identifiers reliably.
::
tokens.::
; pad the missing quartets with zero strings until eight groups exist.::
, and remove redundant leading zeros to create the compressed form.Type | Leading Pattern | Typical Scope |
---|---|---|
Loopback | ::1 | Local host only |
Unspecified | :: | Unknown source |
Link-local | fe80::/10 | Single segment |
Unique-local | fc00::/7 | Private network |
Multicast | ff00::/8 | Group addressing |
Documentation | 2001:db8::/32 | Examples only |
Global | All others | Public Internet |
The first quartet quickly signals routing behavior. For instance, multicast addresses beginning with ff
never identify single hosts, whereas link-local addresses cannot traverse routers.
Example (input 2001:db8::ff00:42:8329
):
%eth0
).::
tokens invalidate the address.The procedure conforms to RFC 4291 (IPv6 Addressing Architecture) and RFC 5952 (Preferred IPv6 Text Representation) and aligns with examples in IETF BCP 198.
Address strings are processed wholly within the browser; no personal data is transmitted, ensuring GDPR compliance.
Follow these steps to validate and normalize an IPv6 address.
An address is valid when it contains exactly eight hexadecimal quartets after expansion, uses at most one double-colon for compression, and includes only characters 0-9 and a-f.
No. All processing runs locally in your browser and nothing leaves your device.
The ::1
address routes traffic back to the originating host’s network stack, letting you test services without external connectivity.
The compressed form removes leading zeros and shortens the longest all-zero sequence to ::
, yielding the shortest canonical representation per RFC 5952.
No. Supply individual host addresses only; network prefixes such as 2001:db8::/32
will be rejected by the validator.
::
.