How to Use Email Deliverability Monitoring Tools to Track Inbox Placement, Spam Folder Rates, Blocklist Status, IP and Domain Reputation, Authentication Pass Rates, and Engagement Metrics Across Email Service Providers
On this page
The Difference Between Sent and Delivered
An email that is "sent" is not necessarily "delivered." An email platform may report that a message was sent successfully, meaning the sending server transmitted it and the receiving server accepted it without returning a hard bounce. But acceptance by the receiving server does not mean the message reached the recipient's inbox. The receiving server may have routed the message to the spam or junk folder based on content filtering, sender reputation, authentication failures, or recipient engagement history. The message may have been silently discarded (accepted by the server but not delivered to any folder). Or the message may have been delayed in a processing queue and delivered hours or days after it was sent.
The gap between "sent" and "inbox" is where deliverability monitoring tools operate. These tools measure what actually happens to email after it leaves the sending platform, providing visibility into inbox placement rates (the percentage of messages that reach the inbox versus the spam folder), sender reputation scores (how mailbox providers view the sending IP address and domain), authentication status (whether SPF, DKIM, and DMARC are passing correctly), and blocklist status (whether the sending IP or domain has been listed on DNS-based blocklists that mailbox providers use as filtering inputs).
For companies that depend on email for revenue -- whether through marketing campaigns, sales outreach, transactional notifications, or customer communications -- deliverability monitoring is not optional. A 10% decline in inbox placement rate on a list of 100,000 subscribers means 10,000 fewer people see each message. At a typical $0.50-$2.00 revenue per email delivered to the inbox, that represents $5,000-$20,000 in lost revenue per send.
Inbox Placement Testing with Seed Lists
The most direct way to measure inbox placement is seed list testing. A seed list is a set of email addresses maintained across major mailbox providers (Gmail, Outlook.com/Hotmail, Office 365, Yahoo Mail, AOL, Apple iCloud Mail, Comcast, and others) that the deliverability monitoring tool controls. Before or during a campaign send, the monitoring tool's seed addresses are included in the recipient list. After the send, the monitoring tool checks each seed mailbox to determine whether the message arrived in the inbox, was routed to the spam/junk folder, or was not delivered at all.
Seed list testing provides actual inbox placement data segmented by mailbox provider. A campaign might show 95% inbox placement at Gmail but only 60% inbox placement at Microsoft -- a critical distinction that aggregate bounce rates would never reveal. The provider-specific data enables targeted troubleshooting: if Gmail is delivering to the inbox but Microsoft is filtering to spam, the issue may be related to Microsoft-specific content filtering, a blocklist that Microsoft weighs more heavily, or a domain reputation problem at Microsoft that doesn't affect Gmail.
Seed list testing has limitations. The seed addresses do not have the same engagement history as real recipients (they do not open, click, or reply to messages the way real subscribers do), and modern mailbox providers increasingly use individual recipient engagement history to determine inbox placement. A message that reaches the inbox for a seed address may still be filtered to spam for a real recipient who has never opened messages from that sender. Despite this limitation, seed list testing remains the most reliable method for detecting systematic deliverability problems.
Upload your email list to Email Extractor to clean and deduplicate addresses before running deliverability tests. Sending test campaigns to invalid addresses, spam traps, or duplicate records pollutes the deliverability data and can damage the sender reputation you are trying to measure.
IP and Domain Reputation Monitoring
Mailbox providers assign reputation scores to both the sending IP address and the sending domain. These reputation scores, along with content analysis and recipient engagement signals, determine whether incoming messages are delivered to the inbox or filtered to spam.
Google Postmaster Tools provides reputation data for domains that send significant volume to Gmail. It reports domain reputation (categorized as Bad, Low, Medium, or High), IP reputation for each sending IP associated with the domain, spam complaint rate (the percentage of recipients who clicked "Report spam" -- Google recommends staying below 0.10%, and spam rates above 0.30% cause significant filtering), authentication rates (SPF, DKIM, and DMARC pass/fail percentages), and encryption rates (the percentage of messages sent over TLS). Google Postmaster Tools data is available only for domains that send enough volume to Gmail to generate statistically meaningful data, typically a few hundred messages per day or more.
Microsoft provides sender reputation data through SNDS (Smart Network Data Services), which reports on sending IP addresses rather than domains. SNDS shows the volume of messages sent from each IP to Microsoft recipients, the spam complaint rate, trap hit rate (messages sent to known spam trap addresses maintained by Microsoft), and the resulting filtering status (whether messages from that IP are being filtered).
Third-party reputation monitoring tools aggregate reputation data across multiple sources and provide alerting when reputation scores decline. These tools check the sending IP and domain against dozens of DNS-based blocklists, monitor feedback loop complaints from mailbox providers that provide them, and track reputation trends over time. Declining reputation is often a leading indicator of deliverability problems -- the reputation drops first, and inbox placement follows days or weeks later.
Authentication Monitoring and DMARC Reporting
SPF (Sender Policy Framework), DKIM (DomainKeys Identified Mail), and DMARC (Domain-based Message Authentication, Reporting, and Conformance) are the three email authentication protocols that mailbox providers use to verify that incoming messages are legitimately sent from the domain they claim to be from. Proper authentication is a prerequisite for good deliverability -- messages that fail authentication are significantly more likely to be filtered to spam or rejected outright.
DMARC reporting is a particularly valuable monitoring capability. When a domain publishes a DMARC record with a reporting address (the rua tag), every mailbox provider that receives email claiming to be from that domain sends aggregate DMARC reports back to the specified address. These XML reports show every IP address that sent email using the domain, whether SPF and DKIM passed or failed for each sending source, and how many messages were sent from each source.
DMARC reports reveal problems that would otherwise be invisible. An SPF record that is missing an authorized sending service (causing SPF failures for legitimate email). A DKIM signing configuration that is incorrectly set up (causing DKIM failures). An unauthorized sender using the domain (phishing, spoofing, or a forgotten legacy system still sending email from the domain). A forwarding service that breaks SPF alignment (the forwarding server's IP is not in the domain's SPF record).
Monitoring DMARC reports requires a DMARC report processing tool because the raw XML reports are generated by thousands of mailbox providers and are not human-readable in aggregate without processing. The monitoring tool ingests the DMARC reports, aggregates the data, identifies authentication failures, and alerts when new sending sources appear or when pass rates decline.
