Skip to content
https://g1.globo.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
89
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
4 PASS 4 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
DNS Records
1 A records, 25 ms lookup
REVIEW
1 A records, 25 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 168.75.98.245
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
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: g1.cache.gcp.cloud.globo
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: 25 ms
Got: 25 ms
A168.75.98.245
AAAA—
CNAMEg1.cache.gcp.cloud.globo
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 25 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

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)

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

C
HTTP Probe Timing
Action
Total 1729 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
239 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
212 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
428 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.30 s
Total Time Total request time from DNS lookup through full response.
1.73 s

Connection waterfall

DNS Lookup 239 ms TCP Connect 212 ms TLS Handshake 428 ms Server Processing 426 ms Content Transfer 425 ms
B
TLS Certificate Expiry & Recommendations
82 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • 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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://g1.globo.com

https://g1.globo.com

860 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://g1.globo.com200860 msHTTP/1.1
A+
Crawlability
robots.txt present, sitemap with 8938 URLs
PASS
robots.txt present, sitemap with 8938 URLs
Info::
robots.txt is present
Got: 608 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 8938 entries
Info::
Sitemap index with 8938 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 608 B Sitemaps referenced 3 User-agents * Blocking No — crawling allowed
User-Agent: *
Disallow: /jornalismo/g1/
Disallow: /_ssi/
Disallow: /teste-*.html$
Disallow: /beta/
Disallow: /componentes/
Disallow: /busca/*
Disallow: /globo-news/jornal-globo-news/videos/v/globo-news-ao-vivo/61910/
Disallow: /globonews/playlist/globonews-ao-vivo.ghtml
Disallow: *globo-cdn-src/*
Disallow: /zeta/
Disallow: /content-aggregator/
Disallow: /jogos-app/
Disallow: /espiar/
Disallow: /especiais-publicitarios/*/check/
Sitemap: https://g1.globo.com/sitemap/g1/sitemap.xml
Sitemap: https://g1.globo.com/sitemap/Apuração/g1/sitemap.xml
Sitemap: https://g1.globo.com/sitemap/videos/g1/sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 8938 entries Valid XML Yes
Child Sitemaps:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

https://www.g1.globo.com/
200https://g1.globo.com/

HTTP → HTTPS

301http://g1.globo.com/ → https://g1.globo.com/

Consistent

A+
Domain Intelligence
globo.com — via 1API GmbH, 27 years, 8 months old, hosted on Globo Comunicacao e Participacoes SA, BR
PASS
globo.com — via 1API GmbH, 27 years, 8 months old, hosted on Globo Comunicacao e Participacoes SA, BR
Info::
Domain registered until Dec 21, 2026 (8 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: 1API GmbH
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: Globo Comunicacao e Participacoes SA, BR
Got: AS28604
Domain expiry

161 days

December 21, 2026

SSL certificate

82 days

Issued by DigiCert Inc

Domain age

27 years, 8 months

Registered December 21, 1998

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Globo Comunicacao e Participacoes SA, BR

ASN AS28604

186.192.83.12

Registrar

1API GmbH

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 1API GmbH
Created December 21, 1998 (27 years, 8 months ago)
Expires December 21, 2026 (8 months)
Last Updated December 22, 2025
Name Servers ns01.globo.com, ns02.globo.com, ns03.globo.com, ns04.globo.com
DNSSEC Not enabled
Hosting
IP Address 186.192.83.12
ASN AS28604 (Globo Comunicacao e Participacoes SA, BR)
Provider Globo Comunicacao e Participacoes SA, BR
Data source: rdap (0.5s)

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback