Theme

Popular tools

IPv6 Test

Runs by itself: IPv4 and IPv6 from your browser, by name and without DNS, and which one your browser picks.

Test addresses at Cloudflare, Google and ipify, and RIPE's registry, asked from your browser · nothing stored

Checking0 s so far

Checking your connection over IPv4 and IPv6…

Your browser

Round trip to Cloudflare
IPv4timing…
IPv6timing…
warm: median of 5 on a connection that's already open · latency, not speed
  • Results land as each request answers; a family that doesn't answer takes up to 15 s.
How each address family reached Cloudflare
  • IPv4 by name: A asking…, Checking
  • IPv4 without DNS: Checking
  • IPv6 by name: AAAA asking…, Checking
  • IPv6 without DNS: Checking
DNS
Your network
Cloudflare
A site with both
Your device
looking up…
looking up…
…
…
racing…dnsrobot.org
  • IPv4looking up…
  • IPv6looking up…
  • Results land as each request answers; a family that doesn't answer takes up to 15 s.
Problems firstChecking
  • IPv4 by nameRFC 1035Checking

    Asking ipv4.icanhazip.com…

    ipv4.icanhazip.com · A only

  • IPv6 by nameRFC 3596Checking

    Asking ipv6.icanhazip.com…

    ipv6.icanhazip.com · AAAA only

  • IPv4 without DNSRFC 6146Checking

    Asking 1.0.0.1…

    1.0.0.1 · no DNS

  • IPv6 without DNSRFC 8200Checking

    Asking 2606:4700:4700::1111…

    2606:4700:4700::1111 · no DNS

  • Browser's choiceRFC 8305Checking

    Racing IPv4 and IPv6 to dnsrobot.org…

    dnsrobot.org · A + AAAA

  • Full-size IPv6 packetsRFC 4890Checking

    Sending full-size IPv6 packets to api6.ipify.org…

    api6.ipify.org · AAAA only · MSS 1440

  • IPv6 as fast as IPv4RFC 8305 §5Checking

    Timing both families…

  • IPv6 address typeRFC 6724Checking

    Waiting for an IPv6 address…

What a browser can't test
  • Whether your DNS resolver reaches IPv6-only nameservers.
  • Large-packet problems between about 1,420 and 1,500 bytes on Cloudflare's paths.
  • Whether your IPv4 is shared (CGNAT), or travels inside IPv6 (DS-Lite, MAP-E): only who owns each address.
  • The prefix size your provider gives you (/48, /56, /64): the announced block isn't it.
  • Whether an address is temporary or stable-random, and your LAN or link-local addresses.
  • Whether the internet can reach your IPv6 (your router's firewall).

Cloudflare runs most test addresses (icanhazip.com, 1.0.0.1, 2606:4700:4700::1111, dnsrobot.org) and sees both your addresses; Google sees your IPv4 (8.8.8.8) and ipify your IPv6 (api6.ipify.org). When your IPv4 is registered with RIPE NCC (Europe, the Middle East, Central Asia), your browser also asks RIPE's registry (rdap.db.ripe.net) how its block is labelled. Our server names each network through Team Cymru (asked over Cloudflare's DNS) and looks up each address's reverse name: your provider's DNS servers see that lookup. A website check sends only the domain, read through Google Public DNS. Nothing is stored, and a shared link carries results, never addresses.

How do I check if I have IPv6?

Open this page: the IPv6 connectivity test runs by itself in a few seconds and says in one line whether you have IPv6, whether it works and whether your browser uses it.

Behind that line are six requests from your browser. Four go to Cloudflare addresses that answer over one family only: ipv4.icanhazip.com has only an A record, ipv6.icanhazip.com only an AAAA record, and 1.0.0.1 and 2606:4700:4700::1111 are typed as numbers, so they need no DNS. A fifth asks dnsrobot.org, which has both, to see which family your browser picks; with the sixth, your browser sends api6.ipify.org a 3 KB request and gets a 3 KB reply, both in full-size packets. If 1.0.0.1 is refused, a seventh asks Google's 8.8.8.8, to tell a blocked address from a network with no IPv4.

