More than 70,000 organisations turned the setting on in preview; it stays off by default for existing tenants, while new ones get it with no way to switch it off.
Spamhaus starts requiring valid HELO and reverse DNS on every sending IP
EditorialBy TrustList Editorial
The blocklist operator is phasing in the rule during November 2026; a mail server whose PTR record, HELO name and A record do not agree risks a listing.
- Anti Spam
- Cybersecurity
- Email Marketing
About Spamhaus starts requiring valid HELO and reverse DNS on every sending IP
Spamhaus starts requiring valid HELO and reverse DNS on every sending IP
18 November 2026: Spamhaus, whose blocklists many mail receivers use to filter spam, is rolling out a requirement that every IP address sending email has a valid HELO name, a reverse DNS (PTR) record and a forward A record that points back to the same address. A sender that misses any of the three can be listed, and receivers that query Spamhaus data may then filter or refuse its mail.
Not yet independently verified. Spamhaus states the rule on its sender guidelines page, which gives "November 2026" as the start of a gradual rollout but no exact date, and no dated announcement was found. We will add the date when Spamhaus publishes one. We will update this when it can be confirmed, and remove this note.
Three records that must agree
The guidelines describe the check as forward-confirmed reverse DNS. The sending IP must have a PTR record that resolves to a fully qualified host name, and that host name must resolve back to the same IP. Separately, the name the server announces in its HELO or EHLO command must resolve to the address it is connecting from, and must stay the same across connections.
Spamhaus says an IP with missing or mismatched reverse DNS "is treated as suspicious", and calls this one of the most common reasons an address is considered for listing. Placeholder HELO values, hosting-provider defaults and names that change between connections are read as signs of misconfiguration or compromise. Listings for these failures go into the Combined Spam Sources (CSS) zone or the Exploits Blocklist (XBL), the page says.
Generic hosting names count against a sender
The page goes further than a bare PTR record. For dedicated IPs it advises against auto-generated reverse names that point at the hosting provider, giving examples in the style of static-203-0-113-25.hosting.example.net, and recommends a branded reverse name on the sender's own domain instead. It also asks that the PTR name be recognisable as sending infrastructure rather than a random dictionary word.
Mail sent over IPv6 has its own minimum: the address must sit in an allocation of /64 or larger, and that space must have valid reverse DNS.
The rest of the minimum list
Alongside the DNS rule, the guidelines set out what Spamhaus calls the minimum requirements for all senders:
- confirmed opt-in for every subscriber, with no mail to an address that has not clicked a confirmation link;
- SPF and DMARC records for every sending domain;
- a DKIM signature on every outbound message, with the signing domain aligned to the domain in the From header.
Purchased, rented and harvested lists are named as the most common source of spam trap hits. A separate section covers email service providers and other shared sending infrastructure.
Checking a server before the rollout reaches it
Spamhaus offers a HELO and DNS checker on the same page, which takes a sending IP and compares its setup with the guidelines, and says the current HELO can also be checked by sending a message to helocheck@abuseat.org. Teams that run their own mail servers, relay through a VPS or send from on-premises appliances such as printers and ticketing systems are the ones most likely to have an unmatched PTR record; mail sent through a large email provider normally inherits that provider's records.
Our email security category lists 11 products and the transactional email category 19.
The page gives no end date for the phased rollout.
Sources
- Spamhaus: Sender Guidelines, 18 November 2026
Categories & features
- Anti Spam
- Cybersecurity
- Email Marketing
TrustList Weekly
The week in software and IT, in one email
The news that matters to buyers, new rankings and our own research. Every Thursday, free, and easy to leave.
You may be interested in
APSB26-162 covers code injection, OS command injection and SQL injection in ACC v7 on Windows and Linux; one SQL injection needs no login. Build 9403 fixes all eight, and Adobe knows of no exploitation.
Nine CVEs land at once in the open-source marketing automation platform. The worst lets any user allowed to import campaigns place a script in the web root of a 7.x install.
Marketers could register from 15 September; consumers can start blocking contact from May 2027. Draft guidelines cite fines up to R1 million or 10% of turnover.
Sign-ups and credit purchases have already stopped. Refunds are not automatic and must be requested by the closing date, when results, uploaded lists and API keys are erased.
Braze shareholders get $47.50 a share; the customer engagement platform, used by about 2,770 brands including Canva and Instacart, would join Marketing Cloud, with closing expected in Salesforce's fiscal 2028.
Twilio’s Heightened Awareness Period runs from 19 November 2026 to 4 January 2027: US sending rates for toll-free, short code and 10DLC may be limited per account, and high-volume short code and toll-free senders may move to Market Throughput.
After a French court ruling, Quad9 says it can no longer offer its free service to users in France from 24 November 2026; French organisations using 9.9.9.9 need another resolver before then.
More on TrustList
Everything here links back to the same verified catalogue. Pick your next stop.
- CompaniesAgencies, consultancies and IT service providers, ranked by verified reviews.
- ProductsSoftware and SaaS with pricing, features, integrations and alternatives.
- AwardsAnnual recognition decided by verified reviews and an independent jury.
- LaunchesNew products and releases, voted up by the community every day.
- AI ModelsBenchmark scores and community ratings for every major model.
- RequestsBuyers describe what they need; vendors respond directly.
- PeopleReviewers, authors and makers with public profiles.
- ComparePut up to four listings side by side before you shortlist.