Skip to content
https://unibas.ch

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
73
GRADE
C
FIX
2
REVIEW
3
PASS
3
INFO
1
Probed from Santa Clara, United States
301 Moved Permanently
Checks
9
3 PASS 3 REVIEW 2 FIX
D
Redirect Chain
Action
2 redirect(s), 2646 ms total
FIX
2 redirect(s), 2646 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect
Warning::
Redirect overhead: 2646 ms total
Got: 2646 ms

https://unibas.ch

636 ms · HTTP/1.1

301

https://unibas.ch/de

636 ms · HTTP/1.1

301

https://www.unibas.ch/de

1374 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://unibas.ch301636 msHTTP/1.1Apache
2https://unibas.ch/de301636 msHTTP/1.1Apache
3https://www.unibas.ch/de2001374 msHTTP/1.1

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
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, sitemap with 1716 URLs
REVIEW
robots.txt present, sitemap with 1716 URLs
Info::
robots.txt is present
Got: 116 bytes
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.
Info::
sitemap.xml contains 1716 entries
Info::
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

robots.txt 200 OK
Size 116 B Sitemaps referenced 2 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /

Sitemap: https://www.unibas.ch/de/sitemap.xml
Sitemap: https://www.unibas.ch/en/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 1716 entries Valid XML No
Sample URLs:
B
TLS Certificate Expiry & Recommendations
75 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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, 320 ms lookup
PASS
1 A records, 320 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 131.152.215.57
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: ns1-ext.unibas.ch, ns2-ext.unibas.ch, scsnms.switch.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
Warning::
DNS resolution is slow (320 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 320 ms
A131.152.215.57
AAAA—
CNAME—
NSns1-ext.unibas.ch, ns2-ext.unibas.ch, scsnms.switch.ch
MX
10 unibas-ch.mail.protection.outlook.com
TXT
adobe-idp-site-verification=436f76e07f446b09133441f29006ba5d3a745ba696884502e9cd...
google-site-verification=f31BGWXkgIjce5ZOz3CNdKVV9Np-_j76uZT0QiLfT9A
65t-9jh-gd5
mindmanager-verification=a80be184f50daf8680bb73ffe6ad93b72bc204aaec68be6e6b33f5b...
_d9sga8js5y2hpyxq7kzpobajwsxulkv
SPF v=spf1 ip4:131.152.231.230 ip4:131.152.226.208/30 include:spf.protection.outlook...
MS=ms14683477
ZOOM_verify_XEObkK_wTwWD3x_cgl14Zg
google-site-verification=u1RGStDhqHk6Rx70H1NUUOZEiQXJcw7qzX8vYe29C4w
mistral-domain-verification=b8b4807b324a1bc50daebc68c86b08f45e476e91
ZOOM_verify_3ibFhaTdTWugZYxGjpml4g
jamf-site-verification=3MP_01XF6kgHpdWpyPLuGg
atlassian-domain-verification=JDxBb5EbsPH3EVNizQTCO58lFuZ0UPBsm7t1vmM3MuW/CL73hH...
cisco-ci-domain-verification=1add387b964c7b722d1546a82d38823dff244ac342a3cdbf3ab...
CAALookup not available with standard resolver
Resolved in 320 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.

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

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

301https://www.unibas.ch/
200https://unibas.ch/

Preferred variant: non-www

HTTP → HTTPS

302http://unibas.ch/ → https://unibas.ch/

Use 301 (permanent) instead of 302 (temporary)

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

Connection waterfall

DNS Lookup 161 ms TCP Connect 162 ms TLS Handshake 166 ms Server Processing 164 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