Free tool
A DNS checker for sending domains. Enter a domain to look up the MX, SPF, DKIM and DMARC records your cold email depends on, plus its A, AAAA, TXT and NS records, and see which email authentication records are missing.
Want to see what is published? Use this checker. Want a pass or fail verdict on whether SPF, DKIM, DMARC and MX are set up correctly? Use the DNS record validator.
Automate everything
Inboxkit InfraGuard rechecks your DNS records, blacklists and bounces every 6 hours and alerts you when something breaks.
Walkthrough
A 39-second walkthrough of the records that matter for cold email: MX tells the world where replies go, SPF lists who may send as you, DKIM proves the email came from you, and DMARC tells inboxes what to do when those checks fail. In the demo the domain has no DMARC, so the checker recommends adding one.
Step 1
Type the domain you send cold email from, such as yourdomain.com. A pasted https:// or trailing slash is stripped. To look at a subdomain, enter it in full.
Step 2
The checker queries each record type and the email subdomains (_dmarc and the DKIM selectors) in one run.
Step 3
The Email Authentication Records block shows a check or a cross for SPF, DKIM and DMARC, with the published value. MX records are listed with their priority.
Step 4
Recommendations name each missing email record. Publish it at your DNS host, wait for the TTL to pass, and click New Check.
One check reads every record below. The four email records come first because they decide whether your mail is accepted and authenticated. The rest describe the domain itself.
| Record | Where it looks | What you see |
|---|---|---|
| MX | yourdomain.com | Each mail server with its priority. A warning if there are none, because replies cannot be delivered. |
| SPF | TXT at yourdomain.com starting with v=spf1 | The full SPF record, or a cross if none is published. |
| DKIM | TXT at google, default, selector1, selector2, dkim and mail._domainkey.yourdomain.com | Each selector that returned a public key. |
| DMARC | TXT at _dmarc.yourdomain.com starting with v=DMARC1 | The full DMARC policy, or a cross if none is published. |
| A and AAAA | yourdomain.com | The IPv4 and IPv6 addresses the domain points to. |
| TXT | yourdomain.com | Every TXT record, including Google and Microsoft verification values. |
| NS | yourdomain.com | The name servers, which tell you which DNS host to log in to for changes. |
The checker shows what is published, not whether it is correct. It does not count SPF lookups, parse DMARC tags or measure DKIM key length. For that, run the DNS validator.
Here is a complete set for a domain sending through Google Workspace. Your values change with your provider, but every sending domain needs the same four records.
| Type | Host | Value | Job |
|---|---|---|---|
| MX | @ | 1 aspmx.l.google.com | Routes replies to your inbox. Google also gives you alt1 to alt4 backups. |
| TXT | @ | v=spf1 include:_spf.google.com ~all | SPF: lists the servers allowed to send as you. |
| TXT | google._domainkey | v=DKIM1; k=rsa; p=MIIBIjANBgkq... | DKIM: the public key that proves you signed the message. Copy it from your provider. |
| TXT | _dmarc | v=DMARC1; p=quarantine; rua=mailto:dmarc@yourdomain.com | DMARC: tells inboxes what to do when SPF or DKIM fails, and where to send reports. |
Most sending tools also ask for a custom tracking domain, a CNAME on a subdomain such as track.yourdomain.com. This checker does not display CNAME targets, so confirm that one at your DNS host. For step-by-step setup, follow the SPF setup guide and the DKIM setup guide, and build your DMARC record with the DMARC generator.
No MX records found
The domain cannot receive mail, so replies to your cold emails bounce. Add the MX records your email provider gives you.
Add SPF record
No TXT record at the root starts with v=spf1. Publish one SPF record that includes every service that sends as you. If the TXT list shows two v=spf1 records, merge them into one: receivers treat two as an error.
Configure DKIM signing
None of the six selectors returned a key. Turn on DKIM in your email provider and publish the key it gives you. If DKIM is already on, your selector is a different one: check it in the DKIM checker or the DNS validator.
Implement DMARC policy
Nothing at _dmarc.yourdomain.com starts with v=DMARC1. Start with p=none and a rua address so you receive reports, then move to quarantine once SPF and DKIM pass.
Consider adding CAA or AAAA records
CAA limits which certificate authorities can issue SSL certificates for the domain, and AAAA adds IPv6 for the website. Neither is needed to send cold email.
Related
Validate your SPF records and ensure proper email authentication.
Verify DKIM signatures and public key configuration.
Pass or fail validation of SPF, DKIM, DMARC and MX records.
Analyze your domain's email deliverability health score.
Analyze DMARC policies and email authentication alignment.
Check if your emails are likely to be marked as spam.
FAQ
An email DNS checker looks up the DNS records a sending domain depends on and shows them in one place. This one reads the MX, SPF, DKIM and DMARC records that decide whether your mail is accepted and authenticated, plus the A, AAAA, TXT and NS records at the root of the domain, and flags any email record that is missing.
Four. MX records tell other servers where replies to your domain go. An SPF record lists the servers allowed to send as your domain. A DKIM record publishes the public key that proves a message was signed by you. A DMARC record at _dmarc.yourdomain.com tells inboxes what to do when SPF or DKIM fails. Without them, Gmail and Outlook treat cold email from the domain as unauthenticated.
Enter the domain in the checker above and click Check DNS Records. It queries each record type and lists what is published. From a terminal you can run the same lookups one at a time: dig MX yourdomain.com, dig TXT yourdomain.com for SPF, dig TXT _dmarc.yourdomain.com for DMARC and dig TXT google._domainkey.yourdomain.com for a DKIM key with the selector google.
DNS verification is how a provider such as Google Workspace or Microsoft 365 confirms you own a domain: it gives you a TXT record (for example google-site-verification=...) or a CNAME to publish, then looks for it. The checker lists every TXT record at the root of the domain, so you can confirm the verification value is live before you click verify in the provider's console.
DKIM keys live at selector._domainkey.yourdomain.com, and a DNS lookup only finds a key if it knows the selector. This checker tries six common selectors: google, default, selector1, selector2, dkim and mail. If your provider uses a different one, look it up in the DKIM checker with your selector, or run the DNS validator, which tries 43 common selectors.
Each MX record has a priority number and a mail server hostname. Lower numbers are tried first. Google Workspace uses aspmx.l.google.com at priority 1 with alt1 to alt4.aspmx.l.google.com as backups. Microsoft 365 uses a single record such as yourdomain-com.mail.protection.outlook.com at priority 0. If the checker finds no MX records, mail sent to the domain, including replies to your cold emails, cannot be delivered.
Yes. The checker lists the A records (IPv4 addresses) and AAAA records (IPv6 addresses) for the domain you enter, and the Website tile shows whether any A record exists. To check a subdomain, such as a tracking domain, enter the full subdomain. Note that the results show the addresses a name resolves to, not the CNAME target behind them.
The DNS checker is a lookup: it shows the raw records published on your domain, across email and website record types, so you can see what is there. The DNS validator is a pass or fail test: it runs SPF, DKIM, DMARC and MX against the rules receivers enforce, such as a single SPF record and no more than 10 DNS lookups, and returns Valid, Invalid or Not found with each issue. Use the checker to see your records and the validator to confirm they are correct.
Most changes are visible within minutes to a few hours, but they can take up to 48 hours. The delay depends on the TTL (time to live) of the old record, since resolvers cache it until the TTL runs out. If the checker still shows an old value, wait for the TTL to pass and run the check again.
Get started
Inboxkit InfraGuard rechecks your DNS records, blacklists and bounces every 6 hours and alerts you when something breaks.