OutboundFree tools
<- All tools
Free outbound tool

Free Email Deliverability Test: DNS & Copy Readiness

Check public MX, SPF, DMARC and optional DKIM records plus email copy. Get clear next steps, without an invented inbox-placement score.

live

Email deliverability test

Inspect public DNS and message text with clear next steps. Inbox placement and reputation are not measured.

Inbox placement: not measured. This checks public DNS records and limited text patterns. No email is sent. Reputation, blocklists, SPF authorization, DKIM signatures, DMARC alignment and PTR/TLS are not tested. There is no deliverability score.

Use a domain, not an email address or website URL. Subdomains are preserved. For DKIM, use the signing domain (d=) and selector (s=) from a sent message; they may differ from your visible From domain. Leave the selector blank if unknown.

Only domain and selector are sent to our server for public DNS lookups. Message text stays in this browser; do not paste secrets. This tool adds no input logging or storage.

DNS observations

DNS unchecked. No assumptions made about your domain.

mx — unchecked

Run a DNS check to inspect this record.

MX describes receiving mail routing, not permission to send. Missing MX alone does not prove sending failure; check reply handling with your provider.

spf — unchecked

Run a DNS check to inspect this record.

Inspect SPF syntax and recursive lookup limits in the SPF checker. Authorization needs the actual sending IP and envelope-from domain.

dmarc — unchecked

Run a DNS check to inspect this record.

Inspect the DMARC policy in the DMARC checker. A subdomain can inherit policy; this lookup only checks the exact domain. Message alignment is not tested.

dkim — unchecked

No selector checked. Find s= in a sent message’s DKIM-Signature header.

Use the signing domain (d=) and selector (s=) from a sent message. A published key does not verify a signature; a missing selector result says nothing about other selectors.

Limits: 998 subject characters and 50,000 body characters. HTML rendering, attachments and actual message headers are not inspected.

Content observations

Content unchecked — paste your message or load the example.

    These are transparent text checks, not AI analysis or a spam-filter simulation. No list of words can establish where this message will land.

    Plain-text report (select to copy)
    Email deliverability readiness — inbox placement and reputation NOT measured
DNS: unchecked
MX: unchecked. Run a DNS check to inspect this record. MX describes receiving mail routing, not permission to send. Missing MX alone does not prove sending failure; check reply handling with your provider.
SPF: unchecked. Run a DNS check to inspect this record. Inspect SPF syntax and recursive lookup limits in the SPF checker. Authorization needs the actual sending IP and envelope-from domain.
DMARC: unchecked. Run a DNS check to inspect this record. Inspect the DMARC policy in the DMARC checker. A subdomain can inherit policy; this lookup only checks the exact domain. Message alignment is not tested.
DKIM: unchecked. No selector checked. Find s= in a sent message’s DKIM-Signature header. Use the signing domain (d=) and selector (s=) from a sent message. A published key does not verify a signature; a missing selector result says nothing about other selectors.
Content: unchecked; 0 words; 0 HTTP(S) links; 0 subject characters.
No email sent. SPF authorization, DKIM signature, DMARC alignment, PTR/TLS, blocklists and recipient placement are not tested.

    What to check next

    1. Investigate DNS observations with the SPF record checker, DMARC policy checker and DKIM selector checker. Don’t switch to enforcement until legitimate senders and alignment are verified.
    2. Review message findings with the email copy spam checker. Preview the final merged message and confirm accurate sender identity and recipient consent.
    3. Send your actual campaign through your normal sender to test inboxes you control, or a seed-mail testing service. Inspect received authentication headers and placement per provider. A sample result still cannot guarantee placement for real recipients.
    4. If authenticated mail still struggles, assess bounces, complaints, sending patterns and reputation before selecting tools to investigate low deliverability.

    Sources checked August 31, 2026: Google’s sender requirements and Amazon SES inbox placement testing documentation.

    How to get more from this tool

    What this deliverability test checks

    Run a public DNS inventory for your exact domain and optional DKIM selector. Review plain-text subject/body observations separately. Published means a record was returned, not that authentication passed. SPF evaluation, key validation and DMARC alignment need further investigation.

    How to interpret the results

    Unchecked means no lookup was run. Unavailable means the lookup failed or timed out; retry before changing records. Missing means no matching record returned at that hostname. Published records still need validation. DMARC p=none is monitoring, not an authentication failure. There is no aggregate score.

    Readiness is not inbox placement

    For example, SPF and DMARC may be published while DKIM remains unchecked because no selector was supplied. That is an incomplete inventory, not a low deliverability score. Even complete authentication does not measure reputation, complaints, list quality, delivery or spam-folder placement. Send actual test mail through your normal provider and inspect received headers and placement separately.

    Frequently asked questions

    Does this email deliverability test send a test email?

    No. It looks up public DNS and inspects limited text patterns locally. It does not send seed mail, access mailboxes, test blocklists or measure inbox placement or reputation.

    Why is there no deliverability score?

    DNS record presence and content heuristics cannot establish a probability of reaching an inbox. Separate observations show what was checked, what failed, what is missing and what remains unknown.

    What if I do not know my DKIM selector?

    Leave it blank. DKIM remains unchecked. Find s= and the signing domain d= in a sent message’s DKIM-Signature header or ask your provider. Missing one selector is not proof that the entire domain lacks DKIM.

    Can my email still land in spam with published authentication records?

    Yes. Records do not establish successful message authentication. Even authenticated mail can be filtered based on reputation, complaints and other signals. Inspect actual received messages and monitor provider feedback.

    Related free tools

    Email spam checker

    Review plain-text email with highlighted copy notes, unresolved tokens and practical next steps.

    DMARC checker

    Live TXT lookup with plain-English interpretation of p=none, quarantine, reject, rua, and pct.

    DKIM checker

    Selector-specific DNS lookup with public-key syntax checks and clear next steps.

    SPF record checker

    SPF syntax checks, duplicate-record detection and bounded recursive include/redirect inspection.