Privacy
Privacy statement
When you investigate a domain, we retrieve its public settings from external services. Those services therefore receive information such as the domain name. DNS Radar has no accounts, advertising profiles or database of scan reports. Below, each function explains what stays on your device, what is sent and what may appear in temporary logs.
Last updated: 15 November 2026
Who operates DNS Radar
DNS Radar is operated by Joris de Vaan. This statement applies to the website, domain scan and separate tools on dnsradar.eu. We use received data to run the function you start, protect the service and investigate technical faults. We do not sell the data or use it for targeted advertising, a mailing list or a customer profile.
What stays on your device
Your browser remembers up to six recently scanned domains. For up to six domains it also saves a small part of the latest comparable scan, so the next report can show changes. This includes the email sender policy (DMARC), DNS security (DNSSEC) and receiving mail servers (MX), with the domain, scan time, scan route and selected DNS services. Full reports are not saved. This data is not synchronised or sent to a first-party database.
Use ‘Clear scan history’ below a report to remove the comparison data. Clear this site's data in your browser to remove recent domains as well.
The Mail headers tool parses the pasted technical email header in your browser and does not save it. Only the extracted domains from the visible sender address (From) and return address (Return-Path) are checked through public DNS services. The part before @, subject and message body are not sent. A blacklist check uses a selected or detected IP address only when you request it.
What data the tools send
To look up a DNS setting, the tool sends the name being queried and the type of record. The public DNS service that answers is called a resolver. Depending on the tool, we use Cloudflare, Google, DNS4EU, IIJ or AliDNS. For reverse DNS, the IP address is encoded in the name we query. The Mail headers tool queries only the extracted From and Return-Path domains.
For domain registration details, we send the domain name to the public service of the relevant registry or registrar. This uses the registration protocol RDAP.
If you select ‘Use my IP addresses’ in Reverse DNS, your browser tries to retrieve your IPv4 and IPv6 addresses through connections to our Cloudflare Worker. The Worker reads the connecting IP address from each request. When you start a blacklist check, we query names containing the selected IPv4 address through Cloudflare DNS. These names belong to the blacklists used (DNSBL). The pasted email header is not sent.
When our server helps
If your browser cannot reach a DNS or registration service directly, our server can make the query instead. It runs at Cloudflare and is called a Worker. The Worker receives what your task needs, such as the domain, scan mode, record type and any manually entered DKIM key names.
During a full scan, the Worker may also retrieve the public rules for secure mail transport: the MTA-STS policy file. The application does not write the request or scan report to its own database, KV store, object storage or other application storage.
How we limit abuse
Cloudflare sees your public IP address when you connect to the website or our server. The server uses that address to limit requests per user or network.
The protected scan, registration and DNS routes also use Cloudflare Turnstile to check for automated or abusive traffic. Your browser sends a short-lived token for this check. DNS Radar asks Cloudflare Siteverify to validate it together with the request IP. Cloudflare processes browser and network signals for this check.
What temporary logs may contain
We use Cloudflare Workers Observability to investigate faults and monitor availability. Cloudflare may therefore keep technical data about a server request: when the Worker ran, request and response metadata, errors and technical context.
Workers Logs have a maximum retention period of seven days here. Cloudflare then removes them under the configured service limits. DNS Radar does not deliberately log the domain from the request body or the full scan report. Technical connection data and the requested route may still appear in platform logs. External DNS services and registries set their own logging and retention periods.
Web Analytics and cookies
We use Cloudflare Web Analytics for aggregated visitor and performance statistics. This measurement uses no analytics cookies. Cloudflare states that the source IP is discarded at the nearest data centre and is not stored in the performance measurement dataset (RUM).
DNS Radar does not set advertising or tracking cookies itself. Cloudflare may use strictly necessary cookies or similar browser storage for network security and Turnstile. Cloudflare's privacy and cookie policies apply to that processing.
External services and processing outside the EEA
An external service receives only the requests sent to it. These services include Cloudflare, Google, DNS4EU, IIJ, AliDNS, domain registration services (RDAP) and blacklist operators (DNSBL).
Depending on the service and network route, processing may take place inside or outside the European Economic Area, including in the United States, Japan and China. DNS Radar does not choose which data centre handles a DNS query. Routing to services that share one address across multiple locations is called anycast. Each provider's privacy terms govern processing, transfer and retention.
Choices you control
You can select ‘Measure in my browser only’ for a domain scan. Our server will then not help with the scan. Where a tool supports it, you can choose a DNS service yourself. You can also skip ‘Use my IP addresses’ and the blacklist check.
Your browser, firewall or ad blocker may block external DNS requests and the Turnstile check. Parts of the scan may then fail. DNS and domain registration are public systems: do not put confidential information in a domain name or DKIM key name. Check an email header before pasting it too. It may contain personal data, even though the full header stays on your device during this analysis.
Changes to this statement
We update this statement when the data DNS Radar sends or stores changes, or when the external services we use change. The date above shows when the text was last changed materially. After a relevant technical change, we update this page as soon as possible. A wording change alone does not change which data the tools process.