Skip to content
https://uniroma1.it

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
86
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
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

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

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

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 No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Certificate validity

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

Recommended actions

  • 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, 83 ms lookup
PASS
1 A records, 83 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 151.100.101.140
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
3 nameserver(s) configured
Got: desiree.cics.uniroma1.it, ns1.garr.net, risc-ns.cics.uniroma1.it
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: 83 ms
Got: 83 ms
A151.100.101.140
AAAA
CNAME
NSdesiree.cics.uniroma1.it, ns1.garr.net, risc-ns.cics.uniroma1.it
MX
1 ASPMX.L.GOOGLE.COM
5 ALT1.ASPMX.L.GOOGLE.COM
5 ALT2.ASPMX.L.GOOGLE.COM
10 ASPMX3.GOOGLEMAIL.COM
10 ASPMX2.GOOGLEMAIL.COM
TXT
openai-domain-verification=dv-Fq2Na25o0bPchigx6vsiI9W5
SPF v=spf1 ip4:151.100.101.67 ip4:151.100.101.143 ip4:130.186.31.160/27 IP4:130.186....
DGtCecNbjgKcoUbP
google-site-verification=yZ-z-HABYTCZg4tGtbPi03lSx6woSWUKtsD-rDVa2zA*google-site...
HARICA-txCZmjKrV1LKA6IQbrY
MS=22A67665DB98E326A6B60369C4AA780B1BEAC8A7
CAALookup not available with standard resolver
Resolved in 83 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), 326 ms total
PASS
1 redirect(s), 326 ms total
Info::
Single redirect
Got: https://uniroma1.it → https://www.uniroma1.it/it/ (301)
Info::
WWW normalization redirect

https://uniroma1.it

124 ms · HTTP/1.1

301

https://www.uniroma1.it/it/

202 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://uniroma1.it301124 msHTTP/1.1nginx
2https://www.uniroma1.it/it/200202 msHTTP/1.1nginx

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.uniroma1.it/
200https://uniroma1.it/

Preferred variant: non-www

HTTP → HTTPS

301http://uniroma1.it/ https://www.uniroma1.it/

Consistent

A+
Domain Intelligence
uniroma1.it — via GARR-REG, 30 years, 8 months old, hosted on ASGARR Consortium GARR, IT
PASS
uniroma1.it — via GARR-REG, 30 years, 8 months old, hosted on ASGARR Consortium GARR, IT
Info::
Domain registered until Jan 29, 2027 (9 months remaining)
Info::
Registrar: GARR-REG
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.
Info::
Hosting: ASGARR Consortium GARR, IT
Got: AS137
Domain expiry

198 days

January 29, 2027

SSL certificate

197 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

151.100.101.140

Registrar

GARR-REG

Unlocked 3 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar GARR-REG
Created January 29, 1996 (30 years, 8 months ago)
Expires January 29, 2027 (9 months)
Last Updated February 14, 2026
Name Servers risc-ns.cics.uniroma1.it, desiree.cics.uniroma1.it, ns1.garr.net
Registrant Universita' degli Studi di Roma La Sapienza
Hosting
IP Address 151.100.101.140
ASN AS137 (ASGARR Consortium GARR, IT)
Provider ASGARR Consortium GARR, IT
Data source: whois (0.9s)

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

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

Connection waterfall

DNS Lookup 70 ms TCP Connect 39 ms TLS Handshake 48 ms Server Processing 38 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