IP LensHow to read an IP address, location and ASN
An IP lookup helps you understand the address a service sees and the network associated with it. It cannot establish who is using that address or exactly where they are. This guide explains how to gather useful evidence without reading too much into a result.
Read the guide: How to read an IP address, location and ASN →Check DNS records and understand the answer
A useful DNS check starts with a specific question: which address should this name resolve to, where should mail go, or has a recent record change become visible? Choose the relevant record type before interpreting a response.
Read the guide: Check DNS records and understand the answer →Read WebRTC candidates and browser information carefully
IP Lens provides two different checks: WebRTC candidate gathering and a local summary of browser properties. Use them for a specific diagnostic question. Neither is a universal privacy score or a certificate of anonymity.
Read the guide: Read WebRTC candidates and browser information carefully →Check IPv4, IPv6 and browser HTTP latency
A connection can behave differently over IPv4 and IPv6, and a successful address lookup does not explain every slow page. These separate checks help you gather a few useful observations before changing your setup.
Read the guide: Check IPv4, IPv6 and browser HTTP latency →Why is my IP location wrong?
Your connection works, but an IP lookup places you in another city or region. Start by separating a network-exit estimate from the position of your device; changing a city label alone cannot establish which route your traffic uses.
Read the guide: Why is my IP location wrong? →VPN connected, but websites still see my IP
A VPN connection indicator describes the app’s state. To investigate the route used by a browser request, compare actual observations while keeping the browser, network and address family consistent.
Read the guide: VPN connected, but websites still see my IP →Check DNS after changing your hosting
A migrated site can reach the old server, work only on some networks, or fail for one hostname. Keep the expected new targets from your host nearby and inspect one name and record type at a time.
Read the guide: Check DNS after changing your hosting →IPv4 works, but IPv6 does not
A working IPv4 connection can coexist with unavailable IPv6. Determine which observation failed before deciding whether the cause is service availability, a route, browser filtering or a particular website.
Read the guide: IPv4 works, but IPv6 does not →WebRTC test shows no results: what does it mean?
An empty candidate list is a limited observation. Before describing it as safe or broken, check whether the browser supports the test, whether gathering finished and whether STUN traffic can reach its destination.
Read the guide: WebRTC test shows no results: what does it mean? →Before you start
Run only the checks you need, use targets you are authorized to investigate, and record the time and data source when comparing results. These guides describe the current browser tools, including their limits.
For storage and external requests, read the Privacy Policy. For quick answers, visit the FAQ.