Read together, they tell the failures apart, which an IPv6 checker that gives a single answer can't. The by-name IPv6 request fails but the numeric one answers: IPv6 works and your DNS is the problem. Both stay silent, though each is asked twice within 15 seconds: packets leave, nothing comes back, broken IPv6. Both fail at once: no IPv6 on this device.

RequestDNS recordsFamilyAn answer provesChecks it feeds
dnsrobot.netThis pageA + AAAAIPv4IPv6the family this page already came over, and the Cloudflare data centreBrowser's choice
ipv4.icanhazip.comCloudflareA onlyIPv4IPv4 works by nameIPv4 by name · IPv6 as fast as IPv4
ipv6.icanhazip.comCloudflareAAAA onlyIPv6DNS gives out IPv6 addresses and IPv6 packets come backIPv6 by name · IPv6 as fast as IPv4 · IPv6 address type
1.0.0.1Cloudflare 1.1.1.1no DNSIPv4IPv4 routes without a translator (fails behind NAT64)IPv4 without DNS · IPv6 as fast as IPv4
2606:4700:4700::1111Cloudflare 1.1.1.1no DNSIPv6IPv6 routes, whatever DNS saysIPv6 without DNS · IPv6 as fast as IPv4
dnsrobot.orgCloudflareA + AAAAIPv4IPv6which family your browser picks when a site offers bothBrowser's choice
api6.ipify.orgipifyAAAA onlyIPv6full 1,500-byte IPv6 packets get through both ways: your browser's 3 KB request out, ipify's 3 KB reply and TLS handshake backFull-size IPv6 packets
The six requests the test makes, and this page's own connection: the DNS records each name has and what an answer proves. All of them answer any website (Access-Control-Allow-Origin: *); the Cloudflare ones reply with /cdn-cgi/trace, which names the family and the data centre. Records read on October 24, 2026.
IPv6 test result on a healthy dual-stack line: 8 of 8 checks passed, IPv4 and IPv6 reaching Cloudflare with and without DNSIPv6 test result on a healthy dual-stack line: 8 of 8 checks passed, IPv4 and IPv6 reaching Cloudflare with and without DNSThe verdictIn one line, with how many of the 8 checks passed: no invented score.Round tripsTo Cloudflare per family, the median of 5 on a connection that's already open. Latency, not speed.DNSThe A or AAAA answer each by-name request needed. A missing AAAA turns this gate red.Without DNSThe dotted lanes use addresses typed as numbers, so a DNS fault and a line fault break in different places.The browser's choiceFor a name with both records: which family won the race (RFC 8305).ChecksProblems first, each with its RFC and, when it fails, the fix.
A healthy dual-stack result. Select a number to see what each part shows.

Am I using IPv4 or IPv6?

When a site offers both, your browser tries IPv6 first and gives it a short head start: if IPv6 hasn't connected after about 0.3 s, IPv4 starts too, and the first to connect wins.

That race is Happy Eyeballs (RFC 8305). The standard waits up to 50 ms for the AAAA answer, recommends 250 ms between attempts and lets a browser use what it learned from earlier connections; Chrome waits 300 ms, Firefox 250 ms. So working IPv6 is used almost every time, broken IPv6 costs about 0.3 s on every new connection, and IPv6 slower than the head start loses to IPv4.

The test shows the outcome as Browser's choice: the family your browser picked for dnsrobot.org, a name with both records, beside the family this page itself came over.

Working IPv6IPv6 connects first; IPv4 never starts

IPv6connects at 29 ms, wins the raceIPv4

Broken IPv6IPv6 gets no answer; IPv4 starts at 300 ms

IPv6no answer · 10 sIPv4connects at 325 ms, wins the race

Slow IPv6 (a tunnel)IPv4 starts at 300 ms and connects first

IPv6431 msIPv4connects at 325 ms, wins the race
  • RFC 8305 §3: wait up to 50 ms for the AAAA answer
  • RFC 8305 §5 and Firefox: a 250 ms head start for IPv6
  • Chrome: a 300 ms head start for IPv6
Three races to a name with both A and AAAA records. The connect times, 29 ms over IPv6 and 25 ms over IPv4, were measured from one line on October 24, 2026; the broken and slow IPv6 attempts are drawn to the timers' rules.

Why is my IPv6 not working?

Most often the router hands out IPv6 that doesn't reach the internet, or something in between removes IPv6 answers from DNS; the four by-name and by-number requests show which.

