You can locate the official removal portal using our Delisting Directory and submit a removal request once you have resolved the underlying spam or security issue.
SPF defines which IP addresses/servers are authorized to send email on behalf of your domain. DMARC instructs receiving servers how to handle messages that fail SPF or DKIM checks.
Common causes include missing DMARC enforcement policies, blacklisted sending IPs, high spam complaint rates, or syntax errors exceeding the 10 DNS lookup limit in SPF records.
To implement BIMI, your domain must enforce a strict DMARC policy (p=quarantine or p=reject), host a valid SVG Tiny P/S logo, and optionally secure a VMC (Verified Mark Certificate).
Major DNSBLs (such as Spamhaus and Barracuda) update their databases in real-time. Our automated checks query live DNS zone files to give you real-time status updates.
While a high Health Score ensures your DNS authentication (SPF, DKIM, DMARC) is flawless, deliverability also depends on domain reputation, email content quality, and recipient engagement rates.
The official SPF specification (RFC 7208) limits the maximum number of DNS lookups required to evaluate a record to 10. If your domain exceeds this limit, receiving servers will return an SPF PermError, failing authentication. You can fix this by removing unused include: mechanisms or using an SPF flattening technique.
This happens due to an Alignment Failure. For DMARC to pass, the domain in the visible "From" header must strictly or relaxed match the domain authenticated by SPF (Return-Path) or DKIM (d= tag). If the domains do not match, DMARC will fail despite valid signatures.
Our platform executes live, high-speed DNS queries against over 100+ trusted DNSBL (DNS Blacklist) and RBL databases. It queries the target IP or domain zone directly to provide immediate status feedback without caching stale results.