Baseline

Connected dual-stack + WebRTC

IPLeak connected result showing ZBEVPN IPv4 and IPv6 egress.

BrowserLeaks connected result reporting WebRTC Leak Test No Leak — BrowserLeaks connected result reporting WebRTC Leak Test — No Leak.

IPinfo + ZBEVPN location corroboration

IPinfo result showing matching IPv4 IPv6 and Montreal Quebec location — IPinfo: matching IPv4, IPv6 and Montreal, Quebec location.

ZBEVPN connected to Montreal with matching public egress addresses — ZBEVPN: CA-1 Montreal selected with matching public egress addresses.

Scope: IPv4, IPv6, dual-stack connectivity, WebRTC public-IP behavior and location corroboration. No DNS-leak claim is made.

TEXT SUMMARY OF THE PUBLISHED EVIDENCE

What the documented tests observed

The screenshots on this page are the original evidence captures. This table states the same observations in text so the evidence is readable without image interpretation. These are point-in-time observations, not a claim that every future network path will produce the same result.

Evidence	Test service / source	Documented observation
Pre-VPN baseline	IPLeak + BrowserLeaks	Baseline ISP-facing public network information was captured before ZBEVPN connection; identifying details were redacted in the published images.
Connected IPv4 + IPv6	IPLeak	The connected capture showed ZBEVPN IPv4 and IPv6 egress rather than the baseline public addresses.
WebRTC public-IP behavior	BrowserLeaks	The documented connected test reported “WebRTC Leak Test — No Leak.”
Location corroboration	IPinfo + ZBEVPN connected state	The published IPinfo capture and ZBEVPN connected-state capture showed matching Montreal public egress/location information.
Windows DNS test — Stockholm	DNSLeakTest.com, documented 2026-08-27	No DNS leak was observed in the published Windows test.
Android DNS test — São Paulo	DNSLeakTest.com, documented 2026-08-27	No DNS leak was observed in the published Android test.