Line survey.
What your connection actually does, measured from this browser.
Which address Russian and foreign sites see, where your DNS queries go, whether WebRTC gives away your real IP, which services answer, and whether the line stalls after 16 KB. Every result comes with its method and its limits.
Runs in your browser. Nothing is stored and no results are sent to me. Requests go only to the test nodes listed below; like any website, they see your IP.
01 · Addresses
Who sees which address
One checker inside Russia (my function in Yandex Cloud, region ru-central1: returns only your IP, keeps no logs) and five outside. If the Russian and foreign sides see different addresses, your traffic is split: that is how a split tunnel works. Network and country come from GeoJS, with ipinfo.io as a fallback.
| Checker | Side | IP | Network · country |
|---|
02 · DNS
Where your DNS queries go
The browser opens three one-time random subdomains of edns.ip-api.com. Its authoritative server records which resolver asked for each name and reports it back. If the resolver is in Russia while your foreign exit is not, your ISP or that resolver sees every domain you open, VPN or not. Limit: this shows the resolver for these test names; clients with per-domain DNS rules may resolve other names elsewhere.
| Query | Resolver | Network · country |
|---|
03 · WebRTC
What WebRTC gives away
The page opens a WebRTC connection to nobody and asks public STUN servers (Google, Cloudflare) for its address over UDP, exactly what any site can do silently. A public (srflx) address different from your VPN exit is a leak: the site learns your real IP. Local addresses are usually hidden by the browser behind random .local names.
| Candidate | Address | Protocol | Network · country |
|---|
04 · Services
Which services answer
For each service the browser opens HTTPS to its main domain. Where the service sits behind Cloudflare, its /cdn-cgi/trace shows the address and country that service sees, so per-domain routing becomes visible. Elsewhere the browser gets only an opaque answer: it can tell "responds", "refused" (reset, TLS or DNS failure) and "no answer" (blackholed or frozen), but it cannot see an HTTP 403 geo-block page.
| Service | Status | Sees you as |
|---|
05 · TCP 16-20
Does the line freeze after 16 KB
A known behaviour of TSPU filtering on Russian networks: connections to some foreign hosting networks are not blocked outright but stall once about 16-20 KB have passed. The test first checks that a node answers, then sends 64 KB in one POST; if the small request passes and the large one stalls, the freeze is detected. A second method sends about 64 KB as a series of long URLs. Method and node list: hyperion-cs/dpi-checkers (Apache 2.0). The test measures the route your browser actually uses: with a full tunnel it checks the VPN path, not your ISP.
| Node | Provider · host | Answers | Freeze |
|---|
06 · Method
Method, privacy, sources
- Privacy. Every check runs in your browser. This page has no analytics, no cookies and no server of its own besides the Russian checker. Results stay on your screen until you copy them.
- Russian checker. A Yandex Cloud function of ten lines: it answers with the IP the request came from. Logging is switched off for it.
- Sources. IP: Cloudflare trace, ipify, GeoJS, ipinfo.io. DNS: ip-api.com EDNS. WebRTC: STUN of Google and Cloudflare. TCP 16-20: method and node list from hyperion-cs/dpi-checkers under the Apache License 2.0, adapted.
- What a browser cannot measure. Traceroute and ICMP, QUIC and UDP to arbitrary ports, the exact reason a connection was cut, HTTP status codes of foreign sites. Those need a local tool.