SPF.Guru

SPF Guru

Reads public DNS only. Nothing is changed for you.

0 of 10 lookups

_spf.google.com uses 0 of 10 DNS lookups and is already within the limit.

  • You do not need SPF Guru for this domain today. The record below is offered in case you are about to add more senders.

Current what _spf.google.com publishes today

v=spf1 ip4:74.125.0.0/16 ip4:209.85.128.0/17 ip6:2001:4860:4864::/56 ip6:2404:6800:4864::/56 ip6:2607:f8b0:4864::/56 ip6:2800:3f0:4864::/56 ip6:2a00:1450:4864::/56 ip6:2c0f:fb50:4864::/56 ~all

costs one DNS lookup.

Replacement publish this as your SPF TXT record

v=spf1 exists:i.%{ir}._d.%{d}.my.spf.guru ~all ip4:74.125.0.0/16 ip4:209.85.128.0/17 ip6:2001:4860:4864::/56 ip6:2404:6800:4864::/56 ip6:2607:f8b0:4864::/56 ip6:2800:3f0:4864::/56 ip6:2a00:1450:4864::/56 ip6:2c0f:fb50:4864::/56

is what a receiver looks up. Everything after the all is read by SPF Guru instead, and costs nothing.

See how this record behaves before you publish it. It opens with a documentation IP that matches nothing, which is what shows the lookup count; change it to one of your senders to see them pass.

Leave the rest of the record exactly as it is. Those mechanisms are what SPF Guru reads when it answers the query above. Delete them and every sender starts failing. How that works.

See where these lookups go, or confirm a specific server passes with the SPF checker.