Free tool

Email deliverability checker for cold email

Check the observable infrastructure signals that can block a cold email launch before you send: authentication, mail routing, blacklist status, domain age, and tracking-domain readiness.

This checks observable cold email infrastructure readiness for one domain. For a real launch verdict, run every domain, inbox, and tracking domain through the full QA pass.

Runs live in your browser via public DNS. Nothing is stored.

Infrastructure readiness, not inbox promises

This checker is built for the pre-launch work operators actually control. It looks for DNS, authentication, blacklist, age, and tracking-domain issues that can be fixed before a campaign goes live.

It does not claim to know private Gmail or Microsoft reputation scores, and it does not guarantee inbox placement. Treat the result as a one-domain infrastructure preview, then run the full OutboundQA pass across the whole workspace.

How to read the result

A pass means the observable checks did not find a blocker for this one domain. A warning means a field was missing, inconclusive, or deserves review before sending. A fail means the launch should pause until the issue is fixed.

What this check does not catch

A passing observable cold email infrastructure readiness lookup is useful, but it is not launch signoff. Cold email campaigns still fail when adjacent records, tracking domains, or inbox-level settings are broken.

inbox placement

sending history

list quality

message copy

reply handling

client-ready signoff

Setup guides for this check

Read the setup notes behind this result, then verify the neighboring records before launch.

Google and Yahoo bulk sender requirements

SPF, DKIM, DMARC, one-click unsubscribe, and the spam-rate thresholds bulk senders must meet.

Tracking domains: CNAME and SSL

Custom tracking domains, the CNAME to your sending tool, and why broken SSL kills click-through.

Email blacklists: check and delist

The RBLs that matter, how listings happen, how to check before launch, and the delisting process.

Domain warmup and safe sending volume

Why new domains are high risk, ramp schedules, per-inbox daily limits, and domain age.

Need to check a full outbound workspace?

OutboundQA checks every domain, inbox, and tracking domain in the workspace, then gives you a shareable report with a Ready, Needs Fix, or Do Not Launch verdict.

Cold email launch checks to run next

Use this result as one checkpoint in the launch flow. Then verify the neighboring records and run the combined domain check before the outbound launch goes live.

SPF Checker

Look up a domain's SPF record and count its DNS lookups against the limit of 10.

DMARC Checker

Look up a domain's DMARC record and read its policy in plain English.

DKIM Checker

Look up a domain's DKIM selector and confirm the public key exists.

Auth Checker

Run SPF, DKIM, and DMARC together for a sending domain before launch.

MX Checker

Look up a domain's MX records and detect the mail provider.

Blacklist Checker

Check a domain and sampled mail server IPs against domain and email blocklists.

Reputation Checker

Check observable cold email reputation risks across age, blacklist, authentication, MX, and HTTPS signals.

Domain Checker

Run MX, SPF, and DMARC in one pass for a quick readiness verdict on a sending domain.

Sample Launch QA Report

See the report founders, teams, and agencies can share after the full QA pass.

Email Deliverability Tool

See how one-off checks turn into pre-launch QA for full cold email workspaces.

Questions

No. This checker reviews observable cold email infrastructure signals: MX, SPF, DKIM if you provide a selector, DMARC, blacklist status, domain age, and tracking-domain routing. Inbox placement also depends on reputation history, sending behavior, list quality, and mailbox-provider filtering.

DKIM is published under a selector chosen by the sending platform. If you know it, enter it for a real DKIM lookup. If you do not, the result marks DKIM as a review item instead of guessing.

Enter the branded click or open tracking host used by your outbound platform, such as links.yourdomain.com. If the campaign does not use a tracking domain, leave it blank and review that separately before launch.

It means the observable infrastructure for one domain looks usable. A real launch QA should run the same checks across every sending domain, inbox, and tracking domain, then produce a client-ready verdict.