Modern IP, browser and network visibility
What is my IP address, and what can a website actually see about my connection?
This dashboard combines live public IP detection, browser-side network hints, WebRTC discovery, device telemetry and permission-based geolocation to show the maximum practical information a modern website can gather in a single visit.
Public Internet Identity
Live IPv4 or IPv6 detection, ISP, ASN, organization, reverse DNS, city-level geolocation and timezone signals.
Browser and Device Environment
Operating system, browser engine, locale, screen profile, secure context, touch support and hardware hints.
Connection and WebRTC Signals
Estimated connection type, downlink, RTT, save-data preference, online status and browser-exposed network candidates.
Live dashboard
Connection diagnostics at a glance
The cards below update in real time using your browser and public IP data providers. Results vary by browser, operating system and privacy settings.
Public IP Intelligence
Loading- IP address
- Detecting...
- Hostname
- Checking...
- City / region
- Checking...
- Country
- Checking...
- Coordinates
- Checking...
- ISP
- Checking...
- Organization
- Checking...
- ASN
- Checking...
- IP version
- Checking...
- IP timezone
- Checking...
Browser and Device
Local- Browser
- Collecting...
- Operating system
- Collecting...
- Platform
- Collecting...
- Language
- Collecting...
- Timezone
- Collecting...
- Screen
- Collecting...
- Device memory
- Collecting...
- CPU cores
- Collecting...
- Touch points
- Collecting...
- Viewport
- Collecting...
Connection Signals
Runtime- Protocol
- Checking...
- Secure context
- Checking...
- Online status
- Checking...
- Connection type
- Checking...
- Estimated downlink
- Checking...
- Round-trip time
- Checking...
- Data saver
- Checking...
- Cookies enabled
- Do Not Track
- Checking...
- Referrer
- Checking...
WebRTC and Local Network Hints
Scanning- STUN public candidate
- Scanning...
- Private IP candidates
- Scanning...
- Masked host candidates
- Scanning...
- Transport hints
- Scanning...
- ICE candidate count
- Scanning...
- Privacy note
- Modern browsers may hide local IPs.
Browser Capability and Privacy Surface
Feature map- Local storage
- Checking...
- Session storage
- Checking...
- IndexedDB
- Checking...
- Service worker
- Checking...
- Dark mode preference
- Checking...
- Reduced motion
- Checking...
- Color gamut
- Checking...
- Standalone mode
- Checking...
IP Source Comparison
Comparing- Provider 1
- Checking...
- Provider 2
- Checking...
- Provider 3
- Checking...
- IP consensus
- Checking...
- Location confidence
- Checking...
- Interpretation
- Checking...
Location Permission Diagnostics
Permission not requested- Permission state
- Checking...
- Precise coordinates
- Not requested
- Accuracy radius
- Not requested
- Last update
- Not requested
IP geolocation is approximate. If you want higher precision, you can grant browser location access. This is optional and stays under your browser's permission model.
Exposure Assessment
Scoring
Visibility level
Building profile...
We are combining public IP data, browser telemetry and privacy protections to estimate how visible this session is to an ordinary website.
- Assessing exposure surface...
Analyst Notes
Interpreted- Building your diagnostic narrative...
Speed test
Measure latency, jitter, download and upload speed
This built-in test uses your own hosting to estimate round-trip latency, download throughput and upload throughput. Results are more trustworthy than a decorative widget because the measurements are performed against your server endpoints.
Internet Speed Test
Ready
Idle
--
Run the test on HTTPS for the most realistic result and avoid other heavy downloads during the measurement.
Speed Test Results
Measured- Latency
- Not tested
- Jitter
- Not tested
- Download speed
- Not tested
- Upload speed
- Not tested
- Test server
- This host
- Measured at
- Not tested
Speed Interpretation
Helpful readout- Connection grade
- Not tested
- Streaming readiness
- Not tested
- Video call readiness
- Not tested
- Cloud work suitability
- Not tested
- Notes
- Run the test to generate an interpretation.
How it works
What this website can reveal, and what remains protected
What websites usually know
Any website you visit can see the public IP address used to reach it. From that, it can often estimate your city, region, country, ASN, ISP and timezone. It can also observe browser headers, language preferences, screen size, device class, secure transport status and general runtime capabilities.
Where browser-side diagnostics add value
Browser APIs can expose connection quality estimates, online state, touch support, CPU and memory hints, and in some cases WebRTC network candidates. These extra signals help show how a session appears from the client side, not just from a public IP database.
What a website cannot safely promise
A normal browser-based website cannot silently enumerate every device on your network, inspect all open connections, or guarantee accurate private IP discovery on every browser. Modern privacy protections intentionally limit that visibility. A trustworthy tool should show the boundary clearly instead of overstating its powers.
Why this is stronger than a basic what-is-my-IP page
Most IP checker websites stop at a single public address and a basic map pin. This build goes further by comparing multiple browser-visible signals in one interface: public IP intelligence from live providers, local environment telemetry from the browser, WebRTC candidate discovery, and optional precise geolocation if the visitor explicitly allows it.
That creates a more useful diagnostic surface for users troubleshooting VPN behavior, verifying whether a network path changed, understanding how their browser presents itself online, or seeing how much passive connection information is exposed during an ordinary web session.
Useful for normal users
A normal visitor can use this page to check whether a VPN is active, understand why a website thinks they are in another city, confirm if their browser location permission is working, and learn why some sites know more than expected about their device.
Useful for IT and security teams
A technical user can compare IP data sources, look for timezone or WebRTC mismatches, verify secure-context requirements, and quickly gauge whether a browser is exposing enough client-side surface for troubleshooting remote access, SaaS access policies or privacy hardening.
What to add later with a backend
If you later move from a purely static site to a lightweight backend, you can add server-observed request headers, real TLS certificate details, dual-stack endpoint testing, DNS leak style resolver checks, and ASN reputation or blacklist enrichment for even deeper diagnostics.
Security reality check
A public website can and should block directory listing, protect sensitive files, and enforce strong response headers. But it cannot stop visitors from receiving and viewing the frontend code that their browser must download to render the page. Real protection comes from keeping secrets and business logic on the server, not from trying to hide shipped client files.
FAQ
Frequently asked questions about IP visibility
Does this show my real IP address?
It shows the public IP address that websites and APIs see for your session. If you are using a VPN, proxy or enterprise gateway, the address shown may be that intermediary rather than your ISP-issued home IP.
Why does the location not match my exact place?
Public IP geolocation is approximate and is often mapped to a nearby city, metro area or network hub. Precise device location requires browser permission and depends on device sensors, Wi-Fi data and operating system services.
Why are private IP fields blank on some browsers?
Browsers such as Chrome, Safari and Firefox increasingly restrict direct exposure of local addresses. When that happens, you may only see masked hostnames or no WebRTC host candidates at all. That is normal and privacy-positive behavior.
Can a website see all my network connections?
No. A standard website cannot inspect all active sockets or enumerate every destination your device is connected to. It can only use browser APIs and information inferred from the incoming web request and permitted client-side features.
Why compare multiple IP providers?
Different IP intelligence providers maintain different datasets and refresh schedules. Comparing multiple sources helps show when the public IP is consistent but the city, ISP or ASN metadata is lagging or disputed.
Can this detect a VPN or proxy with certainty?
Not with certainty from a static browser page alone. What it can do is surface indicators such as timezone mismatches, unexpected ASN ownership, geolocation drift, and differences between WebRTC-exposed candidates and the main public IP.