Am I Using IPv6
IPv6 connectivity
Checking…
No IPv6 addresses detected on this connection
Checks your HTTP connection and WebRTC for IPv6. IPv4-only networks show No.
How to use
- Open the page — Yes or No appears at the top after HTTP and WebRTC checks.
- If Yes, read the IPv6 addresses listed in the subheadline and Details.
- Click Refresh after changing networks or enabling IPv6 on your router.
FAQ
Am I using IPv6?
Yes if this page detects at least one IPv6 address on your HTTP connection or via WebRTC ICE candidates, or if your HTTP session reports IPv6 as the IP version. No means only IPv4 was observed on this path.
Why do I have IPv6 at home but this says No?
Some networks, VPNs, or browsers disable IPv6 or hide it in WebRTC. Try disabling VPN, confirm router IPv6 settings, and refresh.
Is IPv6 required in 2026?
Most sites still work on IPv4. IPv6 matters for dual-stack networks, some games, P2P, and future-proofing when carriers expand deployment.
How is this different from What Is My IPv6?
What Is My IPv6 lists every address found with more detail. This page gives a simple Yes/No answer for quick connectivity checks.
Can a VPN hide IPv6?
Yes. IPv4-only VPN tunnels may leave IPv6 exposed outside the VPN. If you use a VPN, also run [WebRTC leak test](/tools/webrtc-leak) when IPv6 appears unexpectedly.
Is anything uploaded?
HTTP IP detection may use the site’s my-ip API. WebRTC scanning runs locally in the browser.
Introduction
Am I Using IPv6 answers a simple question with a clear Yes or No headline, then lists any IPv6 addresses detected on your current connection. Dual-stack internet is common on modern fiber and mobile networks, but many setups still run IPv4 only — this page tells you which world your browser is in right now.
IPv6 matters when a game server prefers AAAA records, when your VPN claims “IPv6 leak protection,” or when a hosting panel asks for dual-stack. You should not need to run ping6 from a terminal for a first answer — open this page instead.
IPv4-only vs dual-stack
| Result | Meaning |
|---|---|
| Yes — IPv6 detected | At least one IPv6 address or IPv6 HTTP path observed |
| No — IPv4-only | No IPv6 on HTTP or WebRTC for this session |
| Addresses listed | Concrete IPv6 candidates (may be multiple interfaces) |
IPv6 addresses look like 2001:db8::1 — longer hexadecimal groups separated by colons.
What we check
- HTTP path — whether your connection to this site (and the my-ip lookup) sees an IPv6 client address.
- WebRTC ICE — whether IPv6 candidates appear in a local STUN gather (same technique as leak tests).
Either path saying IPv6 yields Yes.
Common use cases
- Router setup — confirm ISP delegated IPv6 after enabling it in admin UI.
- VPN audit — see if IPv6 still works outside the tunnel.
- Developer testing — verify dual-stack before deploying IPv6-only features.
- Deeper address list — follow up with what is my IPv6.
Best practices
- Test on the network you care about — office Wi‑Fi vs phone data differ.
- Refresh after toggling VPN or rebooting the router.
- Do not confuse Yes with “all traffic is IPv6” — some apps may still prefer IPv4.
- For public IPv4 address, see what is my IP; for leaks, WebRTC leak test.