Check whether a domain is reachable and inspect DNS records such as MX, A, AAAA, SPF, DMARC, BIMI and TXT.
Use this page to inspect the DNS setup of a mail domain, including MX records, SPF, DMARC, BIMI and raw TXT entries.
A domain can look active in a browser but still have incomplete email configuration. This domain checker helps you review whether a domain is reachable, whether it publishes mail routing through MX records, and whether important email authentication records are present.
The result is useful when you want to check a domain before sending email, onboarding a customer domain, reviewing a signup domain, investigating deliverability problems, or comparing DNS settings for known providers.
A domain check becomes more useful when the result is read as a group of signals instead of a single pass or fail value. A and AAAA records usually describe whether the domain points to web or host infrastructure. MX records describe where email for the domain should be delivered. SPF, DMARC and BIMI describe how the domain presents itself to receiving mail systems and compatible inbox providers.
That distinction matters because a domain can be reachable without being ready for email. For example, a company website may load correctly because A records exist, while the same domain has no MX records and therefore does not look prepared to receive messages. The opposite can also happen: a domain can be configured mainly for email and publish MX records even when the root website is not important.
For deliverability and fraud prevention, the authentication records are often just as important as reachability. SPF helps identify authorized sending systems, DMARC publishes a policy for authentication failures, and BIMI can support visible brand identity when the rest of the setup is strong. Reviewing these records together gives a clearer view of whether a domain looks technically consistent and trustworthy.
The tool reads public DNS records and summarizes the signals that matter most for email and basic domain reachability.
MX records show which mail servers receive email for the domain.
A and AAAA records show whether the domain points to IPv4 or IPv6 hosts.
SPF helps receiving mail systems decide which servers may send email for the domain.
DMARC publishes a policy for handling messages that fail email authentication.
BIMI can publish brand logo information for compatible inbox providers.
TXT records expose additional DNS configuration such as SPF and service verification.
Open an example domain result to see how DNS, MX, SPF, DMARC and BIMI signals are presented.
Review DNS and email authentication signals for a large public email provider.
Inspect the DNS setup of a widely used mailbox and Microsoft email domain.
Check domain reachability and email-related DNS records for a developer platform.
Review the DNS and mail configuration signals of a commerce platform domain.
Inspect DNS and authentication records for an infrastructure provider domain.
Check email-related DNS records for a known email marketing platform domain.
If you want to review common provider families instead of a single domain, these links take you straight to the relevant validation pages.
Useful for Google Workspace and consumer Gmail addresses.
gmail.com, googlemail.com
Useful for Microsoft 365 and legacy Hotmail-style addresses.
outlook.com, hotmail.com, live.com +1
Useful for long-standing consumer Yahoo inboxes.
yahoo.com, yahoo.co.uk, yahoo.de
Useful for Apple ecosystem inboxes and legacy Apple aliases.
icloud.com, me.com, mac.com
Useful for privacy-focused inboxes and alias-style addressing.
proton.me, protonmail.com, pm.me
Useful for DACH-region consumer addresses across GMX domains.
gmx.com, gmx.net, gmx.de +2
No. A domain check can show whether the domain publishes DNS and mail-related records, but it cannot prove that a specific mailbox exists.
MX records tell other mail systems where to deliver email for the domain. Missing MX records can indicate that email reception is not intentionally configured.
Yes. A domain can have A or AAAA records for website traffic while still missing MX records or email authentication records.