Skip to content
EssentialSecurity, theme, and saved preferences.Always on

We do not send your name or email to affiliates.

Specialist check

Email infrastructure readiness checker

Check observable infrastructure signals that can block a cold email launch. This does not test inbox placement.

Checks
Checks observable public infrastructure signals that can block a launch.
Cannot tell
It cannot observe inbox placement, complaints, list quality, content, or private provider reputation.

Example:

Required for a DKIM decision. Common examples: Google google, Microsoft 365 selector1 or selector2. Confirm the value in your sending provider.

Expected time: about 5 to 20 seconds. Some public services can take longer.

Source: Live public DNS and public risk sources. No inbox-placement evidence is collected.

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.