IPAnalyser · http2-vs-http3
HTTP/2 vs HTTP/3: what changes for your connection?
This page explains the observable network signal, how the method works and where its limits are. IPAnalyser does not intentionally store the result in application logs, analytics or a database.
Key signals and concepts
| Key signals and concepts | Methodology |
|---|---|
| HTTP/2 | Privacy by design |
| HTTP/3 | Privacy by design |
| TCP | Privacy by design |
| QUIC | Privacy by design |
| RFC 9113 | Privacy by design |
| RFC 9114 | Privacy by design |
Understand the result
What a public IP shows
A public IP identifies a network connection on the internet. It does not identify a person or exact physical address.
Why location is approximate
IP location can point to a network gateway, mobile hub, company network or VPN exit instead of your device.
Privacy by design
The basic result comes from the current edge response. IPAnalyser does not intentionally write it to an application database, analytics profile or application log.
Network assessment
Network signals are heuristic. They cannot confirm VPN, proxy, Tor or residential use.
Data sources
FAQ
Frequently asked questions
Is IP location exact?
No. IP geolocation estimates where an address block or network gateway is registered or routed. It may point to a mobile carrier hub, company network, ISP facility, or VPN exit instead of your device. Treat country and region as approximate signals, never as a person’s identity or exact physical address.
Does a hosting ASN prove VPN use?
No. A hosting ASN can indicate that traffic exits through infrastructure used by cloud providers, VPN services, proxies, or ordinary business systems. IPAnalyser combines it with limited network signals and reports uncertainty. It cannot determine who controls the connection or prove that a VPN, proxy, or Tor is in use.