Skip to content
https://uchile.cl

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
0
REVIEW
4
PASS
4
INFO
1
Probed from Amsterdam, Netherlands
200 OK
Checks
9
4 PASS 4 REVIEW
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: 163 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 163 B Sitemaps referenced 0 User-agents *, Googlebot Blocking No — crawling allowed
User-agent: *
Allow: /
Disallow: /noticias/archivo
Disallow: /audios/archivo
Disallow: /fotos/archivo
Disallow: /multimedia/archivo

User-agent: Googlebot
Allow: /
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Connection waterfall

DNS Lookup 193 ms TCP Connect 210 ms TLS Handshake 216 ms Server Processing 211 ms Content Transfer 210 ms
B
TLS Certificate Expiry & Recommendations
198 days until leaf cert expires — 5 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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, 197 ms lookup
PASS
1 A records, 197 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 200.89.76.36
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: ns4.uchile.cl, ns1.uchile.cl, ns2.uchile.cl, ns5.uchile.cl
Info::
5 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: 197 ms
Got: 197 ms
A200.89.76.36
AAAA—
CNAME—
NSns4.uchile.cl, ns1.uchile.cl, ns2.uchile.cl, ns5.uchile.cl
MX
1 ASPMX.L.GOOGLE.COM
5 ALT1.ASPMX.L.GOOGLE.COM
5 ALT2.ASPMX.L.GOOGLE.COM
10 ALT4.ASPMX.L.GOOGLE.COM
10 ALT3.ASPMX.L.GOOGLE.COM
TXT
google-site-verification=xMbs9Oicr99G7exi2v2TbzhQaxJk5zO516XhCH2u_GI
ZOOM_verify_vZ6Y--SrQuGADrn4ig1OAw
SPF v=spf1 include:_spf.google.com include:_spf.embluemail.com include:_spf.uchile.c...
abuseipdb-verification=hJLbm9dN
MS=ms11688190
adobe-idp-site-verification=777800ea652496dce8a28235004545673ce096b3d597671677e0...
google-site-verification=Imj5oc9610W4NzSSggF-oi2aStOUo3HGQVLzCk9A8Mc
google-site-verification=4_P-kIVweatFgfMCsPdlM1CjAdD0_weMiTvSp3HM0g0
brevo-code:d5040ab1ccd6bfdbf0791b1627cc946c
CAALookup not available with standard resolver
Resolved in 197 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+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://uchile.cl

https://uchile.cl

827 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://uchile.cl200827 msHTTP/1.1nginx
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: non-www)
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

302https://www.uchile.cl/
200https://uchile.cl/

Preferred variant: non-www

HTTP → HTTPS

302http://uchile.cl/ → https://uchile.cl/

Use 301 (permanent) instead of 302 (temporary)

A+
CDN & Delivery
Varnish (HIT)
PASS
Varnish (HIT)
Info::
Site is served via Varnish CDN
Got: via: 1.1 varnish (Varnish/6.6)
Info::
CDN cache status: HIT
CDN Detected: Varnish
Provider Varnish Cache Status HIT Evidence via: 1.1 varnish (Varnish/6.6)
Domain Intelligence
Domain intelligence data not available
INFO
Domain intelligence data not available

RDAP and WHOIS lookup both failed

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

Send Feedback