Email deliverability
Email deliverability check — SPF, DKIM, DMARC, MX, BIMI
See if a domain is configured to reach the inbox. We query SPF, DKIM (on common selectors), DMARC, MX, and BIMI in parallel and give you a 0–100 score plus a per-record breakdown. Free, instant, no login.
What this email deliverability check does
Email deliverability is whether your messages reach the inbox — not the spam folder, not a bounce, not a silent drop. Receivers like Gmail, Outlook, and Yahoo check a chain of DNS records on every incoming message: SPF says which servers are allowed to send for you, DKIM proves the message wasn't tampered with, and DMARC tells the receiver what to do when something fails. This tool queries all five of those public records plus MX (where your incoming mail goes) in one shot and gives you a single score and a per-record diagnosis. No email is sent, no credentials are needed, and nothing leaves your browser except the domain you typed.
Querying DNS records…
Use a bare domain like example.com — no protocol, no path.
How email deliverability checking works
When a receiving mail server gets a message claiming to be from your domain, it looks up four public DNS records in parallel: SPF (TXT at the apex), DKIM (TXT at a selector under _domainkey), DMARC (TXT at _dmarc), and MX (where to deliver mail to you). This tool runs the same lookups your recipients run, and scores the configuration from 0 to 100 based on what's present and whether each record is configured for strict enforcement. A score of 80+ means your domain is properly authenticated; below that, the issues list tells you exactly what to add or change.
SPF, DKIM, DMARC, MX, BIMI — what each one does
SPF (Sender Policy Framework) is a TXT record at the apex that lists the IP addresses and servers allowed to send mail for your domain. Receivers reject mail that arrives from a server not on the list. DKIM (DomainKeys Identified Mail) is a cryptographic signature added to outgoing messages; the matching public key is published as a TXT record at <selector>._domainkey.yourdomain.com. DMARC (Domain-based Message Authentication, Reporting, and Conformance) ties SPF and DKIM together with a policy of none, quarantine, or reject. MX records tell other servers where to deliver mail sent to your domain. BIMI (Brand Indicators for Message Identification) is an emerging standard that lets you attach your brand logo to authenticated messages.
Frequently asked questions
What is email deliverability?
Email deliverability is whether your messages reach the inbox — not the spam folder, not a bounce, not a silent drop. It depends on a chain of DNS records (SPF, DKIM, DMARC) and the reputation of the IP addresses you send from. Receivers like Gmail, Outlook, and Yahoo check these records on every message and use them to decide whether to accept, flag, or reject the mail.
What does SPF do?
SPF (Sender Policy Framework) is a DNS TXT record that lists the IP addresses and servers allowed to send mail for your domain. When a receiver gets a message claiming to be from you, it checks your SPF record. If the sending server is not on the list, the message is treated as forged. The record looks like v=spf1 ip4:192.0.2.0/24 include:_spf.google.com -all. The -all at the end means "only these sources are allowed, reject everything else" — that is the strict setting.
What does DKIM do?
DKIM (DomainKeys Identified Mail) is a cryptographic signature that proves the message was not altered in transit and was sent by a server holding the private key. The matching public key is published as a DNS TXT record at <selector>._domainkey.yourdomain.com. Common selectors include default, google, k1, s1, s2, mailgun, and sendgrid.
What does DMARC do?
DMARC ties SPF and DKIM together and tells receivers what to do when a message fails. A DMARC record at _dmarc.yourdomain.com can be set to p=none (monitor only), p=quarantine (send failing mail to spam), or p=reject (refuse failing mail outright). Without DMARC, receivers have no instruction — they may accept, flag, or reject forged mail however they like.
Why does my DKIM record not show up?
This tool probes the most common DKIM selectors (default, google, k1, s1, s2, mailgun, sendgrid, and a few others). If your mail server uses a custom selector, it will not be found. To find your actual selector, log into your mail server or ESP and look at the DKIM configuration, or send yourself a real email and inspect the DKIM-Signature header — the part before .dkim in the d= tag is your selector.
Will this tool send a real test email?
No. It only reads public DNS records (TXT and MX) for the domain you enter. It does not send mail, does not contact the mail server, and does not require any credentials.