I'm currently using 2 providers to send e-Mails and one host which directly sends e-Mails.
Personal mails are sent via Google and application generated via a bulk e-mail provider.
Both are sent from the same domain (example.com).

Google specifies to use this record ("Create SPF records"):
v=spf1 include:_spf.google.com ~all

The other provider specifies:
v=spf1 include:spf.provider.com ?all

I created the following TXT record (ip4 value changed):
v=spf1 ip4: include:_spf.google.com include:spf.provider.com ?all

I have tested this by sending mails via both providers to a Googlemail address and it passes.
However the check-auth@verifier.port25.com service of port25.com reports (again hostnames/IPs changed):

Result:         permerror (multiple SPF records)  
ID(s) verified: smtp.mailfrom=faker@example.com  
 DNS record(s):  
    example.com. SPF (no records)  
    example.com. 3600 IN TXT "v=spf1 ip4: include:_spf.google.com include:spf.provider.com ?all"  
     example.com. 3600 IN TXT "google-site-verification=$hash$"  
     _spf.google.com. SPF (no records)  
     _spf.google.com. 300 IN TXT "v=spf1 ip4: ip4: ip4: ip4: ip4: ip4: ip4: ip4: ip4: ip4: ?all"  
     spf.provider.com. SPF (no records)  
     spf.provider.com. 3600 IN TXT "v=spf1 ip4: ~all"  
     spf.provider.com. 3600 IN TXT "v=spf1 ip4: ~all"  

Is this verifier correct with its conclusion?

1 Answer 1


It's hard to be sure, since you obscured the relevant details, but it appears that one of your providers has two SPF records in their DNS, which is not allowed.

You can validate your SPF records with the SPF Parser tool.

  • Sorry about the obscuration. You are absolutely right though, I was only focused on my records and missed the two TXT records of spf.provider.com completely.
    – faker
    Aug 22, 2012 at 18:32

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.