IPv6 Test — Check IPv6 Connectivity & Address

Before you tweak router settings or publish DNS records, you need to know what your connection actually does today — not what your ISP brochure promised. This page runs a quick ipv6 test in your browser: public IPv4 on one side, IPv6 on the other, plus a plain-English label for Dual-Stack or IPv4-only.

That is the whole job. No command line, no account. If you searched test ipv6 or what is my ipv6, the answer appears in the panels above once loading finishes on Rankify.

IPv6 is the modern Internet Protocol. Addresses are 128 bits long, written as eight groups of hexadecimal separated by colons — for example 2001:db8::1. Shorthand :: collapses long runs of zeros so you are not typing forty characters by hand.

IPv4 ran out of fresh addresses at the registry level years ago. Carriers still make v4 work with NAT and carrier-grade NAT, but IPv6 is how mobile networks and cloud hosts assign unique addresses at scale without sharing one public IP among thousands of homes.

IPv4 is the protocol most of the internet grew up on — four numbers from 0 to 255, like 192.0.2.1. Only about 4.3 billion combinations exist, and they are long spoken for.

Your home router almost certainly uses private RFC1918 space (192.168.x.x or 10.x.x.x) and translates everything through one public IPv4. That NAT model is familiar and still works; it is also why port forwarding and “what is my IP” questions never go away.

When the page loads, the tool performs these checks automatically:

Readiness score

Weighted score out of 10 from IPv4/v6 address detection, IPv4-only host reachability, IPv6-only host reachability, dual-stack fetch, and large-packet v6 probe.

Browser connection test

Probes run from your browser over the network path you use now — Wi‑Fi, Ethernet, or mobile data.

IPv4 detection

Public IPv4 from our API plus client-side confirmation, with ISP and ASN when available.

IPv6 detection

Global IPv6 when your path supports it — scope, compressed form, and /64 prefix shown.

Connectivity probes

Separate pass/fail checks for IPv4-only, IPv6-only, dual-stack, and large IPv6 requests — the same ideas top IPv6 checkers use.

DNS A / AAAA samples

Server-side lookup showing whether major domains publish both record types — use DNS Lookup for your own domain.

IPv6 Detected with a global address means your ISP (or tunnel) delegated v6 and your device accepted it. You are ready for dual-stack browsing and hosting experiments.

IPv6 Not Detected with working IPv4 is common on older routers or IPv4-only plans. The internet still works — you are missing future-proofing and possible performance wins on v6-native paths.

Partial IPv6 Support sometimes appears when link-local fe80:: exists but no global prefix arrived. That is not enough for public internet reachability — check router DHCPv6-PD and ISP settings.

Dual-Stack Networks show both IPv4 and IPv6 badges. That is the recommended state for homes and offices during the transition.

Native IPv6 comes straight from your provider. IPv6 through a tunnel wraps v6 inside v4 when the ISP lacks native support — fine for homelab experiments, less ideal for production latency.

Both carry the same websites when a network is set up well. The table below spells out how they differ — one row at a time, v4 on the left column, v6 on the right.

Same internet, different plumbing:

• Larger address space — every device can have a global address without NAT gymnastics.
• Better routing efficiency — designed for hierarchical aggregation at ISP scale.
• End-to-end connectivity — remote access and P2P apps face fewer NAT traversal hacks.
• Reduced NAT dependency — carrier-grade NAT becomes less necessary as v6 grows.
• Improved network scalability — cloud VPCs, IoT fleets, and mobile cores rely on v6.
• Future-proof internet access — regulators and hosting panels increasingly expect AAAA records.

When the test shows IPv4 only or flaky v6, start here:

Only enable v6 after your ISP confirms support. Then configure edge and devices:

Turn v6 off only if you confirmed broken v6 is causing timeouts — not as a default:

IPv6 privacy extensions rotate interface identifiers so devices do not expose a permanent hardware-derived address on every network. That helps on coffee-shop Wi‑Fi; it does not replace a VPN when you need location privacy.

Firewalls still matter. A global v6 address means reachable in theory — default deny inbound on home routers remains best practice. Corporate networks often segment v6 like v4 with explicit allow rules.

Security teams should log both v4 and v6 in SIEM rules. Attackers use whichever path is open. Pair this test with Port Checker on services you expose.

• Dual-stack office Wi‑Fi avoids blind spots where only v4 is monitored.
• Hosting panels and load balancers increasingly offer v6 listeners — test before cutover.
• Publish AAAA alongside A; verify worldwide with DNS Propagation Checker on this site.
• Procurement questionnaires now ask about v6 readiness — screenshot this test for internal docs.

Public measurement sites show v6 traffic share climbing past 40% in several countries. Mobile carriers led because assigning a v6 prefix per phone scales better than sharing scarce v4.

Home broadband varies — fiber and business lines often get v6 first; older DSL plans may lag. If your phone shows Supported here on LTE but Wi‑Fi does not, the router is the usual suspect.

Websites without AAAA still reach most visitors over v4 today. Dual-stack now saves emergency work when a partner or regulator asks for v6 proof later.

Symptom → likely fix:

This ipv6 connectivity test reflects the browser session’s current network path — not every app on the device. A game or mail client may use different routes.

Detection uses IPv6-reachable endpoints from your browser’s current path. Corporate proxies, captive portals, and VPNs can produce IPv4-only results even when the underlying ISP supports v6.

Link-local fe80:: addresses are ignored for pass/fail — only global routable v6 counts as supported.

Use results for planning and troubleshooting, not contractual SLA proof. For domain readiness, combine with DNS Lookup (AAAA), Traceroute, and hosting panel checks.

• Best practice: test on a clean network before enabling AAAA on production DNS.
• Interpretation: Dual-Stack is ideal; IPv4-only is fixable if ISP supports v6 upstream.
• Follow-up: IP WHOIS and ASN Lookup help identify ISP networks when opening support tickets.

• Run the test after router firmware updates and ISP plan changes.
• Compare Wi‑Fi, Ethernet, and mobile data before blaming one device.
• Publish AAAA records only after global v6 succeeds here and on your server.
• Monitor both protocols in logs — security events may arrive on either.
• Keep IPv4 DNS during transition — dual-stack means both A and AAAA.

• Google — IPv6 adoption statistics
• RIPE — IPv6 FAQ
• APNIC — IPv6 program

Browser-based ipv6 checker results depend on ISP routing, VPN software, and router settings. Outcomes may differ from command-line tools (ping -6, traceroute6) run on the same machine.

Rankify provides this test for education and network planning — not as certification that your organization meets regulatory IPv6 mandates.