Skip to content
Start with 100 free verification credits
Qualisend
Free tool

Test your email deliverability.

Send one real email to a one-time address and see exactly what a receiving mail server sees: whether SPF, DKIM, and DMARC pass and align, whether the sending IP has reverse DNS or sits on a blocklist, whether the connection used TLS, and what in the content might trip a filter. One score, fourteen checks, no account.

We give you a one-time address. Send it a real message from the system you want to test and get a full deliverability report the moment it lands: SPF, DKIM, DMARC, sending-IP reputation, TLS, and content checks.

We keep the analysis for 24 hours and never store the message body.

What the test checks

The report covers the four layers a mailbox provider scores before deciding where a message lands. Authentication: SPF, DKIM, and DMARC, evaluated against your real sending server and checked for alignment with the From domain, the same way Gmail and Yahoo do under the sender requirements. Sending server: the IP's reverse DNS (PTR) and forward confirmation, a lookup against five major DNS blocklists, and whether the SMTP session used TLS. Content: an HTML part with a plain-text alternative, image-to-text balance, an empty or ALL-CAPS subject, a Reply-To on a different domain, a List-Unsubscribe header with one-click support, and common spam trigger phrases. Message: total size and attachments.

How to read the score

The score starts at 100 and each failing check subtracts a weighted amount: a DMARC failure or a blocklist listing costs the most, a missing plain-text part or a shouting subject only a few points. 90 and above is excellent, 75 to 89 is good, 50 to 74 needs work, and below 50 means filters have real reasons to distrust the message. Fix the authentication and server rows first; they decide whether the message is trusted at all. The content rows are the second pass, the things that separate the inbox from the promotions tab or the spam folder once trust is established. Build any missing records with the SPF record generator and the DMARC record generator, then run the test again.

How it differs from the free email checker

The free email checker and the domain health check look outward: they read what a domain publishes in DNS and whether an address exists. This test looks inward, at a message you actually sent, so it catches what DNS alone can't: a DKIM signature that breaks because a template was rewritten in transit, SPF that passes for the envelope domain but doesn't align with the From, a sending IP that landed on a blocklist overnight, or a campaign whose content reads like spam. Run it for every sending system you use. Each ESP, CRM, and transactional provider sends from its own servers, and each one needs its own passing report.

Email deliverability test FAQ

Our receiving server accepts the message, runs the checks, and stores only the analysis: authentication results, the sending IP and its lookups, header facts such as From, Subject, and size, and derived content counts. The message body itself is never stored. The analysis is kept for 24 hours so you can revisit the report, then deleted. The address you send to is valid for one hour and accepts a single message.

Three usual reasons. The public key in DNS doesn't match the private key your provider signs with, typically after a key rotation or a copy-paste error in the TXT record. The message was modified after signing, often by a footer or link-tracking rewrite added downstream of the signer. Or the signature is present but for a different domain than your From address, which passes DKIM on its own yet fails DMARC alignment. The DKIM row names the signing domain and selector so you can compare them with your provider's settings.

DMARC passes when at least one of SPF or DKIM passes and aligns with the domain in the From header: the SPF-authenticated envelope domain or the DKIM signing domain must match it, exactly or as a subdomain, depending on your alignment mode. If your domain publishes no DMARC record the row shows a warning, because receivers then have no policy to apply. Publish a record at p=none to start collecting reports before moving to quarantine or reject.

The sending IP is looked up on five widely used DNS blocklists: Spamhaus ZEN, SpamCop, Barracuda, UCEPROTECT level 1, and PSBL. A listing on any of them costs the score heavily because major providers consult the same lists. If a list could not be queried during your test, the row says so rather than guessing. Delisting instructions are on each list's own site; find and fix the cause first or the listing comes back.

No. The score covers what can be measured from one message: authentication, the server that sent it, the connection, and the content. Inbox placement also depends on your sending reputation, engagement, complaint rate, and list quality, which build up over many messages. A high score means nothing in the message gives a filter a reason to distrust it; keeping your list clean and your complaints low is what earns the inbox from there.

Domain health monitoring

A check today does not cover next month

Qualisend checks MX, SPF, DKIM, DMARC, MTA-STS and BIMI on your domains every day and emails you when a record breaks and again when it is fixed.

See domain health monitoring From $8.99/mo

Passing today? Keep it that way

Monitor the domain's blocklists, DNS, and DMARC reports, and verify the list you send to so bounces never undo a clean setup. Start free with 100 credits, no card required.

Start free