How to Check If You Have IPv6? IPv6 Online Test Methods and Guide

After getting a new router at home, or when your ISP claims to support IPv6, many people's first instinct is to look for an IPv6 address in their computer's network settings. Seeing a string of characters with colons often leads to the assumption that IPv6 is working. However, having an IPv6 address in the network is just the first step. Some devices automatically generate link-local addresses starting with fe80:: even without public IPv6; others may successfully obtain a public IPv6 address, but due to routing, DNS, or ISP egress issues, accessing IPv6 websites may still fail.

So, to confirm whether you actually have IPv6, you can't just look at whether an address exists; you also need to verify that the IPv6 network can actually access the internet. The simplest approach is: First check the address, then run an online test, and finally verify with Ping or DNS.

1. How to Determine If You Have IPv6?

First, clarify which type of IPv6 address you see on your device.

If the network information only shows an IPv4 address like:

192.168.1.100

And there's no IPv6 at all, it generally means your device hasn't obtained IPv6 configuration. The cause could be in the router, modem, ISP line, or your local network settings.

If you see:

fe80::2c31:8aff:fe7b:1234

That's a different situation.

fe80::/10 is the IPv6 link-local address range, mainly used for communication between devices on the same network link. Windows, macOS, and other systems typically auto-generate such addresses, so having only fe80:: does not mean you have public IPv6 access.

What really matters is whether your device has obtained a globally routable IPv6 address and can access external IPv6 networks through that path.

For example, if your network information shows other IPv6 addresses besides fe80::, and online tools confirm that external IPv6 connectivity is normal, you can basically conclude that your broadband has usable IPv6.

In short, to truly determine if IPv6 is working, two conditions must be met:

Your device has a public IPv6 address, and IPv6 internet access works.

2. Use Chahu for IPv6 Online Test

If you don't want to dig into system commands first, you can directly test with Chahu's IPv6 detection feature. Enter the domain or IPv6 address you want to test, and it will check IPv6 accessibility from different network nodes.

When testing, don't just look at "success" or "failure"; pay attention to the following results:

• Whether IPv6 resolves correctly;

• Whether a network connection can be established;

• Whether the overall response time is normal;

• Whether there are significant differences between nodes in different regions;

• Whether only a specific ISP shows timeouts.

For example, if a website has just configured IPv6 and tests show that China Telecom, China Unicom, and overseas nodes are mostly fine, but some China Mobile nodes consistently time out, it's less likely a server-wide failure and more worth checking the IPv6 routing or upstream network quality for China Mobile.

If multiple regions and ISPs cannot connect simultaneously, you should prioritize checking domain AAAA resolution, server IPv6 address, firewall, and web server configuration.

For regular users, if you just want to know if your home network has IPv6, you can check your local address first; if you also want to assess IPv6 connection stability or test the IPv6 status of a specific website or server, using Chahu's online test is more intuitive.

3. How to Check IPv6 Addresses on Windows, macOS, and Mobile

Online tests can determine the actual network status, but if you want to know what IPv6 address your device has obtained, you can also check directly in the system.

Check IPv6 on Windows

The most direct method on Windows is to use ipconfig.

Press: Win + R

Type: cmd

Open Command Prompt, then run:

ipconfig

Find the Wi-Fi or Ethernet adapter you're using; you might see something like:

IPv6 Address . . . . . . . . . . : 240e:xxxx:xxxx:xxxx::1234
Temporary IPv6 Address . . . . . . : 240e:xxxx:xxxx:xxxx::5678
Link-local IPv6 Address . . . . . . : fe80::xxxx:xxxx:xxxx
IPv4 Address . . . . . . . . . . . : 192.168.1.100

If you see other IPv6 addresses besides fe80::, you can proceed with public connectivity tests.

Check IPv6 on macOS

On macOS, you can go to:

System Settings → Network → Wi-Fi / Ethernet → Details → TCP/IP

to view the IPv4 and IPv6 information for your current connection.

Alternatively, open Terminal and run:

ifconfig

Find the network interface you're using and look for the corresponding inet6 address.

Check IPv6 on Mobile

On Android, menus vary by brand, but generally you can go to:

Settings → Wi-Fi → Current Network → Network Details

to view IP address information.

On iPhone, go to:

Settings → Wi-Fi → Tap the "i" icon next to the current network

to see the IPv6 address assigned to your current network.

Whether on a computer or phone, don't overthink the meaning of each address. For practical judgment, remember one principle:

If you only have fe80::, it doesn't mean public IPv6 is available.

4. After Having an IPv6 Address, How to Confirm It Actually Works?

Once your device has an IPv6 address, you can run two simple tests to verify further.

1. Use Ping Test for IPv6 Connectivity

On Windows, you can run:

