MIYAIP TOOLS
Use this IP and Browser Environment Check to compare the public IPv4 and IPv6 paths visible to your browser with DNS, WebRTC, network ownership, reverse DNS, and local browser facts.
Local browser checks
Checks run in this browserBrowser facts and the local digest are neither uploaded nor stored.
The public IPv4 or IPv6 address seen by a website identifies a network exit, not a precise device location. Country, region, city, ISP, organization, ASN, reverse DNS, and approximate coordinates describe that exit using current network data.
VPNs, proxies, carrier gateways, mobile networks, and cloud relays can place the public exit in a different region from the browser. Treat location as an estimate and network ownership as a separate fact.
The page compares IPv4, IPv6, DNS resolver, WebRTC, reverse DNS, proxy-related headers, and browser facts as separate evidence. A path difference is a reason to review the setup, not automatic proof of a leak, and an unavailable check is not proof that the setup is safe.
VPN split tunnelling, enterprise DNS, Anycast, privacy relays, browser policies, and extensions can all create legitimate differences. Repeat the check after changing one setting so the effect is easier to isolate.
DNS resolver addresses indicate which public resolver path answered the browser-side check. WebRTC candidates show only the addresses the browser exposes under its current privacy and network policy; modern browsers may hide local candidates or replace them with hostnames.
Documented DNS resolver and WebRTC public IP fields can be submitted for server-side comparison. Local browser facts and the browser summary remain on this device, and the page still shows a partial local result if server analysis fails.
Read every result with its source and limitation. The browser initiates IPv4, IPv6, DNS, and WebRTC observations because a backend can see only its own network paths, not the device and connection currently in use.
MiyaIP presents evidence separately instead of producing an anonymity score. Use the dual-stack test for protocol reachability and the proxy anonymity checker for server-observed proxy-header evidence.
FAQ
It shows public IPv4 and IPv6 addresses, network owner, approximate location, DNS resolver path, WebRTC candidates, reverse DNS, proxy-related headers, and local browser facts. MiyaIP presents these signals separately instead of turning them into one anonymity score.
Backend requests see only the application server's DNS, WebRTC, and network paths. Checks initiated in the current browser are needed to describe the device and network you are using.
No. Public DNS, Anycast, enterprise gateways, and proxies may use resolvers in other regions, so the page reports a different path without directly concluding that it is a leak.
Each signal has different limits and reliability. Combining them into one score can create false certainty, so MiyaIP shows observed evidence, trigger conditions, and unavailable checks separately.
No. Browser facts and the locally generated browser summary are not sent to the aggregation interface or saved as history. Only the documented network observation fields are used for server-side comparison.
The network may not provide IPv6, a browser policy or extension may block the probe, or the probe may be temporarily unreachable. Use the IPv4/IPv6 dual-stack test to check again independently.
MIYAIP
Create an account to manage proxy products, or review rotating residential proxy pricing first.
