Skip to content
https://cnnbrasil.com.br

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
80
GRADE
B
FIX
1
REVIEW
5
PASS
3
INFO
0
Probed from Madrid, Spain
307 Temporary Redirect
Checks
9
3 PASS 5 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

B
Redirect Chain
1 redirect(s), 1928 ms total
REVIEW
1 redirect(s), 1928 ms total
Info::
Single redirect
Got: https://cnnbrasil.com.br → https://www.cnnbrasil.com.br (307)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1928 ms total
Got: 1928 ms

https://cnnbrasil.com.br

6 ms · HTTP/1.1

307

https://www.cnnbrasil.com.br

1922 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://cnnbrasil.com.br3076 msHTTP/1.1nginx
2https://www.cnnbrasil.com.br2001922 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 759 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 759 B Sitemaps referenced 0 User-agents AmazonAdBot, * Blocking No — crawling allowed
# Robots.txt

User-Agent: *

Disallow: /wp-admin/
Disallow: /wp-json/
Disallow: /wp-includes/
Disallow: /_next/

Allow: /_next/static/

Disallow: /partners_sdk/
Disallow: /component/
Disallow: /obrigado-newsletter-business
Disallow: /youtube/video
Disallow: /migrate-all-posts/
Disallow: /author/

Disallow: /*?s=
Disallow: /*?p=
Disallow: /*?search=
Disallow: /*?orderby=
Disallow: /*?order=
Disallow: /*?post_type=
Disallow: /*?hidemenu=true

User-agent: AmazonAdBot
Allow: /

Disallow: /esportes/agenda/2027
Disallow: /esportes/agenda/2028
Disallow: /esportes/agenda/2029
Disallow: /esportes/agenda/2030
Disallow: /esportes/agenda/2031
Disallow: /esportes/agenda/203
Disallow: /esportes/agenda/204
Disallow: /esportes/agenda/205

# Atualizado em 15/04/2026
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.cnnbrasil.com.br/
200https://cnnbrasil.com.br/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://cnnbrasil.com.br/ https://cnnbrasil.com.br/

Consistent

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

Certificate validity

66
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+
DNS Records
1 A records, 59 ms lookup
PASS
1 A records, 59 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 192.0.66.182
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns1-08.azure-dns.com, ns4-08.azure-dns.info, ns3-08.azure-dns.org, ns2-08.azure-dns.net
Info::
1 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 59 ms
Got: 59 ms
A192.0.66.182
AAAA
CNAME
NSns1-08.azure-dns.com, ns4-08.azure-dns.info, ns3-08.azure-dns.org, ns2-08.azure-dns.net
MX
0 cnnbrasil-com-br.mail.protection.outlook.com
TXT
SPF v=spf1 include:spf.protection.outlook.com include:_spf.rdstation.com.br include:...
google-site-verification=-Ehs7R3_jx32weSXELXsFkkKM8xCv65LahvggbbopqA
cisco-ci-domain-verification=b1fb8a4d3a5999a93ccb3d020ff5a57d4b42d628703760ad19a...
google-site-verification=rSNWUo4HZ4z6DRx61_qMWf4P4G9rGByGOkqb-IaYFFA
7b9o0btvp97han9r81jerlf67n
jpginll8ivtknca51qh7770jvp
MS=ms36243824
google-site-verification=qg69836k7A1UKYnnkEo_efNO3dj-5zFeKwFahwC1zPc
SPF v=spf1 include:_spf.rdstation.com.brinclude:sendgrid.net ~all
apple-domain-verification=5DNPlWRxAQp8KTiU
3i8epk6j346a82shd7gkqjj71l
8itkn7vr6it8do4c174poc7bgn
sjj5imi3telj1dh5jlfl6u6pio
CAALookup not available with standard resolver
Resolved in 59 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

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.

A+
Domain Intelligence
cnnbrasil.com.br — 23 years, 11 months old, hosted on WordPress.com (Automattic)
PASS
cnnbrasil.com.br — 23 years, 11 months old, hosted on WordPress.com (Automattic)
Info::
Domain registered until Sep 20, 2026 (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.
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Info::
Hosting: WordPress.com (Automattic)
Got: AS2635
Domain expiry

97 days

September 20, 2026

SSL certificate

66 days

Issued by Let's Encrypt

Domain age

23 years, 11 months

Registered September 20, 2002

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

WordPress.com (Automattic)

ASN AS2635

192.0.66.182

Registrar

Registrar unknown

Unlocked 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
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar
Created September 20, 2002 (23 years, 11 months ago)
Expires September 20, 2026 (5 months)
Last Updated August 19, 2025
Name Servers ns1-08.azure-dns.com, ns2-08.azure-dns.net, ns3-08.azure-dns.org, ns4-08.azure-dns.info
DNSSEC Not enabled
Registrant TopSports Ventures LTDA
Hosting
IP Address 192.0.66.182
ASN AS2635 (AUTOMATTIC - Automattic, Inc, US)
Provider WordPress.com (Automattic)
Data source: rdap (1.0s)

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

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

A+
HTTP Probe Timing
Total 204 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
55 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.
204 ms
Total Time Total request time from DNS lookup through full response.
204 ms

Connection waterfall

DNS Lookup 55 ms TCP Connect 0 ms TLS Handshake 3 ms Server Processing 146 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback