Infrastructure - https://uni-heidelberg.de BeaverCheck Audit

D

Redirect Chain

Action

2 redirect(s), 2634 ms total

FIX

2 redirect(s), 2634 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: 2634 ms total

Got: 2634 ms

https://uni-heidelberg.de

873 ms · HTTP/1.1

301

https://www.uni-heidelberg.de/

875 ms · HTTP/1.1

301

https://www.uni-heidelberg.de/en

886 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://uni-heidelberg.de	301	873 ms	HTTP/1.1	nginx
2	https://www.uni-heidelberg.de/	301	875 ms	HTTP/1.1	nginx
3	https://www.uni-heidelberg.de/en	200	886 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

HTTP Probe Timing

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

REVIEW

DNS Lookup

217 ms

TCP Connect

216 ms

TLS Handshake

231 ms

Time to First Byte

883 ms

Total Time

883 ms

Connection waterfall

DNS Lookup 217 ms TCP Connect 216 ms TLS Handshake 231 ms Server Processing 218 ms Content Transfer 0 ms

B

TLS Certificate Expiry & Recommendations

234 days until leaf cert expires — 4 issues to address

REVIEW

Certificate validity

234

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

PASS

1 A records, 253 ms lookup

Resolves to 1 IPv4 address(es)

Got: 129.206.13.71

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

No IPv6 (AAAA) records

4 nameserver(s) configured

Got: dns2.uni-heidelberg.de, dns.uni-heidelberg.de, dns1.belwue.de, dns3.belwue.de

3 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 is slow (253 ms)

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

Got: 253 ms

A	129.206.13.71
AAAA	—
CNAME	—
NS	dns2.uni-heidelberg.de, dns.uni-heidelberg.de, dns1.belwue.de, dns3.belwue.de
MX	10 relay2.uni-heidelberg.de 10 relay.uni-heidelberg.de 10 relay3.uni-heidelberg.de
TXT	SPF v=spf1 ip4:129.206.100.212 ip4:129.206.119.212 ip4:129.206.100.213 include:spf.p... cisco-ci-domain-verification=30f96646ddb8814399410d5700143249881b4eb5948ddcc31e8... 1 baa827de-94e8-11d1-9294-0006292e8152 Master /.../uni-heidelberg.de/dcesrv1_... cloudflare-verify.uni-heidelberg.de 392311672-383734000 HARICA-lOJzgBA3AntUs6PwzHj google-site-verification=HZuDm00bKKT2fU_i2mLun2aw8IUNa64kg9ilP3b8-AQ 1 baa827de-94e8-11d1-9294-0006292e8152 Readonly /.../uni-heidelberg.de/dcesrv2_... apple-domain-verification=rTpijAWdQfNd3V8I
CAA	Lookup not available with standard resolver

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

Crawlability

robots.txt present, sitemap with 13 URLs

PASS

robots.txt present, sitemap with 13 URLs

robots.txt is present

Got: 1651 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 13 entries

Sitemap index with 13 child sitemaps

robots.txt does not reference a sitemap

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 1651 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed

#

# robots.txt

#

# This file is to prevent the crawling and indexing of certain parts

# of your site by web crawlers and spiders run by sites like Yahoo!

# and Google. By telling these “robots” where not to go on your site,

# you save bandwidth and server resources.

#

# This file will be ignored unless it is at the root of your host:

# Used:    http://example.com/robots.txt

# Ignored: http://example.com/site/robots.txt

#

# For more information about the robots.txt standard, see:

# http://www.robotstxt.org/robotstxt.html


User-agent: *

# CSS, JS, Images

Allow: /core/*.css$

Allow: /core/*.css?

Allow: /core/*.js$

Allow: /core/*.js?

Allow: /core/*.gif

Allow: /core/*.jpg

Allow: /core/*.jpeg

Allow: /core/*.png

Allow: /core/*.svg

Allow: /profiles/*.css$

Allow: /profiles/*.css?

Allow: /profiles/*.js$

Allow: /profiles/*.js?

Allow: /profiles/*.gif

Allow: /profiles/*.jpg

Allow: /profiles/*.jpeg

Allow: /profiles/*.png

Allow: /profiles/*.svg

# Directories

Disallow: /core/

Disallow: /profiles/

# Files

Disallow: /README.txt

Disallow: /web.config

# Paths (clean URLs)

Disallow: /admin/

Disallow: /comment/reply/

Disallow: /filter/tips

Disallow: /node/add/

Disallow: /search/

Disallow: /user/register

Disallow: /user/password

Disallow: /user/login

Disallow: /user/logout

# Paths (no clean URLs)

Disallow: /index.php/admin/

Disallow: /index.php/comment/reply/

Disallow: /index.php/filter/tips

Disallow: /index.php/node/add/

Disallow: /index.php/search/

Disallow: /index.php/user/password

Disallow: /index.php/user/register

Disallow: /index.php/user/login

Disallow: /index.php/user/logout

sitemap.xml 200 OK

Type Sitemap Index URLs 13 entries Valid XML Yes

Child Sitemaps:

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→HTTPS redirect uses 302 instead of 301

Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

301https://www.uni-heidelberg.de/

200https://uni-heidelberg.de/

Preferred variant: non-www

HTTP → HTTPS

302http://uni-heidelberg.de/ → https://uni-heidelberg.de/

Use 301 (permanent) instead of 302 (temporary)

A+

Domain Intelligence

uni-heidelberg.de — hosted on BELWUE BelWue-Koordination, DE

PASS

uni-heidelberg.de — hosted on BELWUE BelWue-Koordination, DE

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: BELWUE BelWue-Koordination, DE

Got: AS553

Domain expiry

Unknown

SSL certificate

234 days

Issued by Hellenic Academic and Research Institutions CA

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

BELWUE BelWue-Koordination, DE

ASN AS553

129.206.13.71

Registrar

Registrar unknown

Unlocked Name servers unknown

Expiry timeline

Today

+1 year

SSL expiry Danger zone (≤30 days)

Recommended actions

Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers

Registrar

Hosting

IP Address 129.206.13.71

ASN AS553 (BELWUE BelWue-Koordination, DE)

Provider BELWUE BelWue-Koordination, DE

Data source: whois (1.4s)

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