Guides/What websites see about your connection
What websites see about your connection
Every normal website visit sends some technical details so pages can load and respond. This guide lists the signals getwhatismy.com focuses on—public IP, basic network context, and browser-declared headers—so you can separate myth from what is actually transmitted.
Your public IP address
Servers see the source IP of the TCP/TLS connection. That is your ISP assignment or your VPN/proxy exit. It is required for the internet to route packets; you cannot browse while hiding it from the server you are talking to unless you relay through another host (which then becomes the visible IP).
Check yours on the [home page](/) or IP address tool.
Headers your browser sends
Alongside the IP, browsers send headers such as User-Agent (what browser you appear to be) and Accept-Language (language preferences). Sites use them for compatibility and localization. Modern browsers reduce User-Agent granularity to limit passive fingerprinting, but some string is still present.
Explore user agent, browser, and related device tools for a decoded view.
What a VPN changes—and what it does not
A VPN typically changes the public IP and the ISP/ASN location estimate to the exit network. It does not by itself change your device clock, screen size, or necessarily your User-Agent. Browser extensions and “fingerprint spoofers” are separate from VPN apps.
If you only care whether the VPN is up, reload the IP tools before and after connecting.
What this site does not read
We do not need your contacts, files, or GPS to show a public IP. Altitude and precise location tools that use the Geolocation API ask permission explicitly and are separate from IP lookup. We do not keep an application-level archive of IP lookups; see Privacy.
Canvas and WebGL pages demonstrate client-side signals that some trackers discuss; they are optional educational tools, not a requirement to use the IP checker.