Excellent: no problems found

cnbc.com scored 100/100 (grade A). No problems were found in the checks that ran. Detected senders: Amazon SES.

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

3 passed0 failing5 for informationDetected senders: Amazon SES

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?DKIM key publishedPass

Pass: DKIM key published
cnbc.com publishes a DKIM key under k2, k3.

DMARCWhat happens to fakes?No issues foundPass

Nothing to report.

AlignmentDoes it match your From?SPF alignment depends on a custom Return-PathInfo

Info: SPF alignment depends on a custom Return-Path
This is a heuristic. Your SPF record only authorizes third-party senders (amazonses.com). By default they bounce from their own Return-Path domain, and SPF then passes for that domain, not cnbc.com. Even relaxed alignment needs the Return-Path's organizational domain to be cnbc.com, so set up a custom Return-Path (bounce) domain under cnbc.com with each provider, and sign with DKIM as cnbc.com.

BIMICan inboxes show your logo?No BIMI recordInfo

Info: No BIMI record
No BIMI record at default._bimi.cnbc.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.cnbc.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.cnbc.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 cnbc.com publishes an MTA-STS policy at https://mta-sts.cnbc.com/.well-known/mta-sts.txt. Change the id whenever the policy file changes.

TypeTXT

Name / Host

_mta-sts.cnbc.com

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

Value

v=STSv1; id=202610040211

Host the MTA-STS policy filepolicy-file

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

Contents

version: STSv1
mode: testing
mx: mxa-00a17301.gslb.pphosted.com
mx: mxb-00a17301.gslb.pphosted.com
mx: mx0a-00a17301.pphosted.com
mx: mx0b-00a17301.pphosted.com
max_age: 604800

Set up a TLS report addressinstruction

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

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

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