ping -6 example.com

If the target domain supports IPv6, the system will attempt to ping via IPv6.

Under normal circumstances, you might see:

Reply from 2606:xxxx::xxxx
time=25ms

This at least indicates that there is a reachable path from your network to the target IPv6 address.

Besides whether there's a response, you can also check latency and packet loss. If IPv4 is only 20-30 ms while IPv6 consistently exceeds 100 ms, it's worth investigating the IPv6 route.

However, a ping timeout alone doesn't prove a website is inaccessible. Some servers restrict ICMPv6 requests, but HTTP or HTTPS may still work, so it's best to combine with actual web access.

2. Query the Domain's AAAA Record

When a website provides services over IPv6, the DNS typically includes AAAA records.

On Windows, you can run:

nslookup -type=AAAA example.com

If IPv6 resolution exists, you'll typically see something like:

AAAA address:
2606:xxxx:xxxx::1

This indicates the domain points to an IPv6 address.

But there's an easily overlooked issue: Having an AAAA record doesn't guarantee the website is accessible over IPv6.

DNS just tells users which IPv6 address to go to. If the server isn't listening on IPv6, port 443 isn't open, or the firewall blocks IPv6 requests, the website will still be inaccessible.

So for actual verification, it's best to check all three:

Correct AAAA resolution + IPv6 network reachability + Website loads properly.

5. If IPv6 Detection Fails, What's Usually Wrong?

If test results are abnormal, you don't need to change many network settings at once. First, determine which layer the problem is likely in based on the symptoms; troubleshooting will be faster.

Among these, "IPv4 works but IPv6 doesn't" is not uncommon.

Even though you're accessing the same website, IPv4 and IPv6 may take different network paths. IPv4 might go directly through your local ISP's backbone to the server, while IPv6 might traverse different upstream networks or even detour.

So you might see:

In such cases, you shouldn't simply conclude that "IPv6 is slower than IPv4"; you should continue to check the IPv6 route.

If only your network is abnormal, check the router and ISP line first; if a specific ISP is generally abnormal, you can use multi-node tests or Traceroute to see where the problem starts.

If all IPv6 nodes fail to access the website, focus on checking the server's IPv6 address, AAAA resolution, security groups, firewall, and whether web services like Nginx or Apache are correctly listening on IPv6.

6. How to Quickly Determine If IPv6 Is Working?

If you just want to confirm whether your network has truly usable IPv6, you don't need overly complex tests. First, check if your device has a public IPv6 address, then use online tools like Chahu to verify IPv6 connectivity or whether the target website can be reached. For further confirmation, use Ping and AAAA queries to check network and DNS. The whole process can be summarized as: Check IPv6 address → Online test → Ping / AAAA verification

If all these are normal, you can basically confirm IPv6 is working. For website owners and operations staff, there's one more step: Check whether different regions and ISPs can access it normally. Because your own computer loading the site only means your current network path is fine. After actually deploying IPv6, it's more important to ensure that users in different network environments don't experience access issues due to DNS, routing, or ISP interconnection problems.

Whether IPv6 is truly usable ultimately depends on actual connection results, not just whether a string of IPv6 addresses appears on your device.

FAQ

1. I see an address starting with fe80 in my network settings. Does that mean I have IPv6?

No. fe80::/10 is a link-local address, equivalent to an "internal communication pass" auto-generated by Windows and macOS, only usable within the same LAN. To determine if you have public IPv6, check if there's another IPv6 address not starting with fe80, such as 240e or 2001, which are globally routable unicast addresses.

2. Why does an online test show IPv6 unavailable, but I see an IPv6 address locally?

This is common. Obtaining a public IPv6 address only means the assignment step succeeded, but routing, ISP egress, DNS resolution, or firewall rules may still have issues. Think of it like this: you have the building access card (address), but the unit door system hasn't granted your permissions (routing not working), so you can't get in. Using multi-node tools like Chahu can help you pinpoint whether the problem is on your network or the target server.

3. How can I check if my phone is connected to IPv6?

On Android, go to "Settings → Wi-Fi → tap the current network details," though some brands may hide it under "Advanced settings." On iPhone, it's simpler: Settings → Wi-Fi → tap the blue "i" icon next to the network, and scroll down to see IPv6 address info. As with computers, if you only see an address starting with fe80, you haven't obtained public IPv6.

4. The AAAA record shows an IPv6 address, but the website won't load. What's wrong?

DNS resolution just "tells the browser which address to go to," like having the address but finding the door locked. Common causes include: the server's 80/443 ports not listening on IPv6, firewall rules not allowing IPv6 traffic, or Nginx/Apache config missing the listen [::] directive. First, check if the server can curl its own IPv6 address, then troubleshoot security groups and web service config layer by layer.