googledomains.com
Needs work, with 3 things to fix
googledomains.com scored 65/100 (grade C). The main issues are DMARC policy is none and no DKIM key found for the common selectors, plus 1 more. Detected senders: Google Workspace.
Checked 2026-10-04 02:02 UTC · fresh check
Strengthen the DMARC policy
Quarantines 25% of mail that fails DMARC, a safe first step: check the reports for legitimate senders that fail before going further.
_dmarc.googledomains.com
Some DNS providers want just “_dmarc” here.
v=DMARC1; p=quarantine; pct=25; rua=mailto:mailauth-reports@google.com; adkim=r; aspf=r
v=DMARC1; p=none; rua=mailto:mailauth-reports@google.com
How to apply it
- Sign in where your domain’s DNS is managed. This is often where you bought the domain, such as Cloudflare, GoDaddy or Namecheap.
- Find the existing TXT record with that name and replace its value.
- Save, then come back and re-check. DNS changes can take up to a few hours to show.
All checks
MXCan servers find your inbox?Only one MX hostInfo
- Info: Only one MX host
All mail for googledomains.com goes to smtp.google.com. Most hosted providers make that one name highly available; if you run your own server, consider a backup MX.
SPFWho may send as you?SPF ends in neutral (?all)Needs attention
- Warning: SPF ends in neutral (?all)
"?all" tells receivers to treat mail from unlisted servers as neither pass nor fail, so SPF gives no protection. End the record with "-all" or "~all".
DKIMAre your emails signed?No DKIM key found for the common selectorsNeeds attention
- Warning: No DKIM key found for the common selectors
None of the 47 selectors probed under googledomains.com publish a DKIM key. DNS cannot list selectors, so a key under a custom selector may exist: find the s= value in the DKIM-Signature header of a message you sent and check that selector. If DKIM is not set up, enable it at each service that sends mail for googledomains.com.
DMARCWhat happens to fakes?DMARC policy is noneNeeds attention
- Warning: DMARC policy is none
A none policy only monitors: mail that fails DMARC is still delivered, so anyone can spoof the domain. Once reports show your legitimate senders pass, move to quarantine and then reject.
How to fix this
AlignmentDoes it match your From?No issues foundPass
Nothing to report.
BIMICan inboxes show your logo?No BIMI recordInfo
- Info: No BIMI record
No BIMI record at default._bimi.googledomains.com. BIMI is optional: it shows your logo next to your mail in supporting inboxes once DMARC is enforced.
How to fix this
MTA-STSIs mail to you encrypted?No MTA-STS recordInfo
- Info: No MTA-STS record
No MTA-STS record at _mta-sts.googledomains.com. MTA-STS (RFC 8461) makes sending servers require TLS and a valid certificate when delivering to you, which blocks downgrade attacks.
How to fix this
TLS-RPTWill you hear about failures?No TLS-RPT recordInfo
- Info: No TLS-RPT record
No TLS reporting record at _smtp._tls.googledomains.com. TLS-RPT (RFC 8460) tells senders where to send daily reports about failed encrypted deliveries to you.
How to fix this
Other fixes
Enable DKIM for Google Workspaceinstruction
Google Workspace generates the DKIM key for each account, so the exact record must come from Google Workspace. Without DKIM, mail it sends for googledomains.com cannot pass DMARC through DKIM.
Applies to: google._domainkey.googledomains.com
- In Google Workspace, enable DKIM signing for googledomains.com: Generate the key in Admin console > Apps > Gmail > Authenticate email, then publish the TXT record shown there. Publish exactly the record Google Workspace shows (TXT or CNAME) at the host name it gives, then turn signing on. Instructions: https://support.google.com/a/answer/174124
Publish the MTA-STS recordTXT
Tells sending servers that googledomains.com publishes an MTA-STS policy at https://mta-sts.googledomains.com/.well-known/mta-sts.txt. Change the id whenever the policy file changes.
_mta-sts.googledomains.com
Some DNS providers want just “_mta-sts” here.
v=STSv1; id=202610040202
Host the MTA-STS policy filepolicy-file
Serve this file over HTTPS with a valid certificate for mta-sts.googledomains.com. It lists your MX hosts and starts in testing mode; switch to mode: enforce once TLS-RPT reports show no failures.
https://mta-sts.googledomains.com/.well-known/mta-sts.txt
version: STSv1 mode: testing mx: smtp.google.com max_age: 604800
Set up a TLS report addressinstruction
Sending servers will report TLS failures when delivering to googledomains.com, which you need before enforcing MTA-STS. The address must accept TLS reports; a DMARC report address does not necessarily do so.
Applies to: _smtp._tls.googledomains.com
- Pick an address that will receive TLS reports: a mailbox you read (for example tls-reports@googledomains.com, created first) or a TLS reporting service. 2. Publish a TXT record at _smtp._tls.googledomains.com with the value v=TLSRPTv1; rua=mailto:<that address>.
Prepare BIMIinstruction
BIMI shows your logo next to messages in supporting inboxes, but only for mail that passes DMARC under an enforced policy.
Applies to: default._bimi.googledomains.com
- Enforce DMARC first: p=quarantine or p=reject at 100% (no pct below 100). 2. Convert your logo to an SVG Tiny PS file and host it over HTTPS, for example https://googledomains.com/bimi/logo.svg. 3. For Gmail and Apple Mail, obtain a VMC or CMC certificate for the logo. 4. Publish a TXT record at default._bimi.googledomains.com with v=BIMI1, l= set to the logo URL and a= set to the certificate URL.