googleusercontent.com
Poor, with 6 things to fix
googleusercontent.com scored 57/100 (grade D). The main issues are DMARC policy is none and no DKIM key found for the common selectors, plus 5 more. Detected senders: Google Workspace.
Checked 2026-10-04 02:02 UTC · fresh check
Diagnosis notes
- Warning: DNS lookup budget exhausted
This diagnosis stopped sending DNS queries after 150 queries. Checks that needed more lookups report their remaining results as unknown; the domain's records may be unusually large or slow to answer.
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.googleusercontent.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?Mail relies on implicit A recordNeeds attention
- Warning: Mail relies on implicit A record
googleusercontent.com has no MX records, so senders fall back to its A/AAAA address (RFC 5321 implicit MX). Publish an explicit MX record, or a null MX ("0 .") if the domain should not receive mail.
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 googleusercontent.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 googleusercontent.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?Could not look up the BIMI recordNeeds attention
- Warning: Could not look up the BIMI record
The TXT query for default._bimi.googleusercontent.com returned TIMEOUT, so BIMI status is unknown. Try again later.
MTA-STSIs mail to you encrypted?Could not look up the MTA-STS recordNeeds attention
- Warning: Could not look up the MTA-STS record
The TXT query for _mta-sts.googleusercontent.com returned TIMEOUT, so MTA-STS status is unknown. Try again later.
TLS-RPTWill you hear about failures?No TLS-RPT recordInfo
- Info: No TLS-RPT record
No TLS reporting record at _smtp._tls.googleusercontent.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 googleusercontent.com cannot pass DMARC through DKIM.
Applies to: google._domainkey.googleusercontent.com
- In Google Workspace, enable DKIM signing for googleusercontent.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
Set up a TLS report addressinstruction
Sending servers will report TLS failures when delivering to googleusercontent.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.googleusercontent.com
- Pick an address that will receive TLS reports: a mailbox you read (for example tls-reports@googleusercontent.com, created first) or a TLS reporting service. 2. Publish a TXT record at _smtp._tls.googleusercontent.com with the value v=TLSRPTv1; rua=mailto:<that address>.