MyIPScan

Independent self-test

Twingate Leak Test

Twingate is not a full tunnel, and its documentation makes that a matter of mechanism rather than marketing: the client watches for connection requests to protected Resources and builds a connection only when the destination matches one in the access list. Everything else leaves your machine the way it always did. That single design decision explains most of what these checks return here, including a public address that has not moved. The reading is about this browser.

Read methodology

Live test

Run the test on Twingate now

Twingate routes traffic only when the destination matches a Resource in its access list, so the address below is normally your own. The line that can move is DNS.

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 Twingate, does not test every server, app or device, and does not prove anonymity.

Current-session checks

What this Twingate self-test checks

Read the signals once with the client signed out and once signed in. On Twingate the line that can move is DNS, because resolution for protected Resources is proxied while everything else is not.

Before you read the result

What Twingate documents about these signals

The points below come from Twingate's own documentation, which describes the client as matching destinations against an access list rather than capturing everything a device sends.

Only Resource traffic is routed

Twingate documents the client as detecting network connection requests to protected Resources, and states that if the destination address matches a Resource in the access list, a connection is initiated via Twingate to the remote network. Traffic to anything else is untouched. A public IP check run during a Twingate session is therefore reading your ordinary connection, correctly, and there is no tunnel address for it to report.

DNS for Resources is proxied, not replaced

The client proxies DNS requests for protected Resources, forwarding them for resolution to a Connector inside the remote network. That is split DNS: private names resolve on the far side, public names resolve the way they always did. A DNS leak test asking about a public domain is measuring the second half of that arrangement, which is the half Twingate deliberately leaves alone.

DNS over HTTPS is a separate switch

Twingate documents native DNS-over-HTTPS for users running its macOS, Windows or Linux clients, and states that it encrypts all DNS traffic regardless of the originating application with no configuration changes required. That changes what a resolver check can observe about this device, so it is worth knowing which state you were in before you read one.

Filtering happens at resolution time

Twingate's Internet Security features include DNS filtering, which decides at resolution time whether a name is answered at all. A page that will not load during a check may have been filtered rather than blocked by a network fault, and those are different findings that a single reading will not separate for you.

Comparing it with a consumer VPN misleads

Twingate publishes its own comparison against traditional VPNs, and the difference is the point. A consumer VPN is judged by whether your visible address changed. This product is judged by whether a named Resource became reachable to the people entitled to it. Reading one result with the other's expectations is the usual route to concluding that something has failed.

Between the readings

Record a kill-switch drop on Twingate

A Twingate client that stops running does not expose internet traffic, because that traffic was never inside it. What ends is a private hostname resolving, and a recording is still the way to see how quickly the change takes effect.

Known leak issues and fixes

Twingate has not published a statement on the VPN leak attacks below. We looked on its site, blog and changelog; each row says where, and when we last checked. Compare every provider side by side.

AttackAppsStatusWhat the provider saidSource
TunnelVisionCVE-2024-3661 All apps Not statedChecked 18 Oct 2026 A Twingate glossary post describes TunnelVision but gives no status for its own clients. twingate.comRead 18 Oct 2026
TunnelCrack LocalNetCVE-2023-36672, CVE-2023-35838 All apps Not statedChecked 18 Oct 2026 No statement for Twingate's own clients. twingate.comRead 18 Oct 2026
TunnelCrack ServerIPCVE-2023-36673, CVE-2023-36671 All apps Not statedChecked 18 Oct 2026 No statement for Twingate's own clients. twingate.comRead 18 Oct 2026

Latest app versions: Windows 2026.280 (9 Oct 2026); macOS 2026.279 (9 Oct 2026); iOS 2026.279 (13 Oct 2026); Linux 2026.239 (6 Oct 2026); Android 2026.237 (2 Sep 2026).

The leak test on this page checks your own connection; these attacks need a hostile local network and cannot be reproduced from a web page.

Published audits

No published independent audit found as of 28 Oct 2026. Twingate's security documentation says Hacker House does ongoing testing, with no dates and no public report; its SOC 2 report is available on request. No published audit was found through Oct 2026. twingate.comChecked 28 Oct 2026 All published VPN audits we track.

Who runs Twingate, and on what

Company
Twingate Inc., United States. A Delaware corporation. twingate.comRead 18 Oct 2026

Who owns which VPN: every provider’s company and the groups that run several brands.

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 Twingate

  1. Note your address, your resolver and any IPv6 result before you sign in to the client.
  2. Sign in, and note which Resources your account is authorised for and whether DNS over HTTPS is enabled.
  3. Rerun the same checks in the same browser, without switching profile.
  4. Expect the public address to stay put. The change to look for is a private hostname resolving that did not resolve before.
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

Twingate leak test FAQ

Why has my IP address not changed with Twingate running?

Because Twingate documents the client as initiating a connection only when the destination matches a Resource in the access list. Traffic to everything else keeps its ordinary path, so a public IP check reports the address it always would.

Is Twingate a VPN?

Twingate publishes its own comparison against traditional VPNs and describes a per-Resource model rather than a device-wide tunnel. That difference is why leak-test expectations carried over from a consumer VPN produce confusing readings here.

How does DNS work while Twingate is connected?

The client proxies DNS requests for protected Resources and forwards them to a Connector in the remote network for resolution. Public names are resolved the way they were before, which is what a public DNS check will see.

What does Twingate's DNS over HTTPS change?

Twingate documents it as encrypting all DNS traffic regardless of the originating application, with no configuration changes required, on its macOS, Windows and Linux clients. Whether it was on changes what a resolver check can observe.

A site would not load during the test. Was that Twingate?

It can be. Twingate includes DNS filtering as part of its Internet Security features, and a filtered name is refused at resolution time. Check the filtering policy before treating the failure as a network fault.

Can this page tell me whether my Resources are secure?

No. It reports what this browser exposed to a public site in one session. Access to private Resources happens between the client and a Connector and is never visible here.