Engineer's DNS Intelligence Report
TLP:AMBER
Limited disclosure — recipients may share within their organization only
Engineer's DNS Intelligence Report
cnn.com
Posture Drift Detected
Compared against your previous observation on 6 Mar 2026 14:24 UTC.
| Field | Previous | Current | |
|---|---|---|---|
| BIMI Status | warning | success |
DNS Security & Trust Posture
Risk Level:
Low Risk
4 protocols configured, 4 not configured, 1 unavailable on provider
Why we go beyond letter grades
Analysis Confidence (ICD 203)
MODERATE
66/100
Resolver agreement is inconsistent for some protocols, limiting confidence. Data currency and system maturity are adequate.
Accuracy 63%
Currency 70/100
Maturity verified
Limiting factor: Resolver agreement is low for this scan — some protocols returned inconsistent results across resolvers
Intelligence Currency
Data Currency:
Adequate
70/100
Currentness Excellent
TTL Compliance Excellent
Completeness Degraded
Source Credibility Excellent
TTL Relevance Stale
DNS data shows some aging or gaps — consider re-scanning for critical decisions
The following DNS record TTLs deviate from recommended values. Incorrect TTLs can cause caching issues, slow propagation, or unnecessary DNS traffic.
| Record Type | Observed TTL | Typical TTL | Severity | Context |
|---|---|---|---|---|
| A | 54s |
1 hour (3600s) |
high | A TTL is below typical — observed 54s, typical value is 1 hour (3600s). Short TTLs increase DNS query volume but enable faster propagation. If you are preparing for a migration or need rapid failover, this may be intentional (RFC 1035 §3.2.1). For steady-state production, consider 3600 seconds per NIST SP 800-53 SI-18 relevance guidance. Use the TTL Tuner for profile-specific recommendations. |
| AAAA | 76s |
1 hour (3600s) |
high | AAAA TTL is below typical — observed 76s, typical value is 1 hour (3600s). Short TTLs increase DNS query volume but enable faster propagation. If you are preparing for a migration or need rapid failover, this may be intentional (RFC 1035 §3.2.1). For steady-state production, consider 3600 seconds per NIST SP 800-53 SI-18 relevance guidance. Use the TTL Tuner for profile-specific recommendations. |
| NS | 13370s |
1 day (86400s) |
medium | NS TTL is below typical — observed 13370s, typical value is 1 day (86400s). Short TTLs increase DNS query volume but enable faster propagation. If you are preparing for a migration or need rapid failover, this may be intentional (RFC 1035 §3.2.1). For steady-state production, consider 86400 seconds per NIST SP 800-53 SI-18 relevance guidance. Use the TTL Tuner for profile-specific recommendations. |
| MX | 5 minutes (300s) |
1 hour (3600s) |
high | MX TTL is below typical — observed 5 minutes (300s), typical value is 1 hour (3600s). Short TTLs increase DNS query volume but enable faster propagation. If you are preparing for a migration or need rapid failover, this may be intentional (RFC 1035 §3.2.1). For steady-state production, consider 3600 seconds per NIST SP 800-53 SI-18 relevance guidance. Use the TTL Tuner for profile-specific recommendations. |
| SOA | 15 minutes (900s) |
1 hour (3600s) |
medium | SOA TTL is below typical — observed 15 minutes (900s), typical value is 1 hour (3600s). Short TTLs increase DNS query volume but enable faster propagation. If you are preparing for a migration or need rapid failover, this may be intentional (RFC 1035 §3.2.1). For steady-state production, consider 3600 seconds per NIST SP 800-53 SI-18 relevance guidance. Use the TTL Tuner for profile-specific recommendations. |
| TXT | 5 minutes (300s) |
1 hour (3600s) |
high | TXT TTL is below typical — observed 5 minutes (300s), typical value is 1 hour (3600s). Short TTLs increase DNS query volume but enable faster propagation. If you are preparing for a migration or need rapid failover, this may be intentional (RFC 1035 §3.2.1). For steady-state production, consider 3600 seconds per NIST SP 800-53 SI-18 relevance guidance. Use the TTL Tuner for profile-specific recommendations. |
Big Picture Questions
- How often do you actually change this record? If it hasn’t changed in months, a short TTL is generating unnecessary DNS queries without any benefit.
- Are you preparing for a migration or IP change? Short TTLs make sense temporarily — but should be raised back to 1 hour (3600s) once the change is complete.
- Every DNS lookup adds 20–150ms of latency. With a 60s TTL, returning visitors trigger a fresh lookup every minute. With 3600s, they get cached responses for an hour — faster page loads, no extra infrastructure needed.
- Google runs A records at ~30s because they operate a global anycast network and need to steer traffic dynamically. For a typical website without that infrastructure, copying those TTLs increases query volume with zero upside.
Primary NS
ns-1652.awsdns-14.co.uk
Serial
1
Admin
awsdns-hostmaster.amazon.com
Provider
AWS Route 53
| Timer | Value | RFC 1912 Range |
|---|---|---|
| Refresh | 7200s | 1,200–43,200s (20 min – 12 hrs) |
| Retry | 900s | Fraction of Refresh |
| Expire | 1209600s | 1,209,600–2,419,200s (14–28 days) |
| Minimum (Neg. Cache) | 86400s | 300–86,400s (5 min – 1 day) |
All SOA timer values are within RFC 1912 recommended ranges.
Independent RFC compliance assessment for AWS Route 53. Each finding cites the specific RFC section and reports what the engineering community consensus is. We report honestly — if a provider deviates from standards, we explain what they did differently and what the RFCs actually say.
Alias record TTLs fixed at 60s
RFC 1035 §3.2.1
AWS Route 53 alias records pointing to AWS resources (ELB, CloudFront, S3, API Gateway) have a fixed TTL of 60 seconds that cannot be modified. Route 53 alias records are an AWS-specific extension — not part of standard DNS RFCs. They solve the CNAME-at-apex problem (RFC prohibits CNAME at zone apex) by appearing as A/AAAA records to resolvers. The 60-second TTL ensures fast failover but removes administrator TTL control.
Proprietary extension — not covered by DNS RFCs
Email Spoofing
Protected
Brand Impersonation
Protected
DNS Tampering
Unsigned
Certificate Control
Open
Configured
SPF, DMARC (reject), DKIM, BIMI
Not Configured
MTA-STS, TLS-RPT, DNSSEC, CAA
Unavailable on Provider
DANE
Priority Actions
4 total
Achievable posture: Secure
Medium
Enable DNSSEC
DNSSEC is not enabled for this domain. DNSSEC provides cryptographic authentication of DNS responses, preventing cache poisoning and DNS spoofing attacks.
Low
Add CAA Records
CAA records specify which Certificate Authorities may issue certificates for your domain, reducing the risk of unauthorized certificate issuance.
CAA constrains which CAs can issue certificates for this domain.
| Field | Value |
|---|---|
| Type | CAA |
| Host | cnn.com (root of domain — adjust CA to match your provider) |
| Value | 0 issue "letsencrypt.org" |
Low
Add TLS-RPT Reporting
TLS-RPT (TLS Reporting) sends you reports about TLS connection failures when other servers try to deliver mail to your domain.
TLS-RPT sends you reports about TLS connection failures to your mail servers.
| Field | Value |
|---|---|
| Type | TXT |
| Host | _smtp._tls.cnn.com (SMTP TLS reporting record) |
| Value | v=TLSRPTv1; rua=mailto:tls-reports@cnn.com |
Low
Deploy MTA-STS
MTA-STS enforces TLS encryption for inbound mail delivery, preventing downgrade attacks on your mail transport.
MTA-STS tells sending servers to require TLS when delivering mail to your domain.
| Field | Value |
|---|---|
| Type | TXT |
| Host | _mta-sts.cnn.com (MTA-STS policy record) |
| Value | v=STSv1; id=cnn.com |
Registrar (RDAP)
OBSERVED
LIVE
Nom-iq Ltd. dba COM LAUDE
Where domain was purchased
Email Service Provider
INFERRED
Microsoft 365
Strongly Protected
Web Hosting
Unknown
Where website is hosted
DNS Hosting
OBSERVED
Amazon Route 53
Where DNS records are edited
Email Security Methodology Can this domain be impersonated by email? No SPF and DMARC reject policy enforced
SPF Record RFC 7208 §4 Verified
Does this domain declare who may send email on its behalf?
Yes
Success
~all
3/10 lookups
SPF valid with industry-standard soft fail (~all), 3/10 lookups
v=spf1 include:cnn.com._nspf.vali.email include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email include:mail.zendesk.com ~all
RFC 7208 Conformant — This SPF record conforms to the syntax and semantics defined in RFC 7208 §4.
RFC Failure Mode: Unlike DMARC (where unknown tags are silently ignored per RFC 7489 §6.3), SPF with unrecognized mechanisms produces a PermError per RFC 7208 §4.6 — the record fails loudly rather than silently.
Related CVEs:
CVE-2024-7208 (multi-tenant domain spoofing),
CVE-2024-7209 (shared SPF exploitation),
CVE-2023-51764 (SMTP smuggling bypasses SPF)
~all is the industry standard.
Google, Apple, and most providers default to soft fail. CISA (BOD 18-01) and RFC 7489 confirm that DMARC policy — not SPF alone — is the primary enforcement control. Using ~all allows DKIM to be evaluated before a DMARC decision is made.
This domain uses ~all + DMARC reject: the strongest compatible security stance, aligned with CISA and RFC guidance.
DMARC Policy RFC 7489 §6.3 Verified
Are spoofed emails rejected or quarantined?
Yes — reject policy
Success
p=reject
DMARC policy reject (100%) - excellent protection
v=DMARC1; p=reject; rua=mailto:dmarc_agg@vali.email; ruf=mailto:Njk3@ruf.vali.email
Alignment:
SPF relaxed
DKIM relaxed
No np= tag (DMARCbis) — non-existent subdomains inherit p= policy but adding np=reject provides explicit protection against subdomain spoofing
Forensic reporting (ruf) is configured, but most major providers do not send forensic reports.
RFC 7489 §7.3 warns that forensic reports can expose PII (full message headers or bodies). Google, Microsoft, and Yahoo do not honour ruf= requests. The DMARCbis draft (draft-ietf-dmarc-dmarcbis) has formally removed ruf= from the specification. Consider removing this tag to simplify your record.
RFC 7489 §7.3 — Forensic Reports
RFC 7489 Conformant — DMARC record conforms to RFC 7489 §6.3 with full enforcement.
DMARCbis (Pending): draft-ietf-dmarc-dmarcbis will elevate DMARC to Standards Track, obsolete RFC 7489, replace
pct= with t= (testing flag), add np= (non-existent subdomain policy), and mandate DNS tree walk for policy discovery instead of the Public Suffix List.Related CVEs:
CVE-2024-49040 (Exchange sender spoofing),
CVE-2024-7208 (multi-tenant DMARC bypass)
DKIM Records RFC 6376 §3.6 Verified
Are outbound emails cryptographically signed?
Yes — verified
Found
2048-bit
Found DKIM for 9 selector(s) with strong keys (2048-bit)
DKIM key management delegated —
_domainkey.cnn.com NS records point to
an external service
(ns.vali.email).
DKIM selectors are dynamically managed and may include keys for services beyond what static scanning discovers.
cm._domainkey
Campaign Monitor
2048-bit
Adequate
v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDJkTS3JcJ4hQRsv1cliVntd8zWldCF+myBiXRgwIdqdlbQ+s/yIsTBHd0gk+A+FpqNH+2BLeyqPEsgeaO4/o4YlwiN7OKP43+s01i/jLBHKDOI37XRz3muKZeAoYDXlXvOWo9FDnzvcQtbxI89qtBEwgtfSloQaIa+Vc+fny8m2wIDAQAB
k1._domainkey
MailChimp
2048-bit
Adequate
k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDbNrX2cY/GUKIFx2G/1I00ftdAj713WP9AQ1xir85i89sA2guU0ta4UX1Xzm06XIU6iBP41VwmPwBGRNofhBVR+e6WHUoNyIR4Bn84LVcfZE20rmDeXQblIupNWBqLXM1Q+VieI/eZu/7k9/vOkLSaQQdml4Cv8lb3PcnluMVIhQIDAQAB;
k2._domainkey
MailChimp
2048-bit
Adequate
v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAv2aC2KjGKLOwTweBY5A9RpjsxaBXR9r7OAU6U8/zn92ivImI75naUujWbItRI/QmL1jy5PWGqLwoUA0b90ObWaLDc+i9MtTNmGeWO009hr20fIxhGg6XBT2kjZ1DTThopSe1nAndsupmcBwlQ5Q6LJ+ZAxLcujnPIxM0ZBLmgpkv8u6RfY4eFP8OLvdAW3oSuB0DyLDigQX4Sj8wBO4YIdQH6AAmBeOsidsKAFNFUCpc3vCxtBDR12U+cBg724l3sBkMQ8evnz6idnqxq9QAVYh8k4kJ+RP+6cqTdy7LjIm8xY/bQNpQIpGUAuDo2DjLcCDun9DAI4Q/3z+Q0o9QuQIDAQAB;
k3._domainkey
MailChimp
2048-bit
Adequate
v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAsYGiMSn7fsUqSvfSX40x9R1OlRtbNiCY80lHRIlcKx3XDIR7257aUx+q9CSIARdfTL6KCuLGNFx5g9TgVr6png4ajcieSQGtOehBgxnkDN8aAA5TX0FmFrcefJU0JoxLOF09EKgXxhSSHCk/ekVb0PXSboHXoZ9+EI404F1qhcwXXIgHXTaUthHTut2P6BBZhIXIgvDe/w49GchR7MRJqjNb7neEBbYHbgWuBTvvHCg7Gy6m6n9krYK+ROWq3dVvXy9plAGK3ygM+HtjIiMt7arRGMOF0WgDTz7YdN9BGpt6BvXxLnjiQcgS5T9n+cIyPZgiWzDMXNlaEEdKTEKxrwIDAQAB;
s1._domainkey
SendGrid
2048-bit
Adequate
v=DKIM1; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA88f6zN6iyp0Ap9i5+jvyXNYobGlrz2yQa9satn9k/iVN3w3/mdlza3725zeY0uGF0eTbSYzKoyAhztZIYTvzGVnAdMYN0ZtHGt357SfWDfaUykyvm2Q/OEH9DejvQLc+GKCLUK3M0h8h9iCsB7OdFNAI/F1KpZn1IuXwcPY8ecRKy98DU71Ef+JU4CoSj3G/yn5j3B9xmxjOx7av9RoCdyoSqyXBHOtt3V+h+k/3IQOtvjG1FqSg/nxx4Dnbh/0q0RYu3KXLVDSVNUZ5bGDF1kuWzd/P+GCn2rIHVb7FgruAzmLFkKecgZ1NmnS01teUFnvlPu1bJJV4PpKhjW+IKQIDAQAB
s2._domainkey
SendGrid
2048-bit
Adequate
v=DKIM1; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAv/LydSz5l39sYLpWSJsw8BZ8x0RdaBUc31QWlsia/V+E0ow0l9uo4bWaYC46ODGOlAVmZ6Q5jojNLWp6YU/lv9gjEomYdTqhPvq02LbEQTpkmSNX1QYtu/QCsOS2DffbnjRXuJnzJ21PHOMn6XR7eZlQTVR1kd8ilR632gwaPzwxWAqMn0UkxE/TjqqRNpqP5iDhJEbILKOoVoVQzenKoRMSC09Rhep3N3oMjzGjtL+uchdxJpXA/X4KMKAlt9HogXm8gQuwEdWhSwzVgayxn0BH5Hs6ylwa7hALnbG6rBN/tTNJ9+Uu0PmIrMdu1cUU3EPtyeXPWbwumOnCmnDyjwIDAQAB
selector1._domainkey
Microsoft 365
2048-bit
Adequate
v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAsZc1FOMkCaNoC09qvvioKK+kWxS6jryfj6cm9XM/tUOFLANNhYR/x+UegUkG9Dmnr50vQw51Pc+I6zYwfxMC/AAQNblgbLkRm6+hyowhrkF3YJUtCOK8Z1XFpqC3Ra86ajMiphbHGRlkJpvvPdqqYbHayfeMbWg0Hd3FsigRfGZKAllvVO3Y8IK5Ivi6PlNf7Yr66BVPEPB99gJXqnRH8+IWmOIOwIVwrYQcDAYxmhM1tp7ULCC+1d7a9IS9X+BzxExHINvJRU5p9RBArAZPrD8/tZ91jkOF+Rf65wsGs+nKtVr6HTtjizIH2YGRiBTzBhWKGMpAgge1Xue4VQoXCQIDAQAB;
zendesk1._domainkey
Zendesk
2048-bit
Adequate
v=DKIM1;t=s;n=core;k=rsa;p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA9IqdLrO3Zr2/56MHt8oQVCQorP0Bl2Fz9sM2tFBnJCdB/HogQmuudEg2xAovCN2PYpw44UijIvPuBoT9vxiv6ZCBJTLJXa82r6ke5rE4tbe9NKFIrVIb9S306cJDrnKFMDb8p0dU/Su0+eUR5gVAOtCuz2L8HAzs5edvsEvD/Fb4ny1RLNSEPZkIQLfGhVxQeWANm3+1Jwb/OBVXV9k0nKpWrpgqcmO7NzroJirp014RQY7rGi60JLUubc6XhvoFQBQrtOAdVlZC5wvfS1bgpq5kQpdP7cajIqWCeqxPTeo0ZUpey2ZcaygEsZz0Z3Gs5wDzyuqd7/ADpr2jNF7ozwIDAQAB
zendesk2._domainkey
Zendesk
2048-bit
Adequate
v=DKIM1; t=s; n=core; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAmiSFNkgXrO3I8aOaPONDZWHv027rkiGIwb838OyXPgvFDEkCV/qGcdXSjZnaVAadrTm/oKnL8WOltP9zB1FLEuKt0fTi5zRyKPE4oIYCnEzXwrGqzjUcCABQBawQVqvXjDOaYh9Lhp8W5PYOLo905vRW7ipyIMDhuzBOJls91/WWXnNK0OwP3RghiisZjA3K2KqtRwf7w6GjNeNuAMNhvcmgAN15d/mhK+dev/hcRbal66RoYyTD8c0F0isahWH0envEX8aj+SBhheNk0/U37dGE+4nFaY5yP9CUlYjFKDSIKZgHzG4Hci3t/RubU58pi6BCrQQdAFvIOeDFeCZ0ywIDAQAB
RFC 6376 Conformant — DKIM keys and signatures conform to RFC 6376 §3.6 (Internet Standard).
Known Vulnerabilities:
DKIM
l= tag body length vulnerability (attacker appends unsigned content to signed mail),
weak key exploitation (keys below 1024-bit are cryptographically breakable per RFC 6376 §3.3.3),
DKIM replay attacks (re-sending legitimately signed messages at scale)
MTA-STS RFC 8461 §3 Verified
Can attackers downgrade SMTP to intercept mail?
Not prevented
Warning
No MTA-STS record found
MTA-STS policy enforcement is evaluated in Mail Transport Security below.
TLS-RPT RFC 8460 §3 Verified
Will failures in TLS delivery be reported?
No reporting
Warning
No TLS-RPT record found
DMARC External Reporting Authorization RFC 7489 §7.1
Are external report receivers authorized?
Yes — all authorized
Success
All 2 external reporting domains properly authorized
| External Domain | Authorization | Auth Record |
|---|---|---|
vali.email |
Authorized |
v=DMARC1;
|
ruf.vali.email |
Authorized |
v=DMARC1;
|
DANE / TLSA Verified Recon Methodology Can mail servers establish identity without a public CA? No
DANE not available — Microsoft 365 does not support inbound DANE/TLSA on its MX infrastructure
DANE not deployable on Microsoft 365
Microsoft 365 does not support DANE for inbound mail. Microsoft uses its own certificate pinning mechanism.
Recommended alternative: MTA-STS
Email Transport Security
Two mechanisms protect email in transit. DANE is the primary standard; MTA-STS is the alternative for domains that cannot deploy DNSSEC:
- DNSSEC + DANE (RFC 7672) — Cryptographic chain of trust from DNS root to mail server certificate. Eliminates reliance on certificate authorities. No trust-on-first-use weakness. Requires DNSSEC.
- MTA-STS (RFC 8461) — HTTPS-based policy requiring TLS for mail delivery. Works without DNSSEC but relies on CA trust and is vulnerable on first use (§10). Created for domains where “deploying DNSSEC is undesirable or impractical” (§2).
Industry trend: Microsoft Exchange Online enforces inbound DANE with DNSSEC (GA October 2024), and providers like Proton Mail and Fastmail also support DANE. Google Workspace does not support DANE and relies on MTA-STS. Both mechanisms coexist because DANE is backward-compatible — senders skip the check if the domain isn't DNSSEC-signed (RFC 7672 §1.3).
Brand Security Can this brand be convincingly faked? Unlikely DMARC reject policy blocks email spoofing (RFC 7489 §6.3) and BIMI with VMC provides verified brand identity in inboxes — email-based brand faking is effectively blocked; adding CAA records (RFC 8659) would further restrict certificate issuance for lookalike domains
BIMI BIMI Spec Verified Success VMC SVG
Is the brand identity verified and displayed in inboxes?
Yes
BIMI with VMC certificate (from Verified CA)
VMC certificate accessible (from Verified CA) - logo displays in Gmail, Apple Mail, and all major providers.
v=BIMI1; l=https://amplify.valimail.com/bimi/time-warner/vmNHnljIYyW-cable_news_network_inc_1325272691.svg; a=https://amplify.valimail.com/bimi/time-warner/vmNHnljIYyW-cable_news_network_inc_1325272691.pem
Logo validated (SVG)
View full logo
CAA RFC 8659 §4 Verified Warning
Does this domain restrict who can issue TLS certificates?
No
No CAA records found - any CA can issue certificates
Vulnerability Disclosure Policy (security.txt) Is there a verified way to report security issues? No RFC 9116
No security.txt found
A security.txt file at
/.well-known/security.txt provides security researchers with a standardized way to report vulnerabilities.
See securitytxt.org for a generator.
AI Surface Scanner Beta Is this domain discoverable by AI — and protected from abuse? No
No AI governance measures detected
llms.txt llmstxt.org
Is this domain publishing AI-readable brand context?
No
No llms.txt found
No llms-full.txt found
AI Crawler Governance (robots.txt) RFC 9309 IETF Draft
Are AI crawlers explicitly allowed or blocked?
Not blocked
No AI crawler blocking observed — no blocking directives found in robots.txt
Content-Usage Directive IETF Draft
Does the site express AI content-usage preferences?
Not Configured
No Content-Usage directive detected.
The IETF AI Preferences working group is developing a
Content-Usage: directive for robots.txt that lets site owners declare whether their content may be used for AI training and inference. This is an active draft, not yet a ratified standard.
Example: Add
Content-Usage: ai=no to robots.txt to deny AI training, or Content-Usage: ai=allow to explicitly permit it.
Without this directive, AI crawler behavior depends on individual crawler policies and User-agent rules.
AI Recommendation Poisoning
Is this site trying to manipulate AI recommendations?
No
No AI recommendation poisoning indicators found
Hidden Prompt Artifacts
Is hidden prompt-injection text present in the source?
No
No hidden prompt-like artifacts detected
Evidence Log (1 item)
| Type | Detail | Severity | Confidence |
|---|---|---|---|
robots_txt_no_ai_blocks |
robots.txt found but no AI-specific blocking directives | low | Observed |
Public Exposure Checks Are sensitive files or secrets exposed? No
No exposed secrets detected in public page source — same-origin, non-intrusive scan of publicly visible page source and scripts.
No exposed secrets, API keys, or credentials were detected in publicly accessible page source or scripts.
What type of scan is this?
This is OSINT (Open Source Intelligence) collection — we check the same publicly accessible URLs that any web browser could visit. No authentication is bypassed, no ports are probed, no vulnerabilities are exploited.
Is this a PCI compliance scan? No. PCI DSS requires scans performed by an Approved Scanning Vendor (ASV) certified by the PCI Security Standards Council. DNS Tool is not an ASV. If you need PCI compliance scanning, engage a certified ASV such as Qualys, Tenable, or Trustwave.
Is this a penetration test? No. Penetration testing involves active exploitation attempts against systems with authorization. Our checks are passive observation of publicly accessible resources — the same methodology used by Shodan, Mozilla Observatory, and other OSINT platforms.
DNS Server Security Hardened
No DNS server misconfigurations found on ns-1242.awsdns-27.org — Nmap NSE probes for zone transfer (AXFR), open recursion (RFC 5358), nameserver identity disclosure, and DNS cache snooping.
| Check | Result | Detail |
|---|---|---|
| Zone Transfer (AXFR) | Denied | Test inconclusive |
| Open Recursion | Disabled | Test inconclusive |
| Nameserver Identity | Hidden | Test inconclusive |
| Cache Snooping | Protected | Test inconclusive |
Tested nameservers: ns-1242.awsdns-27.org, ns-587.awsdns-09.net, ns-378.awsdns-47.com, ns-1652.awsdns-14.co.uk
Delegation Consistency 1 Issue
Delegation consistency: 1 issue(s) found — Parent/child NS delegation alignment: DS↔DNSKEY, glue records, TTL drift, SOA serial sync.
Findings:
- Could not retrieve NS TTL from parent zone
DS ↔ DNSKEY Alignment Aligned
Glue Record Completeness Complete
| Nameserver | In-Bailiwick | IPv4 Glue | IPv6 Glue | Status |
|---|---|---|---|---|
ns-1242.awsdns-27.org |
No | N/A | N/A | OK |
ns-1652.awsdns-14.co.uk |
No | N/A | N/A | OK |
ns-378.awsdns-47.com |
No | N/A | N/A | OK |
ns-587.awsdns-09.net |
No | N/A | N/A | OK |
NS TTL Comparison Drift
Child TTL: 172800s
Drift: 0s
SOA Serial Consistency Consistent
ns-1242.awsdns-27.org: 1ns-1652.awsdns-14.co.uk: 1ns-378.awsdns-47.com: 1ns-587.awsdns-09.net: 1Nameserver Fleet Matrix Healthy
Analyzed 4 nameserver(s) for cnn.com — Per-nameserver reachability, ASN diversity, SOA serial sync, and lame delegation checks.
| Nameserver | IPv4 | IPv6 | ASN / Operator | UDP | TCP | AA | SOA Serial |
|---|---|---|---|---|---|---|---|
ns-1652.awsdns-14.co.uk |
205.251.198.116 | 2600:9000:5306:7400::1 |
AS16509
Amazon.com, Inc. |
1 | |||
ns-1242.awsdns-27.org |
205.251.196.218 | 2600:9000:5304:da00::1 |
AS16509
Amazon.com, Inc. |
1 | |||
ns-587.awsdns-09.net |
205.251.194.75 | 2600:9000:5302:4b00::1 |
AS16509
Amazon.com, Inc. |
1 | |||
ns-378.awsdns-47.com |
205.251.193.122 | 2600:9000:5301:7a00::1 |
AS16509
Amazon.com, Inc. |
1 |
Unique ASNs
1
Unique Operators
1
Unique /24 Prefixes
4
Diversity Score
Fair
1 ASN(s), 4 /24 prefix(es) — consider adding diversity
Mail Transport Security Beta Is mail transport encrypted and verified? No No MTA-STS or DANE — mail transport encryption is opportunistic only
All 1 server(s) verified: encrypted transport confirmed via direct SMTP probe and DNS policy
Policy Assessment Primary
- Microsoft 365 enforces TLS 1.2+ with DANE (GA Oct 2024) and valid certificates
Telemetry
TLS-RPT not configured — domain has no visibility into TLS delivery failures from real senders
Live Probe Supplementary
| MX Host | STARTTLS | TLS Version | Cipher | Certificate |
|---|---|---|---|---|
cnn-com.mail.protection.outlook.com |
TLSv1.3 | TLS_AES_256_GCM_SHA384 |
Valid
Expires: 2026-08-26 (172 days) Issuer: DigiCert Inc |
Multi-Vantage Probe Results
Unanimous: TLS verified
2 probes, 1 responded
France - EU
observed
All servers support TLS
US-East (Boston)
skipped
Infrastructure Intelligence Who hosts this domain and what services power it? Direct
ASN / Network Success
Resolved 1 unique ASN(s) across 8 IP address(es)
| ASN | Name | Country |
|---|---|---|
AS54113 |
Fastly, Inc. | US |
IPv4 Mappings:
151.101.3.5 → AS54113 (151.101.0.0/22)151.101.131.5 → AS54113 (151.101.128.0/22)151.101.67.5 → AS54113 (151.101.64.0/22)151.101.195.5 → AS54113 (151.101.192.0/22)
IPv6 Mappings:
2a04:4e42:400::773 → AS54113 (2a04:4e42:400::/48)2a04:4e42:600::773 → AS54113 (2a04:4e42:600::/48)2a04:4e42:200::773 → AS54113 (2a04:4e42:200::/48)2a04:4e42::773 → AS54113 (2a04:4e42::/48)Edge / CDN Success
Domain appears to use direct origin hosting
SaaS TXT Footprint Success 9 services
9 SaaS services detected via DNS TXT verification records
Detects SaaS services that leave DNS TXT verification records (e.g., domain ownership proofs). Does not detect all SaaS platforms — only those indicated by DNS.
| Service | Verification Record |
|---|---|
| Google Workspace | google-site-verification=R-Btow3Z8oU_9H1IWU4Gm4lvUQ_OVmsfxonIKhIaiPE |
| Stripe | stripe-verification=1488a36c1dc125ea564dc5822d1414eeed68875825aaf90df27ac3131d05... |
| Microsoft 365 | MS=ms66433104 |
| MongoDB Atlas | mongodb-site-verification=mtrxHeW3jOzWtwEwnOLpeQo9NXh6Lqas |
| Facebook / Meta | facebook-domain-verification=xszi21kow2trmw3xt3ph6s631zyu3i |
| Adobe | adobe-idp-site-verification=279ead95-3581-42b7-82f4-73c97f8cebfa |
| Canva | canva-site-verification=_RUUWoBDVpt0pfonUPWJgg |
| Atlassian | atlassian-domain-verification=joqe6L8dNi+aisGbB1XHQa0pDc53V2l0GQQRUtLEcr2997x0+r... |
| Cisco Umbrella | cisco-ci-domain-verification=4a1c92ef69fe42f8125c3ca9ce0696dcf6cc16fa80243257de5... |
Domain Security Methodology Can DNS responses be tampered with in transit? Possible DNSSEC is not deployed, DNS responses are not cryptographically verified
DNSSEC RFC 4033 §2 Verified Unsigned
DNSSEC not configured - DNS responses are unsigned
Enterprise DNS Context: DNSSEC is the only standardized, DNS-verifiable mechanism that cryptographically authenticates responses between authoritative servers and resolvers (RFC 4033 §2, RFC 4035). Without it, DNS responses are technically vulnerable to in-transit tampering. Enterprise operators may employ compensating controls (anycast, DDoS mitigation, private peering, TSIG) — however, these do not provide DNS-layer data authentication to third-party resolvers and are not verifiable via DNS alone.
Visibility: DNS-only — network-layer compensating controls cannot be observed or verified through DNS queries. This assessment reflects what is provable from the DNS evidence available.
NS Delegation Verified
4 nameserver(s) configured
Nameservers:
ns-1242.awsdns-27.org
ns-1652.awsdns-14.co.uk
ns-378.awsdns-47.com
ns-587.awsdns-09.net
Managed DNS
All 4 nameservers hosted by Amazon Route 53. Managed DNS provides reliable resolution with provider-maintained infrastructure.
DNS provider(s):
Amazon Route 53
Multi-Resolver Verification
Recon:
Discrepancy detected -
Some resolvers returned different results
(1 difference found)
Resolver Differences:
TXT: OpenDNS returned different results: [126953328-4422040 133461244-4422058 178953534-4422001 186844776-4422028 228426766-4422034 267933795-4422004 287893558-4422013 294913881-4422049 299762315-4422055 321159687-4422031 349997471-4422043 353665828-4422052 528183251-4422019 553992719-4400647 MS=ms66433104 ms=ms97284866]
This may indicate DNS propagation in progress or geo-based DNS routing.
Traffic & Routing Where does this domain's traffic actually terminate?
AIPv4 Address
151.101.3.5
151.101.131.5
151.101.67.5
151.101.195.5
Where the domain points for web traffic
AAAAIPv6 Address
2a04:4e42:400::773
2a04:4e42:600::773
2a04:4e42:200::773
2a04:4e42::773
IPv6 ready
MXMail Servers
10 cnn-com.mail.protection.outlook.com.
Priority + mail server for email delivery
Microsoft 365
SRVServices
_autodiscover._tcp: 0 0 443 autodiscover.turner.com.
_sip._tls: 100 1 443 sipdir.online.lync.com.
_sipfederationtls._tcp: 100 1 5061 sipfed.online.lync.com.
SIP, XMPP, or other service endpoints
Web:
Reachable
(4 IPv4, 4 IPv6)
Mail:
1 server
Services:
3 endpoints
Subdomain Discovery RFC 6962 Recon LIVE What subdomains and infrastructure are exposed in certificate logs? 1068 subdomains discovered
How did we find these?
303 unique certificates
1068 current
0 expired
23 CNAMEs
Source: Certificate Transparency + DNS Intelligence
Subdomains discovered via CT logs (RFC 6962), DNS probing of common service names, and CNAME chain traversal.
Wildcard certificate detected:
*.cnn.com
Active
10 certs
2 CAs: Amazon, GlobalSign nv-sa
Explicit SANs found on wildcard certificates:
These hostnames were specifically listed alongside the wildcard — revealing infrastructure the operator intentionally secured.
*.api.cnn.com
*.api.electiontracker.cnn.com
*.api.platform.cnn.com
*.arabic.cnn.com
*.blogs.cnn.com
*.cdn.cnn.com
*.cdp.cnn.com
*.cerebro.api.cnn.com
*.client.appletv.cnn.com
*.edition.cnn.com
*.edition.i.cdn.cnn.com
*.edition.stage.next.cnn.com
*.edition.stage2.next.cnn.com
*.edition.stage3.next.cnn.com
*.elections.cnn.com
*.electiontracker.cnn.com
*.go.cnn.com
*.i.cdn.cnn.com
*.money.cnn.com
*.next.cnn.com
*.odm.platform.cnn.com
*.platform.cnn.com
*.stage.next.cnn.com
*.stage2.next.cnn.com
*.stage3.next.cnn.com
*.stellar.cnn.com
*.travel.cnn.com
*.www.i.cdn.cnn.com
api.etp.cnn.com
client.appletv.cnn.com
i.cdn.travel.cnn.com
preview.dev.money.cnn.com
preview.qa.money.cnn.com
preview.ref.money.cnn.com
preview.train.money.cnn.com
preview2.ref.money.cnn.com
DNS probing and CNAME chain traversal were used to discover additional subdomains below.
Certificate Authority Diversity
(7 CAs observed across CT log history)
| Certificate Authority | Certs | First Issued | Last Issued | Status |
|---|---|---|---|---|
Amazon |
252 | 2025-02-10 | 2025-09-05 | Active |
GlobalSign nv-sa |
45 | 2025-02-20 | 2025-10-01 | Active |
Starfield Technologies, Inc. |
2 | 2025-10-08 | 2025-10-08 | Active |
Google Trust Services |
1 | 2026-01-24 | 2026-01-24 | Active |
DigiCert, Inc. |
1 | 2025-08-11 | 2025-08-11 | Active |
GoDaddy.com, Inc. |
1 | 2025-07-27 | 2025-07-27 | Active |
DigiCert Inc |
1 | 2025-03-12 | 2025-03-12 | Active |
| Subdomain | Source | Status | Provider / CNAME | Certificates | First Seen | Issuer(s) |
|---|---|---|---|---|---|---|
aaz.stellar.cnn.com
|
CT Log | Current | — | 4 | 2025-03-26T00:00:00 | Amazon |
academy.cnn.com
|
CT Log | Current | — | 1 | 2025-05-06T00:00:00 | Amazon |
account.cnn.com
|
DNS | Current | — | 10 | 2025-02-20 | Amazon, GlobalSign nv-sa |
admin.alertshub.cnn.com
|
CT Log | Current | — | 2 | 2025-04-15T00:00:00 | Amazon |
admin.dev.alertshub.cnn.com
|
CT Log | Current | — | 2 | 2025-08-13T00:00:00 | Amazon |
admin.ref.alertshub.cnn.com
|
CT Log | Current | — | 1 | 2025-03-12T00:00:00 | Amazon |
ads-analytics.stellar.cnn.com
|
CT Log | Current | — | 4 | 2025-03-26T00:00:00 | Amazon |
alerts.cnn.com
|
DNS | Current |
www.cnn.com
|
10 | 2025-02-20 | Amazon, GlobalSign nv-sa |
any-amer.dev.api.bolt.cnn.com
|
CT Log | Current | — | 27 | 2025-06-04T00:00:00 | Amazon |
any-amer.int.api.bolt.cnn.com
|
CT Log | Current | — | 18 | 2025-06-04T00:00:00 | Amazon |
any-amer.prd.api.bolt.cnn.com
|
CT Log | Current | — | 33 | 2025-06-09T00:00:00 | Amazon |
any-amer.stg.api.bolt.cnn.com
|
CT Log | Current | — | 31 | 2025-06-04T00:00:00 | Amazon |
any-amer.use.dev.api.bolt.cnn.com
|
CT Log | Current | — | 5 | 2025-06-04T00:00:00 | Amazon |
any-amer.use.int.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
any-amer.use.prd.api.bolt.cnn.com
|
CT Log | Current | — | 4 | 2025-06-09T00:00:00 | Amazon |
any-amer.use.stg.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-06-04T00:00:00 | Amazon |
any-amer.use1.dev.api.bolt.cnn.com
|
CT Log | Current | — | 27 | 2025-06-04T00:00:00 | Amazon |
any-amer.use1.int.api.bolt.cnn.com
|
CT Log | Current | — | 11 | 2025-06-04T00:00:00 | Amazon |
any-amer.use1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 15 | 2025-06-09T00:00:00 | Amazon |
any-amer.use1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 11 | 2025-06-04T00:00:00 | Amazon |
any-amer.use2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 10 | 2025-06-09T00:00:00 | Amazon |
any-amer.use2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 12 | 2025-06-04T00:00:00 | Amazon |
any-amer.usw2.int.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-06-04T00:00:00 | Amazon |
any-amer.usw2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 8 | 2025-06-09T00:00:00 | Amazon |
any-amer.usw2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 8 | 2025-06-04T00:00:00 | Amazon |
any-any.apne1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 10 | 2025-06-23T00:00:00 | Amazon |
any-any.aps1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 11 | 2025-06-23T00:00:00 | Amazon |
any-any.aps1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 9 | 2025-06-18T00:00:00 | Amazon |
any-any.apse1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 11 | 2025-06-23T00:00:00 | Amazon |
any-any.apse1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 9 | 2025-06-18T00:00:00 | Amazon |
any-any.dev.api.bolt.cnn.com
|
CT Log | Current | — | 27 | 2025-06-04T00:00:00 | Amazon |
any-any.euc1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-06-09T00:00:00 | Amazon |
any-any.euc1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-06-04T00:00:00 | Amazon |
any-any.eun1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 8 | 2025-06-09T00:00:00 | Amazon |
any-any.euw1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-06-09T00:00:00 | Amazon |
any-any.euw1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 6 | 2025-06-04T00:00:00 | Amazon |
any-any.int.api.bolt.cnn.com
|
CT Log | Current | — | 18 | 2025-06-04T00:00:00 | Amazon |
any-any.prd.api.bolt.cnn.com
|
CT Log | Current | — | 87 | 2025-06-23T00:00:00 | Amazon |
any-any.stg.api.bolt.cnn.com
|
CT Log | Current | — | 62 | 2025-06-18T00:00:00 | Amazon |
any-any.use.dev.api.bolt.cnn.com
|
CT Log | Current | — | 5 | 2025-06-04T00:00:00 | Amazon |
any-any.use.int.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
any-any.use.prd.api.bolt.cnn.com
|
CT Log | Current | — | 4 | 2025-06-09T00:00:00 | Amazon |
any-any.use.stg.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-06-04T00:00:00 | Amazon |
any-any.use1.dev.api.bolt.cnn.com
|
CT Log | Current | — | 27 | 2025-06-04T00:00:00 | Amazon |
any-any.use1.int.api.bolt.cnn.com
|
CT Log | Current | — | 11 | 2025-06-04T00:00:00 | Amazon |
any-any.use1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 15 | 2025-06-09T00:00:00 | Amazon |
any-any.use1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 11 | 2025-06-04T00:00:00 | Amazon |
any-any.use2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 10 | 2025-06-09T00:00:00 | Amazon |
any-any.use2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 12 | 2025-06-04T00:00:00 | Amazon |
any-any.usw2.int.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-06-04T00:00:00 | Amazon |
any-any.usw2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 8 | 2025-06-09T00:00:00 | Amazon |
any-any.usw2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 8 | 2025-06-04T00:00:00 | Amazon |
any-apac.apne1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 10 | 2025-06-23T00:00:00 | Amazon |
any-apac.aps1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 11 | 2025-06-23T00:00:00 | Amazon |
any-apac.aps1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 9 | 2025-06-18T00:00:00 | Amazon |
any-apac.apse1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 11 | 2025-06-23T00:00:00 | Amazon |
any-apac.apse1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 9 | 2025-06-18T00:00:00 | Amazon |
any-apac.dev.api.bolt.cnn.com
|
CT Log | Current | — | 21 | 2025-06-03T00:00:00 | Amazon |
any-apac.int.api.bolt.cnn.com
|
CT Log | Current | — | 17 | 2025-06-04T00:00:00 | Amazon |
any-apac.prd.api.bolt.cnn.com
|
CT Log | Current | — | 32 | 2025-06-23T00:00:00 | Amazon |
any-apac.stg.api.bolt.cnn.com
|
CT Log | Current | — | 18 | 2025-06-18T00:00:00 | Amazon |
any-apac.use.dev.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
any-apac.use1.dev.api.bolt.cnn.com
|
CT Log | Current | — | 20 | 2025-06-03T00:00:00 | Amazon |
any-apac.use1.int.api.bolt.cnn.com
|
CT Log | Current | — | 9 | 2025-06-04T00:00:00 | Amazon |
any-apac.usw2.int.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-06-04T00:00:00 | Amazon |
any-emea.dev.api.bolt.cnn.com
|
CT Log | Current | — | 21 | 2025-06-03T00:00:00 | Amazon |
any-emea.euc1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-06-09T00:00:00 | Amazon |
any-emea.euc1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-06-04T00:00:00 | Amazon |
any-emea.eun1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 8 | 2025-06-09T00:00:00 | Amazon |
any-emea.euw1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-06-09T00:00:00 | Amazon |
any-emea.euw1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 6 | 2025-06-04T00:00:00 | Amazon |
any-emea.int.api.bolt.cnn.com
|
CT Log | Current | — | 17 | 2025-06-04T00:00:00 | Amazon |
any-emea.prd.api.bolt.cnn.com
|
CT Log | Current | — | 22 | 2025-06-09T00:00:00 | Amazon |
any-emea.stg.api.bolt.cnn.com
|
CT Log | Current | — | 13 | 2025-06-04T00:00:00 | Amazon |
any-emea.use.dev.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
any-emea.use1.dev.api.bolt.cnn.com
|
CT Log | Current | — | 20 | 2025-06-03T00:00:00 | Amazon |
any-emea.use1.int.api.bolt.cnn.com
|
CT Log | Current | — | 9 | 2025-06-04T00:00:00 | Amazon |
any-emea.usw2.int.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-06-04T00:00:00 | Amazon |
any-latam.aps1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
any-latam.apse1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
any-latam.dev.api.bolt.cnn.com
|
CT Log | Current | — | 28 | 2025-06-04T00:00:00 | Amazon |
any-latam.euc1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
any-latam.eun1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
any-latam.euw1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
any-latam.int.api.bolt.cnn.com
|
CT Log | Current | — | 19 | 2025-06-04T00:00:00 | Amazon |
any-latam.prd.api.bolt.cnn.com
|
CT Log | Current | — | 35 | 2025-06-09T00:00:00 | Amazon |
any-latam.stg.api.bolt.cnn.com
|
CT Log | Current | — | 31 | 2025-06-04T00:00:00 | Amazon |
any-latam.use.dev.api.bolt.cnn.com
|
CT Log | Current | — | 5 | 2025-06-04T00:00:00 | Amazon |
any-latam.use.int.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
any-latam.use.prd.api.bolt.cnn.com
|
CT Log | Current | — | 6 | 2025-06-09T00:00:00 | Amazon |
any-latam.use.stg.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-06-04T00:00:00 | Amazon |
any-latam.use1.dev.api.bolt.cnn.com
|
CT Log | Current | — | 27 | 2025-06-04T00:00:00 | Amazon |
any-latam.use1.int.api.bolt.cnn.com
|
CT Log | Current | — | 11 | 2025-06-04T00:00:00 | Amazon |
any-latam.use1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 17 | 2025-06-09T00:00:00 | Amazon |
any-latam.use1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 11 | 2025-06-04T00:00:00 | Amazon |
any-latam.use2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 12 | 2025-06-09T00:00:00 | Amazon |
any-latam.use2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 12 | 2025-06-04T00:00:00 | Amazon |
any-latam.usw2.int.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-06-04T00:00:00 | Amazon |
any-latam.usw2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 10 | 2025-06-09T00:00:00 | Amazon |
any-latam.usw2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 8 | 2025-06-04T00:00:00 | Amazon |
api.cnn.com
|
CT Log | Current | — | 8 | 2025-08-13T00:00:00 | Amazon, GlobalSign nv-sa |
api.electiontracker.cnn.com
|
CT Log | Current | — | 2 | 2025-04-15T19:26:45 | GlobalSign nv-sa |
api.etp.cnn.com
|
CT Log | Current | — | 2 | 2025-04-15T19:26:45 | GlobalSign nv-sa |
api.platform.cnn.com
|
CT Log | Current | — | 6 | 2025-02-21T19:56:02 | GlobalSign nv-sa |
apne1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 12 | 2025-06-23T00:00:00 | Amazon |
aps1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 13 | 2025-06-23T00:00:00 | Amazon |
aps1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 9 | 2025-06-18T00:00:00 | Amazon |
apse1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 13 | 2025-06-23T00:00:00 | Amazon |
apse1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 9 | 2025-06-18T00:00:00 | Amazon |
arabic.cnn.com
|
CT Log | Current | — | 6 | 2025-04-29T14:42:17 | GlobalSign nv-sa |
archives.cnn.com
|
DNS | Current | — | 10 | 2025-02-20 | Amazon, GlobalSign nv-sa |
asia.cnn.com
|
DNS | Current |
asia.cnn.com.edgesuite.net
|
10 | 2025-02-20 | Amazon, GlobalSign nv-sa |
audience.qa.cnn.com
|
CT Log | Current | — | 2 | 2025-02-16T00:00:00 | Amazon |
av.stellar.cnn.com
|
CT Log | Current | — | 4 | 2025-03-26T00:00:00 | Amazon |
beam-amer.apne1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
beam-amer.aps1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
beam-amer.apse1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
beam-amer.dev.api.bolt.cnn.com
|
CT Log | Current | — | 12 | 2025-05-01T00:00:00 | Amazon |
beam-amer.euc1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
beam-amer.eun1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
beam-amer.euw1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
beam-amer.euw1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
beam-amer.int.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-04-29T00:00:00 | Amazon |
beam-amer.prd.api.bolt.cnn.com
|
CT Log | Current | — | 18 | 2025-05-08T00:00:00 | Amazon |
beam-amer.stg.api.bolt.cnn.com
|
CT Log | Current | — | 19 | 2025-05-02T00:00:00 | Amazon |
beam-amer.use.dev.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-01T00:00:00 | Amazon |
beam-amer.use.int.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
beam-amer.use.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
beam-amer.use.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
beam-amer.use1.dev.api.bolt.cnn.com
|
CT Log | Current | — | 12 | 2025-05-01T00:00:00 | Amazon |
beam-amer.use1.int.api.bolt.cnn.com
|
CT Log | Current | — | 4 | 2025-04-29T00:00:00 | Amazon |
beam-amer.use1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 9 | 2025-05-08T00:00:00 | Amazon |
beam-amer.use1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 6 | 2025-05-02T00:00:00 | Amazon |
beam-amer.use2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 6 | 2025-05-08T00:00:00 | Amazon |
beam-amer.use2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 8 | 2025-05-02T00:00:00 | Amazon |
beam-amer.usw2.int.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-04-23T00:00:00 | Amazon |
beam-amer.usw2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-05-08T00:00:00 | Amazon |
beam-amer.usw2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-05-02T00:00:00 | Amazon |
beam-any.apne1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 8 | 2025-05-08T00:00:00 | Amazon |
beam-any.aps1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-05-08T00:00:00 | Amazon |
beam-any.aps1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 5 | 2025-05-02T00:00:00 | Amazon |
beam-any.apse1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 8 | 2025-05-08T00:00:00 | Amazon |
beam-any.apse1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 4 | 2025-05-02T00:00:00 | Amazon |
beam-any.dev.api.bolt.cnn.com
|
CT Log | Current | — | 12 | 2025-05-01T00:00:00 | Amazon |
beam-any.euc1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 4 | 2025-05-08T00:00:00 | Amazon |
beam-any.euc1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 5 | 2025-05-02T00:00:00 | Amazon |
beam-any.eun1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 6 | 2025-05-08T00:00:00 | Amazon |
beam-any.euw1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 5 | 2025-05-08T00:00:00 | Amazon |
beam-any.euw1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-02T00:00:00 | Amazon |
beam-any.int.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-04-29T00:00:00 | Amazon |
beam-any.prd.api.bolt.cnn.com
|
CT Log | Current | — | 44 | 2025-05-08T00:00:00 | Amazon |
beam-any.stg.api.bolt.cnn.com
|
CT Log | Current | — | 31 | 2025-05-02T00:00:00 | Amazon |
beam-any.use.dev.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-01T00:00:00 | Amazon |
beam-any.use.int.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
beam-any.use.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
beam-any.use.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
beam-any.use1.dev.api.bolt.cnn.com
|
CT Log | Current | — | 12 | 2025-05-01T00:00:00 | Amazon |
beam-any.use1.int.api.bolt.cnn.com
|
CT Log | Current | — | 4 | 2025-04-29T00:00:00 | Amazon |
beam-any.use1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 9 | 2025-05-08T00:00:00 | Amazon |
beam-any.use1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 6 | 2025-05-02T00:00:00 | Amazon |
beam-any.use2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 6 | 2025-05-08T00:00:00 | Amazon |
beam-any.use2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 8 | 2025-05-02T00:00:00 | Amazon |
beam-any.usw2.int.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-04-23T00:00:00 | Amazon |
beam-any.usw2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-05-08T00:00:00 | Amazon |
beam-any.usw2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-05-02T00:00:00 | Amazon |
beam-apac.apne1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 8 | 2025-05-08T00:00:00 | Amazon |
beam-apac.aps1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-05-08T00:00:00 | Amazon |
beam-apac.aps1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 5 | 2025-05-02T00:00:00 | Amazon |
beam-apac.apse1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 8 | 2025-05-08T00:00:00 | Amazon |
beam-apac.apse1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 4 | 2025-05-02T00:00:00 | Amazon |
beam-apac.dev.api.bolt.cnn.com
|
CT Log | Current | — | 8 | 2025-04-29T00:00:00 | Amazon |
beam-apac.euc1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
beam-apac.euc1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
beam-apac.eun1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
beam-apac.euw1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
beam-apac.euw1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
beam-apac.int.api.bolt.cnn.com
|
CT Log | Current | — | 6 | 2025-04-23T00:00:00 | Amazon |
beam-apac.prd.api.bolt.cnn.com
|
CT Log | Current | — | 19 | 2025-05-08T00:00:00 | Amazon |
beam-apac.stg.api.bolt.cnn.com
|
CT Log | Current | — | 8 | 2025-05-02T00:00:00 | Amazon |
beam-apac.use.dev.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
beam-apac.use.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
beam-apac.use.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
beam-apac.use1.dev.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-04-29T00:00:00 | Amazon |
beam-apac.use1.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-23T00:00:00 | Amazon |
beam-apac.use1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
beam-apac.use1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
beam-apac.use2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
beam-apac.use2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
beam-apac.usw2.int.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-04-23T00:00:00 | Amazon |
beam-apac.usw2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
beam-apac.usw2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
beam-emea.apne1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
beam-emea.aps1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
beam-emea.aps1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
beam-emea.apse1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
beam-emea.apse1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
beam-emea.dev.api.bolt.cnn.com
|
CT Log | Current | — | 8 | 2025-04-29T00:00:00 | Amazon |
beam-emea.euc1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 4 | 2025-05-08T00:00:00 | Amazon |
beam-emea.euc1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 5 | 2025-05-02T00:00:00 | Amazon |
beam-emea.eun1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 6 | 2025-05-08T00:00:00 | Amazon |
beam-emea.euw1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 5 | 2025-05-08T00:00:00 | Amazon |
beam-emea.euw1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-02T00:00:00 | Amazon |
beam-emea.int.api.bolt.cnn.com
|
CT Log | Current | — | 6 | 2025-04-23T00:00:00 | Amazon |
beam-emea.prd.api.bolt.cnn.com
|
CT Log | Current | — | 11 | 2025-05-08T00:00:00 | Amazon |
beam-emea.stg.api.bolt.cnn.com
|
CT Log | Current | — | 6 | 2025-05-02T00:00:00 | Amazon |
beam-emea.use.dev.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
beam-emea.use.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
beam-emea.use.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
beam-emea.use1.dev.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-04-29T00:00:00 | Amazon |
beam-emea.use1.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-23T00:00:00 | Amazon |
beam-emea.use1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
beam-emea.use1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
beam-emea.use2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-08T00:00:00 | Amazon |
beam-emea.use2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
beam-emea.usw2.int.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-04-23T00:00:00 | Amazon |
beam-emea.usw2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-08T00:00:00 | Amazon |
beam-emea.usw2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
beam-latam.apne1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-08T00:00:00 | Amazon |
beam-latam.aps1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-08T00:00:00 | Amazon |
beam-latam.aps1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
beam-latam.apse1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-08T00:00:00 | Amazon |
beam-latam.apse1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
beam-latam.dev.api.bolt.cnn.com
|
CT Log | Current | — | 13 | 2025-05-01T00:00:00 | Amazon |
beam-latam.euc1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-08T00:00:00 | Amazon |
beam-latam.euc1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
beam-latam.eun1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-08T00:00:00 | Amazon |
beam-latam.euw1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-08T00:00:00 | Amazon |
beam-latam.euw1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
beam-latam.int.api.bolt.cnn.com
|
CT Log | Current | — | 8 | 2025-04-29T00:00:00 | Amazon |
beam-latam.prd.api.bolt.cnn.com
|
CT Log | Current | — | 19 | 2025-05-08T00:00:00 | Amazon |
beam-latam.stg.api.bolt.cnn.com
|
CT Log | Current | — | 19 | 2025-05-02T00:00:00 | Amazon |
beam-latam.use.dev.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-01T00:00:00 | Amazon |
beam-latam.use.int.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
beam-latam.use.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-08T00:00:00 | Amazon |
beam-latam.use.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
beam-latam.use1.dev.api.bolt.cnn.com
|
CT Log | Current | — | 12 | 2025-05-01T00:00:00 | Amazon |
beam-latam.use1.int.api.bolt.cnn.com
|
CT Log | Current | — | 4 | 2025-04-29T00:00:00 | Amazon |
beam-latam.use1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 10 | 2025-05-08T00:00:00 | Amazon |
beam-latam.use1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 6 | 2025-05-02T00:00:00 | Amazon |
beam-latam.use2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-05-08T00:00:00 | Amazon |
beam-latam.use2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 8 | 2025-05-02T00:00:00 | Amazon |
beam-latam.usw2.int.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-04-23T00:00:00 | Amazon |
beam-latam.usw2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 8 | 2025-05-08T00:00:00 | Amazon |
beam-latam.usw2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-05-02T00:00:00 | Amazon |
blogs.cnn.com
|
CT Log | Current | — | 6 | 2025-04-29T14:42:40 | GlobalSign nv-sa |
br-amer.apne1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-08T00:00:00 | Amazon |
br-amer.aps1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-08T00:00:00 | Amazon |
br-amer.aps1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
br-amer.apse1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-08T00:00:00 | Amazon |
br-amer.apse1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
br-amer.dev.api.bolt.cnn.com
|
CT Log | Current | — | 12 | 2025-05-01T00:00:00 | Amazon |
br-amer.euc1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-08T00:00:00 | Amazon |
br-amer.euc1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
br-amer.eun1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-08T00:00:00 | Amazon |
br-amer.euw1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-08T00:00:00 | Amazon |
br-amer.euw1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
br-amer.int.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-04-29T00:00:00 | Amazon |
br-amer.prd.api.bolt.cnn.com
|
CT Log | Current | — | 19 | 2025-05-08T00:00:00 | Amazon |
br-amer.stg.api.bolt.cnn.com
|
CT Log | Current | — | 19 | 2025-05-02T00:00:00 | Amazon |
br-amer.use.dev.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-01T00:00:00 | Amazon |
br-amer.use.int.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
br-amer.use.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-08T00:00:00 | Amazon |
br-amer.use.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
br-amer.use1.dev.api.bolt.cnn.com
|
CT Log | Current | — | 12 | 2025-05-01T00:00:00 | Amazon |
br-amer.use1.int.api.bolt.cnn.com
|
CT Log | Current | — | 4 | 2025-04-29T00:00:00 | Amazon |
br-amer.use1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 10 | 2025-05-08T00:00:00 | Amazon |
br-amer.use1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 6 | 2025-05-02T00:00:00 | Amazon |
br-amer.use2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-05-08T00:00:00 | Amazon |
br-amer.use2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 8 | 2025-05-02T00:00:00 | Amazon |
br-amer.usw2.int.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-04-23T00:00:00 | Amazon |
br-amer.usw2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 8 | 2025-05-08T00:00:00 | Amazon |
br-amer.usw2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 8 | 2025-05-02T00:00:00 | Amazon |
br-any.apne1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-08T00:00:00 | Amazon |
br-any.aps1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-08T00:00:00 | Amazon |
br-any.aps1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
br-any.apse1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-08T00:00:00 | Amazon |
br-any.apse1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
br-any.dev.api.bolt.cnn.com
|
CT Log | Current | — | 12 | 2025-05-01T00:00:00 | Amazon |
br-any.euc1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 5 | 2025-05-08T00:00:00 | Amazon |
br-any.euc1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 6 | 2025-05-02T00:00:00 | Amazon |
br-any.eun1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-05-08T00:00:00 | Amazon |
br-any.euw1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 6 | 2025-05-08T00:00:00 | Amazon |
br-any.euw1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-02T00:00:00 | Amazon |
br-any.int.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-04-29T00:00:00 | Amazon |
br-any.prd.api.bolt.cnn.com
|
CT Log | Current | — | 28 | 2025-05-08T00:00:00 | Amazon |
br-any.stg.api.bolt.cnn.com
|
CT Log | Current | — | 25 | 2025-05-02T00:00:00 | Amazon |
br-any.use.dev.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-01T00:00:00 | Amazon |
br-any.use.int.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
br-any.use.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-08T00:00:00 | Amazon |
br-any.use.stg.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
br-any.use1.dev.api.bolt.cnn.com
|
CT Log | Current | — | 12 | 2025-05-01T00:00:00 | Amazon |
br-any.use1.int.api.bolt.cnn.com
|
CT Log | Current | — | 4 | 2025-04-29T00:00:00 | Amazon |
br-any.use1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 10 | 2025-05-08T00:00:00 | Amazon |
br-any.use1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-05-02T00:00:00 | Amazon |
br-any.use2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-05-08T00:00:00 | Amazon |
br-any.use2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 9 | 2025-05-02T00:00:00 | Amazon |
br-any.usw2.int.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-04-23T00:00:00 | Amazon |
br-any.usw2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 8 | 2025-05-08T00:00:00 | Amazon |
br-any.usw2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 8 | 2025-05-02T00:00:00 | Amazon |
br-apac.apne1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-08T00:00:00 | Amazon |
br-apac.aps1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-08T00:00:00 | Amazon |
br-apac.aps1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
br-apac.apse1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-08T00:00:00 | Amazon |
br-apac.apse1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
br-apac.dev.api.bolt.cnn.com
|
CT Log | Current | — | 8 | 2025-04-29T00:00:00 | Amazon |
br-apac.euc1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-08T00:00:00 | Amazon |
br-apac.euc1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
br-apac.eun1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-08T00:00:00 | Amazon |
br-apac.euw1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-08T00:00:00 | Amazon |
br-apac.euw1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
br-apac.int.api.bolt.cnn.com
|
CT Log | Current | — | 6 | 2025-04-23T00:00:00 | Amazon |
br-apac.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-08T00:00:00 | Amazon |
br-apac.stg.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
br-apac.use.dev.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
br-apac.use.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-08T00:00:00 | Amazon |
br-apac.use.stg.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
br-apac.use1.dev.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-04-29T00:00:00 | Amazon |
br-apac.use1.int.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-04-23T00:00:00 | Amazon |
br-apac.use1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-08T00:00:00 | Amazon |
br-apac.use1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
br-apac.use2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-08T00:00:00 | Amazon |
br-apac.use2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
br-apac.usw2.int.api.bolt.cnn.com
|
CT Log | Current | — | 4 | 2025-04-23T00:00:00 | Amazon |
br-apac.usw2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-08T00:00:00 | Amazon |
br-apac.usw2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
br-emea.apne1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-08T00:00:00 | Amazon |
br-emea.aps1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-08T00:00:00 | Amazon |
br-emea.aps1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
br-emea.apse1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-08T00:00:00 | Amazon |
br-emea.apse1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
br-emea.dev.api.bolt.cnn.com
|
CT Log | Current | — | 8 | 2025-04-29T00:00:00 | Amazon |
br-emea.euc1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 5 | 2025-05-08T00:00:00 | Amazon |
br-emea.euc1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 6 | 2025-05-02T00:00:00 | Amazon |
br-emea.eun1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 6 | 2025-05-08T00:00:00 | Amazon |
br-emea.euw1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 5 | 2025-05-08T00:00:00 | Amazon |
br-emea.euw1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-02T00:00:00 | Amazon |
br-emea.int.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-04-23T00:00:00 | Amazon |
br-emea.prd.api.bolt.cnn.com
|
CT Log | Current | — | 11 | 2025-05-08T00:00:00 | Amazon |
br-emea.stg.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-05-02T00:00:00 | Amazon |
br-emea.use.dev.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
br-emea.use.int.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
br-emea.use.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
br-emea.use.stg.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
br-emea.use1.dev.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-04-29T00:00:00 | Amazon |
br-emea.use1.int.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-04-23T00:00:00 | Amazon |
br-emea.use1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
br-emea.use1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
br-emea.use2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
br-emea.use2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
br-emea.usw2.int.api.bolt.cnn.com
|
CT Log | Current | — | 4 | 2025-04-23T00:00:00 | Amazon |
br-emea.usw2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
br-emea.usw2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
br-latam.apne1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
br-latam.aps1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
br-latam.aps1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
br-latam.apse1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
br-latam.apse1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
br-latam.dev.api.bolt.cnn.com
|
CT Log | Current | — | 13 | 2025-05-01T00:00:00 | Amazon |
br-latam.euc1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
br-latam.euc1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
br-latam.eun1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
br-latam.euw1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
br-latam.euw1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
br-latam.int.api.bolt.cnn.com
|
CT Log | Current | — | 9 | 2025-04-29T00:00:00 | Amazon |
br-latam.prd.api.bolt.cnn.com
|
CT Log | Current | — | 18 | 2025-05-08T00:00:00 | Amazon |
br-latam.stg.api.bolt.cnn.com
|
CT Log | Current | — | 20 | 2025-05-02T00:00:00 | Amazon |
br-latam.use.dev.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-01T00:00:00 | Amazon |
br-latam.use.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
br-latam.use.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
br-latam.use.stg.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
br-latam.use1.dev.api.bolt.cnn.com
|
CT Log | Current | — | 12 | 2025-05-01T00:00:00 | Amazon |
br-latam.use1.int.api.bolt.cnn.com
|
CT Log | Current | — | 5 | 2025-04-29T00:00:00 | Amazon |
br-latam.use1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 9 | 2025-05-08T00:00:00 | Amazon |
br-latam.use1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-05-02T00:00:00 | Amazon |
br-latam.use2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 6 | 2025-05-08T00:00:00 | Amazon |
br-latam.use2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 9 | 2025-05-02T00:00:00 | Amazon |
br-latam.usw2.int.api.bolt.cnn.com
|
CT Log | Current | — | 4 | 2025-04-23T00:00:00 | Amazon |
br-latam.usw2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-05-08T00:00:00 | Amazon |
br-latam.usw2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 8 | 2025-05-02T00:00:00 | Amazon |
ca.commerce.cnn.com
|
CT Log | Current | — | 1 | 2025-03-13T05:26:02 | GlobalSign nv-sa |
ca.emailalerts.cnn.com
|
CT Log | Current | — | 1 | 2025-03-13T05:26:02 | GlobalSign nv-sa |
ca.mail.cnn.com
|
CT Log | Current | — | 1 | 2025-03-13T05:26:02 | GlobalSign nv-sa |
ca.newsletters.cnn.com
|
CT Log | Current |
cnn.ca.maas.zetaglobal.net
|
1 | 2025-03-13T05:26:02 | GlobalSign nv-sa |
ca.specials.cnn.com
|
CT Log | Current | — | 1 | 2025-03-13T05:26:02 | GlobalSign nv-sa |
ca.transactional.cnn.com
|
CT Log | Current | — | 1 | 2025-03-13T05:26:02 | GlobalSign nv-sa |
cdn.cnn.com
|
CT Log | Current | — | 5 | 2025-07-17T00:00:00 | Amazon, GlobalSign nv-sa |
cdp-dev.cnn.com
|
CT Log | Current | — | 4 | 2025-06-29T00:00:00 | Amazon, GlobalSign nv-sa |
cdp.cnn.com
|
CT Log | Current | — | 6 | 2025-09-05T00:00:00 | Amazon, GlobalSign nv-sa |
cerebro.api.cnn.com
|
CT Log | Current | — | 3 | 2025-07-09T17:31:02 | GlobalSign nv-sa |
cert.stellar.cnn.com
|
CT Log | Current | — | 4 | 2025-03-26T00:00:00 | Amazon |
cgtcj.cnn.com
|
CT Log | Current | — | 6 | 2025-08-21T00:00:00 | Amazon |
client.appletv.cnn.com
|
CT Log | Current | — | 4 | 2025-04-15T19:26:45 | GlobalSign nv-sa |
clients.cnn.com
|
DNS | Current | — | 10 | 2025-02-20 | Amazon, GlobalSign nv-sa |
cms.cnn.com
|
CT Log | Current | — | 2 | 2025-05-20T00:00:00 | Amazon |
cnn-amer.aps1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
cnn-amer.apse1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
cnn-amer.dev.api.bolt.cnn.com
|
CT Log | Current | — | 18 | 2025-06-04T00:00:00 | Amazon |
cnn-amer.euc1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
cnn-amer.euw1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
cnn-amer.int.api.bolt.cnn.com
|
CT Log | Current | — | 12 | 2025-06-04T00:00:00 | Amazon |
cnn-amer.prd.api.bolt.cnn.com
|
CT Log | Current | — | 17 | 2025-06-09T00:00:00 | Amazon |
cnn-amer.stg.api.bolt.cnn.com
|
CT Log | Current | — | 14 | 2025-06-04T00:00:00 | Amazon |
cnn-amer.use.dev.api.bolt.cnn.com
|
CT Log | Current | — | 5 | 2025-06-04T00:00:00 | Amazon |
cnn-amer.use.int.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
cnn-amer.use.prd.api.bolt.cnn.com
|
CT Log | Current | — | 4 | 2025-06-09T00:00:00 | Amazon |
cnn-amer.use.stg.api.bolt.cnn.com
|
CT Log | Current | — | 4 | 2025-06-04T00:00:00 | Amazon |
cnn-amer.use1.dev.api.bolt.cnn.com
|
CT Log | Current | — | 18 | 2025-06-04T00:00:00 | Amazon |
cnn-amer.use1.int.api.bolt.cnn.com
|
CT Log | Current | — | 8 | 2025-06-04T00:00:00 | Amazon |
cnn-amer.use1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 8 | 2025-06-09T00:00:00 | Amazon |
cnn-amer.use1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-06-04T00:00:00 | Amazon |
cnn-amer.use2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 6 | 2025-06-09T00:00:00 | Amazon |
cnn-amer.use2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 6 | 2025-06-04T00:00:00 | Amazon |
cnn-amer.usw2.int.api.bolt.cnn.com
|
CT Log | Current | — | 4 | 2025-06-04T00:00:00 | Amazon |
cnn-amer.usw2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-06-09T00:00:00 | Amazon |
cnn-amer.usw2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-06-04T00:00:00 | Amazon |
cnn-any.apne1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 4 | 2025-06-23T00:00:00 | Amazon |
cnn-any.aps1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 6 | 2025-06-23T00:00:00 | Amazon |
cnn-any.aps1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 6 | 2025-06-18T00:00:00 | Amazon |
cnn-any.apse1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 5 | 2025-06-23T00:00:00 | Amazon |
cnn-any.apse1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-06-18T00:00:00 | Amazon |
cnn-any.dev.api.bolt.cnn.com
|
CT Log | Current | — | 18 | 2025-06-04T00:00:00 | Amazon |
cnn-any.euc1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 5 | 2025-06-09T00:00:00 | Amazon |
cnn-any.euc1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 4 | 2025-06-04T00:00:00 | Amazon |
cnn-any.eun1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 4 | 2025-06-09T00:00:00 | Amazon |
cnn-any.euw1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 4 | 2025-06-09T00:00:00 | Amazon |
cnn-any.euw1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 6 | 2025-06-04T00:00:00 | Amazon |
cnn-any.int.api.bolt.cnn.com
|
CT Log | Current | — | 12 | 2025-06-04T00:00:00 | Amazon |
cnn-any.prd.api.bolt.cnn.com
|
CT Log | Current | — | 45 | 2025-06-23T00:00:00 | Amazon |
cnn-any.stg.api.bolt.cnn.com
|
CT Log | Current | — | 33 | 2025-06-18T00:00:00 | Amazon |
cnn-any.use.dev.api.bolt.cnn.com
|
CT Log | Current | — | 5 | 2025-06-04T00:00:00 | Amazon |
cnn-any.use.int.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
cnn-any.use.prd.api.bolt.cnn.com
|
CT Log | Current | — | 4 | 2025-06-09T00:00:00 | Amazon |
cnn-any.use.stg.api.bolt.cnn.com
|
CT Log | Current | — | 4 | 2025-06-04T00:00:00 | Amazon |
cnn-any.use1.dev.api.bolt.cnn.com
|
CT Log | Current | — | 17 | 2025-06-04T00:00:00 | Amazon |
cnn-any.use1.int.api.bolt.cnn.com
|
CT Log | Current | — | 8 | 2025-06-04T00:00:00 | Amazon |
cnn-any.use1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 8 | 2025-06-09T00:00:00 | Amazon |
cnn-any.use1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-06-04T00:00:00 | Amazon |
cnn-any.use2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 6 | 2025-06-09T00:00:00 | Amazon |
cnn-any.use2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 6 | 2025-06-04T00:00:00 | Amazon |
cnn-any.usw2.int.api.bolt.cnn.com
|
CT Log | Current | — | 4 | 2025-06-04T00:00:00 | Amazon |
cnn-any.usw2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-06-09T00:00:00 | Amazon |
cnn-any.usw2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-06-04T00:00:00 | Amazon |
cnn-apac.apne1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 4 | 2025-06-23T00:00:00 | Amazon |
cnn-apac.aps1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 6 | 2025-06-23T00:00:00 | Amazon |
cnn-apac.aps1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 6 | 2025-06-18T00:00:00 | Amazon |
cnn-apac.apse1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 5 | 2025-06-23T00:00:00 | Amazon |
cnn-apac.apse1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-06-18T00:00:00 | Amazon |
cnn-apac.dev.api.bolt.cnn.com
|
CT Log | Current | — | 13 | 2025-06-03T00:00:00 | Amazon |
cnn-apac.euc1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
cnn-apac.euw1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
cnn-apac.int.api.bolt.cnn.com
|
CT Log | Current | — | 11 | 2025-06-04T00:00:00 | Amazon |
cnn-apac.prd.api.bolt.cnn.com
|
CT Log | Current | — | 15 | 2025-06-23T00:00:00 | Amazon |
cnn-apac.stg.api.bolt.cnn.com
|
CT Log | Current | — | 12 | 2025-06-18T00:00:00 | Amazon |
cnn-apac.use.dev.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-01T00:00:00 | Amazon |
cnn-apac.use.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
cnn-apac.use1.dev.api.bolt.cnn.com
|
CT Log | Current | — | 13 | 2025-06-03T00:00:00 | Amazon |
cnn-apac.use1.int.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-06-04T00:00:00 | Amazon |
cnn-apac.use1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
cnn-apac.use2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
cnn-apac.usw2.int.api.bolt.cnn.com
|
CT Log | Current | — | 4 | 2025-06-04T00:00:00 | Amazon |
cnn-apac.usw2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
cnn-apac.usw2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
cnn-emea.apne1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
cnn-emea.aps1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
cnn-emea.aps1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
cnn-emea.apse1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
cnn-emea.apse1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
cnn-emea.dev.api.bolt.cnn.com
|
CT Log | Current | — | 13 | 2025-06-03T00:00:00 | Amazon |
cnn-emea.euc1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 6 | 2025-06-09T00:00:00 | Amazon |
cnn-emea.euc1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 4 | 2025-06-04T00:00:00 | Amazon |
cnn-emea.eun1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 5 | 2025-06-09T00:00:00 | Amazon |
cnn-emea.euw1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 5 | 2025-06-09T00:00:00 | Amazon |
cnn-emea.euw1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 6 | 2025-06-04T00:00:00 | Amazon |
cnn-emea.int.api.bolt.cnn.com
|
CT Log | Current | — | 11 | 2025-06-04T00:00:00 | Amazon |
cnn-emea.prd.api.bolt.cnn.com
|
CT Log | Current | — | 14 | 2025-06-09T00:00:00 | Amazon |
cnn-emea.stg.api.bolt.cnn.com
|
CT Log | Current | — | 9 | 2025-06-04T00:00:00 | Amazon |
cnn-emea.use.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
cnn-emea.use.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
cnn-emea.use1.dev.api.bolt.cnn.com
|
CT Log | Current | — | 13 | 2025-06-03T00:00:00 | Amazon |
cnn-emea.use1.int.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-06-04T00:00:00 | Amazon |
cnn-emea.use1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
cnn-emea.use1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
cnn-emea.use2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
cnn-emea.use2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
cnn-emea.usw2.int.api.bolt.cnn.com
|
CT Log | Current | — | 4 | 2025-06-04T00:00:00 | Amazon |
cnn-emea.usw2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
cnn-emea.usw2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
cnn-latam.apne1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
cnn-latam.aps1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
cnn-latam.aps1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
cnn-latam.apse1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
cnn-latam.apse1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
cnn-latam.dev.api.bolt.cnn.com
|
CT Log | Current | — | 17 | 2025-06-04T00:00:00 | Amazon |
cnn-latam.euc1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
cnn-latam.euc1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
cnn-latam.eun1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
cnn-latam.euw1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
cnn-latam.euw1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
cnn-latam.int.api.bolt.cnn.com
|
CT Log | Current | — | 12 | 2025-06-04T00:00:00 | Amazon |
cnn-latam.prd.api.bolt.cnn.com
|
CT Log | Current | — | 18 | 2025-06-09T00:00:00 | Amazon |
cnn-latam.stg.api.bolt.cnn.com
|
CT Log | Current | — | 14 | 2025-06-04T00:00:00 | Amazon |
cnn-latam.use.dev.api.bolt.cnn.com
|
CT Log | Current | — | 4 | 2025-06-04T00:00:00 | Amazon |
cnn-latam.use.int.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
cnn-latam.use.prd.api.bolt.cnn.com
|
CT Log | Current | — | 5 | 2025-06-09T00:00:00 | Amazon |
cnn-latam.use.stg.api.bolt.cnn.com
|
CT Log | Current | — | 4 | 2025-06-04T00:00:00 | Amazon |
cnn-latam.use1.dev.api.bolt.cnn.com
|
CT Log | Current | — | 17 | 2025-06-04T00:00:00 | Amazon |
cnn-latam.use1.int.api.bolt.cnn.com
|
CT Log | Current | — | 8 | 2025-06-04T00:00:00 | Amazon |
cnn-latam.use1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 9 | 2025-06-09T00:00:00 | Amazon |
cnn-latam.use1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-06-04T00:00:00 | Amazon |
cnn-latam.use2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-06-09T00:00:00 | Amazon |
cnn-latam.use2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 6 | 2025-06-04T00:00:00 | Amazon |
cnn-latam.usw2.int.api.bolt.cnn.com
|
CT Log | Current | — | 4 | 2025-06-04T00:00:00 | Amazon |
cnn-latam.usw2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 4 | 2025-06-09T00:00:00 | Amazon |
cnn-latam.usw2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-06-04T00:00:00 | Amazon |
cnne-admin.cnn.com
|
CT Log | Current | — | 1 | 2025-03-11T08:41:02 | GlobalSign nv-sa |
cnne-test.cnn.com
|
CT Log | Current | — | 1 | 2025-10-01T14:24:30 | GlobalSign nv-sa |
collection.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T14:11:22 | GlobalSign nv-sa |
commercial.cnn.com
|
CT Log | Current | — | 1 | 2025-06-25T12:41:01 | GlobalSign nv-sa |
commercial.stg.cnn.com
|
CT Log | Current | — | 2 | 2025-06-25T12:41:01 | GlobalSign nv-sa |
community.cnn.com
|
DNS | Current |
reflector.cnn.com
|
10 | 2025-02-20 | Amazon, GlobalSign nv-sa |
config.cnn.com
|
CT Log | Current | — | 3 | 2025-04-29T14:43:47 | GlobalSign nv-sa |
content.cnn.com
|
DNS | Current |
cnn-content-api-prod.56m.vgtf.net
|
10 | 2025-02-20 | Amazon, GlobalSign nv-sa |
coupons.cnn.com
|
CT Log | Current | — | 1 | 2025-02-10T00:00:00 | Amazon |
data.cnn.com
|
DNS | Current |
cnn-tls.map.fastly.net
|
10 | 2025-02-20 | Amazon, GlobalSign nv-sa |
default.private-vpce.apne1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-09T00:00:00 | Amazon |
default.private-vpce.aps1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-09T00:00:00 | Amazon |
default.private-vpce.aps1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
default.private-vpce.apse1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-09T00:00:00 | Amazon |
default.private-vpce.apse1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
default.private-vpce.euc1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-09T00:00:00 | Amazon |
default.private-vpce.euc1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
default.private-vpce.eun1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-09T00:00:00 | Amazon |
default.private-vpce.euw1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-09T00:00:00 | Amazon |
default.private-vpce.euw1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
default.private-vpce.use1.dev.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
default.private-vpce.use1.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
default.private-vpce.use1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-09T00:00:00 | Amazon |
default.private-vpce.use1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
default.private-vpce.use2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-09T00:00:00 | Amazon |
default.private-vpce.use2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
default.private-vpce.usw2.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
default.private-vpce.usw2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-09T00:00:00 | Amazon |
default.private-vpce.usw2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
dev.alertshub.cnn.com
|
CT Log | Current | — | 4 | 2025-08-13T00:00:00 | Amazon |
dev.api.bolt.cnn.com
|
CT Log | Current | — | 58 | 2025-06-04T00:00:00 | Amazon |
dev.cnne-test.cnn.com
|
CT Log | Current | — | 1 | 2026-01-24T12:31:42 | Google Trust Services |
developer.cnn.com
|
DNS | Current |
developer.cnn.com.s3-website-us-east-1.amazonaws.com
|
10 | 2025-02-20 | Amazon, GlobalSign nv-sa |
download.cnn.com
|
DNS | Current | — | 10 | 2025-02-20 | Amazon, GlobalSign nv-sa |
dplus-amer.apne1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-08T00:00:00 | Amazon |
dplus-amer.aps1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-08T00:00:00 | Amazon |
dplus-amer.aps1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
dplus-amer.apse1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-08T00:00:00 | Amazon |
dplus-amer.apse1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
dplus-amer.dev.api.bolt.cnn.com
|
CT Log | Current | — | 12 | 2025-05-01T00:00:00 | Amazon |
dplus-amer.euc1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-08T00:00:00 | Amazon |
dplus-amer.euc1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
dplus-amer.eun1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-08T00:00:00 | Amazon |
dplus-amer.euw1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-08T00:00:00 | Amazon |
dplus-amer.euw1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
dplus-amer.int.api.bolt.cnn.com
|
CT Log | Current | — | 9 | 2025-04-29T00:00:00 | Amazon |
dplus-amer.prd.api.bolt.cnn.com
|
CT Log | Current | — | 19 | 2025-05-08T00:00:00 | Amazon |
dplus-amer.stg.api.bolt.cnn.com
|
CT Log | Current | — | 20 | 2025-05-02T00:00:00 | Amazon |
dplus-amer.use.dev.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-01T00:00:00 | Amazon |
dplus-amer.use.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
dplus-amer.use.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-08T00:00:00 | Amazon |
dplus-amer.use.stg.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
dplus-amer.use1.dev.api.bolt.cnn.com
|
CT Log | Current | — | 11 | 2025-05-01T00:00:00 | Amazon |
dplus-amer.use1.int.api.bolt.cnn.com
|
CT Log | Current | — | 5 | 2025-04-29T00:00:00 | Amazon |
dplus-amer.use1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 10 | 2025-05-08T00:00:00 | Amazon |
dplus-amer.use1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-05-02T00:00:00 | Amazon |
dplus-amer.use2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-05-08T00:00:00 | Amazon |
dplus-amer.use2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 9 | 2025-05-02T00:00:00 | Amazon |
dplus-amer.usw2.int.api.bolt.cnn.com
|
CT Log | Current | — | 4 | 2025-04-23T00:00:00 | Amazon |
dplus-amer.usw2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 8 | 2025-05-08T00:00:00 | Amazon |
dplus-amer.usw2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 8 | 2025-05-02T00:00:00 | Amazon |
dplus-any.apne1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-08T00:00:00 | Amazon |
dplus-any.aps1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-08T00:00:00 | Amazon |
dplus-any.aps1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
dplus-any.apse1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-08T00:00:00 | Amazon |
dplus-any.apse1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
dplus-any.dev.api.bolt.cnn.com
|
CT Log | Current | — | 11 | 2025-05-01T00:00:00 | Amazon |
dplus-any.euc1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 5 | 2025-05-08T00:00:00 | Amazon |
dplus-any.euc1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 6 | 2025-05-02T00:00:00 | Amazon |
dplus-any.eun1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-05-08T00:00:00 | Amazon |
dplus-any.euw1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 6 | 2025-05-08T00:00:00 | Amazon |
dplus-any.euw1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-02T00:00:00 | Amazon |
dplus-any.int.api.bolt.cnn.com
|
CT Log | Current | — | 8 | 2025-04-29T00:00:00 | Amazon |
dplus-any.prd.api.bolt.cnn.com
|
CT Log | Current | — | 28 | 2025-05-08T00:00:00 | Amazon |
dplus-any.stg.api.bolt.cnn.com
|
CT Log | Current | — | 24 | 2025-05-02T00:00:00 | Amazon |
dplus-any.use.dev.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-01T00:00:00 | Amazon |
dplus-any.use.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
dplus-any.use.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-08T00:00:00 | Amazon |
dplus-any.use.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
dplus-any.use1.dev.api.bolt.cnn.com
|
CT Log | Current | — | 12 | 2025-05-01T00:00:00 | Amazon |
dplus-any.use1.int.api.bolt.cnn.com
|
CT Log | Current | — | 5 | 2025-04-29T00:00:00 | Amazon |
dplus-any.use1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 10 | 2025-05-08T00:00:00 | Amazon |
dplus-any.use1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 6 | 2025-05-02T00:00:00 | Amazon |
dplus-any.use2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-05-08T00:00:00 | Amazon |
dplus-any.use2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 8 | 2025-05-02T00:00:00 | Amazon |
dplus-any.usw2.int.api.bolt.cnn.com
|
CT Log | Current | — | 4 | 2025-04-23T00:00:00 | Amazon |
dplus-any.usw2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 8 | 2025-05-08T00:00:00 | Amazon |
dplus-any.usw2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-05-02T00:00:00 | Amazon |
dplus-apac.apne1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-08T00:00:00 | Amazon |
dplus-apac.aps1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-08T00:00:00 | Amazon |
dplus-apac.aps1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
dplus-apac.apse1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-08T00:00:00 | Amazon |
dplus-apac.apse1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
dplus-apac.dev.api.bolt.cnn.com
|
CT Log | Current | — | 8 | 2025-04-23T00:00:00 | Amazon |
dplus-apac.euc1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-08T00:00:00 | Amazon |
dplus-apac.euc1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
dplus-apac.eun1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-08T00:00:00 | Amazon |
dplus-apac.euw1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
dplus-apac.euw1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
dplus-apac.int.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-04-23T00:00:00 | Amazon |
dplus-apac.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
dplus-apac.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
dplus-apac.use.dev.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
dplus-apac.use.int.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
dplus-apac.use.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
dplus-apac.use.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
dplus-apac.use1.dev.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-04-23T00:00:00 | Amazon |
dplus-apac.use1.int.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-04-23T00:00:00 | Amazon |
dplus-apac.use1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
dplus-apac.use1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
dplus-apac.use2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
dplus-apac.use2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
dplus-apac.usw2.int.api.bolt.cnn.com
|
CT Log | Current | — | 4 | 2025-04-23T00:00:00 | Amazon |
dplus-apac.usw2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
dplus-apac.usw2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
dplus-emea.apne1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
dplus-emea.aps1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
dplus-emea.aps1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
dplus-emea.apse1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
dplus-emea.apse1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
dplus-emea.dev.api.bolt.cnn.com
|
CT Log | Current | — | 8 | 2025-04-23T00:00:00 | Amazon |
dplus-emea.euc1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-08T00:00:00 | Amazon |
dplus-emea.euc1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 5 | 2025-05-02T00:00:00 | Amazon |
dplus-emea.eun1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 5 | 2025-05-08T00:00:00 | Amazon |
dplus-emea.euw1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 4 | 2025-05-08T00:00:00 | Amazon |
dplus-emea.euw1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-02T00:00:00 | Amazon |
dplus-emea.int.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-04-23T00:00:00 | Amazon |
dplus-emea.prd.api.bolt.cnn.com
|
CT Log | Current | — | 10 | 2025-05-08T00:00:00 | Amazon |
dplus-emea.stg.api.bolt.cnn.com
|
CT Log | Current | — | 6 | 2025-05-02T00:00:00 | Amazon |
dplus-emea.use.dev.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
dplus-emea.use.int.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
dplus-emea.use.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
dplus-emea.use.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
dplus-emea.use1.dev.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-04-23T00:00:00 | Amazon |
dplus-emea.use1.int.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-04-23T00:00:00 | Amazon |
dplus-emea.use1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
dplus-emea.use1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
dplus-emea.use2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
dplus-emea.use2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
dplus-emea.usw2.int.api.bolt.cnn.com
|
CT Log | Current | — | 4 | 2025-04-23T00:00:00 | Amazon |
dplus-emea.usw2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
dplus-emea.usw2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
dplus-latam.apne1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
dplus-latam.aps1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
dplus-latam.aps1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
dplus-latam.apse1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
dplus-latam.apse1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
dplus-latam.dev.api.bolt.cnn.com
|
CT Log | Current | — | 13 | 2025-05-01T00:00:00 | Amazon |
dplus-latam.euc1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
dplus-latam.euc1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
dplus-latam.eun1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
dplus-latam.euw1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
dplus-latam.euw1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
dplus-latam.int.api.bolt.cnn.com
|
CT Log | Current | — | 9 | 2025-04-29T00:00:00 | Amazon |
dplus-latam.prd.api.bolt.cnn.com
|
CT Log | Current | — | 17 | 2025-05-08T00:00:00 | Amazon |
dplus-latam.stg.api.bolt.cnn.com
|
CT Log | Current | — | 19 | 2025-05-02T00:00:00 | Amazon |
dplus-latam.use.dev.api.bolt.cnn.com
|
CT Log | Current | — | 3 | 2025-05-01T00:00:00 | Amazon |
dplus-latam.use.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
dplus-latam.use.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
dplus-latam.use.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
dplus-latam.use1.dev.api.bolt.cnn.com
|
CT Log | Current | — | 12 | 2025-05-01T00:00:00 | Amazon |
dplus-latam.use1.int.api.bolt.cnn.com
|
CT Log | Current | — | 5 | 2025-04-29T00:00:00 | Amazon |
dplus-latam.use1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 8 | 2025-05-08T00:00:00 | Amazon |
dplus-latam.use1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 6 | 2025-05-02T00:00:00 | Amazon |
dplus-latam.use2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 5 | 2025-05-08T00:00:00 | Amazon |
dplus-latam.use2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 8 | 2025-05-02T00:00:00 | Amazon |
dplus-latam.usw2.int.api.bolt.cnn.com
|
CT Log | Current | — | 4 | 2025-04-23T00:00:00 | Amazon |
dplus-latam.usw2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 6 | 2025-05-08T00:00:00 | Amazon |
dplus-latam.usw2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-05-02T00:00:00 | Amazon |
e.commerce.cnn.com
|
CT Log | Current | — | 1 | 2025-03-13T05:26:02 | GlobalSign nv-sa |
e.emailalerts.cnn.com
|
CT Log | Current | — | 1 | 2025-03-13T05:26:02 | GlobalSign nv-sa |
e.mail.cnn.com
|
CT Log | Current | — | 2 | 2025-03-17T15:42:06 | GlobalSign nv-sa |
e.newsletters.cnn.com
|
CT Log | Current | — | 1 | 2025-03-13T05:26:02 | GlobalSign nv-sa |
e.specials.cnn.com
|
CT Log | Current | — | 1 | 2025-03-13T05:26:02 | GlobalSign nv-sa |
e.transactional.cnn.com
|
CT Log | Current | — | 1 | 2025-03-13T05:26:02 | GlobalSign nv-sa |
edition.cnn.com
|
CT Log | Current | — | 6 | 2025-04-29T14:44:03 | GlobalSign nv-sa |
edition.i.cdn.cnn.com
|
CT Log | Current | — | 2 | 2025-04-15T19:26:45 | GlobalSign nv-sa |
edition.stage.next.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T18:58:13 | GlobalSign nv-sa |
edition.stage2.next.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T18:58:13 | GlobalSign nv-sa |
edition.stage3.next.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T18:58:13 | GlobalSign nv-sa |
elections.cnn.com
|
CT Log | Current | — | 10 | 2025-04-30T18:30:38 | GlobalSign nv-sa, Amazon |
electiontracker.cnn.com
|
CT Log | Current | — | 2 | 2025-04-15T19:26:45 | GlobalSign nv-sa |
euc1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 8 | 2025-06-09T00:00:00 | Amazon |
euc1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 8 | 2025-06-04T00:00:00 | Amazon |
eun1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 9 | 2025-06-09T00:00:00 | Amazon |
euw1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 8 | 2025-06-09T00:00:00 | Amazon |
euw1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-06-04T00:00:00 | Amazon |
feeds.cnn.com
|
DNS | Current |
cnn-tls.map.fastly.net
|
10 | 2025-02-20 | Amazon, GlobalSign nv-sa |
flash-automation.cdn.dev.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
flash-automation.cdn.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
flash-automation.cdn.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-09T00:00:00 | Amazon |
flash-automation.cdn.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
forums.cnn.com
|
DNS | Current | — | 10 | 2025-02-20 | Amazon, GlobalSign nv-sa |
foundations.stellar.cnn.com
|
CT Log | Current | — | 4 | 2025-03-26T00:00:00 | Amazon |
go.cnn.com
|
CT Log | Current | — | 9 | 2025-07-09T17:31:02 | GlobalSign nv-sa |
help.cnn.com
|
CT Log | Current | — | 1 | 2025-10-08T18:05:14 | Starfield Technologies, Inc. |
hub.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
i.cdn.cnn.com
|
CT Log | Current | — | 6 | 2025-04-29T14:46:29 | GlobalSign nv-sa |
i.cdn.travel.cnn.com
|
CT Log | Current |
cnn-tls.map.fastly.net
|
4 | 2025-04-15T20:42:59 | GlobalSign nv-sa |
images.cdn.dev.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
images.cdn.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
images.cdn.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-09T00:00:00 | Amazon |
images.cdn.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
images.commerce.cnn.com
|
CT Log | Current | — | 1 | 2025-03-13T05:31:02 | GlobalSign nv-sa |
images.emailalerts.cnn.com
|
CT Log | Current | — | 1 | 2025-03-13T05:31:02 | GlobalSign nv-sa |
images.mail.cnn.com
|
CT Log | Current | — | 1 | 2025-03-13T05:31:02 | GlobalSign nv-sa |
images.newsletters.cnn.com
|
CT Log | Current | — | 1 | 2025-03-13T05:31:02 | GlobalSign nv-sa |
images.specials.cnn.com
|
CT Log | Current | — | 1 | 2025-03-13T05:31:02 | GlobalSign nv-sa |
images.transactional.cnn.com
|
CT Log | Current | — | 1 | 2025-03-13T05:31:02 | GlobalSign nv-sa |
int.api.bolt.cnn.com
|
CT Log | Current | — | 40 | 2025-06-04T00:00:00 | Amazon |
li.cnn.com
|
CT Log | Current | — | 2 | 2025-05-19T00:00:00 | Amazon |
links.cnn.com
|
DNS | Current |
sendgrid.net
|
10 | 2025-02-20 | Amazon, GlobalSign nv-sa |
live.cnn.com
|
DNS | Current |
live.cnn.com.edgesuite.net
|
10 | 2025-02-20 | Amazon, GlobalSign nv-sa |
m.cnn.com
|
DNS | Current |
lite.cnn.com
|
10 | 2025-02-20 | Amazon, GlobalSign nv-sa |
mail.cnn.com
|
DNS | Current | — | 10 | 2025-02-20 | Amazon, GlobalSign nv-sa |
mail2.cnn.com
|
DNS | Current | — | 10 | 2025-02-20 | Amazon, GlobalSign nv-sa |
markets.money.cnn.com
|
CT Log | Current | — | 3 | 2025-09-29T15:22:02 | GlobalSign nv-sa |
media.cnn.com
|
CT Log | Current | — | 4 | 2025-09-11T16:51:48 | GlobalSign nv-sa |
metadata.cdn.dev.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
metadata.cdn.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
metadata.cdn.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-09T00:00:00 | Amazon |
metadata.cdn.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
metrics.cnn.com
|
DNS | Current |
cnn.122.2o7.net
|
10 | 2025-02-20 | Amazon, GlobalSign nv-sa |
mobile.cnn.com
|
DNS | Current | — | 10 | 2025-02-20 | Amazon, GlobalSign nv-sa |
money.cnn.com
|
CT Log | Current | — | 8 | 2025-07-09T17:31:02 | GlobalSign nv-sa |
my.cnn.com
|
DNS | Current |
reflector.cnn.com
|
10 | 2025-02-20 | Amazon, GlobalSign nv-sa |
next.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T18:58:13 | GlobalSign nv-sa |
odm.platform.cnn.com
|
CT Log | Current | — | 5 | 2025-04-29T14:41:57 | GlobalSign nv-sa |
partner-logos.cdn.dev.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
partner-logos.cdn.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
partner-logos.cdn.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-09T00:00:00 | Amazon |
partner-logos.cdn.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
partner.any-amer.dev.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
partner.any-amer.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
partner.any-amer.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
partner.any-amer.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
partner.any-any.dev.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
partner.any-any.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
partner.any-any.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
partner.any-any.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
partner.any-apac.dev.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
partner.any-apac.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
partner.any-apac.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
partner.any-apac.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
partner.any-emea.dev.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
partner.any-emea.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
partner.any-emea.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
partner.any-emea.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
partner.any-latam.dev.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
partner.any-latam.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
partner.any-latam.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
partner.any-latam.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
partner.beam-amer.dev.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
partner.beam-amer.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
partner.beam-amer.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
partner.beam-amer.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
partner.beam-any.dev.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
partner.beam-any.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
partner.beam-any.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
partner.beam-any.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
partner.beam-apac.dev.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
partner.beam-apac.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
partner.beam-apac.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
partner.beam-apac.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
partner.beam-emea.dev.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
partner.beam-emea.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
partner.beam-emea.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
partner.beam-emea.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
partner.beam-latam.dev.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
partner.beam-latam.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
partner.beam-latam.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
partner.beam-latam.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
partner.br-amer.dev.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
partner.br-amer.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
partner.br-amer.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
partner.br-amer.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
partner.br-any.dev.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
partner.br-any.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
partner.br-any.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
partner.br-any.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
partner.br-apac.dev.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
partner.br-apac.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
partner.br-apac.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
partner.br-apac.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
partner.br-emea.dev.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
partner.br-emea.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
partner.br-emea.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
partner.br-emea.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
partner.br-latam.dev.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
partner.br-latam.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
partner.br-latam.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
partner.br-latam.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
partner.cnn-amer.int.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
partner.cnn-amer.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
partner.cnn-amer.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
partner.cnn-any.int.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
partner.cnn-any.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
partner.cnn-any.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
partner.cnn-apac.int.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
partner.cnn-apac.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
partner.cnn-apac.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
partner.cnn-emea.int.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
partner.cnn-emea.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
partner.cnn-emea.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
partner.cnn-latam.int.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
partner.cnn-latam.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-09T00:00:00 | Amazon |
partner.cnn-latam.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
partner.cnn.com
|
CT Log | Current | — | 1 | 2025-04-10T12:21:02 | GlobalSign nv-sa |
partner.dev.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
partner.dplus-amer.dev.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
partner.dplus-amer.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
partner.dplus-amer.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-09T00:00:00 | Amazon |
partner.dplus-amer.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
partner.dplus-any.dev.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
partner.dplus-any.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
partner.dplus-any.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-09T00:00:00 | Amazon |
partner.dplus-any.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
partner.dplus-apac.dev.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
partner.dplus-apac.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
partner.dplus-apac.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-09T00:00:00 | Amazon |
partner.dplus-apac.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
partner.dplus-emea.dev.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
partner.dplus-emea.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
partner.dplus-emea.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-09T00:00:00 | Amazon |
partner.dplus-emea.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
partner.dplus-latam.dev.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
partner.dplus-latam.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
partner.dplus-latam.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-09T00:00:00 | Amazon |
partner.dplus-latam.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
partner.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
partner.int.cnn.com
|
CT Log | Current | — | 1 | 2025-04-10T12:21:02 | GlobalSign nv-sa |
partner.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-09T00:00:00 | Amazon |
partner.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
partner.stg.cnn.com
|
CT Log | Current | — | 2 | 2025-04-10T12:21:02 | GlobalSign nv-sa |
partners.cnn.com
|
DNS | Current | — | 10 | 2025-02-20 | Amazon, GlobalSign nv-sa |
pdx.stellar.cnn.com
|
CT Log | Current | — | 4 | 2025-03-26T00:00:00 | Amazon |
phone.cnn.com
|
DNS | Current |
phone.cnn.com.edgesuite.net
|
10 | 2025-02-20 | Amazon, GlobalSign nv-sa |
platform.cnn.com
|
CT Log | Current | — | 6 | 2025-04-29T14:41:57 | GlobalSign nv-sa |
prd.api.bolt.cnn.com
|
CT Log | Current | — | 176 | 2025-06-23T00:00:00 | Amazon |
preprod.stellar.cnn.com
|
CT Log | Current | — | 4 | 2025-03-26T00:00:00 | Amazon |
preview.dev.money.cnn.com
|
CT Log | Current | — | 8 | 2025-04-30T19:08:07 | GlobalSign nv-sa |
preview.qa.money.cnn.com
|
CT Log | Current | — | 6 | 2025-04-30T18:30:38 | GlobalSign nv-sa |
preview.ref.money.cnn.com
|
CT Log | Current | — | 8 | 2025-04-30T19:08:07 | GlobalSign nv-sa |
preview.train.money.cnn.com
|
CT Log | Current | — | 6 | 2025-04-30T18:30:38 | GlobalSign nv-sa |
preview2.ref.money.cnn.com
|
CT Log | Current | — | 8 | 2025-04-30T19:08:07 | GlobalSign nv-sa |
private-vpce.apne1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-09T00:00:00 | Amazon |
private-vpce.aps1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-09T00:00:00 | Amazon |
private-vpce.aps1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
private-vpce.apse1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-09T00:00:00 | Amazon |
private-vpce.apse1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
private-vpce.euc1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-09T00:00:00 | Amazon |
private-vpce.euc1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
private-vpce.eun1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-09T00:00:00 | Amazon |
private-vpce.euw1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-09T00:00:00 | Amazon |
private-vpce.euw1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
private-vpce.use1.dev.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
private-vpce.use1.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
private-vpce.use1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-09T00:00:00 | Amazon |
private-vpce.use1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
private-vpce.use2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-09T00:00:00 | Amazon |
private-vpce.use2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
private-vpce.usw2.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
private-vpce.usw2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-09T00:00:00 | Amazon |
private-vpce.usw2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
private.ap.dev.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
private.ap.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
private.ap.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-09T00:00:00 | Amazon |
private.ap.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
private.apne1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-09T00:00:00 | Amazon |
private.aps1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-09T00:00:00 | Amazon |
private.aps1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
private.apse1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-09T00:00:00 | Amazon |
private.apse1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
private.eu.dev.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
private.eu.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
private.eu.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-09T00:00:00 | Amazon |
private.eu.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
private.euc1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-09T00:00:00 | Amazon |
private.euc1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
private.eun1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-09T00:00:00 | Amazon |
private.euw1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-09T00:00:00 | Amazon |
private.euw1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
private.us.dev.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
private.us.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
private.us.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-09T00:00:00 | Amazon |
private.us.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
private.use1.dev.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
private.use1.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
private.use1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-09T00:00:00 | Amazon |
private.use1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
private.use2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-09T00:00:00 | Amazon |
private.use2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
private.usw2.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
private.usw2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-09T00:00:00 | Amazon |
private.usw2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
proxy.cnn.com
|
DNS | Current | — | 10 | 2025-02-20 | Amazon, GlobalSign nv-sa |
qa.stellar.cnn.com
|
CT Log | Current | — | 4 | 2025-03-26T00:00:00 | Amazon |
ref.alertshub.cnn.com
|
CT Log | Current | — | 2 | 2025-03-15T00:00:00 | Amazon |
roku.partner.any-amer.dev.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
roku.partner.any-amer.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
roku.partner.any-amer.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-09T00:00:00 | Amazon |
roku.partner.any-amer.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
roku.partner.any-any.dev.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
roku.partner.any-any.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
roku.partner.any-any.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-09T00:00:00 | Amazon |
roku.partner.any-any.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
roku.partner.any-apac.dev.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
roku.partner.any-apac.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
roku.partner.any-apac.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-09T00:00:00 | Amazon |
roku.partner.any-apac.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
roku.partner.any-emea.dev.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
roku.partner.any-emea.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
roku.partner.any-emea.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-09T00:00:00 | Amazon |
roku.partner.any-emea.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
roku.partner.any-latam.dev.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
roku.partner.any-latam.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
roku.partner.any-latam.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
roku.partner.any-latam.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
roku.partner.beam-amer.dev.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
roku.partner.beam-amer.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
roku.partner.beam-amer.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
roku.partner.beam-amer.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
roku.partner.beam-any.dev.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
roku.partner.beam-any.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
roku.partner.beam-any.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
roku.partner.beam-any.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
roku.partner.beam-apac.dev.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
roku.partner.beam-apac.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
roku.partner.beam-apac.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
roku.partner.beam-apac.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
roku.partner.beam-emea.dev.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
roku.partner.beam-emea.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
roku.partner.beam-emea.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
roku.partner.beam-emea.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
roku.partner.beam-latam.dev.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
roku.partner.beam-latam.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
roku.partner.beam-latam.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
roku.partner.beam-latam.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
roku.partner.br-amer.dev.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
roku.partner.br-amer.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
roku.partner.br-amer.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
roku.partner.br-amer.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
roku.partner.br-any.dev.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
roku.partner.br-any.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
roku.partner.br-any.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
roku.partner.br-any.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
roku.partner.br-apac.dev.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
roku.partner.br-apac.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
roku.partner.br-apac.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
roku.partner.br-apac.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T00:00:00 | Amazon |
roku.partner.br-emea.dev.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
roku.partner.br-emea.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
roku.partner.br-emea.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
roku.partner.br-emea.stg.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
roku.partner.br-latam.dev.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
roku.partner.br-latam.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
roku.partner.br-latam.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
roku.partner.br-latam.stg.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
roku.partner.cnn-amer.dev.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
roku.partner.cnn-amer.int.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
roku.partner.cnn-amer.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
roku.partner.cnn-amer.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
roku.partner.cnn-any.dev.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
roku.partner.cnn-any.int.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
roku.partner.cnn-any.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
roku.partner.cnn-any.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
roku.partner.cnn-apac.dev.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
roku.partner.cnn-apac.int.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
roku.partner.cnn-apac.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
roku.partner.cnn-apac.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
roku.partner.cnn-emea.dev.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
roku.partner.cnn-emea.int.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
roku.partner.cnn-emea.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
roku.partner.cnn-emea.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
roku.partner.cnn-latam.dev.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
roku.partner.cnn-latam.int.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
roku.partner.cnn-latam.prd.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-05-08T00:00:00 | Amazon |
roku.partner.cnn-latam.stg.api.bolt.cnn.com
|
CT Log | Current | — | 1 | 2025-04-29T00:00:00 | Amazon |
roku.partner.dev.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
roku.partner.dplus-amer.dev.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
roku.partner.dplus-amer.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
roku.partner.dplus-amer.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
roku.partner.dplus-amer.stg.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
roku.partner.dplus-any.dev.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
roku.partner.dplus-any.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
roku.partner.dplus-any.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
roku.partner.dplus-any.stg.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
roku.partner.dplus-apac.dev.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
roku.partner.dplus-apac.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
roku.partner.dplus-apac.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
roku.partner.dplus-apac.stg.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
roku.partner.dplus-emea.dev.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
roku.partner.dplus-emea.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
roku.partner.dplus-emea.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
roku.partner.dplus-emea.stg.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
roku.partner.dplus-latam.dev.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
roku.partner.dplus-latam.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
roku.partner.dplus-latam.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
roku.partner.dplus-latam.stg.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
roku.partner.int.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
roku.partner.prd.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-05-08T00:00:00 | Amazon |
roku.partner.stg.api.bolt.cnn.com
|
CT Log | Current | — | 2 | 2025-04-29T00:00:00 | Amazon |
rss.cnn.com
|
DNS | Current |
i0bub0.feedproxy.ghs.google.com
|
10 | 2025-02-20 | Amazon, GlobalSign nv-sa |
sandbox.cnn.com
|
DNS | Current | — | 10 | 2025-02-20 | Amazon, GlobalSign nv-sa |
services.cnn.com
|
DNS | Current |
newsgraph.api.cnn.io
|
10 | 2025-02-20 | Amazon, GlobalSign nv-sa |
settop.cnn.com
|
CT Log | Current | — | 3 | 2025-04-29T14:44:59 | GlobalSign nv-sa, Amazon |
smetrics.cnn.com
|
CT Log | Current | — | 1 | 2025-03-12T00:00:00 | DigiCert Inc |
social.academy.cnn.com
|
CT Log | Current | — | 2 | 2025-05-09T00:00:00 | Amazon |
sponsorcontent.cnn.com
|
CT Log | Current |
www.cnn.com
|
3 | 2025-04-29T14:45:45 | GlobalSign nv-sa |
stage-partner.cnn.com
|
CT Log | Current | — | 1 | 2025-04-10T12:21:02 | GlobalSign nv-sa |
stage.cnn.com
|
DNS | Current |
cnn-tls.map.fastly.net
|
10 | 2025-02-20 | Amazon, GlobalSign nv-sa |
stage.next.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T18:58:13 | GlobalSign nv-sa |
stage.stellar.cnn.com
|
CT Log | Current | — | 4 | 2025-03-26T00:00:00 | Amazon |
stage2.next.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T18:58:13 | GlobalSign nv-sa |
stage3.next.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T18:58:13 | GlobalSign nv-sa |
static.cnn.com
|
DNS | Current |
i.cnn.net
|
10 | 2025-02-20 | Amazon, GlobalSign nv-sa |
stellar.cnn.com
|
CT Log | Current | — | 14 | 2025-04-29T14:46:05 | GlobalSign nv-sa, Amazon |
stg.api.bolt.cnn.com
|
CT Log | Current | — | 126 | 2025-06-18T00:00:00 | Amazon |
store.academy.cnn.com
|
CT Log | Current | — | 2 | 2025-05-09T00:00:00 | Amazon |
store.cnn.com
|
DNS | Current | — | 10 | 2025-02-20 | Amazon, GlobalSign nv-sa |
training.cnn.com
|
DNS | Current |
cnn-tls.map.fastly.net
|
10 | 2025-02-20 | Amazon, GlobalSign nv-sa |
travel.cnn.com
|
CT Log | Current | — | 4 | 2025-04-15T20:42:59 | GlobalSign nv-sa |
uk.help.cnn.com
|
CT Log | Current | — | 1 | 2025-10-08T18:06:29 | Starfield Technologies, Inc. |
underscored.stellar.cnn.com
|
CT Log | Current | — | 4 | 2025-03-26T00:00:00 | Amazon |
us.cnn.com
|
DNS | Current |
cnn-tls.map.fastly.net
|
10 | 2025-02-20 | Amazon, GlobalSign nv-sa |
use.dev.api.bolt.cnn.com
|
CT Log | Current | — | 12 | 2025-06-04T00:00:00 | Amazon |
use.int.api.bolt.cnn.com
|
CT Log | Current | — | 4 | 2025-04-29T00:00:00 | Amazon |
use.prd.api.bolt.cnn.com
|
CT Log | Current | — | 10 | 2025-06-09T00:00:00 | Amazon |
use.stg.api.bolt.cnn.com
|
CT Log | Current | — | 7 | 2025-06-04T00:00:00 | Amazon |
use1.dev.api.bolt.cnn.com
|
CT Log | Current | — | 28 | 2025-06-04T00:00:00 | Amazon |
use1.int.api.bolt.cnn.com
|
CT Log | Current | — | 13 | 2025-06-04T00:00:00 | Amazon |
use1.prd.api.bolt.cnn.com
|
CT Log | Current | — | 17 | 2025-06-09T00:00:00 | Amazon |
use1.stg.api.bolt.cnn.com
|
CT Log | Current | — | 12 | 2025-06-04T00:00:00 | Amazon |
use2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 12 | 2025-06-09T00:00:00 | Amazon |
use2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 13 | 2025-06-04T00:00:00 | Amazon |
usw2.int.api.bolt.cnn.com
|
CT Log | Current | — | 9 | 2025-06-04T00:00:00 | Amazon |
usw2.prd.api.bolt.cnn.com
|
CT Log | Current | — | 10 | 2025-06-09T00:00:00 | Amazon |
usw2.stg.api.bolt.cnn.com
|
CT Log | Current | — | 9 | 2025-06-04T00:00:00 | Amazon |
video.cnn.com
|
DNS | Current |
vxtreme.cnn.com
|
10 | 2025-02-20 | Amazon, GlobalSign nv-sa |
view.commerce.cnn.com
|
CT Log | Current | — | 1 | 2025-03-13T05:31:02 | GlobalSign nv-sa |
view.emailalerts.cnn.com
|
CT Log | Current | — | 1 | 2025-03-13T05:31:02 | GlobalSign nv-sa |
view.mail.cnn.com
|
CT Log | Current | — | 2 | 2025-03-17T15:40:22 | GlobalSign nv-sa |
view.newsletters.cnn.com
|
CT Log | Current | — | 1 | 2025-03-13T05:31:02 | GlobalSign nv-sa |
view.specials.cnn.com
|
CT Log | Current | — | 1 | 2025-03-13T05:31:02 | GlobalSign nv-sa |
view.transactional.cnn.com
|
CT Log | Current | — | 1 | 2025-03-13T05:31:02 | GlobalSign nv-sa |
www.cnn.com
|
DNS | Current |
cnn-tls.map.fastly.net
|
10 | 2025-02-20 | Amazon, GlobalSign nv-sa |
www.collection.cnn.com
|
CT Log | Current | — | 1 | 2025-04-15T14:11:22 | GlobalSign nv-sa |
www.help.cnn.com
|
CT Log | Current | — | 1 | 2025-10-08T18:05:14 | Starfield Technologies, Inc. |
www.i.cdn.cnn.com
|
CT Log | Current | — | 2 | 2025-04-15T19:26:45 | GlobalSign nv-sa |
www.uk.help.cnn.com
|
CT Log | Current | — | 1 | 2025-10-08T18:06:29 | Starfield Technologies, Inc. |
www1.cnn.com
|
DNS | Current | — | 10 | 2025-02-20 | Amazon, GlobalSign nv-sa |
www2.cnn.com
|
DNS | Current |
ion-ma.turner.com.edgekey.net
|
10 | 2025-02-20 | Amazon, GlobalSign nv-sa |
www3.cnn.com
|
DNS | Current | — | 10 | 2025-02-20 | Amazon, GlobalSign nv-sa |
xml.cnn.com
|
DNS | Current |
robots.cnn.com
|
10 | 2025-02-20 | Amazon, GlobalSign nv-sa |
Δ No Propagation Issues:
All DNS records are synchronized between resolver and authoritative nameserver.
DNS Intelligence
What does DNS look like right now — and what changed over time?
DNS Evidence Diff Side-by-side comparison
Resolver Records
(Public DNS cache)
Authoritative Records
(Source of truth)
A
Synchronized
4 / 4 records
151.101.3.5
151.101.131.5
151.101.131.5
151.101.195.5
151.101.67.5
151.101.3.5
151.101.195.5
151.101.67.5
AAAA
Synchronized
4 / 4 records
2a04:4e42:400::773
2a04:4e42:600::773
2a04:4e42:600::773
2a04:4e42:200::773
2a04:4e42:200::773
2a04:4e42::773
2a04:4e42::773
2a04:4e42:400::773
No records
No records
v=DMARC1; p=reject; rua=mailto:dmarc_agg@vali.email; ruf=mailto:Njk3@ruf.vali.email
—
10 cnn-com.mail.protection.outlook.com.
10 cnn-com.mail.protection.outlook.com.
ns-1652.awsdns-14.co.uk.
ns-1242.awsdns-27.org.
ns-378.awsdns-47.com.
ns-1652.awsdns-14.co.uk.
ns-587.awsdns-09.net.
ns-378.awsdns-47.com.
ns-1242.awsdns-27.org.
ns-587.awsdns-09.net.
ns-1652.awsdns-14.co.uk. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400
ns-1652.awsdns-14.co.uk. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400
353665828-4422052
—
google-site-verification=R-Btow3Z8oU_9H1IWU4Gm4lvUQ_OVmsfxonIKhIaiPE
—
764482256-4422025
—
_globalsign-domain-verification=9hlGg1_xFQ9m6kVqzsG0EO121UTChwQZQCgxCRvgyn
—
133461244-4422058
—
528183251-4422019
—
stripe-verification=1488a36c1dc125ea564dc5822d1414eeed68875825aaf90df27ac3131d053935
—
882269757-4422010
—
stripe-verification=5535d8a3c7b3517ee3765df8bd66b8a5cf70a65c3437f5be5d3a8f0108b790ef
—
598362927-4422061
—
294913881-4422049
—
_globalsign-domain-verification=5ckEJ4VIhQ6weCdCfmfzQPVP6ED1LtCX9jw1OKX5Mv
—
186844776-4422028
—
stripe-verification=e5dad290205182f6bdbd4e72697ce3cf9a965f35cb0349d538e09706345fb673
—
MS=ms66433104
—
globalsign-domain-verification=2lI5pahhCu_jg_2RC5GEdolQmAa4K7rhP7_OA-lZBK
—
mongodb-site-verification=mtrxHeW3jOzWtwEwnOLpeQo9NXh6Lqas
—
openai-domain-verification=dv-yGIc9wI1iK7uFqtmBqEp94Xk
—
facebook-domain-verification=xszi21kow2trmw3xt3ph6s631zyu3i
—
553992719-4400647
—
adobe-idp-site-verification=279ead95-3581-42b7-82f4-73c97f8cebfa
—
_globalsign-domain-verification=MK_ZKmss4D_DdzGOsssHxxBOK6hJc6LGycFvNOESdZ
—
globalsign-domain-verification=-Q7umwx2mj164XwLa0PsoUaWe2HBhta50GjggsT98f
—
178953534-4422001
—
google-site-verification=_QivaXNjhXy-V1y_YqrycXdAWZi2mVrcwbXerX6THeY
—
stripe-verification=42CDB310484C1CAA878F12A73EB7505EA6E7F154731CD7E4F5ABB574DE5E7725
—
321159687-4422031
—
349997471-4422043
—
lucidlink-verification=B9TYHWKAXAA93NQ61ST71E7NW8
—
canva-site-verification=_RUUWoBDVpt0pfonUPWJgg
—
atlassian-domain-verification=joqe6L8dNi+aisGbB1XHQa0pDc53V2l0GQQRUtLEcr2997x0+rtrAA5Zw+UgQw3u
—
cisco-ci-domain-verification=4a1c92ef69fe42f8125c3ca9ce0696dcf6cc16fa80243257de578af593d19548
—
754516718-4422064
—
826218936-4422046
—
_globalsign-domain-verification=2lybn8Z2GKCTHNehPEREKdz_jh5SahShpwOeRqCWjl
—
_globalsign-domain-verification=-lBuNJDFRxDkLkNbYOLBU03PlWjnPqAzBPAVUokhAw
—
tollbit-domain-verification=3b1766c3c41ef082750984a8a43089a81344c7af85005466c1a03c6ca1fb47dd
—
714321471-4421998
—
_globalsign-domain-verification=B57sRQpmte4G4w-gavZbVNmmNsMxGp5kcL19UP2599
—
d1xTs9+kADZZSz3bPphLpkMXXxBGjqn5vsQHhi2M6lo0r8AdIbm6j8LfQXPujsywVgeGSP+AXWX0vO9Iep5cUg==
—
755973593-4422016
—
287893558-4422013
—
ms=ms97284866
—
2baPGrmeo+RwsWdIdq/gIVSEWNb4tC9mLGQu0j4l/mduqhm06T+V9vNLXsauLyH9FwMZJSRHvj/YHGKOVWRylw==
—
299762315-4422055
—
v=spf1 include:cnn.com._nspf.vali.email include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email include:mail.zendesk.com ~all
—
691244352-4422022
—
688162515-4422037
—
_globalsign-domain-verification=1McxnrVkIU8RCVwwHslxDiq_r8hp3zjD_f29xgdWgF
—
mixpanel-domain-verify=612e2914-a7fb-4965-95d5-19acc02797df
—
228426766-4422034
—
_globalsign-domain-verification=yTw3T3KnyIyTB1xG2GvVhl1zWJlFp-WqmNskdVI_65
—
782989862-4417942
—
126953328-4422040
—
667921863-4422007
—
adobe-sign-verification=c3dc3217f76deddcb413a23e4e665fad
—
267933795-4422004
—
stripe-verification=094254c9a60a6dc0c1c2a62294b81c0c3b9363d044151a3e562ffeac0a7c4157
—
_globalsign-domain-verification=S6DssfjyL_2kgK4I2Ae_1cdPfwqRRBfB9-3ZhRGMRj
—
google-site-verification=cNhH3bbaizgJp34tQo2r1NgKE0YYLIPNOOvcBVTT5Pk
—
DNS History Timeline BETA
Your key is sent directly to SecurityTrails and is never stored on our servers. Get an API key
DNS History Timeline BETA
When was a record added, removed, or changed — and could that change be the problem?
Confirm Your Email Configuration
This tool analyzes DNS records, but to verify actual email delivery, send a test email to Red Sift Investigate. Their tool shows exactly how your emails arrive, including SPF/DKIM/DMARC pass/fail results in the headers.
DATA FRESHNESS & METHODOLOGY
All security-critical records (SPF, DMARC, DKIM, DANE/TLSA, DNSSEC, MTA-STS, TLS-RPT, BIMI, CAA) are queried live from authoritative nameservers and cross-referenced against 5 independent public DNS resolvers (Cloudflare, Google, Quad9, OpenDNS, DNS4EU) at the time of each analysis. No security verdict uses cached data.
Registrar data (RDAP) is cached for up to 24 hours because domain ownership and registration details change infrequently. Certificate Transparency logs (subdomain discovery via RFC 6962) are cached for 1 hour because CT entries are append-only historical records. Sections using cached data are marked with a CACHED badge; live queries show LIVE.
Intelligence Sources
This analysis used 4 DNS resolvers (consensus), reverse DNS (PTR), Team Cymru (ASN attribution), IANA RDAP (registrar), crt.sh (CT logs), and SMTP probing (transport). All using open-standard protocols.
Verify Report Integrity SHA-3-512 Has this report been altered since generation? Verify below
This cryptographic hash seals the analysis data, domain, timestamp, and tool version into a tamper-evident fingerprint. Any modification to the report data will produce a different hash. This is distinct from the posture hash (used for drift detection) — the integrity hash uniquely identifies this specific report instance.
94cb058b54895137b204769ad99ef9aad7c15fb09e7f412747af9ed2f49e3a924b9615191bc70bfc64e50c362a8caafeb1c84d53092caea0c459335dba9dad0a
Evaluations reference 12 RFCs. Methods are reproducible using the verification commands provided. Results reflect DNS state at 7 Mar 2026, 14:49 UTC.
Download the intelligence dump and verify its integrity, like you would a Kali ISO or any critical artifact. The SHA-3-512 checksum covers every byte of the download — deterministic serialization ensures identical hashes across downloads.
After downloading, verify with any of these commands:
Tip: cd ~/Downloads first (or wherever you saved the files).
OpenSSL + Sidecar (macOS, Linux, WSL)
cat dns-intelligence-cnn.com.json.sha3 && echo '---' && openssl dgst -sha3-512 dns-intelligence-cnn.com.json
Python 3 (cross-platform)
python3 -c "import hashlib; print(hashlib.sha3_512(open('dns-intelligence-cnn.com.json','rb').read()).hexdigest())"
sha3sum (coreutils 9+)
sha3sum -a 512 dns-intelligence-cnn.com.json
Compare the output against the
.sha3 file or the checksum API at /api/analysis/6275/checksum. Hash algorithm: SHA-3-512 (Keccak, NIST FIPS 202).
Every finding in this report is backed by DNS queries you can run yourself. These vetted one-liners reproduce the exact checks used to build this report for cnn.com. Our analysis adds multi-resolver consensus, RFC-based evaluation, and cross-referencing — but the underlying data is always independently verifiable. We are intelligence analysts, not gatekeepers.
DNS Records
Query A records (IPv4) RFC 1035
dig +noall +answer cnn.com A
Query AAAA records (IPv6) RFC 1035
dig +noall +answer cnn.com AAAA
Query MX records (mail servers) RFC 1035
dig +noall +answer cnn.com MX
Query NS records (nameservers) RFC 1035
dig +noall +answer cnn.com NS
Query TXT records RFC 1035
dig +noall +answer cnn.com TXTEmail Authentication
Check SPF record RFC 7208
dig +short cnn.com TXT | grep -i spf
Check DMARC policy RFC 7489
dig +short _dmarc.cnn.com TXT
Check DKIM key for selector 'cm' RFC 6376
dig +short cm._domainkey.cnn.com TXT
Check DKIM key for selector 'k1' RFC 6376
dig +short k1._domainkey.cnn.com TXT
Check DKIM key for selector 'k2' RFC 6376
dig +short k2._domainkey.cnn.com TXT
Check DKIM key for selector 'k3' RFC 6376
dig +short k3._domainkey.cnn.com TXT
Check DKIM key for selector 's1' RFC 6376
dig +short s1._domainkey.cnn.com TXT
Check DKIM key for selector 's2' RFC 6376
dig +short s2._domainkey.cnn.com TXT
Check DKIM key for selector 'selector1' RFC 6376
dig +short selector1._domainkey.cnn.com TXT
Check DKIM key for selector 'zendesk1' RFC 6376
dig +short zendesk1._domainkey.cnn.com TXT
Check DKIM key for selector 'zendesk2' RFC 6376
dig +short zendesk2._domainkey.cnn.com TXTDomain Security
Check DNSSEC DNSKEY records RFC 4035
dig +dnssec +noall +answer cnn.com DNSKEY
Check DNSSEC DS records RFC 4035
dig +noall +answer cnn.com DS
Validate DNSSEC chain (requires DNSSEC-validating resolver) RFC 4035
dig +dnssec +cd cnn.com A @1.1.1.1Transport Security
Check TLSA record for cnn-com.mail.protection.outlook.com RFC 7672
dig +noall +answer _25._tcp.cnn-com.mail.protection.outlook.com TLSA
Verify TLS certificate on primary MX (cnn-com.mail.protection.outlook.com) RFC 6698
openssl s_client -starttls smtp -connect cnn-com.mail.protection.outlook.com:25 -servername cnn-com.mail.protection.outlook.com 2>/dev/null | openssl x509 -noout -subject -dates
Check MTA-STS DNS record RFC 8461
dig +short _mta-sts.cnn.com TXT
Fetch MTA-STS policy file RFC 8461
curl -sL https://mta-sts.cnn.com/.well-known/mta-sts.txt
Check TLS-RPT record RFC 8460
dig +short _smtp._tls.cnn.com TXTBrand & Trust
Check BIMI record BIMI Draft
dig +short default._bimi.cnn.com TXT
Check CAA records (certificate authority authorization) RFC 8659
dig +noall +answer cnn.com CAADNS Records
Check HTTPS/SVCB records RFC 9460
dig +noall +answer cnn.com HTTPSDomain Security
Check CDS/CDNSKEY automation records RFC 7344
dig +noall +answer cnn.com CDSInfrastructure Intelligence
RDAP domain registration lookup RFC 9083
curl -sL 'https://rdap.org/domain/cnn.com' | python3 -m json.tool | head -50Transport Security
Test STARTTLS on primary MX (cnn-com.mail.protection.outlook.com) RFC 3207
openssl s_client -starttls smtp -connect cnn-com.mail.protection.outlook.com:25 -servername cnn-com.mail.protection.outlook.com </dev/null 2>/dev/null | head -5Infrastructure Intelligence
Search Certificate Transparency logs RFC 6962
curl -s 'https://crt.sh/?q=%25.cnn.com&output=json' | python3 -c "import json,sys; [print(e['name_value']) for e in json.load(sys.stdin)]" | sort -u | head -20
Check security.txt RFC 9116
curl -sL https://cnn.com/.well-known/security.txt | head -20AI Surface
Check for llms.txt
curl -sI https://cnn.com/llms.txt | head -5
Check robots.txt for AI crawler rules
curl -s https://cnn.com/robots.txt | grep -i -E 'GPTBot|ChatGPT|Claude|Anthropic|Google-Extended|CCBot|PerplexityBot'Infrastructure Intelligence
ASN lookup for 151.101.3.5 (Team Cymru)
dig +short 5.3.101.151.origin.asn.cymru.com TXT
ASN lookup for 151.101.131.5 (Team Cymru)
dig +short 5.131.101.151.origin.asn.cymru.com TXT
Commands use
dig, openssl, and curl — standard tools available on macOS, Linux, and WSL. Results may vary slightly due to DNS propagation timing and resolver caching.
Intelligence Confidence Audit Engine
verified · 9/9 Evaluated
How confident are these results? Each protocol is independently verified against RFC standards. No self-awarded badges.
SPF
Verified
4874 runs
DKIM
Verified
4692 runs
DMARC
Verified
4857 runs
DANE/TLSA
Verified
4676 runs
DNSSEC
Verified
4855 runs
BIMI
Verified
4691 runs
MTA-STS
Verified
4694 runs
TLS-RPT
Verified
4696 runs
CAA
Verified
4688 runs
Maturity:
Development
→
Verified
→
Consistent
→
Gold
→
Gold Master
Appendix: Verification Commands
DNS Records
dig +noall +answer cnn.com Adig +noall +answer cnn.com AAAAdig +noall +answer cnn.com MXdig +noall +answer cnn.com NSdig +noall +answer cnn.com TXTEmail Authentication
dig +short cnn.com TXT | grep -i spfdig +short _dmarc.cnn.com TXTdig +short cm._domainkey.cnn.com TXTdig +short k1._domainkey.cnn.com TXTdig +short k2._domainkey.cnn.com TXTdig +short k3._domainkey.cnn.com TXTdig +short s1._domainkey.cnn.com TXTdig +short s2._domainkey.cnn.com TXTdig +short selector1._domainkey.cnn.com TXTdig +short zendesk1._domainkey.cnn.com TXTdig +short zendesk2._domainkey.cnn.com TXTDomain Security
dig +dnssec +noall +answer cnn.com DNSKEYdig +noall +answer cnn.com DSdig +dnssec +cd cnn.com A @1.1.1.1Transport Security
dig +noall +answer _25._tcp.cnn-com.mail.protection.outlook.com TLSAopenssl s_client -starttls smtp -connect cnn-com.mail.protection.outlook.com:25 -servername cnn-com.mail.protection.outlook.com 2>/dev/null | openssl x509 -noout -subject -datesdig +short _mta-sts.cnn.com TXTcurl -sL https://mta-sts.cnn.com/.well-known/mta-sts.txtdig +short _smtp._tls.cnn.com TXTBrand & Trust
dig +short default._bimi.cnn.com TXTdig +noall +answer cnn.com CAADNS Records
dig +noall +answer cnn.com HTTPSDomain Security
dig +noall +answer cnn.com CDSInfrastructure Intelligence
curl -sL 'https://rdap.org/domain/cnn.com' | python3 -m json.tool | head -50Transport Security
openssl s_client -starttls smtp -connect cnn-com.mail.protection.outlook.com:25 -servername cnn-com.mail.protection.outlook.com </dev/null 2>/dev/null | head -5Infrastructure Intelligence
curl -s 'https://crt.sh/?q=%25.cnn.com&output=json' | python3 -c "import json,sys; [print(e['name_value']) for e in json.load(sys.stdin)]" | sort -u | head -20curl -sL https://cnn.com/.well-known/security.txt | head -20AI Surface
curl -sI https://cnn.com/llms.txt | head -5curl -s https://cnn.com/robots.txt | grep -i -E 'GPTBot|ChatGPT|Claude|Anthropic|Google-Extended|CCBot|PerplexityBot'Infrastructure Intelligence
dig +short 5.3.101.151.origin.asn.cymru.com TXTdig +short 5.131.101.151.origin.asn.cymru.com TXT