Email Security Analysis of cnn.com
Complete verification of cnn.com's SPF, DKIM, DMARC, and MTA-STS records. Find out if this domain is protected against email spoofing.
Last updated: April 14, 2026
SPF
OKv=spf1 include:cnn.com._nspf.vali.email include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email include:mail.zendesk.com ~allDKIM
OKSelectors: selector1, k1, s1, s2, zendesk1, zendesk2, cmDMARC
OKv=DMARC1; p=reject; rua=mailto:dmarc_agg@vali.email; ruf=mailto:Njk3@ruf.vali.emailMX
OKcnn-com.mail.protection.outlook.comRecommendations
1Add MTA-STS to enforce TLS encryption for incoming emails
Without MTA-STS, an attacker performing a man-in-the-middle attack can downgrade the connection between mail servers to plaintext, intercepting emails in transit. MTA-STS tells sending servers to only deliver via TLS with a valid certificate, preventing downgrade attacks.
Run a live analysis
The results above are updated daily. For an instant check of cnn.com, run a live analysis.
Analyze cnn.com liveGuides to understand these results
SPF Guide
Understand how SPF defines which servers are authorized to send emails for a domain.
DKIM Guide
Discover how DKIM cryptographically signs your emails to guarantee their authenticity.
DMARC Guide
Learn how DMARC orchestrates SPF and DKIM to protect your domain.
MTA-STS Guide
Learn how MTA-STS enforces TLS encryption to protect your emails in transit.
SPF vs DKIM vs DMARC
Compare the three protocols and understand how they work together.