Topic · Authentication
SPF ip4 mechanism
The SPF ip4 mechanism authorizes a specific IPv4 address or CIDR range for the policy domain.
How it works
A receiver compares the connecting IPv4 address with the literal network range; this mechanism does not require DNS lookups.
What can go wrong
Overly broad CIDR blocks authorize more senders than intended and can expose reputation to unrelated traffic.
What to check or do
Use the narrowest stable published ranges and remove addresses that no longer send legitimate mail.
How to investigate SPF ip4 mechanism
- Signal to investigate
- An IPv4 sending host receives SPF fail despite a broad-looking TXT record.
- Evidence to collect
- Identify the connecting IP at the receiving host and compare it with the published ip4 CIDR ranges, including any legacy exclusions.
- Common wrong conclusion
- Adding an address unrelated to the observed connecting IP will not authorize the actual outbound pool.
How to interpret the evidence
ip4 does not itself trigger DNS resolution, but overbroad netblocks may authorize unintended senders. CIDR prefixes should be based on real sending infrastructure ownership.
What to change and how to verify it
Keep IP ranges narrow, review provider change notices, and retest the exact egress address after updates.
Put this into practice
Run a focused check, then explore protection if your domain needs it.