Free tool · China & network
My IP address and network check
See the public IP address you browse with, your network and approximate location, plus WebRTC privacy, DNS leak and latency checks from your own device.
Your address
- IPv4 address
- Checking…
- IPv6 address
- Checking…
- Network
- Checking…
- Approximate location
- Checking…
- Served from
- Checking…
Approximate, derived from your IP address.
DNS leak test
Checking…
Your browser looks up one-time names under our DNS zone. The resolvers that answer are listed here; resolver data stays in our DNS server’s memory for up to 10 minutes.
WebRTC privacy check
Checking…
Checked against a STUN server.
Connectivity check
Best of 3, from your device.
Global
| Site | Status | Latency |
|---|---|---|
| Microsoft | Checking… | — |
| Cloudflare | Checking… | — |
| GitHub | Checking… | — |
| Amazon | Checking… | — |
China
| Site | Status | Latency |
|---|---|---|
| Baidu | Checking… | — |
| Tsinghua University | Checking… | — |
| Peking University | Checking… | — |
| Shanghai Jiao Tong University | Checking… | — |
How this works and its limits
Your address, network and approximate location come from our edge as it saw your visit: the IP address of this connection, the autonomous system (AS) number and registered network name behind it, and the country, region or city and serving location derived from that address. The location is approximate: it describes the address block, not you.
The WebRTC check and the latency check run in your browser. WebRTC asks a STUN server for the public address your browser would expose to a peer; the latency check fetches a small file from each listed site three times and keeps the best round. Both report what your device sees, not what our servers see.
The DNS leak test asks your browser to resolve twelve random one-time names under our DNS zone. Our authoritative name server records the resolver addresses that asked for them, and any part of your address a resolver forwards (EDNS Client Subnet), in memory for up to ten minutes. The page compares those networks and countries with the address our edge saw. If your browser uses DNS over HTTPS, the resolvers you see belong to that provider; that is the correct result for your setup.
Nothing you see here is written to a database or kept after the check. The address lookup answers from the connection itself and keeps no record, the browser checks send nothing back to us, and the DNS server keeps resolver addresses only in memory for up to ten minutes. Carrying a result into the quote form is your choice.
Data sources and licences
Operator names, brands and codes shown here are public reference data compiled from national regulators and other public sources. Their appearance does not indicate any partnership, endorsement, agreement or connectivity between unicomam.com and the named operators. All trademarks belong to their owners. Data is provided “as is” with no warranty; verify against the official source before relying on it for routing, billing or compliance decisions.
Regulatory information is for reference only and is not legal advice; check the regulator link and the “last verified” date.
Source: unicomam.com measurements and curation; the update date is shown with the figures. City-to-city figures only; no path, carrier or supplier information is shown.
What your IP address says about you
Every device on the internet has an address, and every site you visit sees the public one your traffic comes from. That is usually not your laptop or phone: it is the address of your home router, your office gateway or your mobile operator's exit point, shared with many other people. This page shows that address back to you, exactly as our edge saw it when you opened the page.
There are two address systems side by side. IPv4 addresses are the familiar four numbers, and they ran short years ago, so operators share them and translate from one to the other. IPv6 addresses are long and plentiful, and each device can hold its own. Many connections have both, some have one, and a browser does not always reveal each, so the page reports the two families separately and says plainly when one could not be detected.
Addresses come in blocks, and each block belongs to a network with an autonomous system (AS) number: the number is public, and registries record which network holds it. Location databases map those blocks to countries and cities, so a lookup can place you only approximately. The city is often wrong: it may be where the block was registered, where your operator's gateway sits, or simply the middle of the country. It describes the address block's neighborhood, not your position.
WebRTC, the browser technology behind voice and video calls, can expose your public address to the sites you visit, even when the page itself loaded over the other address family. The privacy check compares what WebRTC reveals against the address of the same family: a different address is a signal to check, while an address in the other family just completes the picture. Modern browsers hide local network addresses behind names your device made up, and this tool reports those as hidden without resolving them.
Your device rarely does DNS itself: it asks a resolver, usually run by your ISP, your router or a public provider. The DNS leak test asks for random names that are never reused, then asks our own server which resolver addresses appeared. The verdict compares each resolver's network and located country with the network and country your connection appears in. A resolver in your own network is expected; one in another network is not necessarily a leak; one that answers from another country is the signal worth acting on. If your browser uses DNS over HTTPS, its resolver belongs to that provider, and the result reflects that choice rather than your ISP's resolver.
The latency check measures the round trip from your device to each listed site, three times, keeping the best. The first round includes setting up the connection, so the best of three is the closest single figure for an ordinary page fetch. Expect it to move between runs: home Wi-Fi, mobile signal and busy hours all add their share. It reports reachability and round-trip time only, never the path in between, so it cannot say why a site is slow.