Privacy
This site sets no cookies and runs no analytics. The domain you check never reaches the server that hosts this site.
When you check a domain
Your browser looks up the domain’s DNS records itself, over DNS over HTTPS, using six public DNS services. The domain you check and your IP address reach some of them. Usually two of them. If one does not answer, or answers with something the check cannot use, the next one in the list gets the lookup. The first time one of the two does not answer, a test lookup for example.com goes to all of them, and only those that answer it get the lookups that follow.
The two that usually get the lookups are Cloudflare and Google. They get them at the same time, so the check can compare their answers. The test lookup tells the services your IP address and nothing about your domain.
A service that answers a lookup sees the name looked up, which contains the domain you typed, and your IP address, as with any DNS lookup. Each lookup asks the service not to pass any part of your IP address on to the domain’s own DNS servers. Each service sets out what it keeps in its own privacy policy, linked from its name, in the order the check uses them:
A link to a result, such as /#example.com, keeps the domain, and a DKIM selector if there is one, after the # sign. Browsers keep that part of an address to themselves and do not send it to the server. The site stores nothing about a domain you check, on a server or in your browser. The email test is the exception: it keeps its result on the test server for 15 minutes, locked so that only your browser can read it, and your browser keeps the test in progress, as explained under Email test.
Email test
The email test gives you an address to send an email to. The test server that receives it runs on Cloudflare for this site. It reads the message headers to find the authentication results.
It keeps the SPF, DKIM and DMARC results, the domain in the From line, the domain of the bounce address (the envelope sender), the domain and the selector of each DKIM signature with its result, the time your email arrived and whether the receiving server’s ARC check passed.
The selector is the part of the key’s name that the sender picks, like s1 in s1._domainkey.example.com. If it cannot read the results, it keeps only the time your email arrived. It never keeps the body, the subject, the attachments, the full addresses or the IP addresses in the message. It stores that result locked with a key that only your browser holds, so nobody else can read it, this site and Cloudflare included. The test server deletes it 15 minutes after your email arrives. Getting an address stores only a public key from your browser, used to lock the result, until the address expires 15 minutes later.
Your browser’s requests to the test server go through Cloudflare, which receives your IP address like any web server. The test server uses it only to limit how many test addresses one internet connection can get, and how many times it can ask for a result, each minute.
Cloudflare also keeps its own records of each test email, with the sender, the recipient and the subject, so keep the subject plain. The site’s operator can see them in Cloudflare’s dashboard. Nobody opens them except to deal with abuse of the test. Cloudflare says its email metrics, which hold those details, are kept for 31 days, and it publishes no period for its activity log.
To explain the result, this page also looks up the DNS of the domains in the email: the one in the From line, the one in the bounce address and the one in each DKIM signature, the same way the checker does. Those domains and your IP address then reach the DNS services above, as when you check a domain.
While a test runs, your browser keeps it in the session storage of that tab: the test address, a code to read the result, the time it expires, how many times the page has asked for the result and whether the result has arrived. It also keeps the private key that opens the result in this site’s IndexedDB storage, set so that no script can read the key itself. That way the test survives a reload. Both are cleared when the test ends. If you close the tab first, the key is cleared the first time you open the email test more than 15 minutes after that test ended.
No cookies, no analytics
The site sets no cookies and runs no analytics or tracking scripts. Its pages, fonts and scripts all come from this site, and the only other servers your browser talks to are the DNS services above and, once you start an email test, the test server.
If you choose Light or Dark under Theme, at the foot of a page or in the menu on a phone, your browser keeps that choice in its own storage under the name theme, so the next page opens in the same mode. It is not a cookie, and your browser never sends it to this site or anywhere else. Choosing System deletes it, and so does clearing this site’s data in your browser.
Hosting
Firebase Hosting, a Google service, serves the pages. Like any web server, it receives the usual details of each request: your IP address, the address of the page without the part after #, and the headers your browser sends with every request. Google says Firebase Hosting uses those IP addresses to detect abuse and keeps them for a few months: Privacy and Security in Firebase.
Test domains
The test domains under badmail.dev are served by Cloudflare’s DNS. When you or a checker looks up one of those names, the lookup reaches Cloudflare through a DNS resolver, as with any domain. Cloudflare keeps analytics on those lookups for the zone’s owner for 31 days: each name looked up, its record type, the answer’s response code, the Cloudflare data center that answered, and the source IP address, which is the address of the resolver that asked, usually your DNS provider’s and not your own. The account that runs this site can read them in Cloudflare’s dashboard. It uses them only to count how often the test domains are looked up, and does not connect them with anything else. Cloudflare explains the data in DNS analytics.
Opening badmail.dev or www.badmail.dev in a browser also goes through Cloudflare, which sends you on to this site. On that visit Cloudflare sees your own IP address, and the account that runs this site can see it for 31 days in Cloudflare’s Security Analytics. The answer also asks your browser to report connection errors withbadmail.dev to Cloudflare for the next 7 days. Cloudflare says it does not keep the IP address of those reports: Network Error Logging.
Your rights under the GDPR
The Legal page names the data controller, with an email address for requests. Under the EU General Data Protection Regulation (GDPR), you can ask for access to your personal data, have it corrected or erased, and restrict its use. You can also object to the uses based on legitimate interest, described below, and receive the email test’s data in a form you can take elsewhere.
For the email test, the purpose is to show you the result of the test you ask for, and the legal basis is providing that service at your request (GDPR Article 6(1)(b)). The test server deletes the result 15 minutes after your email arrives. Cloudflare runs the test server and receives the email as a processor for this site, under its Data Processing Addendum.
The limits per IP address on test addresses and on requests for a result, Cloudflare’s records of each test email and Firebase Hosting’s request logs have another purpose: keeping the site working and stopping abuse. Their legal basis is that legitimate interest (GDPR Article 6(1)(f)), and you can object to it. The IP address of your requests is also covered by Cloudflare’s privacy policy.
Cloudflare and Google may handle this data outside the European Economic Area. They do so under the EU-US Data Privacy Framework and the European Commission’s standard contractual clauses, as their data processing terms say.
You can also complain to a data protection authority, such as the one where you live or work. In Spain, where this site is run, it is the AEPD.
Contact
The contact details for this site are on the Legal page.