Topic · Authentication
SPF ip6 mechanism
The SPF ip6 mechanism authorizes IPv6 addresses or ranges for an SPF policy domain.
How it works
The receiver tests the connection’s IPv6 address against literal prefixes, without consuming SPF DNS-querying mechanism budget.
What can go wrong
Ignoring IPv6 mail infrastructure can create authentication failures even when IPv4 sending succeeds.
What to check or do
Record legitimate IPv6 senders and compare observed connections with the exact configured CIDRs.
How to investigate SPF ip6 mechanism
- Signal to investigate
- IPv6 delivery fails SPF while the same sending service works over IPv4.
- Evidence to collect
- Collect the receiver-observed IPv6 source and compare it with ip6 mechanisms, network prefix lengths and provider documentation.
- Common wrong conclusion
- An ip4 mechanism does not authorize the equivalent system over IPv6.
How to interpret the evidence
Dual-stack mail paths can use different outbound addresses and reputation. A server hostname with AAAA records is not itself proof that the outgoing IPv6 address is authorized.
What to change and how to verify it
Add only documented sending IPv6 ranges or correct egress routing; retest from both address families.
Put this into practice
Run a focused check, then explore protection if your domain needs it.