Skip to content
https://uba.ar

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
2
REVIEW
3
PASS
4
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
4 PASS 3 REVIEW 2 FIX
F
HTTP Probe Timing
Action
Total 12452 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
FIX
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
1 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
257 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
518 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
12.45 s
Total Time Total request time from DNS lookup through full response.
12.45 s

Connection waterfall

DNS Lookup 1 ms TCP Connect 257 ms TLS Handshake 518 ms Server Processing 11.68 s Content Transfer 0 ms
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.

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
Crawlability
Action
no robots.txt, sitemap with 0 URLs
REVIEW
no robots.txt, sitemap with 0 URLs
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
sitemap.xml is present
Warning::
sitemap.xml contains invalid XML
Search engines may not be able to parse the sitemap. Fix XML validation errors.
Warning::
sitemap.xml is empty — no URLs found
An empty sitemap provides no value. Add <url> entries for your pages.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more ▾

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

Search engines may not be able to parse the sitemap. Fix XML validation errors.

Why this matters

An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.

Learn more ▾

Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.

Source: sitemaps.org / Google Search Central

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more ▾

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML No
B
TLS Certificate Expiry & Recommendations
77 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

77
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+
DNS Records
1 A records, 43 ms lookup
PASS
1 A records, 43 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 157.92.5.15
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
6 nameserver(s) configured
Got: ns2.uba.ar, ns1.uba.ar, dns34.cloudns.net, dns32.cloudns.net, dns33.cloudns.net, dns31.cloudns.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: 43 ms
Got: 43 ms
A157.92.5.15
AAAA—
CNAME—
NSns2.uba.ar, ns1.uba.ar, dns34.cloudns.net, dns32.cloudns.net, dns33.cloudns.net, dns31.cloudns.net
MX
0 uba-ar.mail.protection.outlook.com
TXT
domain_verification.h=MAih
autodesk-domain-verification=WGWSWDDGeDiDIUPZrlDz
cisco-ci-domain-verification=13001c6eb47e5e86f3d4e5bfdddedbcb2d9077fd2bef584e148...
SPF v=spf1 redirect=_spf.uba.ar
CAALookup not available with standard resolver
Resolved in 43 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 redirect data available
PASS
No redirect data available
Info::
No redirect data captured
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.uba.ar/
200https://uba.ar/

HTTP → HTTPS

301http://uba.ar/ → https://www.uba.ar/

Consistent

A+
Domain Intelligence
uba.ar — via nicar, 9 years, 7 months old, hosted on Universidad Nacional de Buenos Aires, AR
PASS
uba.ar — via nicar, 9 years, 7 months old, hosted on Universidad Nacional de Buenos Aires, AR
Info::
Domain registered until Mar 3, 2027 (10 months remaining)
Info::
Registrar: nicar
Info::
Hosting: Universidad Nacional de Buenos Aires, AR
Got: AS3449
Domain expiry

262 days

March 3, 2027

SSL certificate

77 days

Issued by Let's Encrypt

Domain age

9 years, 7 months

Registered November 8, 2016

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Universidad Nacional de Buenos Aires, AR

ASN AS3449

157.92.5.15

Registrar

nicar

Lock status unknown 9 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar nicar
Created November 8, 2016 (9 years, 7 months ago)
Expires March 3, 2027 (10 months)
Last Updated March 2, 2026
Name Servers dns32.cloudns.net, ns3.uba.ar, dns31.cloudns.net, dns34.cloudns.net, ns1.uba.ar, 157.92.1.1/32), dns33.cloudns.net, ns2.uba.ar, 157.92.4.1/32)
Registrant 30546666561
Hosting
IP Address 157.92.5.15
ASN AS3449 (Universidad Nacional de Buenos Aires, AR)
Provider Universidad Nacional de Buenos Aires, AR
Data source: whois (3.8s)
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback