MyIPScan
Browser IPv6 check

IPv6 Leak Test: Check If Your IPv6 Address Is Exposed

Check whether this browser session shows IPv6 through your current public IP route or WebRTC candidate signals.

IPv6 visibility is not automatically a leak, and no IPv6 detected does not automatically mean your connection is safer. Results depend on ISP, browser, operating system, VPN, and network behavior.

IPv6 exposure

Current Result

Inconclusive
Run the test to check IPv4 and IPv6 signals from this browser session.
IPv4 availability
Not tested
IPv6 availability
Not tested
Observed IPv6 signals
Not tested
VPN context
Not marked as VPN testing
Verdict first Safe Copy Details below
Exposure estimate and receipt limits

An IPv6 review flag means visibility may need review when VPN or privacy routing is expected. Receipt exports use safe categories and remove raw IP and WebRTC candidate values before export. Read the methodology.

See what Safe Copy includes before sharing or saving a result.

Want the full picture? Run the Privacy Exposure Report.

Combine IP, WebRTC, IPv6, DNS leak, fingerprint, user-agent, and related privacy signals in one report.

Run report

Result meanings

How to read the result

IPv6 not detected

This test did not observe a global IPv6 route from the public IP check or WebRTC candidates. It is a session signal, not a complete network audit.

IPv6 detected

A global IPv6 address was visible. That can be normal on a dual-stack connection and is not automatically bad.

Possible IPv6 leak

A global IPv6 address was visible while you marked that you are testing with a VPN. Review VPN IPv6 support or leak-protection settings.

Inconclusive

The test could not gather enough public IP or WebRTC data to classify IPv6 exposure reliably.

What this means

IPv6 is a modern internet addressing system. Many networks support both IPv4 and IPv6, so seeing IPv6 can simply mean your ISP, router, device, browser, and VPN route support it.

If you are connected to a VPN and expected it to hide or tunnel IPv6, a visible global IPv6 address is a signal to review your VPN configuration. It does not prove that the VPN is unsafe.

Common causes

  • Your ISP and router provide dual-stack IPv4 and IPv6 connectivity.
  • Your VPN tunnels IPv4 but handles IPv6 differently.
  • Split tunneling, browser WebRTC, or operating-system settings expose a different route.
  • Private relay, secure DNS, or enterprise network policy changes visible signals.

Fixes

How to reduce IPv6 exposure

Use these steps as a checklist, then rerun this page and compare it with the unified VPN leak test.

  1. Check whether your VPN explicitly supports IPv6 tunneling or IPv6 leak protection.
  2. Enable the VPN app's leak-protection setting if it offers one.
  3. If you do not need IPv6, consider disabling it at the device or router level and retest.
  4. Review split-tunneling rules that may leave browser traffic outside the VPN route.
  5. Test on a second browser and network when the result looks inconsistent.

Methodology

How this IPv6 test works

The page requests same-site /api/ip to see whether the public HTTP route appears IPv4 or IPv6. It also creates a temporary RTCPeerConnection and uses stun:stun.l.google.com:19302 to look for global IPv6 ICE candidates.

Local, link-local, ULA, loopback, and mDNS-masked candidates are not treated as global IPv6 exposure. This test does not audit every app, OS route, router setting, or VPN tunnel. Read the MyIPScan methodology for broader limitations.

Related tools

Continue the privacy check

VPN Leak TestCombine IP, DNS, WebRTC, IPv6, and browser signals. DNS Leak TestCheck common DNS exposure signals and limitations. WebRTC Leak TestSee whether browser ICE candidates expose IP details. IPv6 Leak TestReturn to this IPv6 browser exposure check. What Is My IPCompare the public IP route with IPv6 results. MethodologyRead how MyIPScan diagnostic results are classified.

Related guides

Learn the signals

IPv4 vs IPv6Understand the two public IP address families. How to Check Your IPv6 AddressLearn where IPv6 can appear and how to compare signals. IPv6 Leak Topic HubFollow the IPv6 leak cluster for VPN, browser, and dual-stack troubleshooting. What Is a WebRTC Leak?See why browser networking can expose address candidates. What Is a VPN?Review what VPNs route and what they may not hide. How to Hide Your IP AddressCompare VPNs, proxies, Tor, and browser privacy tradeoffs. Guides HomeOpen the MyIPScan blog for newer privacy guides.

