A computer can display an IPv6 address while an external IPv6 connection still fails. To find out whether your connection supports IPv6, examine the address and route on the device, test a known external destination, and then look at the particular website. Each result describes a different part of the path.
Do I Have IPv6 on This Device?
Do I have IPv6 if my network settings show an address? The device has an IPv6 address, but that alone does not establish internet reachability. An address beginning with fe80:: is link-local: it is used on the local link and is not routed across the public internet. Devices can have link-local addresses even when the network offers no external IPv6 service.
Look at the active Wi-Fi or Ethernet interface, not an inactive adapter or virtual connection. On Windows, ipconfig shows interface addresses and a default gateway. On macOS or Linux, the network settings or system networking commands can show addresses and routes. A globally scoped address and an IPv6 default route are stronger signs of a configured path, but they still need an external test.
A default route tells the device where to send traffic for destinations without a more specific route. The next-hop gateway may itself use a link-local address; that is normal. A device can also have a unique-local IPv6 address, typically beginning with fc or fd, which is not by itself evidence of public internet access.
How do I know if I have IPv6 configured beyond the local link? Check the address scope and the route together, then attempt to reach a known external IPv6 destination. A VPN or another active interface can alter which route is used.
Test the External Path
An IPv6 check should distinguish a configured address from a successful connection. Run an IPv6 website test from a reputable dual-stack testing service and read its individual results. A dual-stack network supports both IPv4 and IPv6; a browser may use either depending on reachability and its connection strategy.
If the test reports an IPv6 connection, it has observed a successful path from that browser to its test service at that time. It does not prove that every website supports IPv6 or that every application on the device follows the same path. If it reports only IPv4, check whether the device has a usable IPv6 address and default route, whether the router enables IPv6, and whether the provider supplies it.
Am I using IPv6 for this connection? A test service can report the address family it sees, but the result applies to that particular browser connection. A VPN, proxy, browser setting, or another network interface may change the path. Compare with the VPN disconnected only when you are authorized to do so, and restore it afterward.
Some networks intentionally do not provide external IPv6. If IPv4 works normally and IPv6 is unavailable, the network may still provide ordinary access to many services. Ask the network administrator or provider about intended support before changing settings.
Check the Website Separately
Checking a destination begins with its DNS records. An AAAA record maps a hostname to an IPv6 address; an A record maps it to an IPv4 address. A DNS lookup for the exact hostname can show whether an AAAA record is published. A site can work over IPv4 even if no AAAA record exists.
When you test an IPv6 website, use a tool or diagnostic that reports whether the connection actually used IPv6. A published AAAA record is not enough: the address must be reachable, the server must respond, and HTTPS must work for the requested name. Some sites use several addresses or a content delivery network, so one failed address does not always characterize every endpoint.
If the external test works over IPv6 but one site has no AAAA record, that site may simply be IPv4-only for the hostname tested. If an AAAA record exists but a connection to it fails while other IPv6 destinations work, investigate that site’s path or service. The failure does not establish that the entire connection is broken.
A browser using dual stack can fall back to IPv4 when an IPv6 attempt fails. That can make a page appear normal while hiding a problem with one address family. Conversely, a site that works over IPv4 says little about the IPv6 path.
Read the Results in Order
To check IPv6, keep the observations separate:
- Device: Does the active interface have only a link-local address, or also a suitable globally scoped address and default route?
- External path: Can a known test service reach your browser over IPv6? If not, inspect the router, provider, VPN, and active route.
- Site: Does the exact hostname publish an AAAA record, and can its IPv6 endpoint accept the intended connection?
- Comparison: Does another IPv6 destination work, and does the site work over IPv4? Use those results to identify whether the issue is local, network-wide, or specific to the destination.
IPv6 connectivity is a path property, not just a setting. Record the network, device, test service, and time so a later comparison is meaningful.