Broken IPv6 is the one you feel: sites still open, but each new connection to a site with IPv6 waits first. A DNS that drops AAAA answers (a router's DNS proxy, a Pi-hole or NextDNS setting, a security app) makes IPv6 look absent while it works. A tunnel, such as a 6in4 tunnel broker or 6to4, works but is often slower than IPv4, so browsers skip it.

A failed request isn't always your line: a VPN replaces your connection with its own, and an extension can block a test address. The test says so instead of reporting no IPv6.

ProblemIPv4IPv6What you noticeFirst fix
by nameno DNSby nameno DNS
Broken IPv6Sites open, but each new one waits about 0.3 sRestart the router; if it stays, switch IPv6 off on the router and tell your provider
DNS gives no AAAAIPv6 works, yet no site uses itTurn off AAAA filtering, or use a public DNS such as 1.1.1.1
No IPv6Usually nothing: sites still answer over IPv4Turn IPv6 on in the router, or ask your provider
IPv6 only + NAT64Apps that use IPv4 numbers failNothing for websites; 464XLAT on the phone or router fixes apps
Slow IPv6Browsers pick IPv4A nearer tunnel server, or native IPv6 from your provider
Large packets droppedSome sites stall after connectingLet ICMPv6 type 2 (Packet Too Big) through the firewall
VPN or WARPThe test describes the VPNTurn the VPN off to test your own line
What each problem looks like in the four requests (by name and without DNS, per family), what you notice, and the first thing to try. From the test's own verdict rules.

IPoE or PPPoE: does my IPv4 travel inside IPv6?

On a Japanese fibre line (FLET'S), IPv6 almost always uses IPoE, while IPv4 either still logs in over PPPoE or travels inside IPv6 through an IPv4 over IPv6 service such as v6プラス (MAP-E) or transix (DS-Lite).

PPPoE takes IPv4 through the network's PPPoE gateways with an ID and password, a path more prone to congestion; IPv4 over IPv6 skips them. With MAP-E your router shares one IPv4 address with other lines, each line getting its own range of ports (RFC 7597); with DS-Lite your router tunnels IPv4 to the provider, which shares the address there (RFC 6333).

A website can't see the tunnel, only who owns each address. Both in blocks of the VNE that sells IPv4 over IPv6: your IPv4 travels inside IPv6. IPv4 from another network: probably PPPoE. Where one company runs both on the same network (OCN, BIGLOBE, ASAHIネット, ARTERIA Networks), the test says it can't tell, and your router's status page will.

PPPoEID and password, through the network's PPPoE gateway

NATYour routerNTT NGNFLET'SPPPoE gatewayISPInternet

MAP-EIPv4 over IPv6: your router shares one IPv4 address by port range

NATYour routerIPv4 inside IPv6NTT NGNFLET'SVNE border relayInternet

RFC 7597: “Port Set ID (PSID): Algorithmically identifies a set of ports exclusively assigned to a CE.”

DS-LiteIPv4 over IPv6: the provider shares one IPv4 address at its AFTR

Your routerIPv4 inside IPv6NTT NGNFLET'SNATVNE AFTRInternet

RFC 6333: “…by combining two well-known technologies: IP in IP (IPv4-in-IPv6) and Network Address Translation (NAT).”

ServiceMethodOperator (VNE)Origin ASFrom the addresses
v6プラスv6 PlusMAP-EJPIX (formerly JPNE)AS2516announced by KDDIcan tell
OCNバーチャルコネクトOCN Virtual ConnectMAP-ENTT DOCOMO BUSINESSAS4713can't tell
IPv6オプションIPv6 optionMAP-EBIGLOBEAS2518can't tell
transixDS-LiteInternet MultifeedAS55391AS55392can tell
XpassDS-LiteARTERIA NetworksAS2519AS17506can't tell
v6 コネクトv6 ConnectDS-LiteASAHI NetAS4685can't tell
IPv6高速ハイブリッドSoftBank Hikarinot publishedBBIX (SoftBank)AS17676can't tell
Three ways IPv4 reaches the internet on a FLET'S line, and the services that use each. Methods from the operators' and router makers' documents; address blocks and origin AS from the registries, RIPEstat and Team Cymru on October 24, 2026. Can't tell: the same network also carries PPPoE, or no block is known. JPIX's own AS55389 announces nothing.

What does my IPv6 address say about my device?

The first half of an IPv6 address names your network; the second half, the interface ID, names your device on it, and on older systems it is built from the device's MAC address.

Your provider announces a large block to the internet, your home gets a /64 (or several) inside it, and each device picks a 64-bit interface ID. An ID with ff:fe in the middle is EUI-64: the network card's MAC with two bytes inserted and one bit flipped, the same on every network. Current systems use random IDs instead: temporary ones replaced every day by default (RFC 8981), or a stable random one per network (RFC 7217).

The test's IPv6 address view says which kind yours is; an EUI-64 ID links to the MAC address lookup, which names the maker.

2001:db8:2c7:1f00

Network (/64) · 2001:db8::/32: the provider's announced block

200:5eff:fe00:532a

Interface ID (64 bits)

  1. MAC00:00:5e:00:53:2a
  2. split in half00:00:5e · 00:53:2a
  3. insert ff:fe00:00:5e:ff:fe:00:53:2a
  4. flip bit 7 (00 → 02)02:00:5e:ff:fe:00:53:2a
  5. interface ID0200:5eff:fe00:532a

00:00:5e:00:53:2a is in IANA's range for documentation (RFC 9542); a real one names the card's maker.

Temporary addresses (RFC 8981): the same /64, a new interface ID

  • Mon2001:db8:2c7:1f00:9d3e:61b2:c84f:1a07
  • Tue2001:db8:2c7:1f00:47a1:be2:f3c9:58d4
  • Wed2001:db8:2c7:1f00:e02c:7d95:1b6a:a3f0

RFC 8981 §3.8 defaults for each address · preferred for: 1 day · valid for: 2 days

An address taken apart, the MAC worked back out of an EUI-64 interface ID, and temporary addresses keeping the /64 while the ID changes. Documentation addresses (RFC 3849) and IANA's documentation MAC.

How do I check if a website supports IPv6?

Choose A website above and type the domain: the test reads whether the domain, its www name, its nameservers and its mail servers publish IPv6 addresses (AAAA records).

A site is reachable over IPv6 when its web name has an AAAA record; nameservers and mail servers matter for IPv6-only networks and for mail. Several big sites still publish only IPv4 for the website while their DNS already answers over IPv6, as the table of well-known domains shows.

An AAAA record says an address is published, not that the server answers on it; our server can't connect over IPv6 to check that.

DomainWebsitewwwNameserversMailResult
wikipedia.orgAAAAAAAA3/32/2IPv6-ready
google.comAAAAAAAA4/41/1IPv6-ready
microsoft.comAAAAAAAA4/41/1IPv6-ready
netflix.comAAAAAAAA4/45/5IPv6-ready
apple.comAAAAAAAA4/40/6website on IPv6
cloudflare.comAAAAAAAA5/50/4website on IPv6
reddit.comAAAAnone4/45/5website on IPv6
amazon.comnoneAAAA4/40/1website on IPv6
github.comnonenone8/81/1website IPv4 only
mercadolibre.com.mxnonenone4/45/5website IPv4 only
rakuten.co.jpnonenone4/40/1website IPv4 only
x.comnonenone0/85/5website IPv4 only
yahoo.co.jpnonenone0/40/4no IPv6
13 well-known domains, read from DNS on October 24, 2026 through 1.1.1.1 from one place (CDN answers vary by place). Nameservers and mail: how many of the hosts listed publish an AAAA record.

How many people have IPv6?

About six in ten users in Japan and the United States can use IPv6, seven in ten in Germany and almost nine in ten in France, but only about one in ten in Spain (APNIC Labs, 30-day average to October 21, 2026).

APNIC Labs measures it through online ads, some 25 million a day, that fetch test objects over IPv4 and IPv6. Capable means the device and network can use IPv6; preferred means it used IPv6 when given both. Google counts its own users: about 47% reached it over IPv6 in the week to October 21, 2026.

If your country is high and the test finds no IPv6, the gap is likely your provider's plan or your router; the IPv4-only result names your network.

  • France85.8%
  • India76.3%
  • Germany72.5%
  • Vietnam64.4%
  • United States62.5%
  • Japan62.1%
  • Brazil59.7%
  • Mexico58.2%
  • Portugal48.5%
  • Indonesia29.5%
  • South Korea29.3%
  • Türkiye21.8%
  • Poland19.7%
  • Spain10.9%
  • Russiasmall sample7.2%
  • World43.8%
Share of users able to use IPv6 (bar) and that used it when offered both (tick), 30-day average to October 21, 2026, with the same day every two years since 2016 (dots). Source: APNIC Labs, stats.labs.apnic.net/ipv6, re-use with attribution. Russia: about 2,500 measurements a day.

How do I test IPv6 from the command line?

Run curl -6 https://ipv6.icanhazip.com: it prints your IPv6 address when IPv6 works, hangs when it's broken, and fails at once when you have none.

curl -4 with ipv4.icanhazip.com does the same for IPv4; nslookup -type=AAAA or dig AAAA shows whether your DNS returns IPv6 addresses; ping -6 tests the path with ICMPv6, which some firewalls drop, so no reply there proves nothing on its own.

1C:\> curl.exe -6 https://ipv6.icanhazip.com
2001:db8:4a1c:7f00:9d3e:61b2:c84f:1a07

2C:\> curl.exe -4 https://ipv4.icanhazip.com
203.0.113.58

3C:\> nslookup -type=AAAA ipv6.icanhazip.com 1.1.1.1
Name:    ipv6.icanhazip.com
Address:  2606:4700:9a90:aa:b9de:0:6810:b8f1

4C:\> ping -6 2606:4700:4700::1111
Reply from 2606:4700:4700::1111: time=24ms
1% curl -6 https://ipv6.icanhazip.com
2001:db8:4a1c:7f00:9d3e:61b2:c84f:1a07

2% curl -4 https://ipv4.icanhazip.com
203.0.113.58

3% dig AAAA ipv6.icanhazip.com @1.1.1.1 +short
2606:4700:9a90:aa:b9de:0:6810:b8f1

4% ping6 -c 3 2606:4700:4700::1111
16 bytes from 2606:4700:4700::1111, icmp_seq=0 hlim=60 time=24.123 ms
1$ curl -6 https://ipv6.icanhazip.com
2001:db8:4a1c:7f00:9d3e:61b2:c84f:1a07

2$ curl -4 https://ipv4.icanhazip.com
203.0.113.58

3$ dig AAAA ipv6.icanhazip.com @1.1.1.1 +short
2606:4700:9a90:aa:b9de:0:6810:b8f1

4$ ping -6 -c 3 2606:4700:4700::1111
64 bytes from 2606:4700:4700::1111: icmp_seq=1 ttl=60 time=24.1 ms
  1. Your IPv6 address: IPv6 works by name. A hang means broken IPv6; an instant error, no IPv6.
  2. Your IPv4 address, for comparison.
  3. An AAAA answer: DNS gives out IPv6 addresses (asked here of 1.1.1.1).
  4. ICMPv6 to an address with no DNS: the path works. No reply can also be a firewall.
The test's four questions in a terminal. The AAAA answer is what 1.1.1.1 returned on October 24, 2026; your own addresses appear as documentation examples.

How do I turn on IPv6?

When the test finds no IPv6, the switch that matters is usually in your router, and sometimes your provider has to turn IPv6 on for your line.

On a router's admin page, look under Internet or WAN for IPv6 and choose Native, Auto or DHCPv6 with prefix delegation. In Japan, IPoE and IPv4 over IPv6 also need the service on your contract and a router that supports it. Don't switch IPv6 off on one device to fix a broken line: switch it off on the router, so every device falls back cleanly, and tell your provider.

  • Windows 11

    Control PanelNetwork and Sharing CenterChange adapter settingsyour adapter › Properties

    Internet Protocol Version 6 (TCP/IPv6)

  • macOS

    System SettingsNetworkyour network › DetailsTCP/IP

    Configure IPv6: Automatically

  • iPhone

    SettingsWi-Fiⓘ beside your network

    IPV6 ADDRESS lists your addresses

  • Android (mobile data)

    SettingsNetwork & internetSIMsAccess Point Namesyour APN

    APN protocol: IPv4/IPv6

  • FRITZ!Box

    InternetAccount InformationIPv6

    IPv6 support enabled

  • Most routers

    Internet or WANIPv6

    Native, Auto or DHCPv6-PD

Where each system shows or switches IPv6. Menu names vary by system version and language; a label we couldn't confirm in your language stays in English.

IPv6 test: questions people ask

Is it bad if I don't have IPv6?

Not today: nearly every website still answers over IPv4, so an IPv4-only line opens almost everything. You miss IPv6-only services and sometimes a shorter path, and where providers are short of IPv4 addresses you may share one with many customers (carrier-grade NAT), which can break port forwarding and hosting games. If your country's IPv6 share is high, ask your provider whether your plan includes it.

What does "IPv6 broken" mean?

Your device has an IPv6 route and sends packets, but no answer comes back, by name or by number, though each request is asked twice within 15 seconds. Sites still load, because browsers fall back to IPv4, but each new connection to a site with IPv6 waits first, about 0.3 seconds in Chrome. The cause is usually the router or the provider's IPv6: restart the router, and if it persists, switch IPv6 off on the router and report it.

Why does my browser use IPv4 when IPv6 works?

Happy Eyeballs (RFC 8305) gives IPv6 a head start, 250 ms in the standard and 300 ms in Chrome, and the first family to connect wins; browsers may also use what they learned from earlier connections. If IPv4 happened to connect first, the browser picks IPv4. That's allowed and harmless: the test warns only when each IPv6 round trip takes at least 100 ms longer than IPv4's, the smallest head start RFC 8305 allows.

Is IPv6 faster than IPv4?

Not by itself: both carry the same data, and the difference is the path. Native IPv6 usually takes the same route as IPv4 and times within a few milliseconds of it. On Japanese FLET'S lines, IPoE skips the PPPoE equipment that is more prone to congestion, so IPv6, and IPv4 over IPv6, are often faster at busy hours. Tunnels to a distant server are usually slower.

Does a VPN affect the IPv6 test?

Yes. With a VPN on, the test sees the VPN's addresses and network, not your provider's, and says so. A VPN that carries only IPv4 can leave IPv6 going out through your provider, an IPv6 leak, and one that blocks IPv6 makes your line look IPv4-only. Turn the VPN off, run the test again, and compare the two results.

What is NAT64, and how does IPv4 work on an IPv6-only network?

Some mobile and campus networks give devices only IPv6. Their DNS (DNS64) makes up an IPv6 address for IPv4-only names, under 64:ff9b::/96 or the network's own prefix (RFC 6052), and a translator (NAT64, RFC 6146) converts the traffic. Names work; IPv4 addresses typed as numbers fail unless the device translates them (464XLAT on Android, Apple's own synthesis). The test reads this when two IPv4 addresses are refused at once, which a filter on IPv4 addresses also does.

What does a 10/10 IPv6 score mean?

Some IPv6 test sites give a score out of 10 from their own rules. No standard defines such a score, and an IPv4-only line can score well on one scale and badly on another. This test counts checks instead: eight, each tied to the RFC behind it, and it shows which passed and why, so you can see what a score would hide.

Can websites track me through my IPv6 address?

Partly. Every site sees your address, and its first 64 bits identify your home network for as long as your provider keeps the prefix. Current systems replace the last 64 bits every day by default (temporary addresses, RFC 8981), but an EUI-64 address carries your network card's MAC address and stays the same on every network. The test warns when yours does.

How do I know if I'm using v6プラス (v6 Plus)?

Run the test: when both your addresses sit in JPIX's v6プラス blocks (JPIX was JPNE until 2023), it says your IPv4 travels inside IPv6 with MAP-E; when the IPv4 is on KDDI's network, which carries JPIX's traffic, it says probably. If your IPv4 comes from another network, it probably still uses PPPoE. Your router's status page names the mode, and JPIX's own check page does too.

Does this test store my IP address?

No. The test runs in your browser. Cloudflare runs most test addresses and sees your IPv4 and IPv6, Google (8.8.8.8) sees your IPv4 and ipify your IPv6; an IPv4 registered with RIPE NCC is also looked up in its registry. Our server asks Team Cymru (through Cloudflare's DNS) which network each address belongs to, and looks up each address's reverse name: your provider's DNS servers see that lookup. Nothing is saved, and a shared link never carries your addresses.

Missing something?Suggest a feature or a new tool

Related tools