Good, with 2 things to fix

britannica.com scored 80/100 (grade B). The main issues are no DKIM key found for the common selectors and MX: mail relies on implicit A record. Detected senders: Google Workspace.

Checked 2026-10-04 02:14 UTC · fresh check

3 passed2 need attention0 failing3 for informationDetected senders: Google Workspace

All checks

MXCan servers find your inbox?Mail relies on implicit A recordNeeds attention

Warning: Mail relies on implicit A record
britannica.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 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 britannica.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 britannica.com.

DMARCWhat happens to fakes?No issues foundPass

Nothing to report.

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.britannica.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.britannica.com. MTA-STS (RFC 8461) makes sending servers require TLS and a valid certificate when delivering to you, which blocks downgrade attacks.

TLS-RPTWill you hear about failures?TLS-RPT is configuredPass

Pass: TLS-RPT is configured
TLS reports will be sent to mailto:d6cbe1b8@in.mailhardener.com.

How to fix it

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 britannica.com cannot pass DMARC through DKIM.

Applies to: google._domainkey.britannica.com

In Google Workspace, enable DKIM signing for britannica.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

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.britannica.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://britannica.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.britannica.com with v=BIMI1, l= set to the logo URL and a= set to the certificate URL.