Skip to content
https://uzh.ch

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
1
REVIEW
2
PASS
5
INFO
1
Probed from Madrid, Spain
302 Found
Checks
9
5 PASS 2 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
TLS Certificate Expiry & Recommendations
55 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

55
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, 36 ms lookup
PASS
1 A records, 36 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 130.60.184.132
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: ns3.uzh.ch, ns2.uzh.ch, ns1.uzh.ch
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: 36 ms
Got: 36 ms
A130.60.184.132
AAAA—
CNAME—
NSns3.uzh.ch, ns2.uzh.ch, ns1.uzh.ch
MX
10 uzh-ch.mail.protection.outlook.com
TXT
google-site-verification=EWRa2h69RPpieZESLmZZO93FUq7lunH9vMu2_2qaS28
atlassian-domain-verification=6iHTrnkqTUQQIDdPY1SKYhUu47uakJGm5eny4rTIFMncSd3ZSl...
SPF v=spf1 ip4:40.95.0.0/16 ip4:130.60.207.240/28 ip4:130.60.206.24/31 include:spf.p...
google-site-verification=ZqW-6jV5MwoVU_1cW50AKiuqUT1tlML5ErjWOqXbW5w
CAALookup not available with standard resolver
Resolved in 36 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), 342 ms total
PASS
1 redirect(s), 342 ms total
Info::
Single redirect
Got: https://uzh.ch → https://www.uzh.ch/de.html (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://uzh.ch

https://uzh.ch

140 ms · HTTP/1.1

302

https://www.uzh.ch/de.html

202 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://uzh.ch302140 msHTTP/1.1Apache
2https://www.uzh.ch/de.html200202 msHTTP/1.1Apache

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more ▾

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

A
Crawlability
robots.txt present, sitemap with 0 URLs
PASS
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 467 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Warning::
sitemap.xml is empty — no URLs found
An empty sitemap provides no value. Add <url> entries for your pages.
Info::
robots.txt references sitemap

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 467 B Sitemaps referenced 1 User-agents *, msnbot Blocking No — crawling allowed
User-agent: *
Disallow: /old-files/
Disallow: /images/
Disallow: /gif/
Disallow: /tiff/
Disallow: /cgi-bin/
Disallow: /search/
Disallow: /oci/counter
Disallow: /oci/intra
Disallow: /oci/pics
Disallow: /VV/
Disallow: /VV-all/
Disallow: /id/cl/dl/mobil/vpn/ssl-dir/
Disallow: /de/studies/programs/pupils/coordinators 
Disallow: /studies/programs/pupils/coordinators 
Allow: /cgi-bin/ssl-dir/kurse

User-agent: msnbot
Disallow: /
Sitemap: https://www.uzh.ch/sitemap.txt
sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML Yes
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.uzh.ch/
200https://uzh.ch/

Preferred variant: non-www

HTTP → HTTPS

302http://uzh.ch/ → https://www.uzh.ch/

Use 301 (permanent) instead of 302 (temporary)

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

Connection waterfall

DNS Lookup 29 ms TCP Connect 38 ms TLS Handshake 44 ms Server Processing 60 ms Content Transfer 0 ms
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