Check the DMARC 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
DMARC record
_dmarc.google.com
Passv=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
SPF record
1 of 10 DNS lookups
Passv=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
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)
- selector1
- selector2
- default
- dkim
- 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
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
v=TLSRPTv1;rua=mailto:sts-reports@google.com
- TLS reports go to sts-reports@google.com.
BIMI
- 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 DMARC works
DMARC builds on SPF and DKIM. A message passes DMARC when SPF passes for a Return-Path domain that matches the visible From domain, or when a DKIM signature verifies for a matching domain. Matching is called alignment: relaxed alignment accepts a subdomain, strict alignment needs the exact domain.
The record also asks receivers for reports. Aggregate reports show every server that sent mail as your domain, so you can find forgotten senders before you tighten the policy to quarantine or reject.
- p
- Policy for failing mail: none, quarantine or reject
- sp
- Policy for subdomains, defaults to p
- pct
- Share of failing mail the policy applies to
- rua
- Where receivers send aggregate reports
- adkim / aspf
- Relaxed (r) or strict (s) alignment
FAQ
DMARC checker FAQ
Common questions about DMARC policies and reports.
Related guides
Learn more from the blog
Step-by-step guides on reading and using these results.
MX Record Check: How to Find a Domain's Mail Servers
Run an MX record check with a DNS lookup tool, dig or nslookup. See the current MX values for Google Workspace, Microsoft 365, Zoho, Proton and Fastmail, what a null MX means, and how to fix common email delivery problems.
DNS Records Explained: Every Record Type With Real Examples
DNS records explained: what A, AAAA, CNAME, MX, TXT, NS, SOA, SRV, PTR, CAA and HTTPS/SVCB records do, with real dig output from live domains and the fields of each record.
How to Check DNS Records for Any Domain (Online and Command Line)
Check DNS records for any domain with an online DNS record lookup, dig, nslookup, PowerShell or DNS over HTTPS. Real output for every command, plus how to query a specific resolver or the authoritative nameserver.
Related tools
More free tools
Explore our other free lookup and analysis tools.
Free lookup tool
Check the DMARC record of any domain
Look up the DMARC record of any domain. See the policy, subdomain policy, percentage, report addresses and alignment, with a check of SPF and DKIM.