Domain History Report
The complete historical WHOIS/RDAP record for a single domain — every snapshot we hold, the ownership-change timeline, and registrar history, delivered as a downloadable report.
Look up a domainLive public DNS
Look up A, AAAA, MX, NS, TXT, CNAME, SOA, CAA and SRV records, then check SPF, DKIM and DMARC before a migration, a mail outage, or a certificate change.
The same lookups you would run with dig or a WHOIS client, returned in a table you can share.
Registrant, registrar, and registration dates for any domain.
Structured registration data via the modern WHOIS successor.
A, AAAA, MX, TXT, NS and other records for any domain.
See which domains a given nameserver hosts.
Ownership and network data for any IPv4 or IPv6 address.
How much historical WHOIS/RDAP we hold for a domain.
Check whether a website is reachable right now.
Browse domain registrars and the domains they manage.
For researchers, investigators, and site owners who need more.
The complete historical WHOIS/RDAP record for a single domain — every snapshot we hold, the ownership-change timeline, and registrar history, delivered as a downloadable report.
Look up a domainWatch the domains that matter: uptime, DNS changes, and TLS-certificate expiry, all from one setup. We probe each domain live so you see exactly what we see, then notify you the moment a site goes down, its DNS shifts, or its certificate nears expiry. Up to 10 domains.
Start monitoringParsed WHOIS, normalized RDAP, and DNS and TLS-certificate history as JSON over HTTPS. Start on the free tier, no card required.
Explore the APIDNSFetch is a free DNS lookup tool for website owners, developers, and email administrators. Enter a domain, choose a record type, and you get the same public answers a resolver would: host, TTL, and value. There is no account, no install, and no daily quota beyond a light per-IP rate limit that keeps the service fair.
Every query runs on the server. That matters because a lookup from your laptop can lie — browsers, operating systems, and recursive resolvers all cache. DNSFetch talks to DNS on your behalf and shows you what is published right now, with a five-minute cache so repeat clicks stay snappy without hammering upstream nameservers.
DNS is invisible until it is not. A site that will not load, mail that vanishes, a certificate that will not issue, a CDN that still points at last year’s host — those are DNS problems more often than application problems. Use DNSFetch to confirm an A record after a hosting move, to see whether MX records still list the old provider, or to check that an SPF include for a new ESP actually landed.
If you are rolling out DMARC, start with the SPF & DMARC checker, then read the email authentication guide. If you only need one address, the dedicated A and AAAA tools keep the noise down.
The full list, with examples, lives in DNS record types.
There is no global push. Resolvers keep the old answer until the TTL expires, and some caches round up. Plan on minutes to hours for a low TTL, and up to 24–48 hours if the previous TTL was a day or more. Details in DNS propagation explained.
Usually a cache still holding the previous value, or the change was saved in the wrong zone (www vs apex, or a nameserver that is not actually authoritative). Check NS records first, then the record itself.
Yes. No registration. A per-IP rate limit protects the resolver path so one script cannot crowd out everyone else.
Short-lived query caches (a few minutes) and ordinary web logs. We do not publish a search history. See the Privacy Policy.
Original explainers on DNS, mail authentication, TTL, and the errors that waste an afternoon.
Open the learn hub