Privacy

This site reads the request IP address to display it and selected request headers when you open the headers tool. An IP submitted through the IP lookup form appears in the resulting page URL; avoid sharing it if you consider it private.

The PHP application creates no accounts, cookies, visitor sessions or saved user lookup history. No advertising or analytics scripts run here.

To retrieve network and approximate location details, the server sends the public IP address being looked up to BigDataCloud. This can be your connection address on the homepage or an address you submit. ASN lookups send the requested autonomous system number to the same provider. Browser headers and cookies are not sent with these lookups. Private, loopback and other excluded addresses are not sent. See BigDataCloud's privacy policy.

A small local cache can retain queried IP addresses, ASN numbers and normalised network facts for up to 3600 seconds, and no-result entries for up to 60 seconds. Expired entries are removed on the next eligible lookup; files may remain on disk while the application is idle. The cache is not linked to individual visitors and does not store raw provider responses or credentials.

The application stores an aggregate daily request count and a retry time to limit provider usage. IP and ASN lookups share this allowance. Reverse DNS uses a separate cache and does not consume this allowance.

When you submit the reverse DNS form, the server sends the public address as a reverse DNS query to Google Public DNS over HTTPS. Google sees the address being queried and the server's connection address. Your browser headers, cookies and our BigDataCloud API key are not forwarded. Client-subnet sharing is disabled. Private and reserved addresses are not queried. See Google Public DNS privacy information.

The separate reverse DNS cache stores only a hashed lookup key, returned hostnames and expiry times. Successful results expire within their DNS lifetime, capped at one hour. Confirmed missing records may be cached for up to one minute, bounded by the DNS negative lifetime. Resolver failures are not stored as missing records; a shared 30-second retry delay limits repeated failures. Expired entries are removed on a later lookup and may remain on disk while idle.

The hosting server may retain diagnostic logs containing IP addresses and requested URLs when errors occur. These logs are separate from the lookup cache and are used to investigate service problems.

Copy controls use your browser clipboard only when you press the button. External links, including rdap.ai, lead to independently operated services.