Skip to content
https://www.cnn.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
93
GRADE
A
FIX
0
REVIEW
2
PASS
7
INFO
0
Probed from Madrid, Spain
302 Found
Checks
9
7 PASS 2 REVIEW
B
DNS Records
4 A records, 24 ms lookup
REVIEW
4 A records, 24 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 151.101.67.5, 151.101.131.5, 151.101.3.5, 151.101.195.5
Info::
Has 4 IPv6 (AAAA) record(s)
Got: 2a04:4e42:200::773, 2a04:4e42::773, 2a04:4e42:400::773, 2a04:4e42:600::773
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: cnn-tls.map.fastly.net
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 24 ms
Got: 24 ms
A151.101.67.5, 151.101.131.5, 151.101.3.5, 151.101.195.5
AAAA2a04:4e42:200::773, 2a04:4e42::773, 2a04:4e42:400::773, 2a04:4e42:600::773
CNAMEcnn-tls.map.fastly.net
NS
MX
TXT
CAALookup not available with standard resolver
Resolved in 24 ms

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

B
TLS Certificate Expiry & Recommendations
87 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

87
days left
0d 30d 60d 90d+

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable DNSSEC on your domain for DNS spoofing protection
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A
Redirect Chain
1 redirect(s), 29 ms total
PASS
1 redirect(s), 29 ms total
Info::
Single redirect
Got: https://www.cnn.com → https://edition.cnn.com/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://www.cnn.com
Info::
Cross-domain redirect detected

https://www.cnn.com

6 ms · HTTP/1.1

302

https://edition.cnn.com/

23 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.cnn.com3026 msHTTP/1.1
2https://edition.cnn.com/20023 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

