---
title: "IPv6 Test – What Is My IPv6 Address? | DeviceTests"
description: "Test IPv6 in your browser. See if IPv4 and IPv6 work, your IPv6 score out of 10, your public IP addresses, and if WebRTC leaks your real IP past a VPN."
url: https://devicetests.com/ipv6-test
language: en
---

# IPv6 test

Check if your internet connection has IPv6, and if your VPN lets your real address slip out.

> **Interactive test.** This test runs in the browser on the user's own device and uses that device's hardware, so an AI agent can't run it for the user. To use it, the user opens <https://devicetests.com/ipv6-test> in a browser.
>
> **What it needs:** The device and internet connection the user wants to check, with this page open in its browser (computer, phone or tablet; Wi-Fi, cable or mobile data). The page asks our server over IPv4 only, IPv6 only and both, and gathers the addresses WebRTC shows, so an agent can't run it for the user: the answer depends on their own connection, router, provider and VPN. It gives an IPv6 score out of 10, the public IPv4 and IPv6 addresses, and whether WebRTC shows an address other than the one websites see (a VPN leak). No DNS leak test.
>
> **Cost:** Free. Nothing to install and no account.

Our server sees your IP address to answer the test, like any website does. We don’t store it. Your result stays in this browser.

This IPv6 test needs JavaScript to contact our test servers over IPv4 and IPv6. Turn on JavaScript, or open this page in a current Chrome, Edge, Firefox or Safari.

## Quick start

1. Press **Start IPv6 test**.
2. Wait a few seconds, at most 15, while each check finishes.
3. Read your IPv6 score and addresses under the test.

## How to read your results

**What is my IPv6 address?** Press **Start IPv6 test**. After a few seconds, your address shows under **Your public addresses**, next to **IPv6 address**. It looks like 2001:db8:85a3::7334. If it says **None found**, your connection has no working IPv6.

Your result starts with your **IPv6 score**, out of 10. It says how ready your connection is for websites that only have IPv6. It is not a speed score. For the cases we test, it gives the same points as the long-standing test-ipv6.com.

| IPv6 score | What it means |
| - | - |
| **10/10** | IPv6 works. Usually your browser also uses it when a website has both. If it picked IPv4 this time, the headline says so: browsers do that when IPv4 answers a little faster, and it’s fine. |
| **1/10** | IPv6 works for small replies, but a larger reply got stuck: a possible packet size problem. Some websites may load forever. See “If something’s wrong”. |
| **0/10** | No IPv6, or IPv6 is broken. The headline says which. Without IPv6, every common website still works over IPv4. |
| **No score** | Our test servers didn’t answer the way they should, so we can’t tell. That’s our side, not your connection. |

Under the score, each check has its own line:

| Check | What we test | Good result |
| - | - | - |
| **IPv4 websites** | Our test server with only an IPv4 address | Works |
| **IPv6 websites** | Our test server with only an IPv6 address | Works |
| **Websites with both** | Our server with both kinds of address: which one your browser picks | Works, uses IPv6 |
| **Large data over IPv6** | A bigger reply of a few kilobytes, which needs full-size packets | Works |
| **WebRTC leak check** | Which public addresses WebRTC shows, for VPN users | No extra address |

**Your public addresses** are the ones websites see: an IPv4 address such as 203.0.113.5, and an IPv6 address such as 2001:db8:85a3::7334. With a VPN on, you see the VPN’s addresses. “None found” means that kind doesn’t work on this connection.

**The WebRTC leak check** is for people who use a VPN. It lists every public address WebRTC shows a website, and whether websites see that address anyway:

| What it says | What it means |
| - | - |
| **WebRTC shows an address that websites don’t see** | With a VPN on, this is likely your real address, leaking past the VPN. Without a VPN, your provider probably uses more than one address, and nothing is wrong. |
| **WebRTC shows no extra address** | WebRTC shows only addresses that websites see anyway. With a VPN on, check that they are the VPN’s addresses, not your own. |
| **WebRTC shows an address we couldn’t compare** | Websites didn’t reach us over that kind of address (often IPv6), so we can’t tell whose it is. Test once with the VPN off and compare. |
| **WebRTC showed no public address** | Your browser, VPN or an extension may block it, or our server’s answer didn’t arrive. It doesn’t prove that nothing can leak. |
| **We couldn’t run the WebRTC check** | Our server or your browser didn’t let the check start. Test again, or try another browser. |
| **WebRTC is turned off in this browser** | Nothing can leak. Video calls in the browser won’t work while it’s off. |

