Lookup inputs
DNS names and IP addresses entered into lookup forms are sent to DNS Look’s server and then to the resolver or RDAP service needed to answer the request. DNS and public registration data are public by design, but a lookup can still reveal what a visitor is investigating.
Analytics
DNS Look uses Google Analytics 4 to understand site usage and improve its tools when analytics is enabled. Lookup-success events describe the tool and record type but do not include the domain or IP address entered. Google may process device, browser, interaction, and approximate-location information under its privacy policy. DNS Look does not require an account for lookups.
IP address tool
The “What is my IP?” response is marked private and is not publicly cached. Approximate location fields are taken from hosting-network request headers when available. On localhost or a private network, where the server can see only a private address, the browser requests its public address from ipify. DNS Look does not send the address to a separate geolocation API.
Upstream services
DNS queries may be handled by Cloudflare or Google Public DNS. Registration lookups are sent to the RDAP operator selected by IANA’s bootstrap registry. Local public-IP fallback requests are sent to ipify. Those operators have their own logging, retention, and privacy practices.
Use of results
Do not enter secrets, passwords, private keys, or confidential internal hostnames. Results should be treated as a snapshot of public data at the time of the request.