Confirm access before launch day
Know who can approve registrar, DNS and email changes, whether multi-factor authentication works and how to reach the provider if a change goes wrong.
Public DNS check
Free domain, DNS & email checker.
Review the public records most likely to cause launch-day website or business-email surprises. Get evidence and cautions without handing over registrar credentials or changing the domain.
Read the result correctly
A clean launch starts with an inventory—not a last-minute nameserver change.
The website, DNS host, registrar and email provider may be four different systems. Record the current evidence, identify who owns each account and change only the records required by the launch plan.
Preserve records that are not part of the move
A website launch rarely requires replacing every DNS record. Preserve mail, verification, subdomain and security records unless the responsible provider explicitly replaces them.
Test the public result and the real service
After a planned change, check public records again, open the website from outside the office network and test business email with the actual provider accounts.
Limits and next steps
Questions about this tool.
What does the Domain, DNS & Email Checker inspect?
It reads public A, AAAA, www, nameserver, MX, TXT, CAA, DS and DMARC records, then adds available registry-published registration details. It does not sign in to any account or change a record.
Can the checker prove that business email works?
No. Public MX, SPF and DMARC records reveal useful configuration evidence, but they cannot prove that a mailbox sends, receives, authenticates or avoids spam folders correctly.
Why does the report not give a single DNS score?
DNS and email choices depend on the provider and business use. A numeric score can make an optional record look like a universal failure, so the report shows evidence, review items and limitations instead.
Why is DKIM listed as requiring a selector?
DKIM records live at provider-specific selector names. Guessing a few common selectors can create false negatives, so confirm the selector with the email provider and check that exact record.
Does the checker prevent bots and abuse?
Yes. It uses same-site signed sessions, honeypots, minimum session age, per-visitor and per-domain rate limits, request caps and a global capacity limit. No email gate is required for legitimate visitors.
WANT A PERSON TO REVIEW THE RESULT?