The Spamhaus Sender Guidelines landed on 21 October 2026 and turned twenty years of scattered advice into one rulebook with five minimum requirements. Beginning this month, the blocklist whose data receivers consult starts enforcing the DNS one — and two of the rules are aimed at things lifecycle teams pay for.
On 21 October 2026 Spamhaus published the Spamhaus Sender Guidelines, and the sentence worth reading is a note at the top of the page rather than anything in the six sections below it: "Starting in November 2026, we are gradually rolling out a requirement for every sending IP to have a valid HELO, a reverse DNS (PTR) record, and a matching A record." A blocklist has published sender requirements with a date attached, and the first thing it enforces is a DNS check you can run against your own sending IPs in about a minute.
That matters more than the checklist, because a listing is not a policy discussion. Spamhaus data is consulted by receivers, and the guidelines say it plainly: mail from IP addresses without reverse DNS is treated as suspicious, and "receivers using Spamhaus data may subject it to additional filtering." None of that arrives as a bounce with an explanation attached. Mail goes somewhere else, or nowhere, and the reason lives in a zone file you did not know anyone was reading.
The announcement is modest about how new any of this is. Spamhaus writes that the answer to "how do I stay off your blocklists" has not changed in twenty years — only mail people who asked for it, and set your sending infrastructure up properly — and that the guidance was scattered across FAQs, blog posts and support tickets. What is new is that it now exists in one place, with numbered minimums, a checker, and an enforcement date.
The minimum requirements page is short by design. Five items, all of which senders must meet "to avoid being listed":
localhost, hosting-provider defaults, and hostnames that vary between connections are read as signals of misconfiguration or compromise.d= domain aligned to the domain in the visible From header.Four of the five are configuration, and the fifth is a decision about how you acquire addresses. That is the shape of the whole document: a postmaster's checklist published by the party that decides whether receivers can trust you.
It is easy to overstate this, so: Spamhaus has not invented a new rule, and its own introduction concedes the point. Three things did change.
helocheck@abuseat.org that returns the HELO your server is presenting.Most of the document is familiar to anyone who has read a postmaster page. Two items are not, and both are aimed at things lifecycle marketing teams buy.
Warm-up services that fake engagement are now a listing criterion. Not discouraged — listed:
Do not use warm-up services that generate artificial traffic or simulate opens, clicks and replies. Using an engagement inflation service will result in the IP or domain being listed.
Spamhaus Sender Guidelines, section 4 — Sending best practices: Warm upA second line in the same section extends the rule: "Infrastructure operated to inflate engagement or otherwise trick filters will be listed as a spam-enabling service." This is a category plenty of programmes have paid for, and it is worth checking whether one is running in your account under a name that does not sound like it. The guidelines describe the legitimate version of the same job in the same section: start slowly for any IP or domain that has not sent in the past 90 days, begin with the most engaged recipients, spread volume across the day rather than in a burst at the top of the hour, and carry the suppression list onto new infrastructure — otherwise old bounces and unsubscribes get mailed again, and that is where recycled spam traps sit.
Do not suppress a spam trap. The instinct when traps appear in a list is to find the addresses and remove them, because that is the obvious thing to do with a bad address. The guidelines say the opposite: audit the acquisition process, identify which segment or collection method introduced the trap, and remove that source entirely. They also point at M3AAWG's spamtrap guidance and note that mailboxes inactive for more than twelve months can be repurposed as traps — which is why a sunset policy is a deliverability control rather than a list-hygiene chore. A suppressed trap is a fix to the symptom; the tap is still running.
Two smaller rules earn a line each. Cousin domains — a lookalike domain for a second product line or region — are out; the guidance is to use subdomains instead. And newly registered domains cannot be used as an SMTP From or HELO domain: domains registered within the last 24 hours sit on the Zero Reputation Domains list, and Spamhaus recommends waiting at least 30 days from registration before sending from one, using the interval to put a website on it.
A separate page covers ESPs and shared sending infrastructure, and its opening premise is the part worth quoting to a vendor: everything in the sender guidelines applies to mail sent via the platform, and hosting abusive senders damages the reputation of shared domains and infrastructure. What it asks operators to do reads as a list of questions for your next review:
The page also states plainly that customers on a shared IP pool or shared domain affect each other's reputation, and that the risk is higher where free accounts are offered. If you have ever had to explain a placement problem you did not cause, that sentence is the mechanism.
helocheck@abuseat.org returns the HELO your server presents. Do it for every IP you send from, not the one you think you use.d= domain, the envelope From and the HELO can each be a different name, and the requirements are written per sending domain and per sending IP. Tools sign with their own selectors, aliases and subdomains multiply the set, and legacy domains kept alive after a rebrand are still sending identities.include: entries for providers you no longer use. The guidelines call dangling records a subdomain-hijacking route.List-Unsubscribe-Post, RFC 8058) present in your bulk mail with unsubscribe requests actioned within two days.Could you produce, today, the list of IPs and HELO hostnames your mail actually leaves from? The DNS check takes a minute per IP. Knowing which IPs to check is the work — and it is the same inventory the last three deliverability announcements have each asked you for in a different form.
Written by the team at LMR — a senior lifecycle marketing studio working in Iterable, Braze, Klaviyo and the tools you already run.
Start a project ↗