Skip to content

Check the SPF record of any domain

Results for

google.com

Email authentication

1 warning

Warning
SPF
Pass:~all (soft fail), 1 of 10 lookups
DMARC
Pass:p=reject
DKIM
Warning:No key found
MTA-STS
Pass:Published
TLS reporting
Pass:Published
BIMI
Note:Not set up
Mail servers
smtp.google.com

SPF record

1 of 10 DNS lookups

Pass

v=spf1 include:_spf.google.com ~all

  • Uses 1 of 10 DNS lookups.
  • Ends in ~all (soft fail), so receivers accept mail from unlisted servers but mark it as suspicious.

Includes

1 domain

  • include:_spf.google.com1 lookup

DMARC record

_dmarc.google.com

Pass

v=DMARC1; p=reject; rua=mailto:mailauth-reports@google.com

  • Policy p=reject: receivers refuse mail that fails DMARC.
  • Aggregate reports go to mailauth-reports@google.com.
Policy
reject (refuse)
Subdomain policy
reject (refuse)
Percentage
100%
Aggregate reports
mailauth-reports@google.com
Failure reports
None
DKIM alignment
Relaxed
SPF alignment
Relaxed

DKIM keys

24 selectors checked

Warning
  • No DKIM key at 24 common selectors. Your mail provider may use its own: look it up as selector._domainkey.google.com.
Selectors we checked (24)
  • google
  • selector1
  • selector2
  • default
  • dkim
  • mail
  • k1
  • k2
  • k3
  • s1
  • s2
  • smtp
  • mx
  • mandrill
  • mxvault
  • protonmail
  • protonmail2
  • fm1
  • fm2
  • sig1
  • zmail
  • kl
  • s1024
  • s2048

To check another selector, enter it as selector._domainkey.google.com.

MTA-STS, TLS reporting and BIMI

Optional records

MTA-STS

Pass:Published

v=STSv1; id=20210803T010101;

  • MTA-STS is on (policy id 20210803T010101). The policy file lives at https://mta-sts.google.com/.well-known/mta-sts.txt.

TLS reporting

Pass:Published

v=TLSRPTv1;rua=mailto:sts-reports@google.com

  • TLS reports go to sts-reports@google.com.

BIMI

Note:Not set up
  • No BIMI record, so inboxes that support it show no brand logo next to your mail.

Run this lookup from code

The API returns this result as JSON. The free plan includes 100 API calls per month.

curl "https://hostingchecker.online/api/v1/email-auth?query=google.com" \
  -H "Authorization: Bearer YOUR_API_KEY"

How it works

How SPF works

When a server receives a message, it reads the domain in the envelope sender (the Return-Path) and looks up that domain's SPF record. If the sending server's IP address matches a mechanism in the record, SPF passes. If nothing matches, the all mechanism at the end decides the result.

SPF alone does not stop spoofing of the From address people see, because it checks the envelope sender only. DMARC closes that gap: it requires SPF or DKIM to pass for the same domain as the visible From address, and it tells receivers what to do when neither does.

ip4 / ip6
Allows an IPv4 or IPv6 address or range
include
Allows the servers in another domain's SPF record
a / mx
Allows the domain's own A or MX hosts
all
Matches everything else: -all fail, ~all soft fail
redirect
Uses another domain's SPF record instead

FAQ

SPF checker FAQ

Common questions about SPF records and why they fail.

Free lookup tool

Check the SPF record of any domain

Check the SPF record of any domain. See every include, the DNS lookup count against the limit of 10, the all qualifier and the errors that make SPF fail.