How to Use Every Domain Tool

Availability is read from RDAP where a registry publishes it and falls back to classic WHOIS where it does not. A few registries rate-limit hard, so if one extension comes back unknown while the others resolve cleanly, that is usually the reason — trying again a few seconds later normally clears it.

Empty contact fields are normal rather than a failed lookup. Since GDPR, most registries and registrars replace registrant names and addresses with a privacy service, and what you get back is a forwarding address at best.

No MX record does not mean mail is broken — it means mail is being delivered to the A record instead, which is almost never what anyone intended. If you expected MX records and there are none, that absence is the finding.

A name mismatch is as fatal to a visitor as an expiry. A certificate issued for example.com does not cover www.example.com unless www appears in the SANs, and a wildcard such as *.example.com covers one level of subdomain but not the bare domain itself.

Geolocation tells you where an address is registered, not where the hardware is. On anycast networks the registered country and the machine actually answering you are routinely on different continents.

If the answer looks wrong for a site you know is local, the site is almost certainly behind a CDN and you are seeing the edge network rather than the origin. Comparing against the A record in DNS Lookup will show you what is really in front of it.

Results are cached for fifteen minutes per keyword-and-extension pair, so re-running the same search is instant. Change either the keyword or the extensions and you get a fresh pass.

Only scan hosts you own or have written permission to test. Scanning someone else's infrastructure is potentially illegal depending on where each of you is, and it will certainly appear in their logs.

The lists do not carry equal weight. A Spamhaus ZEN listing will visibly damage delivery; a listing on an obscure zone almost no receiver checks may not be worth the paperwork. Work the significant ones first — and fix whatever caused the listing before requesting removal, or you will simply be relisted.

This is passive. It resolves names; it does not probe or attack what it finds. A host appearing here only means DNS answers for it — check what is actually served there before treating it as exposed.

Propagation is not a process that runs somewhere — it is caches expiring. How long it takes is decided by the TTL that was on the old record, which is why dropping the TTL a day before a planned move is what actually makes the cutover fast.

A parent/child mismatch is the classic cause of a domain that works intermittently. If you changed nameservers at the registrar but the child still lists the old pair — or the reverse — that is your fault condition, and it is fixed at whichever end is stale.

A thousand names is fifty batches, so give it time. The run deliberately lifts the script timeout — what will interrupt it is closing the tab, not the length of the list.

This only reaches public resolvers. Your own machine, your router and your ISP each keep a separate cache that nothing on the internet can clear on your behalf — those need flushing locally, or simply need time.