Spamhaus will require valid HELO and reverse DNS from every sending IP starting November 2026

Spamhaus new email sender requirements in November

Spamhaus is rolling out a new rule from November 2026: every sending IP must have a valid HELO, a reverse DNS (PTR) record, and a matching A record, or risk being listed. The guidelines also set minimum requirements for confirmed opt-in, SPF, DKIM, DMARC, and IPv6 allocations of at least /64. A DNS checker tool lets senders test their setup before the rollout.

An IP with missing or mismatched reverse DNS is treated as suspicious and is one of the most common reasons for an IP to be considered for listing.
  1. BLKNSLVR

    > Publish forward-confirmed reverse DNS for every sending IP

    > 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. This is known as forward-confirmed reverse DNS (FCrDNS). An IP with missing or mismatched reverse DNS is treated as suspicious and is one of the most common reasons for an IP to be considered for listing.

    I self-host an email server behind my ISPs connection, and so I do not own the IP address that I send mail from, therefore I can't satisfy the reverse DNS requirement.

  2. albertgoeswoof

    These techniques rely on it being hard (or at least long winded) to setup a domain and server properly, such that spammers (who are self selected to be lazy) won’t do it right and give up quickly.

    But with AI, it’s easy to get DKIM, DMARC, HELO etc. set up perfectly for almost no effort (maybe fcrdns is a bit more complex as it’s a manual process at most ISPs)

    I think we are in the end going to go back to it just being based on IP (v4) reputation, and this is all theatre.

  3. cowlevel

    Spamhaus is effectively a protection racket. However, these specific requirements are extremely reasonable.

  4. computer23

    Anyone else having their email blocked by Microsoft and Spamhaus?

    Microsoft Office 365 relies on Spamhaus and was blocking my email because the HELO on the mail server was mydomain.com instead of mailserver.mydomain.com.

    Once the problem was fixed, it took time for Spamhaus to re-scan the mail server and take the mail server off the block list. And it took more time for Microsoft to stop blocking mail.

    https://check.spamhaus.org/

  5. zurfer

    Every now and then I wonder how my mail inbox would feel when people would need to pay 1ct to send me an email, and how it would feel at 10ct and at 1usd.

    Currently it seems to cost 0.001ct.

  6. xmddmx

    Can someone clarify, do these rules apply only to people running their own mail transport?

    Or does it also apply to people sending mail through their mail hosting company (when that company is not Google or Microsoft).

    Specific example: I run servers "at home" that send mail through SMTP.

    I have forward DNS properly set up, but my reverse DNS is syn-123-123-123-123.res.spectrum.com

    My mail servers are, however, sending the mail through my mail host (DreamHost) and so I'm hoping that not having reverse DNS at home won't be a problem.

    Am I reading the Spaumhaus rules correctly?

  7. azinman2

    Is it possible anymore to even acquire an IP address that’s clean and use it to self host?

  8. nikolay

    I checked my site with Codex and it failed due to Cloudflare and Resend.

More from this day

2026-11-16