A+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2a04:4e42:200::773, 2a04:4e42::773, 2a04:4e42:400::773, 2a04:4e42:600::773
Got: 1 ms connect
IPv6 Ready
AAAA Records 2a04:4e42:200::773, 2a04:4e42::773, 2a04:4e42:400::773, 2a04:4e42:600::773 Connection Reachable (1 ms)
A+
Crawlability
robots.txt present, sitemap with 191 URLs
PASS
robots.txt present, sitemap with 191 URLs
Info::
robots.txt is present
Got: 3214 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 191 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 3214 B Sitemaps referenced 15 User-agents PerplexityBot, amzn-user, Brightbot 1.0, Claude-SearchBot, cohere-ai, news-please, omgilibot, QuillBot, AI2Bot, Applebot-Extended, Crawlspace, ISSCyberRiskCrawler, omgili, PetalBot, AwarioSmartBot, Google-Extended, iaskspider/2.0, SemrushBot-SWA, ChatGPT-User, Claude-Web, PiplBot, SBIntuitionsBot, AwarioRssBot, CCBot, Diffbot, quillbot.com, anthropic-ai, YandexAdditional, *, amzn-searchbot, cohere-training-data-crawler, GoogleOther, Perplexity-User, Timpibot, DataForSeoBot, EchoboxBot, FacebookBot, NewsNow, Sidetrade indexer bot, Amazonbot, Kangaroo Bot, Panscient, Scrapy, Ai2Bot-Dolma, GoogleOther-Video, PanguBot, FriendlyCrawler, img2dataset, OAI-SearchBot, SemrushBot-OCOB, GPTBot, GoogleOther-Image, ICC-Crawler, magpie-crawler, VelenPublicWebCrawler, Webzio-Extended, YouBot, Bytespider, ClaudeBot, YandexAdditionalBot, DuckAssistBot, ImagesiftBot, TurnitinBot, Googlebot-News Blocking No — crawling allowed
Sitemap: https://www.cnn.com/sitemap/news.xml
Sitemap: https://www.cnn.com/sitemaps/sitemap-section.xml
Sitemap: https://www.cnn.com/sitemaps/sitemap-interactive.xml
Sitemap: https://www.cnn.com/sitemap/article/cnn-underscored.xml
Sitemap: https://www.cnn.com/sitemap/section/cnn-underscored.xml
Sitemap: https://www.cnn.com/sitemap/section/politics.xml
Sitemap: https://www.cnn.com/sitemap/article/opinions.xml
Sitemap: https://www.cnn.com/sitemap/article.xml
Sitemap: https://www.cnn.com/sitemap/section.xml
Sitemap: https://www.cnn.com/sitemap/video.xml
Sitemap: https://www.cnn.com/sitemap/gallery.xml
Sitemap: https://www.cnn.com/sitemap/markets/stocks.xml
Sitemap: https://www.cnn.com/sitemap/live-story.xml
Sitemap: https://www.cnn.com/sitemap/election-center/politics.xml
Sitemap: https://www.cnn.com/sitemap/tve.xml
User-agent: AI2Bot
User-agent: Ai2Bot-Dolma
User-agent: Amazonbot
User-agent: amzn-searchbot
User-agent: amzn-user
User-agent: anthropic-ai
User-agent: Applebot-Extended
User-agent: AwarioRssBot
User-agent: AwarioSmartBot
User-agent: Brightbot 1.0
User-agent: Bytespider
User-agent: CCBot
User-agent: ChatGPT-User
User-agent: ClaudeBot
User-agent: Claude-SearchBot
User-agent: Claude-Web
User-agent: cohere-ai
User-agent: cohere-training-data-crawler
User-agent: Crawlspace
User-agent: DataForSeoBot
User-agent: Diffbot
User-agent: DuckAssistBot
User-agent: EchoboxBot
User-agent: FacebookBot
User-agent: FriendlyCrawler
User-agent: GPTBot
User-agent: Google-Extended
User-agent: GoogleOther
User-agent: GoogleOther-Image
User-agent: GoogleOther-Video
User-agent: iaskspider/2.0
User-agent: ICC-Crawler
User-agent: img2dataset
User-agent: ISSCyberRiskCrawler
User-agent: ImagesiftBot
User-agent: Kangaroo Bot
User-agent: magpie-crawler
User-agent: NewsNow
User-agent: news-please
User-agent: OAI-SearchBot
User-agent: omgili
User-agent: omgilibot
User-agent: PanguBot
User-agent: Panscient
User-agent: PiplBot
User-agent: PerplexityBot
User-agent: Perplexity-User
User-agent: PetalBot
User-agent: QuillBot
User-agent: quillbot.com
User-agent: SBIntuitionsBot
User-agent: Scrapy
User-agent: SemrushBot-OCOB
User-agent: SemrushBot-SWA
User-agent: Sidetrade indexer bot
User-agent: Timpibot
User-agent: TurnitinBot
User-agent: VelenPublicWebCrawler
User-agent: Webzio-Extended
User-agent: YandexAdditional
User-agent: YandexAdditionalBot
User-agent: YouBot
Disallow: /
User-agent: *
Allow: /partners/ipad/live-video.json
Disallow: /*.jsx$
Disallow: *.jsx$
Disallow: /*.jsx/
Disallow: *.jsx?
Disallow: /ads/
Disallow: /aol/
Disallow: /api/
Disallow: /beta/
Disallow: /browsers/
Disallow: /cl/
Disallow: /cnews/
Disallow: /cnn_adspaces
Disallow: /cnnbeta/
Disallow: /cnnintl_adspaces
Disallow: /development
Disallow: /editionssi
Disallow: /help/cnnx.html
Disallow: /NewsPass
Disallow: /NOKIA
Disallow: /partners/
Disallow: /pipeline/
Disallow: /pointroll/
Disallow: /POLLSERVER/
Disallow: /pr/
Disallow: /PV/
Disallow: /Quickcast/
Disallow: /quickcast/
Disallow: /QUICKNEWS/
Disallow: /search
Disallow: /subscriptions/video-docs
Disallow: /terms
Disallow: /test/
Disallow: /virtual/
Disallow: /WEB-INF/
Disallow: /web.projects/
Disallow: /webview/
User-agent: Googlebot-News
Disallow: /sponsor

A
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: www)
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

200https://www.cnn.com/
301https://cnn.com/

Preferred variant: www

HTTP → HTTPS

302http://www.cnn.com/ https://edition.cnn.com/

Use 301 (permanent) instead of 302 (temporary)

A+
Domain Intelligence
cnn.com — via Nom-iq Ltd. dba COM LAUDE, 33 years old
PASS
cnn.com — via Nom-iq Ltd. dba COM LAUDE, 33 years old
Info::
Domain registered until Sep 21, 2027 (1 years, 5 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: Nom-iq Ltd. dba COM LAUDE
Domain expiry

435 days

September 21, 2027

SSL certificate

87 days

Issued by GlobalSign nv-sa

Domain age

33 years

Registered September 22, 1993

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2a04:4e42:400::773

Registrar

Nom-iq Ltd. dba COM LAUDE

Lock status unknown 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
Registrar Nom-iq Ltd. dba COM LAUDE
Created September 22, 1993 (33 years ago)
Expires September 21, 2027 (1 years, 5 months)
Last Updated April 22, 2025
Name Servers ns-1242.awsdns-27.org, ns-1652.awsdns-14.co.uk, ns-378.awsdns-47.com, ns-587.awsdns-09.net
DNSSEC Not enabled
Hosting
IP Address 2a04:4e42:400::773
Data source: rdap (0.2s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

A+
HTTP Probe Timing
Total 27 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
22 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
0 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
3 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
27 ms
Total Time Total request time from DNS lookup through full response.
28 ms

Connection waterfall

DNS Lookup 22 ms TCP Connect 0 ms TLS Handshake 3 ms Server Processing 2 ms Content Transfer 0 ms
A+
CDN & Delivery
Fastly (HIT)
PASS
Fastly (HIT)
Info::
Site is served via Fastly CDN
Got: x-served-by: cache-toj-leto2350040-TOJ
Info::
CDN cache status: HIT
CDN Detected: Fastly
Provider Fastly Cache Status HIT Evidence x-served-by: cache-toj-leto2350040-TOJ
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback