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

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
1
REVIEW
9
PASS
7
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
17
7 PASS 9 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
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
B
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
B
Reverse DNS
0/2 IPs match cert SAN
REVIEW
0/2 IPs match cert SAN
Info::
PTR for 200.147.35.149 does not match any cert SAN: 200-147-35-149-149.static.uol.com.br
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR lookup failed for 2804:49c:3102:401:ffff:ffff:ffff:36: lookup 2804:49c:3102:401:ffff:ffff:ffff:36: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
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.uol.com.br/
200https://uol.com.br/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://uol.com.br/ https://www.uol.com.br/

Consistent

B
HTTP Probe Timing
Total 932 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
29 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
225 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
453 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
932 ms
Total Time Total request time from DNS lookup through full response.
932 ms

Connection waterfall

DNS Lookup 29 ms TCP Connect 225 ms TLS Handshake 453 ms Server Processing 225 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
288 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

288
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
B
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
No CDN cache-status headers in the response
Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.
A+
DNS Records
1 A records, 185 ms lookup
PASS
1 A records, 185 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 200.147.35.149
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2804:49c:3102:401:ffff:ffff:ffff:36
Info::
3 nameserver(s) configured
Got: borges.uol.com.br, charles.uol.com.br, eliot.uol.com.br
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 185 ms
Got: 185 ms
A200.147.35.149
AAAA2804:49c:3102:401:ffff:ffff:ffff:36
CNAME
NSborges.uol.com.br, charles.uol.com.br, eliot.uol.com.br
MX
10 mx.uol.com.br
TXT
_a3xwwbow0izh24kero6i0yf7s1dd0wu
ct2ns2rvjpch04sh4k9f9l301mrm4sxn
SPF v=spf1 include:spf.uol.com.br include:spfexcl.uol.com.br include:relays.uol.com....
_83pxpdpwjalno6229vnvuiphgnwl0t8
DZC=qvK68EJ
ga6XpdhCRgwFYAxnac1hCt-ZE89FRXAQOt0d0nYuUl9HbucC7pT_626yWrg
_akamai-host-challenge.dex.eks.stg.robinson.service.uol.com.br.TXTga6XpdhCRgwFYA...
_8esp8bv05hm317pw8anflp8qihsth30
_icf9558lsj647ovf9awfysrn20b04ae
_akamai-host-challenge.dex.eks.stg.robinson.service.uol.com.br
_d8uyauhlmikic4bbglmqux1fg7fe6pt
_k1t6hq44koqbgzu2b1og3c96qpgx4js
v2xbmyjp43k50d3539mlpp0h8c9ff03t
CAALookup not available with standard resolver
Resolved in 185 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+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Multi-Resolver DNS Speed
Mean 15ms across 3 resolvers (spread 26ms)
PASS
Mean 15ms across 3 resolvers (spread 26ms)
Info::
Quad9: 1ms
Got: 1ms via 9.9.9.9:53
Info::
Cloudflare: 17ms
Got: 17ms via 1.1.1.1:53
Info::
Google: 27ms
Got: 27ms via 8.8.8.8:53
A
Redirect Chain
1 redirect(s), 983 ms total
PASS
1 redirect(s), 983 ms total
Info::
Single redirect
Got: https://uol.com.br → https://www.uol.com.br/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 983 ms total
Got: 983 ms

https://uol.com.br

927 ms · HTTP/1.0

301

https://www.uol.com.br/

