What an email deliverability test can — and cannot — prove
An email deliverability test can verify the setup and observed provider evidence for one received message; it cannot predict every recipient's inbox. Read Flash's setup grade for authentication, content, blacklist and hygiene findings. Placement is measured only when at least two provider families are active and at least half of all active seeds report; a provider family absent from the result remains unobserved.
Message acceptance, authenticated identity and inbox placement are different evidence. Gmail requires applicable senders to meet authentication, DNS, TLS, message-format, complaint and unsubscribe rules, but its bulk-sender DMARC minimum can be p=none and meeting the requirements does not guarantee inbox placement. Flash therefore separates deterministic checks on the received message from seed observations, requires configured provider-family and seed-reporting quorum before scoring placement, and names the provider families that actually reported.
Primary sources for this guidance
- Gmail email sender guidelines
- Gmail email sender guidelines FAQ
- RFC 9989 — Domain-Based Message Authentication, Reporting, and Conformance
- Folderly Flash scoring and privacy methodology
How to fix it
- Send one representative message through the same domain, ESP, Return-Path, DKIM selector, tracking links and message type you plan to use in production.
- Identify the result type before interpreting the number. A setup grade excludes pending placement; a full score includes placement only after at least two provider families are active and at least half of all active seeds report.
- Read authentication as verdict plus alignment. Check SPF, DKIM and DMARC on the received message, then review the related DNS findings. Do not treat p=none as a DMARC failure or stronger policy as an inbox guarantee.
- Review content as a bounded message check: decoded body structure, links, readable text versus image-only content and the patterns Flash can observe. It cannot measure recipient permission, engagement or every filtering model.
- Confirm any blocklist finding against the exact connecting IP and named list. Flash skips known shared-provider relays because their IP reputation is not controlled by the sender.
- Use hygiene findings to assign the right owner for message headers, reverse DNS and HELO, or MTA-STS and TLS-RPT. For subscribed promotional mail, verify the received one-click-unsubscribe headers and the suppression path separately.
- Read placement only for provider families that actually reported. A Gmail observation does not stand in for Outlook, Yahoo, iCloud or every recipient, and missing provider evidence is inconclusive rather than a zero.
- Choose one highest-confidence blocker, record the expected component or verdict change, make one observable fix and run a comparable production-path retest after the change can be seen.
Limitations
This page interprets one received message and the provider families that actually reported for that test. Flash does not observe every recipient, mailbox provider, complaint, engagement history or receiver policy, and a clean setup grade or measured seed result cannot guarantee future inbox placement.