- December 2022
Infrastructure testing — from authentication verification to inbox placement measurement — should be systematic and ongoing rather than ad-hoc. This note documents the testing methodology stack for commercial email infrastructure.
Email infrastructure testing is one of the most underinvested operational practices in commercial email programmes. Most programmes test reactively — checking something when a problem is suspected — rather than proactively through a systematic testing cadence that catches configuration drift and deliverability changes before they affect production campaigns. This note documents the systematic testing methodology that professional email infrastructure management requires: pre-deployment testing, ongoing monitoring testing, and post-incident diagnostic testing.
Pre-Deployment Testing
Authentication stack verification: Before any new sending configuration goes into production, send a test message from the production infrastructure to a seed address at Gmail. View full headers and verify: Authentication-Results shows spf=pass, dkim=pass, dmarc=pass; DKIM-Signature shows d=own-domain; List-Unsubscribe and List-Unsubscribe-Post headers are present and correctly formatted. This 10-minute test catches authentication misconfigurations before they affect any production sends.
Spam score testing: Use mail-tester.com to send a test message from the production infrastructure and review the spam score analysis. Mail-tester checks authentication, spam filter signals, blacklist status, HTML structure, and header completeness, providing a multi-signal pre-flight check in a single test. A score below 9/10 on mail-tester warrants investigation of the flagged issues before production deployment.
DNS record verification: Use MXToolbox or equivalent to verify all DNS records for the sending configuration: SPF record for the MAIL FROM domain (within the 10-lookup limit), DKIM key records for all active selectors, DMARC record for the sending domain, MX records for the bounce handling domain, and PTR records for all sending IPs (FCrDNS verification). DNS record verification should be run before any new campaign type is deployed and after any DNS change.
Seed inbox placement testing: Send a production-representative test message to seed addresses at Gmail, Yahoo, Microsoft, and any EU ISPs that represent significant list segments. Check whether the test message appears in the inbox or spam folder at each ISP. This test provides the most direct measurement of current inbox placement for the sending configuration and list quality combination. Pre-campaign seed testing should be run before any campaign significantly larger than previous campaigns or after any configuration change.
Ongoing Monitoring Testing
Daily Postmaster Tools review: The most important ongoing monitoring test for Gmail deliverability. Check domain reputation tier and spam rate trend every morning before any campaign injection begins. Set up alerts for any change in domain reputation tier or any spam rate above 0.05%. This daily check takes 5 minutes and is the highest-value monitoring activity available for Gmail inbox placement management.
Weekly SNDS review: Check SNDS status for all sending IPs weekly. Any IP transitioning from Green to Yellow warrants immediate investigation. Yellow SNDS status indicates elevated complaint or spam trap rates from Microsoft's monitoring, which will translate to increased Microsoft throttle and potential email filtering if not addressed.
Weekly per-ISP deferral rate query: Query the operational database for the previous week's per-ISP deferral rate (421 responses as a percentage of total delivery attempts). Any ISP showing above 10% deferral rate warrants investigation and potential domain block recalibration. Tracking this metric weekly reveals trends that indicate reputation changes or configuration drift before they escalate to inbox placement problems.
Monthly DMARC aggregate report review: Review DMARC aggregate reports for all sending domains to verify authentication completeness, detect new unauthorized sending sources, and confirm that all legitimate sending sources are passing DMARC. The monthly review takes 30 minutes with a DMARC reporting tool and provides cross-ISP authentication visibility across all ISPs that send aggregate reports.
Figure 1 — Email Infrastructure Testing Cadence
Post-Incident Diagnostic Testing
When a deliverability incident occurs — sudden inbox placement decline, reputation event, ISP-specific delivery problem — a structured diagnostic testing protocol identifies the root cause faster than ad-hoc investigation. The post-incident diagnostic test sequence: (1) Send an authentication test message and review headers — confirm authentication is passing correctly (eliminates misconfiguration as the cause). (2) Check Postmaster Tools for the incident date — verify whether the spam rate or domain reputation changed on or before the incident date (identifies whether the incident is reputation-driven). (3) Check SNDS for all IPs — verify SNDS status for Microsoft-specific incidents. (4) Run a seed placement test to the affected ISP — confirm the extent of the inbox/spam placement change. (5) Query the accounting log for the incident period — check per-ISP deferral rate, bounce rate by classification, and any unusual response text patterns.
Each diagnostic test answers a specific question about the incident cause. The sequence produces a structured diagnosis within 60-90 minutes rather than the 4-8 hour investigation that undirected troubleshooting typically requires. Document the diagnostic results, the cause identified, and the remediation applied — this documentation becomes the post-incident learning that improves the programme's response to similar incidents in the future.
Testing methodology for email infrastructure is the investment in operational knowledge that makes every other deliverability practice more effective. Pre-deployment testing prevents misconfiguration from reaching production. Ongoing monitoring testing detects changes before they escalate. Post-incident diagnostic testing resolves incidents faster and produces institutional learning that reduces future incident frequency. Together, the three testing layers convert email infrastructure management from reactive firefighting into proactive quality management — the operational posture that produces consistently reliable deliverability performance across the programme's full operational lifetime.
Infrastructure Assessment
Our managed infrastructure operates on a systematic testing cadence — daily Postmaster Tools and header verification, weekly SNDS and deferral rate review, monthly DMARC and blocklist audits, quarterly full infrastructure review — providing the continuous quality assurance that prevents deliverability incidents from developing undetected. Request assessment →