Before / after privacy flow

Compare one browser or VPN change at a time

This page is focused on global IPv6 visibility through public route and WebRTC candidate checks. Run the IPv6 check first, then use Public Exposure Report for the wider VPN/browser session picture. Results are visible browser/session signals, not a certification.

1. BaselineRun the focused check before changing VPN, DNS, browser, profile, or network settings.
2. Change one thingConnect or switch VPN, change Secure DNS, adjust WebRTC/fingerprint settings, or move networks.
3. RetestRun the same check again in the same browser/session when possible.
4. CompareReview changed and unchanged IP route, DNS, WebRTC, IPv6, fingerprint, and User-Agent signals.
5. Safe receiptUse Safe Copy or the Safe Privacy Receipt instead of sharing raw identifiers.

Status language

Use conservative result labels

These labels keep the result understandable without implying a VPN, browser, device, or account is safe.

Visible

A browser/session signal was visible and should be compared with what you expected.

Expected

The observed signal appears consistent with the stated route or browser behavior.

Review

The signal may need closer review before relying on this setup for the current session.

Limited

The check ran, but this page cannot cover every app, device route, server, or future connection.

Not detected

The tested signal was not observed in this browser/session.

Not checked

The signal has not run yet or the browser did not provide enough data.

Fix checklist

Where to review settings after a signal needs attention

Settings names change. Treat this as a route to verify, then rerun the focused check and the Public Exposure Report.

ChromeReview Secure DNS, WebRTC policy/extensions, profile state, and site permissions.
EdgeReview Chromium privacy settings, managed policies, Secure DNS, and VPN split tunneling.
FirefoxReview Enhanced Tracking Protection, DNS over HTTPS, and advanced WebRTC preferences when appropriate.
BraveReview Shields, fingerprinting protections, and WebRTC IP handling policy.
SafariReview website permissions, iCloud Private Relay context, and operating-system privacy settings.
iOSRetest after VPN profile, relay, mobile data, or Wi-Fi changes. Browser controls may be limited.
AndroidReview per-app VPN, Private DNS, browser permissions, and Wi-Fi versus mobile data behavior.
WindowsReview VPN adapter DNS, split tunneling, IPv6, browser Secure DNS, and firewall/proxy rules.
macOSReview VPN profile order, DNS settings, iCloud Private Relay context, and browser-specific privacy controls.
Public Exposure ReportDefault next step for a combined route map and Safe Privacy Receipt. Is My VPN Working?Before/after VPN workflow for visible browser/session signals. What Websites Can See About MePlain-language map of signals websites may read from this browser/session. Check My Browser PrivacyFocused path for fingerprint, WebRTC, IPv6, User-Agent, and browser settings.

Check IPv6

What this checks

Whether this browser session exposes public-route IPv6 or WebRTC IPv6 candidates alongside the IPv4 route you expected.

Limits

What this cannot check

It cannot audit every app, OS route, router setting, VPN tunnel, browser profile, mobile network, or future connection.

Read results

How to interpret results

A good result means no unexpected public IPv6 route appears when VPN or privacy routing is expected. Local, link-local, ULA, loopback, and mDNS values are not public IPv6 leaks by themselves.

Warnings

What a warning means

A warning means public IPv6 visibility may not match the route you expected and should be compared with VPN, DNS, and WebRTC results.

Fix path

What to do next

Review VPN IPv6 leak protection, OS IPv6 settings, router IPv6 settings, and whether the browser exposes IPv6 through WebRTC.

Retest

When to retest

Retest after changing VPN server, toggling IPv6, switching networks, changing router settings, or updating browser privacy settings.

Related tools

Continue with the closest checks

Public Exposure ReportFull browser-session report with Safe Copy, issues, fixes, and clear limits. VPN Leak TestCompare visible IP, DNS, WebRTC, IPv6, and browser signals. DNS Leak TestLimited resolver-signal check with before/after review. WebRTC Leak TestBrowser ICE candidate behavior and WebRTC exposure signals. MethodologyReview how MyIPScan labels signals, limitations, and Safe Copy output.