MyIPScan

Provider-neutral self-test pilot

X-VPN Leak Test

X-VPN documents a behaviour that matters more to a leak test than most feature lists do: if your selected protocol cannot establish a connection on the current network, or your device moves to another network, the app reconnects in the background and may switch protocol. Its help centre recommends turning on the kill switch for exactly that reason, and describes the switch as something you enable yourself. Its feature page adds a private DNS server and app-level split tunnelling. What follows describes your own session, not X-VPN's servers.

Read methodology

Live test

Run the test on X-VPN now

X-VPN can move to another protocol by itself when your network changes, reconnecting in the background, so a reading taken after a Wi-Fi change is a different session. Read the resolver as well: X-VPN describes a private DNS server meant to keep your activity from your ISP.

Open the full VPN Leak Test

This browser session

Leak report

Not tested
Verdict
Visible IP
Not tested
DNS
Not tested
WebRTC
Not tested
IPv6
Not tested
Browser
Not tested
Next step

This reports what your browser shows in this session. It does not certify X-VPN, does not test every server, app or device, and does not prove anonymity.

Current-session checks

What this X-VPN self-test checks

Take each reading twice, once on your normal connection and once connected, then a third time after changing networks. On X-VPN the address and resolver after a reconnect carry the most information, because that is the moment its help centre singles out.

Before you read the result

What X-VPN documents about these signals

The points below are drawn from X-VPN's help centre articles and its feature page. Knowing the intended behaviour first is what lets you tell a normal reading from one worth chasing.

The kill switch is a toggle you turn on

X-VPN's help centre describes Kill Switch as preventing any data transfer by shutting down your device's internet connection if the VPN is unexpectedly disconnected. It tells you to enable it yourself: on mobile under Me, VPN Settings, Kill Switch, and on a computer under Settings, VPN Settings, Kill Switch, after which the button turns blue. If a check shows an address you did not expect, that button is the first thing to confirm.

The protocol can change under you

According to X-VPN's help centre, the app moves to another protocol when the selected one cannot establish a connection in the current network situation, and a change in the network your device is connected to can cause a background reconnect that also switches protocol. A reading taken before you moved from one network to another and one taken after are therefore two different connections, and comparing them is the point of running the checks again.

Some servers use one protocol only

X-VPN states that its Everest Line servers are bound to a specific protocol, TLS-3, and offers an Auto setting that picks the protocol for you. If you connect to an Everest Line location the protocol choice is already made, which is worth knowing when a reading differs from one you took on another server in the same session.

DNS is meant to stay away from your ISP

X-VPN's feature page describes a private DNS server that hides your activities from your ISP and prevents DNS leaks. A DNS check taken while connected should therefore name a resolver other than your provider's. Your ISP's resolver appearing in that line is the result the feature is meant to rule out, and the reading to repeat after the next reconnect.

Split tunnelling decides which apps are inside

X-VPN offers split tunnelling that lets you choose which app is routed through the VPN and which accesses the internet directly. A browser left outside the tunnel reports your own address by design, so when the IP check shows your own connection, confirm which side of that setting this browser is on before reading it as a leak.

Between the readings

Record a kill-switch drop on X-VPN

X-VPN describes its kill switch as shutting down your device's internet connection if the VPN is unexpectedly disconnected, and recommends turning it on because a network change can trigger a background reconnect. A single reading cannot tell you whether that reconnect left a gap, or how long it lasted.

What this cannot prove

  • This checks visible browser/session signals only.
  • This does not certify the provider.
  • This does not test every server, app, device, or connection.
  • This does not prove anonymity.
  • This does not prove every security condition.
  • A clean result does not prove every leak is absent.

How to compare before and after on X-VPN

  1. On your normal connection, note the visible address, which resolver answered, and whether the IPv6 check returned anything.
  2. Open X-VPN, enable Kill Switch until the button turns blue, and note which location and protocol you connected with.
  3. Rerun the same checks in the same browser, then change networks, for example from Wi-Fi to a phone hotspot, and run them once more.
  4. Expect the address and resolver to change and to stay changed after the reconnect. A reading that shows your own address right after the switch is the case the kill switch is there for.
Safe Copy limits

Safe Copy exports use safe summary categories and remove raw IP, exact city, full user-agent, raw fingerprint data, raw resolver IPs and WebRTC candidates. It is not a certificate, provider audit, or proof of anonymity.

FAQ

X-VPN leak test FAQ

Is X-VPN's kill switch on by default?

X-VPN's help centre describes enabling it yourself, under Me, VPN Settings, Kill Switch on mobile or Settings, VPN Settings, Kill Switch on a computer, and says the button turns blue once it is on. Treat it as a setting to confirm rather than one to assume.

Why did X-VPN change protocol by itself?

X-VPN says it moves to another protocol when the selected one cannot connect on the current network, and that a network change can cause a background reconnect that also switches protocol. Rerun the checks after such a change, because it is a new connection.

What are Everest Line servers?

X-VPN states that Everest Line servers are bound to a specific protocol, TLS-3. Connecting to one fixes the protocol, so a reading taken there can differ from one taken on a server where the Auto setting chose for you.

Which DNS servers should answer while X-VPN is connected?

X-VPN describes a private DNS server that hides your activities from your ISP. The DNS check on this page reports which resolver actually answered for your session, so your ISP's resolver appearing there is worth investigating.

My browser shows my own IP with X-VPN on. Is that a leak?

Check split tunnelling first. X-VPN lets you choose which apps go through the VPN and which connect directly, and a browser outside the tunnel shows your own address by design.

Can this page confirm X-VPN's no-logs claim?

No. X-VPN states that its no-logs policy has been independently audited by a trusted third party, which concerns what the company stores. These checks read only what your own browser exposes during one session.