Technical Deep-Dive & Remediation Playbook

Direct IP Blacklisting vs. Subnet Escalation (UCEPROTECT L1, L2, L3 & S5H)

Why Standard Blacklist Checkers Miss Outgoing Newsletter IPs

Many businesses receive company email on Google Workspace or Microsoft 365 (so their MX records point to Google/Microsoft), while sending marketing newsletters or web-app emails from a separate server listed in their v=spf1 record (via ip4: or a:). AmIInSpam.com inspects both your MX IPs and your SPF sending IPs!

Understanding the 9 Blocklists We Check

  • Spamhaus ZEN, SpamCop, Barracuda, SORBS, PSBL & S5H (Direct IP Lists): A listing here means your specific IP address recently sent spam, hit a spam trap, or lacks valid Reverse DNS. Immediate delisting or switching to a clean SMTP provider is required.
  • UCEPROTECT Level 1 (Single IP): Direct abuse detected from your specific IPv4 address in the last 7 days.
  • UCEPROTECT Level 2 (`/24` Subnet Escalation) & Level 3 (ASN Escalation): Indicates that multiple neighboring servers in your data center subnet have been caught spammingβ€”a common reason cloud VPS mailers land in spam even when their own IP is clean on Level 1.
Free Interactive Generator

SPF & DMARC Record Fix-It Builder

Select every service that sends email from your domain to generate a clean, merged SPF record (within the 10-lookup limit) and a compliant DMARC policy.

1. Select Your Email Providers & Marketing Senders

Generated SPF TXT Record
Host / Name: @
Est. DNS Lookups: ~3 / 10
v=spf1 include:_spf.google.com ~all
Generated DMARC TXT Record
Host / Name: _dmarc
RFC 7489 Compliant
v=DMARC1; p=quarantine; pct=100; rua=mailto:dmarc@yourdomain.com; adkim=r; aspf=r;
Step-by-Step DNS Playbooks

Popular Email & DNS Provider Setup Guides

Copy-paste configurations for the most common domain registrars and email platforms.

Email Deliverability Knowledge Base

Frequently Asked Questions

Why does having two SPF records break email delivery?

RFC 7208 Section 3.2 explicitly states that a domain must not have multiple TXT records starting with v=spf1. If you add a second SPF record for Mailchimp or SendGrid instead of merging the include: tags into one record, receiving servers return SPF PermError and treat your authentication as failed.

How do I fix "SPF Too Many DNS Lookups" (>10 limit)?

Every include:, a, mx, ptr, and redirect= inside your SPF record (and nested inside your providers' SPF records) counts toward the strict 10-lookup ceiling. Remove unused senders, drop redundant a/mx tags, or move marketing/transactional emails onto a subdomain like mail.yourdomain.com.

Is DMARC p=none enough for Gmail and Yahoo?

v=DMARC1; p=none; satisfies the minimum entry requirement for bulk senders, but it offers zero protection against phishers spoofing your domain. Once you verify your legitimate email services pass SPF and DKIM, upgrade to p=quarantine or p=reject.

Why wasn't my DKIM key auto-detected?

Unlike SPF and DMARC (which live at fixed DNS locations), DKIM keys live at <selector>._domainkey.yourdomain.com. AmIInSpam.com automatically probes 16 common selectors (google, selector1, s1, k1, resend, etc.). If you use a custom selector, enter it in the DKIM Inspector box to verify it directly.