Current public network address
Test completed—
- IPv4
- not detected
- IPv6
- not detected
MiyaIP Environmental Compass
Your Public IP and Browser Environment
Review the signals visible in this browser session
The current IP, network ownership, DNS resolution path, WebRTC and browser fields will be detected separately. The page only reports the facts that can be reviewed this time and does not package a single result into an anonymous score.
Automatic detectionBrowser fields are not reportedDon't save history
IP and browser environment detection results
Detecting
Building this environment snapshot
The public network connection and the browser's local detection are performed in parallel, and the results are completed one by one.
Detecting the current public network connection, please wait.
online identity
- Operator
- —
- ASN
- —
- organization
- —
- network segment
- —
- time zone
- —
Environment snapshot
"No signal found" only represents completed inspection items.
Locations are city-level estimates
Where is this IP located?
Public network databases typically point to carrier registration areas or exit nodes, not the device's street location.
location details
- Country/Region
- —
- Province/State
- —
- city
- —
- Postal code
- —
- coordinates
- —
- time zone
- —
The map is temporarily unavailable, coordinates are still shown in the location details.
The map only shows the approximate location at the city level and retains the signature of the map data.
Complete evidence matrix
Which items are worth continuing to check?
Items requiring attention are listed first; unavailable items will not be written as approved.
Browser local detection
DNS and WebRTC Evidence
These two items must be initiated from the current browser. The results only describe this path and do not directly prove the true identity leakage.
DNS resolution path
—
- parser
- —
- network organization
- —
- area
- —
WebRTC Candidate
—
- Reflection public network candidate
- —
- Local address exposed
- —
- relay candidate
- —
Structured environment fields
Network Records and Browser Environment
Browser fields are only calculated and displayed locally and are not uploaded to the aggregation interface.
web archives
- Public IP
- —
- ASN
- —
- organization
- —
- IP type
- —
- Reverse DNS
- —
- HTTP proxy header
- —
browser environment
How to understand the results
A difference is not automatically a leak, and unknown is not safe.
Proxies, VPNs, enterprise gateways, Anycast DNS, and browser privacy policies all change visible signals. Multiple pieces of evidence should be combined rather than relying on one color or score.
Check out dynamic residential proxies when you need a stable line- IP location
- Reflects the approximate area of the egress or registration network and cannot locate the device street address.
- DNS paths are different
- It may come from public DNS, proxy, VPN, enterprise policy or cross-zone resolution, and needs to be judged based on the expected configuration.
- WebRTC Candidate
- Key verification is required when the reflected address is different from the visible exit or when the plaintext local address is exposed.
- Browser inconsistency
- Differences in locale and time zone are merely circumstantial facts and do not alone prove camouflage or tracking.
FAQ
About IP and browser environments
Why can't the browser environment be all detected by the backend?
Backend requests only see the app server's own DNS, WebRTC, and network paths. Only results initiated from the current browser represent the device and network you are using.
Are different DNS regions a leak?
No. Public DNS, Anycast, enterprise gateways, and proxies may all have resolvers located in other regions, so the page only says "path is different" and does not directly conclude a leak.
Why are there no anonymous scores?
Different signals have different reliability and applicable ranges, and synthesizing a score can easily create false certainty. MiyaIP directly displays trigger conditions and unavailable items.
Will browser fingerprints be uploaded?
No. The page uses the browser's built-in encryption capability to generate a local summary. Neither the basic fields nor the summary are sent to the aggregation interface, nor are they saved as history.
Why does IPv6 show not detected?
It may be that the current network does not have IPv6, the browser or extension blocks the probe, or the probe may be temporarily unreachable. Can be combined with independent dual-stack tools to confirm again.
Continue to verify