Good, with 2 things to fix

deepl.com scored 84/100 (grade B). The main issues are DKIM key shorter than 2048 bits and SPF record is very long. Detected senders: Google Workspace, Microsoft 365, Amazon SES, HubSpot, Zendesk and Salesforce.

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

3 passed2 need attention0 failing3 for informationDetected senders: Google Workspace, Microsoft 365, Amazon SES, HubSpot, Zendesk, Salesforce

All checks

MXCan servers find your inbox?Only one MX hostInfo

Info: Only one MX host
All mail for deepl.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 record is very longNeeds attention

Warning: SPF record is very long
The SPF record is 735 characters. Long TXT answers can exceed the 512-byte UDP limit and force fallback to TCP, which some receivers do not do. Replace individual IP ranges with includes or ranges, or remove services you no longer use. (Only the total length is checked: the resolver returns the record already joined, so the 255-character limit on each individual string cannot be seen here.)

DKIMAre your emails signed?DKIM key shorter than 2048 bitsNeeds attention

Warning: DKIM key shorter than 2048 bits
selector1 (1024-bit) uses an RSA key below 2048 bits. Short keys can be factored and some receivers treat them as weak. Rotate to a 2048-bit key at your sending provider.
Pass: DKIM key published
deepl.com publishes a DKIM key under google, selector1, selector2.

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 issues foundPass

Nothing to report.

MTA-STSIs mail to you encrypted?No MTA-STS recordInfo

Info: No MTA-STS record
No MTA-STS record at _mta-sts.deepl.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.deepl.com. 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

Publish the MTA-STS recordTXT

Tells sending servers that deepl.com publishes an MTA-STS policy at https://mta-sts.deepl.com/.well-known/mta-sts.txt. Change the id whenever the policy file changes.

TypeTXT

Name / Host

_mta-sts.deepl.com

Some DNS providers want just “_mta-sts” here.

Value

v=STSv1; id=202610040218

Host the MTA-STS policy filepolicy-file

Serve this file over HTTPS with a valid certificate for mta-sts.deepl.com. It lists your MX hosts and starts in testing mode; switch to mode: enforce once TLS-RPT reports show no failures.

Location

https://mta-sts.deepl.com/.well-known/mta-sts.txt

Contents

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 deepl.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.deepl.com

Pick an address that will receive TLS reports: a mailbox you read (for example tls-reports@deepl.com, created first) or a TLS reporting service. 2. Publish a TXT record at _smtp._tls.deepl.com with the value v=TLSRPTv1; rua=mailto:<that address>.