MyIP Info · Information
Data Sources & Accuracy
Learn where MyIP Info IP, GeoIP, ASN, browser and connection details come from and what their accuracy limits are.
2026-10-30
The report combines live server request metadata with selected values read locally by your browser. Each field describes this connection, not a permanent identity or precise physical location.
IP, network and location
The public address comes from the trusted client-address field of the incoming request. ASN and AS organization come from connection metadata and describe the announcing network, which may be a provider, VPN, host or employer.
Country, city, region, postal code, coordinates and timezone are network GeoIP estimates. They are not GPS and can be wrong because of VPNs, CGNAT, mobile routing or outdated mappings.
Connection and server fields
HTTP protocol, TLS version, TLS cipher and available round-trip timing describe the connection between your client and the server handling this request.
Fields the server does not supply are shown as unavailable rather than guessed. Cookie, authorization and arbitrary request headers are never exposed in the report.
Browser details and report scope
Browser name, operating system, screen, viewport, preferred languages, device timezone, cookie support and online state are basic local browser values. They are not an advanced fingerprinting test and can be changed by the browser or extensions.
MyIP Info is not a blacklist, DNS-leak, port-scan or anonymity audit. A single request cannot prove whether an address is safe, static, shared or used by a VPN. Editorial guides explain these limitations and are dated so readers can judge freshness.