FAQ

Answers to common questions about where DNS Coffee's data comes from, how to request its removal, and how to get the most out of the site.

Data Sources

All data on DNS Coffee comes from publicly available sources. Most of it is derived from public zone files, DNS queries to public nameservers, and public domain lists.

API Access

DNS Coffee offers a private, authenticated REST API. See api.dns.coffee for the documentation and how to request access.

Automated scraping of dns.coffee is not permitted. If you need data in bulk or programmatically, use the API instead.

Tips and Tricks

• The quick lookup path /q/<name> sends you straight to a domain, nameserver, IP, or zone. If the term matches more than one thing, or nothing at all, it drops you on the search page instead. For example, /q/example.com.
• Every object has its own URL you can link or bookmark directly: /domains/<name>, /nameservers/<name>, /ip/<address>, and /zones/<name>.

Takedown Requests

The records here are already public, so most takedown requests do not apply. For reference:

• DMCA. There is no copyrightable content on DNS Coffee. All data is derived from publicly available DNS records.
• GDPR and CCPA. There is no Personally Identifiable Information (PII) on DNS Coffee. All data is derived from publicly available DNS records.
• Security. DNS records are public. Every record on DNS Coffee can be retrieved by sending a DNS query to the authoritative nameservers. If you have a DNS record you would rather not be public, remove it from your domain's public nameservers.

If you believe your case still warrants review, submit a request to [email protected] with your reasoning and enough supporting evidence to establish that you own the records in question. Each request is reviewed, and we may take action when it is warranted.