Infrastructure - https://unibo.it BeaverCheck Audit

D

Redirect Chain

Action

2 redirect(s), 1813 ms total

FIX

2 redirect(s), 1813 ms total

2 redirects before reaching final URL

Each redirect adds latency. Try to minimize the chain to 1 hop.

WWW normalization redirect

Redirect overhead: 1813 ms total

Got: 1813 ms

https://unibo.it

806 ms · HTTP/1.1

301

https://www.unibo.it/

688 ms · HTTP/1.1

301

https://www.unibo.it/it

319 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://unibo.it	301	806 ms	HTTP/1.1	nginx
2	https://www.unibo.it/	301	688 ms	HTTP/1.1	nginx
3	https://www.unibo.it/it	200	319 ms	HTTP/1.1	nginx

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

D

CDN & Delivery

Action

No CDN detected

FIX

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

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, sitemap with 0 URLs

REVIEW

robots.txt present, sitemap with 0 URLs

robots.txt is present

Got: 613 bytes

sitemap.xml is present

sitemap.xml contains invalid XML

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

sitemap.xml is empty — no URLs found

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

robots.txt references sitemap

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 200 OK

Size 613 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed

Sitemap: https://www.unibo.it/sitemap.xml.gz

User-agent: *
Disallow: /NR/exeres
Disallow: /NR/rdonlyres
Disallow: /it/allegati/allegati-non-indicizzati
Disallow: /en/attachments/unindexed-attachments
Disallow: /modello
Disallow: /modello-a
Disallow: /modello-b
Disallow: /uniboweb/sites/UniboSearch/results.aspx
Disallow: /UniboWeb/sites/UniboSearch/results.aspx
Disallow: /UniboWeb/UniboSearch/results.aspx
Disallow: /_layouts
Disallow: /avl/charta
Disallow: /bollettino
Disallow: /it/pagina-spostata-sul-portale-intranet

# User-agent: MegaIndex.ru/2.0
# Disallow: /

# User-agent: MegaIndex.ru/
# Disallow: /

sitemap.xml 200 OK

Type URL Set URLs 0 entries Valid XML No

B

Domain Intelligence

unibo.it — via GARR-REG, 30 years, 8 months old, hosted on ASGARR Consortium GARR, IT

REVIEW

unibo.it — via GARR-REG, 30 years, 8 months old, hosted on ASGARR Consortium GARR, IT

Domain expires in 10 days

This domain expires on May 2, 2026. Domains that expire accidentally cause complete website downtime. Enable auto-renewal or renew manually now.

Got: Expires May 2, 2026

Registrar: GARR-REG

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.

Hosting: ASGARR Consortium GARR, IT

Got: AS137

Domain expiry

EXPIRED

May 2, 2026

SSL certificate

118 days

Issued by Hellenic Academic and Research Institutions CA

Domain age

30 years, 8 months

Registered January 29, 1996

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

ASGARR Consortium GARR, IT

ASN AS137

137.204.24.207

Registrar

GARR-REG

Unlocked 3 NS records

Expiry timeline

Today

+1 year

Domain expiry SSL expiry Danger zone (≤30 days)

Recommended actions

Domain has EXPIRED — renew immediately to avoid total site outage
Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers

Registrar GARR-REG

Created January 29, 1996 (30 years, 8 months ago)

Expires May 2, 2026 (10 days)

Last Updated March 24, 2026

Name Servers almadns.unibo.it, dns2.unibo.it, ns1.garr.net

Registrant ALMA MATER STUDIORUM - Universita' di Bologna

Hosting

IP Address 137.204.24.207

ASN AS137 (ASGARR Consortium GARR, IT)

Provider ASGARR Consortium GARR, IT

Data source: whois (1.8s)

This domain expires on May 2, 2026. Domains that expire accidentally cause complete website downtime. Enable auto-renewal or renew manually now.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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

B

HTTP Probe Timing

Total 821 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

REVIEW

DNS Lookup

183 ms

TCP Connect

159 ms

TLS Handshake

322 ms

Time to First Byte

822 ms

Total Time

822 ms

Connection waterfall

DNS Lookup 183 ms TCP Connect 159 ms TLS Handshake 322 ms Server Processing 158 ms Content Transfer 0 ms

B

TLS Certificate Expiry & Recommendations

118 days until leaf cert expires — 4 issues to address

REVIEW

Certificate validity

118

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, 184 ms lookup

PASS

1 A records, 184 ms lookup

Resolves to 1 IPv4 address(es)

Got: 137.204.24.207

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

No IPv6 (AAAA) records

3 nameserver(s) configured

Got: ns1.garr.net, almadns.unibo.it, dns2.unibo.it

1 mail exchanger(s) configured

CAA records not checked

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

SPF record present in TXT

DNS resolution time: 184 ms

Got: 184 ms

A	137.204.24.207
AAAA	—
CNAME	—
NS	ns1.garr.net, almadns.unibo.it, dns2.unibo.it
MX	0 unibo-it.mail.protection.outlook.com
TXT	SPF v=spf1 ip4:137.204.25.93 ip4:137.204.24.44/30 ip4:137.204.6.94 include:spf.prote... MS=ms86659871 docusign=3a9c0591-b64a-4703-8f40-83ba84ef7cd2 openai-domain-verification=dv-DxUDKjTMwE1kGjsRPzfJmYGi HARICA-ZZO5g8CI2PXwVsyZfNZ 3td76084x064gdxbmynxdjwjfg6hsfxm 17Xcz2CTsX2T8USN+ncikY3nQq1wKmywAtd2Cdi/ziKTxsUrkWJDuaE67SS+GOcbiNfcHg8rr6nmf7BH... ms-domain-verification=24f10187-ea62-462d-9dc1-71cb0c4f3981 google-site-verification=VZC5_dvdA_ubTyTcq16rDWVCmaO_HHOni2PlKMLgXaA kJJJMViTpthzDt6FxY0jSWz0/rsX0AP38K9VG3Las7GntKQaWJaskIRTZkzoANQjLC6+uDkHljMxycVl...
CAA	Lookup not available with standard resolver

Resolved in 184 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+

URL Variants

www/non-www, trailing slash, HTTP→HTTPS

PASS

www/non-www, trailing slash, HTTP→HTTPS

www/non-www redirect configured correctly (preferred: non-www)

HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.unibo.it/

200https://unibo.it/

Preferred variant: non-www

HTTP → HTTPS

301http://unibo.it/ → https://www.unibo.it/

Consistent