Use this interactive checklist to audit your email infrastructure and calculate a deliverability score. Each item represents a critical factor that mail servers evaluate when deciding whether to accept, filter, or reject your emails.
| Check | Weight | Category |
|---|

Email deliverability is the measure of how successfully your emails reach the intended recipient's inbox rather than being filtered to spam, quarantined, or rejected entirely. It depends on a combination of technical configuration, sender reputation, and content quality. Poor deliverability means your messages — whether transactional, marketing, or personal — simply never arrive.
Think of it like network connectivity: just as a ping test confirms packets reach their destination, email deliverability confirms your messages reach the inbox. And just as DNS configuration affects how domains resolve, your email DNS records directly impact whether mail servers trust your messages.
Three DNS-based authentication mechanisms form the foundation of email deliverability. Without all three properly configured, major providers like Gmail, Outlook, and Yahoo will likely filter your messages:
| Protocol | DNS Record | What It Verifies | Failure Impact |
|---|---|---|---|
| SPF | TXT on domain | Sending server IP is authorized | Spam folder or rejection |
| DKIM | TXT on selector._domainkey | Message signature is valid | Reduced trust score |
| DMARC | TXT on _dmarc | SPF or DKIM aligns with From domain | Quarantine or rejection per policy |
Verify your records using our DNS Lookup, SPF Record Checker, and DKIM Record Checker.
Pro Tip: Start with a DMARC policy of
p=noneto monitor authentication failures without affecting delivery. Once you confirm everything passes, gradually tighten top=quarantineand eventuallyp=reject. You can check your current DMARC record with a DNS lookup for the TXT record at_dmarc.yourdomain.com.
Proper DNS configuration is the technical foundation of email deliverability. Every sending domain needs these records configured correctly:
| Record Type | Purpose | Example | Check With |
|---|---|---|---|
| MX | Routes incoming email | 10 mail.example.com | MX Checker |
| SPF (TXT) | Authorizes sending IPs | v=spf1 include:_spf.google.com ~all | SPF Checker |
| DKIM (TXT) | Public signing key | v=DKIM1; k=rsa; p=MIGf... | DKIM Checker |
| DMARC (TXT) | Authentication policy | v=DMARC1; p=reject; rua=mailto:... | DNS Lookup |
| PTR | Reverse DNS for sending IP | mail.example.com | rDNS Lookup |
| A | Mail server IP address | 203.0.113.10 | DNS Lookup |
If you're managing DNS through your router or need to change your DNS settings, make sure these records are properly propagated before sending emails.
Mail servers evaluate your sender reputation using multiple signals. A poor reputation leads to emails landing in spam even if your authentication is perfect:
When your emails aren't reaching the inbox, systematically work through these common issues:
| Problem | Symptoms | Solution |
|---|---|---|
| Missing SPF record | SPF softfail/fail in headers | Add TXT record with authorized IPs |
| DKIM misalignment | DKIM fail in authentication results | Ensure DKIM domain matches From domain |
| No DMARC policy | No DMARC enforcement | Publish _dmarc TXT record |
| Missing PTR record | Rejected by receiving servers | Set up reverse DNS with your ISP or hosting provider |
| Blacklisted IP | 550 rejections, spam folder | Request delisting from each blacklist |
| High bounce rate | Reputation declining over time | Clean email list, verify addresses before sending |
| No TLS encryption | Warning badges in Gmail | Enable STARTTLS on mail server |
Follow this systematic approach to audit and improve your email deliverability:
If you need to troubleshoot DNS issues, see our guides on DNS server not responding and changing DNS on your router.
Major email providers have additional requirements beyond the basics. Meeting these ensures better inbox placement:
p=none, one-click unsubscribe, and spam rate below 0.3%.A deliverability score above 90% is considered excellent and means your emails are reaching the inbox consistently. Scores between 75-90% are good but have room for improvement. Below 75% indicates significant issues with your authentication, reputation, or sending practices that need immediate attention.
Emails land in spam for several reasons: missing or failing SPF/DKIM/DMARC authentication, sending from a blacklisted IP, poor sender reputation, spammy content or subject lines, lack of TLS encryption, or recipients previously marking your emails as spam. Use this checklist to identify which factors are affecting your deliverability.
Technical fixes like adding SPF, DKIM, and DMARC records take effect within hours once DNS propagates. However, rebuilding a damaged sender reputation can take 30-90 days of consistent, clean sending. IP warming for new sending IPs typically requires 2-4 weeks of gradually increasing volume.
Yes. While emails can be delivered with only SPF or DKIM, all major providers now recommend (and some require) all three. SPF verifies the sending server, DKIM verifies the message integrity, and DMARC ties them together with a policy. Together they provide the strongest authentication.
A PTR (Pointer) record is a reverse DNS entry that maps an IP address back to a hostname. Many mail servers reject email from IPs without a valid PTR record because legitimate mail servers almost always have reverse DNS configured. Contact your hosting provider or ISP to set up a PTR record for your mail server IP.
Use our IP Blacklist Checker to query major DNS-based blacklists (DNSBLs). If your IP appears on a blacklist, visit the blacklist provider's website to request removal. Common blacklists include Spamhaus, Barracuda, SORBS, and SpamCop.
IP warming is the process of gradually increasing email sending volume from a new IP address over 2-4 weeks. This builds a positive sending reputation with mailbox providers. Start with your most engaged recipients and slowly increase volume by 20-30% daily until you reach your normal sending level.
About Tommy N.
Tommy is the founder of RouterHax and a network engineer with 10+ years of experience in home and enterprise networking. He specializes in router configuration, WiFi optimization, and network security. When not writing guides, he's testing the latest mesh WiFi systems and helping readers troubleshoot their home networks.
![]() |
![]() |
![]() |
![]() |
Promotion for FREE Gifts. Moreover, Free Items here. Disable Ad Blocker to get them all.
Once done, hit any button as below
![]() |
![]() |
![]() |
![]() |