56 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://uol.com.br301927 msHTTP/1.0BigIP
2https://www.uol.com.br/20056 msHTTP/1.1marrakesh 1.25.0

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (227 ms)
PASS
IPv6 reachable (227 ms)
Info::
IPv6 is configured and reachable at 2804:49c:3102:401:ffff:ffff:ffff:36
Got: 227 ms connect
IPv6 Ready
AAAA Records 2804:49c:3102:401:ffff:ffff:ffff:36 Connection Reachable (227 ms)
A+
Crawlability
robots.txt present, sitemap with 4 URLs
PASS
robots.txt present, sitemap with 4 URLs
Info::
robots.txt is present
Got: 2470 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 4 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 2470 B Sitemaps referenced 9 User-agents Kangaroo Bot, NovaAct, PetalBot, FacebookBot, Amazonbot, MistralAI-User, SemrushBot-OCOB, Timpibot, Webzio-Extended, YouBot, Google-Extended, AwarioSmartBot, Claude-Web, DataForSeoBot, DuckAssistBot, Factset_spyderbot, Claude-User, Applebot, Cohere-ai, Meta-ExternalAgent, Meta-ExternalFetcher, Operator, Perplexity-User, PerplexityBot, Applebot-Extended, DeepSeek, Qwen, Cotoyogi, Devin, Gemini-Deep-Research, *, AI2Bot, AwarioRssBot, Bytespider, CCBot, Claude-SearchBot, ClaudeBot, ImagesiftBot, netEstate Imprint Crawler, omgili, Omgilibot, PanguBot, Peer39_crawler/1.0, GoogleAgent-Mariner, Twitterbot, Anthropic-ai, cohere-training-data-crawler, Datenbank Crawler, Diffbot, ICC-Crawler Blocking No — crawling allowed
# robots.txt
#
User-agent: *
Sitemap: https://www.uol.com.br/carros/sitemap/v2/news-01.xml
Sitemap: https://www.uol.com.br/ecoa/sitemap/news-01.xml
Sitemap: https://www.uol.com.br/esporte/sitemap/v2/news-01.xml
Sitemap: https://www.uol.com.br/nossa/sitemap/news-01.xml
Sitemap: https://www.uol.com.br/splash/sitemap/news-01.xml
Sitemap: https://www.uol.com.br/tilt/sitemap/news-01.xml
Sitemap: https://www.uol.com.br/universa/sitemap/v2/news-01.xml
Sitemap: https://www.uol.com.br/vivabem/sitemap/v2/news-01.xml
Sitemap: https://c.jsuol.com.br/assets/jupiter-news/?resource-id=sitemap&source=toca/index.xml
Allow: /
Disallow: /carros/dev/
User-agent: Google-Extended
Disallow: /
Allow: /.ghtm$
User-agent: AI2Bot
Disallow: /
User-agent: Amazonbot
Disallow: /
User-agent: Anthropic-ai
Disallow: /
User-agent: Applebot
Disallow: /
User-agent: Applebot-Extended
Disallow: /
User-agent: AwarioRssBot
Disallow: /
User-agent: AwarioSmartBot
Disallow: /
User-agent: Bytespider
Disallow: /
User-agent: CCBot
Disallow: /
User-agent: Claude-SearchBot
Disallow: /
User-agent: Claude-User
Disallow: /
User-agent: Claude-Web
Disallow: /
User-agent: ClaudeBot
Disallow: /
User-agent: Cohere-ai
Disallow: /
User-agent: cohere-training-data-crawler
Disallow: /
User-agent: Cotoyogi
Disallow: /
User-agent: DataForSeoBot
Disallow: /
User-agent: Datenbank Crawler
Disallow: /
User-agent: DeepSeek
Disallow: /
User-agent: Devin
Disallow: /
User-agent: Diffbot
Disallow: /
User-agent: DuckAssistBot
Disallow: /
User-agent: FacebookBot
Disallow: /
User-agent: Factset_spyderbot
Disallow: /
User-agent: Gemini-Deep-Research
Disallow: /
User-agent: GoogleAgent-Mariner
Disallow: /
User-agent: ICC-Crawler
Disallow: /
User-agent: ImagesiftBot
Disallow: /
User-agent: Kangaroo Bot
Disallow: /
User-agent: Meta-ExternalAgent
Disallow: /
User-agent: Meta-ExternalFetcher
Disallow: /
User-agent: MistralAI-User
Disallow: /
User-agent: netEstate Imprint Crawler
Disallow: /
User-agent: NovaAct
Disallow: /
User-agent: omgili
Disallow: /
User-agent: Omgilibot
Disallow: /
User-agent: Operator
Disallow: /
User-agent: PanguBot
Disallow: /
User-agent: Peer39_crawler/1.0
Disallow: /
User-agent: Perplexity-User
Disallow: /
User-agent: PerplexityBot
Disallow: /
User-agent: PetalBot
Disallow: /
User-agent: Qwen
Disallow: /
User-agent: SemrushBot-OCOB
Disallow: /
User-agent: Timpibot
Disallow: /
User-agent: Twitterbot
Disallow: /
User-agent: Webzio-Extended
Disallow: /
User-agent: YouBot
Disallow: /

A+
Domain Intelligence
uol.com.br — 30 years, 6 months old
PASS
uol.com.br — 30 years, 6 months old
Info::
Domain registered until Apr 24, 2034 (8 years 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.
Domain expiry

2889 days

April 24, 2034

SSL certificate

288 days

Issued by DigiCert Inc

Domain age

30 years, 6 months

Registered April 24, 1996

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2804:49c:3102:401:ffff:ffff:ffff:36

Registrar

Registrar unknown

Unlocked 3 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 April 24, 1996 (30 years, 6 months ago)
Expires April 24, 2034 (8 years)
Last Updated August 27, 2024
Name Servers eliot.uol.com.br, borges.uol.com.br, charles.uol.com.br
DNSSEC Not enabled
Registrant Universo Online S.A.
Hosting
IP Address 2804:49c:3102:401:ffff:ffff:ffff:36
Data source: rdap (0.9s)

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