06 Nov 20266 minutes read
Kiara SaloojeeDMARC EnthusiastWhat the Spamhaus Sender Guidelines Mean for Your Domain

Spamhaus sender guidelines overview:
- Align DKIM with your “From” domain for every sending service
- Move DMARC past p=none to an enforcement policy
- Keep SPF records within the 10 DNS lookup limit
- Check that every sending IP meets the HELO and reverse DNS requirement
- Expect ESPs to check your authentication before you can send
Whether a mail server accepts a message depends partly on the sender’s reputation. To judge that reputation, receiving servers can draw on outside sources such as Spamhaus, a blocklist provider. If your sending IP or domain lands on Spamhaus' blocklist, any receiver using that data can filter or reject your mail. A single blocklist listing can affect delivery to every receiver that uses Spamhaus data, not just one mailbox provider.
The Spamhaus sender guidelines set out what senders need to do to avoid a blocklist listing. They cover infrastructure, authentication, list hygiene, and sending practices. This article covers the authentication requirements, including DKIM alignment. It also explains what they mean for organizations that send through email service providers (ESPs) and the new infrastructure requirement that Spamhaus began rolling out in November.
Why the Spamhaus Sender Guidelines Matter
Google, Yahoo, and Microsoft set rules for mail delivered to their own users. Spamhaus works differently. Its reputation data informs the filtering decisions of every receiver that uses it. A blocklist listing from Spamhaus reaches further than a block at a single provider.
The Spamhaus sender guidelines state that IPs failing the infrastructure requirements can be listed on the Email Spam IPs (CSS) or compromised IPs (XBL) zones.
Authentication gaps also count against a sender. Spamhaus describes authentication as one of the signals that shape reputation. Gaps make a listing more likely when other signals are weak.
Spamhaus states that it doesn’t accept requests to explain attributes or to reset reputation. Prevention is the practical route. That starts with the configuration Spamhaus sets out in its guidelines.
What the Spamhaus Sender Guidelines Say About SPF, DKIM, and DMARC
The authentication section of the Spamhaus sender guidelines sets out requirements and recommendations for each protocol.
DKIM Alignment Is a Requirement, Not a Recommendation
The Spamhaus sender guidelines require the d= domain in the DKIM signature to match the domain in the header "From" address. This goes further than the bulk sender rules from mailbox providers. Microsoft, for example, accepts DMARC alignment through either SPF or DKIM.
When a third-party platform signs your mail with its own domain, the message passes DKIM but fails DKIM alignment. Under the Spamhaus sender guidelines, that mail no longer meets the standard. Every service that sends on your behalf needs to sign with your domain.
Spamhaus also sets a minimum DKIM key length of 1024 bits and recommends 2048 bits. It also recommends rotating keys at least once a year, or immediately if a key may be compromised.
DMARC Enforcement Is the Goal
Spamhaus requires a DMARC record with a defined policy for every sending domain. Starting at p=none is acceptable. Spamhaus recommends an enforcement policy and advises against remaining at p=none permanently. It also recommends adding an aggregate report address (rua) from the start to audit the email sent from your domain.
The SPF 10 DNS Lookup Limit
The Spamhaus sender guidelines require SPF records to stay within the 10 DNS lookup limit. Exceeding the limit returns a permerror. A permerror isn’t a pass, so SPF can’t authenticate the mail or satisfy DMARC alignment. When SPF fails this way, DKIM alignment is the only remaining path to a DMARC pass.
Subdomains, Not Cousin Domains
The Spamhaus sender guidelines tell senders not to use cousin domains for extra mailstreams or regions under the same brand. Use subdomains instead. They also recommend a separate d= domain for each mailstream, such as separate subdomains for transactional and marketing email, so each builds its own reputation.
The HELO and Reverse DNS Requirement in the Spamhaus Sender Guidelines
When a mail server connects to another to deliver a message, it announces a hostname in its HELO (or EHLO) command. Reverse DNS works in the other direction. A pointer (PTR) record maps the sending IP back to a hostname.
Starting in November 2026, Spamhaus is gradually rolling out a requirement for every sending IP to have a valid HELO hostname, a reverse DNS record, and a matching A record. The PTR hostname must resolve back to the same sending IP, which is known as forward-confirmed reverse DNS. The HELO hostname must also resolve to the sending IP and stay consistent across connections.
The requirement mirrors one Google already has: every public IP needs a PTR record, and the sending IP must match the IP of the hostname in that record. The difference is that Spamhaus applies the requirement from the reputation side, where a gap can contribute to a blocklist listing.
This requirement sits with whoever operates the sending infrastructure. For most companies, that’s the ESP or the team running on-premises mail servers.
What the Spamhaus Sender Guidelines Ask of ESPs
Spamhaus publishes separate guidelines for ESPs and large senders. It states that ESPs and shared infrastructure hosts are responsible for the email sent through their infrastructure. Hosting abusive senders damages the reputation of shared domains and infrastructure.
Customers who share an IP pool or domain can affect the reputation of everyone else sending from it. If one customer’s sending puts a shared IP on a blocklist, it affects every other customer sending from that IP.
The ESP guidelines tell providers to:
- Make sure every customer has SPF, DKIM, and DMARC configured before they’re permitted to send
- Sign outbound email with the customer’s own domain to achieve DKIM alignment
- Give each customer a dedicated subdomain to use as both the “From” domain and the DKIM signing domain
- Apply stricter thresholds to customers sending from shared IP pools or shared domains
If your business sends through an ESP, expect these requirements, including DKIM alignment, to show up in onboarding checks and account reviews. A single customer can put shared infrastructure on a blocklist, so ESPs have a direct reason to hold every customer to the same standard.
Meeting the Spamhaus Sender Guidelines Across Every Sender
For most enterprises, the challenge isn’t a single DNS record. The challenge is dozens of domains, multiple departments, and SaaS tools that send email on the organization’s behalf.
Senders that sign with their own domain instead of yours break DKIM alignment. Each new tool also adds SPF lookups, which can push the record past the 10 DNS lookup limit. Until every legitimate sender passes DMARC, the domain can’t safely move past p=none. Authentication gaps like these are reputation signals that can contribute to a blocklist listing.
Sendmarc gives security and IT teams visibility and control across every domain and sending tool. You can see which senders pass DKIM alignment and which don’t, including unapproved SaaS tools that departments start using before authentication is configured. With that visibility, you can fix unauthenticated or misconfigured senders before they affect your reputation.
SPF Flattening keeps SPF records within the 10 DNS lookup limit as your sender list grows. DMARC Management moves domains from p=none to p=reject in stages, so billing, notifications, and marketing email keep reaching inboxes during the transition.
Authentication isn’t a one-time project. New tools, regions, and acquisitions change your sending environment. The Spamhaus sender guidelines expect your configuration to keep up. Ongoing monitoring and optimization keep it current without adding manual work for stretched security and IT teams.
Test your domain to see how your SPF, DKIM, and DMARC configuration measures up against the Spamhaus sender guidelines.


