Ask this server
The page requests the connection details this server already received. The response is marked no-store.
My IP and privacy check
See the connection details this server receives and what WebRTC exposes.
Connection
Your public details
Public address
Waiting for the connection check
Checking version
Data source
—
Last checked
—
Connection tested
Waiting for the connection check
Country
Waiting for the connection check
Network
Waiting for the connection check
Organization
Waiting for the connection check
Lookup status
Waiting for the connection check
Country and network details describe the connection, not a street address. They come only from the sources named above.
Your browser timezone is not your location — This value is read from your device clock settings. It is shown on its own so it is never mixed up with the network details above, which come from a different source.
Keep a copy of what this page showed
The report below is a snapshot of the details in this panel. It is put together in your browser, so copying or saving it makes no new request and leaves no visitor history on the server.
WebRTC
Local address exposure
A WebRTC connection can reveal local network addresses to the page that asks for it. This check opens a data channel, lists what the browser reports, and closes it again.
Browsers hide local addresses behind mDNS names such as abcd.local by default. Seeing
a name like that is normal and is not a leak on its own.
How the check works
Your browser cannot see the address your request came from, because that address sits on the server side of the connection. The server reads the request it received and returns the details it already has.
Where the extra details come from
When the country and network lookup is switched on, the server asks a lookup service once and names that source in the Data source row. The answer is used to render this page and then dropped. It is not written to a database, and the response is sent with caching disabled so it is not stored on the way back to you. If the lookup is off or does not answer, the fields say so instead of showing a guessed value.
What this cannot tell you
It cannot prove that a VPN, proxy, or relay is in use, and it cannot prove that none is. It reports the address your connection presents to this server at this moment. A masked WebRTC result is a normal browser behaviour, not a statement about whether a tunnel is working.
How it works
Check WebRTC locally
A temporary browser connection lists the local-address candidates this device exposes, then closes.
Review the sources
Each result names whether it came from the connection, the optional network lookup, or this browser.
Is my address saved anywhere?
No. The check reads the request, renders the answer, and returns it without caching. There is no history page and no lookup table keyed by address.
Why is there no city or region?
This site does not look up a city or region. The lookup provider used here returns a country and network details only, so a city row would be a guess dressed up as data. The country and network fields are shown when the lookup returns them.
What does a WebRTC result mean?
It shows what a page can learn if it opens a WebRTC connection. Modern browsers hide local
addresses behind random names, so a .local entry is expected. A masked entry does
not prove that a VPN has no leaks, and an unmasked entry is not proof of a working tunnel.