Excellent, with 1 thing to fix

chatgpt.com scored 92/100 (grade A). The main issue is DKIM key revoked. Detected senders: Cloudflare Email Service.

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

4 passed1 needs attention0 failing3 for informationDetected senders: Cloudflare Email Service

All checks

MXCan servers find your inbox?No issues foundPass

Nothing to report.

SPFWho may send as you?No issues foundPass

Nothing to report.

DKIMAre your emails signed?DKIM key revokedNeeds attention

Warning: DKIM key revoked
google, selector1, selector2, k1, k2, k3, s1, s2, mail, default, dkim, smtp, mandrill, pm, pm-bounces, mg, mailo, krs, email, sendinblue, brevo, hs1, hs2, amazonses, ses, zendesk1, zendesk2, fd, fd2, protonmail, protonmail2, protonmail3, zoho, everlytickey1, everlytickey2, sig1, cm, mxvault, turbo-smtp, sparkpost, scph0123, kl, kl2, resend, intercom publishes an empty p= tag, so any mail still signed with that selector fails DKIM. That is correct after a key rotation; otherwise publish the current key or stop signing with this selector.
Pass: DKIM key published
chatgpt.com publishes a DKIM key under cf2024-1, cf-bounce.

DMARCWhat happens to fakes?DMARC uses strict alignmentInfo

Info: DMARC uses strict alignment
With adkim=s or aspf=s the DKIM d= domain or the bounce domain must equal the From domain exactly; a subdomain is not enough. Third-party senders that sign or bounce from a subdomain (or their own domain) will then fail DMARC unless they are configured to use your exact domain.

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.chatgpt.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.chatgpt.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 chatgpt.com publishes an MTA-STS policy at https://mta-sts.chatgpt.com/.well-known/mta-sts.txt. Change the id whenever the policy file changes.

TypeTXT

Name / Host

_mta-sts.chatgpt.com

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

Value

v=STSv1; id=202610040203

Host the MTA-STS policy filepolicy-file

Serve this file over HTTPS with a valid certificate for mta-sts.chatgpt.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.chatgpt.com/.well-known/mta-sts.txt

Contents

version: STSv1
mode: testing
mx: route1.mx.cloudflare.net
mx: route2.mx.cloudflare.net
mx: route3.mx.cloudflare.net
max_age: 604800

Set up a TLS report addressinstruction

Sending servers will report TLS failures when delivering to chatgpt.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.chatgpt.com

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