speedtest.net
Good, with 3 things to fix
speedtest.net scored 88/100 (grade B). The main issues are no DKIM key found for the common selectors and could not look up the BIMI record, plus 3 more. Detected senders: Google Workspace, SendGrid and Zendesk.
Checked 2026-10-04 02:10 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.
All checks
MXCan servers find your inbox?No issues foundPass
Nothing to report.
SPFWho may send as you?SPF ends in softfail (~all)Info
- Info: SPF ends in softfail (~all)
"~all" is common and works well with DMARC. "-all" is stricter; switch when you are sure every sender is listed.
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 speedtest.net 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 speedtest.net.
- Warning: Some DKIM lookups failed
7 of 47 selector lookups under speedtest.net returned TIMEOUT, so whether those selectors hold a key is unknown. Try again later; if it persists, check the domain's nameservers.
DMARCWhat happens to fakes?DMARC policy is quarantine; consider rejectInfo
- Info: DMARC policy is quarantine; consider reject
Failing mail goes to spam rather than being refused. When reports show no legitimate failures, reject gives the strongest protection.
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.speedtest.net 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.speedtest.net 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.speedtest.net. TLS-RPT (RFC 8460) tells senders where to send daily reports about failed encrypted deliveries to you.
How to fix this
How to fix it
Strengthen the DMARC policyTXT
Rejects mail that fails DMARC, the strongest protection against spoofing.
_dmarc.speedtest.net
Some DNS providers want just “_dmarc” here.
v=DMARC1; p=reject; rua=mailto:088836b424@rua.easydmarc.us; adkim=r; aspf=r
v=DMARC1;p=quarantine;rua=mailto:088836b424@rua.easydmarc.us;
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 speedtest.net cannot pass DMARC through DKIM.
Applies to: google._domainkey.speedtest.net
- In Google Workspace, enable DKIM signing for speedtest.net: 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
Enable DKIM for SendGridinstruction
SendGrid generates the DKIM key for each account, so the exact record must come from SendGrid. Without DKIM, mail it sends for speedtest.net cannot pass DMARC through DKIM.
Applies to: s1._domainkey.speedtest.net
- In SendGrid, enable DKIM signing for speedtest.net: account-specific: copy the CNAME/TXT from the SendGrid dashboard. Publish exactly the record SendGrid shows (TXT or CNAME) at the host name it gives, then turn signing on. Instructions: https://docs.sendgrid.com/ui/account-and-settings/how-to-set-up-domain-authentication
Enable DKIM for SendGridinstruction
SendGrid generates the DKIM key for each account, so the exact record must come from SendGrid. Without DKIM, mail it sends for speedtest.net cannot pass DMARC through DKIM.
Applies to: s2._domainkey.speedtest.net
- In SendGrid, enable DKIM signing for speedtest.net: account-specific: copy the CNAME/TXT from the SendGrid dashboard. Publish exactly the record SendGrid shows (TXT or CNAME) at the host name it gives, then turn signing on. Instructions: https://docs.sendgrid.com/ui/account-and-settings/how-to-set-up-domain-authentication
Enable DKIM for Zendesk (zendesk1)CNAME
Points the zendesk1 selector at the key Zendesk manages, so mail it sends for speedtest.net is DKIM-signed and can align with DMARC. Enable DKIM in Zendesk after publishing.
zendesk1._domainkey.speedtest.net
Some DNS providers want just “zendesk1._domainkey” here.
zendesk1._domainkey.zendesk.com
Enable DKIM for Zendesk (zendesk2)CNAME
Points the zendesk2 selector at the key Zendesk manages, so mail it sends for speedtest.net is DKIM-signed and can align with DMARC. Enable DKIM in Zendesk after publishing.
zendesk2._domainkey.speedtest.net
Some DNS providers want just “zendesk2._domainkey” here.
zendesk2._domainkey.zendesk.com
Set up a TLS report addressinstruction
Sending servers will report TLS failures when delivering to speedtest.net, 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.speedtest.net
- Pick an address that will receive TLS reports: a mailbox you read (for example tls-reports@speedtest.net, created first) or a TLS reporting service. 2. Publish a TXT record at _smtp._tls.speedtest.net with the value v=TLSRPTv1; rua=mailto:<that address>.