What it means
Your SPF record uses the ptr mechanism. It asks receivers to look up the reverse DNS name of the sending server and check whether it ends in your domain. The SPF standard itself says not to use it.
Why it matters
ptr is slow and unreliable: it takes several lookups per message, depends on reverse DNS that you often don't control, and large receivers may skip it entirely. The result is that mail can pass at one receiver and fail at another, and each check eats into your 10-lookup limit.
How to fix it
- Find out which servers the
ptrmechanism was meant to cover. It is usually your own mail server or a server at a hosting company. - Replace it with that server's addresses as
ip4:orip6:entries, or with theinclude:your provider documents. - Remove
ptrfrom the record and check it in the SPF builder. - Update the TXT record at your DNS host.
Cloudflare
Open the domain, go to DNS then Records, and edit the TXT record whose content starts with v=spf1. Save, and keep the proxy setting off; TXT records are never proxied.
Other DNS hosts
Open the DNS settings for the domain, find the TXT record for the root of the domain (shown as @ or left blank), and edit its value. Don't add a second TXT record that starts with v=spf1.
Check it worked
Run the SPF checker or the full email check on your domain. Changes show up once the old record's TTL has passed, usually within an hour. The finding should be gone and the SPF section should show your new record with its lookup count. The record should no longer contain ptr.