Skip to content
https://ub.edu

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 3 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.

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: 740 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 740 B Sitemaps referenced 0 User-agents PetalBot, *, TurnitinBot Blocking No — crawling allowed
User-agent: PetalBot
Disallow: /blokdebid/

User-agent: *
Disallow: /dyn/cms/pdf/
Disallow: /dyn/cms/system/
Disallow: /dyn/cms/continguts_ca/menu_eines/web_multimedia/
Disallow: /dyn/cms/continguts_es/menu_eines/web_multimedia/
Disallow: /dyn/cms/continguts_en/menu_eines/web_multimedia/
disallow: /dyn/cms/continguts_ca/altres/muno/
disallow: /dyn/cms/continguts_es/altres/muno/
disallow: /dyn/cms/continguts_en/altres/muno/
Disallow: /web/ub/ca/nodisponible.html
Disallow: /portal/documents/1051544/*?version=
Disallow: /ceremet/?page_id=
# Disallow: /blokdebid/ca/calendar-created/
# Disallow: /blokdebid/es/calendar-created/
# Disallow: /blokdebid/calendar-created/
# 12/04/23: Block Turnitin Robot 
User-agent: TurnitinBot
Disallow: /
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Certificate validity

206
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, 61 ms lookup
PASS
1 A records, 61 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 161.116.109.141
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: sbx06.ub.edu, chico.rediris.es, sun.rediris.es, sbx05.ub.edu
Info::
2 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: 61 ms
Got: 61 ms
A161.116.109.141
AAAA—
CNAME—
NSsbx06.ub.edu, chico.rediris.es, sun.rediris.es, sbx05.ub.edu
MX
10 mxb-006a4e02.gslb.pphosted.com
10 mxa-006a4e02.gslb.pphosted.com
TXT
e8d36IiIDiC/MrV/UjERL0YEQPtoxtC3bvqNyBQ/LV6WvDZ5k/ingiKvB3/Agung3PHLYIgIl0vH/8hl...
valor: 00D250000009W1i=1TBVc00000001aQ
google-site-verification=iTis1BGTC7IKaaaaAcIxRgRoehQEGzql0AEUFvoCrt0
apple-domain-verification=rwiXHJo9tcZiGsgb
adobe-idp-site-verification=e51fff9392be0d21407a44ff546272df7c8ce00d985cd415e7fb...
facebook-domain-verification=f8lgpr25ok2rugzpwo9sficgjyrlwb
MS=ms92893191
valor: 00D68000000Xqo3=1TBTY00000004TR
SPF v=spf1 ip4:161.116.234.11 ip4:161.116.234.12 ip4:161.116.234.17 ip4:161.116.234....
CAALookup not available with standard resolver
Resolved in 61 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
1 redirect(s), 221 ms total
PASS
1 redirect(s), 221 ms total
Info::
Single redirect
Got: https://ub.edu → https://web.ub.edu/web/ub/ (301)
Info::
Cross-domain redirect detected

https://ub.edu

48 ms · HTTP/1.1

301

https://web.ub.edu/web/ub/

173 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://ub.edu30148 msHTTP/1.1
2https://web.ub.edu/web/ub/200173 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

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)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.ub.edu/
200https://ub.edu/

Preferred variant: non-www

HTTP → HTTPS

301http://ub.edu/ → https://web.ub.edu/web/ub/

Consistent

A+
Domain Intelligence
ub.edu — 28 years, 4 months old, hosted on CESCA-AC, ES
PASS
ub.edu — 28 years, 4 months old, hosted on CESCA-AC, ES
Info::
Domain registered until Jul 31, 2027 (1 years, 3 months remaining)
Info::
Hosting: CESCA-AC, ES
Got: AS13041
Domain expiry

412 days

July 31, 2027

SSL certificate

206 days

Issued by Hellenic Academic and Research Institutions CA

Domain age

28 years, 4 months

Registered May 8, 1998

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

CESCA-AC, ES

ASN AS13041

161.116.109.141

Registrar

Registrar unknown

Lock status unknown 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar
Created May 8, 1998 (28 years, 4 months ago)
Expires July 31, 2027 (1 years, 3 months)
Last Updated October 29, 2025
Name Servers sbx05.ub.edu, chico.rediris.es, sun.rediris.es, sbx06.ub.edu
Registrant Universitat de Barcelona
Hosting
IP Address 161.116.109.141
ASN AS13041 (CESCA-AC, ES)
Provider CESCA-AC, ES
Data source: whois (1.0s)
A+
HTTP Probe Timing
Total 81 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
33 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
11 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
27 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
82 ms
Total Time Total request time from DNS lookup through full response.
82 ms

Connection waterfall

DNS Lookup 33 ms TCP Connect 11 ms TLS Handshake 27 ms Server Processing 11 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