Most browsers hide your local network address (such as 192.168.1.20) behind a random name ending in .local. The result says if your browser shows it instead.

> **Tip:** Using a VPN? Run the test twice: once with the VPN off, to see your real addresses, and once with it on. With the VPN on, none of your real addresses should appear anywhere.

## If something’s wrong

These are the most common problems, most likely first.

### No IPv6 on this connection

This is the most common result, and everything still works over IPv4.

1. **At home:** open your router’s settings page and look for IPv6, often under Internet, WAN or Advanced. Turn it on, choose the automatic setting, save, and restart the router.
2. **No IPv6 setting?** Ask your internet provider if they offer IPv6. Many do, at no extra cost. Some need a newer router.
3. **Using a VPN?** Many VPNs turn IPv6 off on purpose, so it can’t leak. Test again with the VPN off.
4. **On a phone:** test once on Wi-Fi and once on mobile data. Many mobile networks have IPv6 even when the home Wi-Fi doesn’t.

### IPv6 is broken: websites load slowly or not at all

Your device thinks it has IPv6, but IPv6 doesn’t get through: a website with both failed, or our IPv6 server got no answer at all. Browsers then wait before they try IPv4, so some websites hang.

1. Turn off any VPN and test again.
2. Restart your router: unplug it for 30 seconds, plug it back in, and wait two minutes.
3. Update your router’s software (firmware) from its settings page.
4. Still broken? Turn IPv6 off in your router for now, so websites load normally. Then tell your provider that IPv6 doesn’t work, and show them your result.

### Larger data gets stuck over IPv6

Small replies arrive, but a bigger one didn’t. Most often the packet size (called MTU) is set wrong somewhere on the way, on a router, VPN or tunnel. A one-off hiccup can look the same, so test again first.

1. Test again. Then turn off any VPN and test again.
2. Restart your router, and update its software.
3. In the router’s IPv6 or WAN settings, an option such as “MTU” or “MSS clamping” may help. Only change it if you know what it does.
4. Still stuck? Tell your provider that larger IPv6 packets get lost, and show them your result.

### WebRTC shows an address that websites don’t see

With a VPN on, this is likely your real address leaking.

1. In your VPN app, turn on its leak protection. It may be called WebRTC protection, IPv6 leak protection or kill switch.
2. Install your VPN’s browser extension, if it has one. Many block WebRTC leaks.
3. Change the browser setting, then test again:

**Firefox**

- Type about:config in the address bar and accept the warning.
- Search for media.peerconnection.enabled and set it to false.

**Chrome and Edge**

- There’s no built-in switch.
- Use your VPN’s extension, or Google’s WebRTC Network Limiter extension.

**Safari**

- There’s no switch for WebRTC.
- Use your VPN app’s leak protection.

**Brave**

- Open Settings, then Privacy and security.
- Set WebRTC IP handling policy to “Disable non-proxied UDP”.

Turning WebRTC off stops video calls in the browser, such as Google Meet. Turn it back on when you need them.

### “We can’t reach our test server”

Check that you’re online. A firewall, VPN, school or work network, or a strict ad blocker can block the test. Try another network or turn off the VPN, then press **Try again**.

### “Too many tests in a short time”

Our server limits how often one connection can test. Wait one minute, then press **Try again**.

### “We couldn’t check IPv6 this time”

Our IPv6 test server didn’t answer the way it should. That’s a problem on our side, not with your connection. Test again later.

## How this test works

When you press **Start IPv6 test**, your browser asks our test server for the address it sees you on. It asks three times at once, using three names for the same server:

- one with only an IPv4 address, to test IPv4
- one with only an IPv6 address, to test IPv6
- one with both, to see which one your browser picks

If IPv6 works, the browser then asks for a larger reply over IPv6 of about 4 kilobytes. That needs full-size packets, which a wrong packet size (MTU) setting can block. A first check that gets no answer within 10 seconds, or a larger reply that takes over 5, counts as not working, so the whole test takes at most 15 seconds.

At the same time, the WebRTC check starts a video-call connection without a camera or microphone. It doesn’t call anyone. It asks our server which public address it sees, the way a video call does, and lists every address WebRTC would show a website. Then we compare those with the addresses from the first part. IPv6 addresses count as the same when their first half matches, because devices change the second half often for privacy.

We don’t use other companies’ servers for any of this. See [how we test your internet](https://devicetests.com/how-we-test#internet).

**What the test can’t tell you**

- Whether your DNS requests leak past a VPN. That needs a DNS leak test, which we don’t offer.
- Whether IPv6 works on your other devices. Each device has its own settings, so test each one.
- Your speed. Use the [internet speed test](https://devicetests.com/internet-speed-test).
- Whether every website works. We test our own servers; a website somewhere else can behave differently.

[How we test our tools](https://devicetests.com/how-we-test)

## Questions and answers

**What is IPv6?**

Every device on the internet needs an address, called an IP address. IPv4 is the old kind, such as 203.0.113.5. There are only about 4 billion of them, and they ran out years ago. IPv6 is the newer kind, such as 2001:db8:85a3::7334, with more than enough for every device.

Today most websites have both kinds. Your device uses whichever works.

**Do I need IPv6?**

Not yet. Almost every website still has an IPv4 address, so a connection without IPv6 works fine. IPv6 can help with some games and video calls, because it often avoids the address sharing that IPv4 needs. If your provider offers it, turn it on. If not, there’s no need to worry. [IPv4 vs IPv6](https://devicetests.com/ipv4-vs-ipv6) explains the difference.

**How do I turn on IPv6?**

At home, IPv6 is a router setting. Open your router’s settings page (often 192.168.1.1 or 192.168.0.1, or the address on its label), look for IPv6 under Internet, WAN or Advanced, and choose the automatic setting. Save, then restart the router. If there is no IPv6 setting, or it doesn’t help, your provider may not offer IPv6 yet: ask them.

On phones and tablets there is usually nothing to turn on. On Wi-Fi it depends on the router, and on mobile data on your mobile provider.

**Why is my IPv6 score 0 out of 10?**

Your connection has no working IPv6, so a website that only had IPv6 wouldn’t load. That is very common, and every common website still works. A score of 0 can also mean IPv6 is broken. The result tells you which.

**What is a WebRTC leak?**

WebRTC is the part of your browser that makes video calls. To connect a call, it asks a server for your public address. With some VPNs, that request goes around the VPN, so a website can learn your real address. Our WebRTC check shows which addresses WebRTC reveals, and if any of them is one that websites don’t see.

**Do you test for DNS leaks?**

No. A DNS leak test needs its own name servers on the internet, which we don’t run. A DNS leak means the names of the websites you visit go to your internet provider instead of through your VPN. Your VPN provider’s app or website often has a DNS leak test.

**Do you store my IP address?**

No. Our test server needs your address to send its answer back, like any website. It keeps it in memory to stop misuse, until about an hour after your last test, then forgets it. It doesn’t write it to a file or log. Your result, without the addresses, stays in this browser. See our privacy policy.

**Why is my IPv6 address different each time?**

That’s normal. To protect your privacy, phones and computers change their IPv6 address every day or so. The first half of the address belongs to your connection and stays the same; the second half changes.

## Related tests

- [Internet speed test](https://devicetests.com/internet-speed-test): Measure your download and upload speed.
- [Ping test](https://devicetests.com/ping-test): Measure how fast your connection responds.
- [Packet loss test](https://devicetests.com/packet-loss-test): Check whether your connection drops data.
- [Bufferbloat test](https://devicetests.com/bufferbloat-test): Check whether your internet lags when it is busy.
- [Internet stability test](https://devicetests.com/internet-stability-test): Record your connection for hours and see when it drops.
