Starting in November 2026, Spamhaus will begin a gradual rollout of stricter requirements for every IP address used to send email. To avoid being listed on Spamhaus's blocklists, senders must now ensure their sending IPs possess a valid HELO, a reverse DNS (PTR) record, and a matching forward DNS (A/AAAA) record.

The official logo for Spamhaus Technology and abuse.ch.
Spamhaus Technology provides the infrastructure and guidelines for these new email security requirements.www.spamhaus.com

The article discusses the new infrastructure requirements being enforced by Spamhaus to improve email trust.

The Mechanics of Forward-Confirmed Reverse DNS

A central pillar of the new requirements is Forward-Confirmed Reverse DNS (FCrDNS). This mechanism requires that a sending IP's reverse DNS entry points to a fully qualified domain name (FQDN), which must then resolve back to that exact same IP address via a forward DNS record.

Spamhaus treats IPs with missing or mismatched reverse DNS as suspicious. By requiring this loop, the system can more easily distinguish legitimate infrastructure from the anonymous or misconfigured setups often used by spammers.

“Every sending IP must have a reverse DNS entry pointing to a fully qualified domain name (FQDN). That hostname must, in turn, resolve back to the same sending IP address.”

— Sender Guidelines | Spamhaus

HELO Consistency and Infrastructure Hygiene

The server's HELO/EHLO command—the initial greeting in an SMTP connection—must use a hostname that resolves to the connecting IP. Spamhaus notes that placeholder values, hosting-provider defaults, or hostnames that vary between connections are treated as signals of compromise or misconfiguration.

To improve trust signals, Spamhaus recommends using a 'branded' reverse DNS that uses the sender's own domain rather than generic entries provided by a hosting company, such as 'static-203-0-113-25.hosting.example.net'.

Authentication and Subscriber Permissions

Beyond DNS configuration, senders must maintain full authentication via SPF (Sender Policy Framework), DKIM (DomainKeys Identified Mail), and DMARC (Domain-based Message Authentication, Reporting, and Conformance). This includes ensuring the DKIM sending domain aligns with the domain in the message's 'From' address.

Spamhaus also emphasizes 'Confirmed Opt-in' (COI) as a requirement for all bulk email. Senders are expected to have recipients click a confirmation link in an initial email; failing to do so before sending further mail is a primary reason for being listed.

Trade-offs and Implementation Barriers

These requirements increase the administrative burden for legitimate senders, requiring them to maintain 'DNS hygiene' and audit records regularly. While this is intended to make it harder for 'lazy' actors to operate, it creates a significant barrier for users who do not own their IP space.

For example, individuals or small organizations sending mail behind an ISP's connection may find it impossible to satisfy the FCrDNS requirement because they lack the authority to modify the ISP's reverse DNS records. This creates a potential conflict between security best practices and the accessibility of email for non-infrastructure owners.

What Hacker News readers are saying

  • Technical note: One commenter shared their experience of being unable to meet the new requirements because they self-host an email server behind an ISP connection where they do not own the IP address. comment ↗
  • Skeptical: A commenter expressed skepticism that these requirements are merely theater, arguing that AI makes it easy for spammers to configure technical records perfectly, potentially forcing a return to IP-based reputation systems. comment ↗
  • Skeptical: Another user pointed out that large providers like Google, Amazon, and Microsoft may be exempt from these issues due to their size, suggesting that convenience often outweighs strict enforcement. comment ↗
  • Experience: One commenter described a practical issue where Microsoft blocked their email due to a HELO hostname mismatch, noting that it took significant time for the block to be lifted after the fix. comment ↗

Summarized opinions from the Hacker News thread, not verified facts. Read the full discussion ↗