Skip to content
https://unige.ch

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
78
GRADE
C
FIX
2
REVIEW
3
PASS
3
INFO
1
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
3 PASS 3 REVIEW 2 FIX
D
TLS Certificate Expiry & Recommendations
Action
13 days until leaf cert expires — 4 issues to address
FIX

Certificate validity

13
days left
0d 30d 60d 90d+
Renew urgently — under 14 days remaining

Recommended actions

  • Renew certificate — 13 days remaining
  • 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
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: 718 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 718 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Crawl-delay: 5
Disallow: /config 
Disallow: /controllers 
Disallow: /elements 
Disallow: /helpers 
Disallow: /jobs 
Disallow: /languages 
Disallow: /libraries 
Disallow: /login
Disallow: /mail 
Disallow: /models 
Disallow: /page_types 
Disallow: /single_pages 
Disallow: /tools
Disallow: /index.php/tools
Disallow: /blocks/*.php$
Disallow: /blocks/*.xml$
Disallow: /concrete/*.php$
Disallow: /concrete/*.xml$
Disallow: /packages/*.php$
Disallow: /packages/*.xml$
Disallow: /updates/*.php$
Disallow: /updates/*.xml$
Disallow: /*/login$
Disallow: /*/do_login$
Disallow: /*?version=
Disallow: /*.print.html
Disallow: /UDK/
Disallow: *.bak
Disallow: /outils/
Disallow: /presse/unilist/
Disallow: /webtools/
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

C
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

200https://www.unige.ch/
200https://unige.ch/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Use 301 (permanent) instead of 302 (temporary)

A+
DNS Records
1 A records, 41 ms lookup
PASS
1 A records, 41 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 129.194.17.21
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: scsnms.switch.ch, nse2.unige.ch, nse1.unige.ch
Info::
3 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: 41 ms
Got: 41 ms
A129.194.17.21
AAAA—
CNAME—
NSscsnms.switch.ch, nse2.unige.ch, nse1.unige.ch
MX
10 mx.unige.ch
20 mx2.unige.ch
30 mx1.unige.ch
TXT
kspk0hwb9sf408m7s32ksl1v400l2cv6
SPF v=spf1 ip4:129.194.9.192/26 ip4:129.194.1.245 ip6:2001:620:600:502:bad:beef::/11...
ZOOM_verify_7ZQwnzm2QFyRPzb3qJuNGg
MS=514467CA2B62B3534B4DB109790683D1812C0391
deepbox-verification=zPxNqhsa-9yw0Wgf3GCsKt7xrnE9XgCnkMRAttcdSqs
google-site-verification=2FvSA56VNZFrG7ClARsrXzS8PBsNj9ekPtzd17OJqM0
QuoVadis=e4cd647d-bb3b-472e-9393-1a61d90949f2
cisco-ci-domain-verification=5d4e74023de31b7525b032bfdf21a81ad69229b43e42ffb33fb...
teamviewer-sso-verification=aa91eeb18d894899b38709f04a9b7e55
ms-domain-verification=0fbb6812-b0e4-4416-9d5c-d05bdb91e46e
apple-domain-verification=zJcLSmwdg1Vig0Lk
have-i-been-pwned-verification=9d36407b87f1d4ceb301957c097a1eaa
CAALookup not available with standard resolver
Resolved in 41 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), 552 ms total
PASS
1 redirect(s), 552 ms total
Info::
Single redirect
Got: https://unige.ch → https://www.unige.ch/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 552 ms total
Got: 552 ms

https://unige.ch

126 ms · HTTP/1.1

301

https://www.unige.ch/

426 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://unige.ch301126 msHTTP/1.1Apache
2https://www.unige.ch/200426 msHTTP/1.1Apache

See the visual redirect chain in the HTTP Probe tab →

A+
HTTP Probe Timing
Total 162 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
35 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
37 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.
162 ms
Total Time Total request time from DNS lookup through full response.
163 ms

Connection waterfall

DNS Lookup 35 ms TCP Connect 37 ms TLS Handshake 44 ms Server Processing 47 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