Deliverability scan

Run a real pre-send deliverability check

Send the exact email you plan to launch to a one-time Scan address and get a practical report covering authentication, sending infrastructure, blacklist signals, content, links, and other deliverability risks.

Email Deliverability Test & Pre-Send Scan | CheckInbox

What CheckInbox Scan helps you verify

Scan analyzes a real received email sample and turns technical deliverability signals into a readable pre-send report.

Analyze the actual email

Scan receives the real message you send, including headers, authentication verdicts, links, HTML, and sending information instead of analyzing only pasted copy.

SPF, DKIM and DMARC in one report

Review received-message authentication evidence, alignment, visible From identity, and available SPF, DKIM, and DMARC verdicts in one place.

Sender infrastructure diagnostics

Inspect sender IP, MX and A records, PTR and reverse DNS, forward-confirmed PTR, technical sender identity, and other infrastructure signals.

IP and domain blacklist signals

Check both IP and domain blacklist layers while avoiding false hard failures from resolver-limited or inconclusive responses.

Content, HTML and link analysis

Review subject quality, aggressive wording, capitalization, HTML-to-text balance, images, tracking pixels, links, shorteners, forms, and attachments.

Readable actions, not raw diagnostics

Get a practical score, delivery-critical status cards, findings, and recommendations designed to help operators understand what to fix first.

How to run a Scan

For the most representative result, test the final email through the same sender, domain, and sending platform you plan to use in production.

1

Generate a Scan address

Open Scan and create a one-time address for the email you want to analyze.

2

Prepare the exact campaign email

Keep the real From identity, subject, HTML, links, images, tracking, and other elements that will be present in the production campaign.

3

Send it through your real ESP

Use the same sending platform, domain, and infrastructure as the real campaign so authentication and infrastructure checks reflect the actual sending path.

4

Wait for automatic analysis

CheckInbox receives the message and automatically builds the deliverability report from the captured email sample.

5

Review critical checks first

Start with From alignment, SPF, DKIM, DMARC, IP and domain blacklists, reverse DNS, and unsubscribe signals before moving to deeper findings and recommendations.

Recommended usage

  • Test the final campaign version, not an early draft. If you materially change links, HTML, sender, tracking, or domain setup, run Scan again.
  • Always use the real sending path. A test sent manually from a personal mailbox does not represent a campaign sent through a different ESP or domain.
  • Fix authentication and infrastructure problems before focusing on smaller cosmetic content changes.
  • Use Scan together with Check: Scan helps explain what may be technically wrong, while Check shows where the email actually lands across monitoring inboxes.

Important to know

Scan is a practical pre-send diagnostic, not a guarantee of inbox placement. A technically healthy email can still land differently for real recipients because mailbox providers also consider sender and domain reputation, engagement history, sending volume, list quality, infrastructure consistency, and provider-specific filtering. Use Scan to identify fixable risks, then use Check to measure actual placement.