Skip to content
https://uni-ulm.de

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Singapore, Singapore
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.

B
Redirect Chain
1 redirect(s), 1321 ms total
REVIEW
1 redirect(s), 1321 ms total
Info::
Single redirect
Got: https://uni-ulm.de → https://www.uni-ulm.de/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1321 ms total
Got: 1321 ms

https://uni-ulm.de

680 ms · HTTP/1.1

301

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

642 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://uni-ulm.de301680 msHTTP/1.1
2https://www.uni-ulm.de/200642 msHTTP/1.1Apache/2.4

See the visual redirect chain in the HTTP Probe tab →

B
URL Variants
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
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.uni-ulm.de/
200https://uni-ulm.de/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://uni-ulm.de/ → https://www.uni-ulm.de/

Consistent

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

Certificate validity

302
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
2 A records, 330 ms lookup
PASS
2 A records, 330 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 134.60.1.202, 134.60.1.177
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2001:7c0:3100::177, 2001:7c0:3100::202
Info::
5 nameserver(s) configured
Got: dns1.uni-ulm.de, dns-1.dfn.de, dns1.belwue.de, dns3.belwue.de, dns5.belwue.de
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
Warning::
DNS resolution is slow (330 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 330 ms
A134.60.1.202, 134.60.1.177
AAAA2001:7c0:3100::177, 2001:7c0:3100::202
CNAME—
NSdns1.uni-ulm.de, dns-1.dfn.de, dns1.belwue.de, dns3.belwue.de, dns5.belwue.de
MX
10 c2951.mx.srv.dfn.de
10 a2951.mx.srv.dfn.de
10 b2951.mx.srv.dfn.de
TXT
SPF v=spf1 redirect=_spf.uni-ulm.de
CAALookup not available with standard resolver
Resolved in 330 ms

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+
IPv6 Readiness
IPv6 reachable (155 ms)
PASS
IPv6 reachable (155 ms)
Info::
IPv6 is configured and reachable at 2001:7c0:3100::177, 2001:7c0:3100::202
Got: 155 ms connect
IPv6 Ready
AAAA Records 2001:7c0:3100::177, 2001:7c0:3100::202 Connection Reachable (155 ms)
A+
Crawlability
robots.txt present, sitemap with 41 URLs
PASS
robots.txt present, sitemap with 41 URLs
Info::
robots.txt is present
Got: 31 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 41 entries
Info::
Sitemap index with 41 child sitemaps
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your 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 31 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /typo3
sitemap.xml 200 OK
Type Sitemap Index URLs 41 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
uni-ulm.de
PASS
uni-ulm.de
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.
Domain expiry

Unknown

SSL certificate

302 days

Issued by Hellenic Academic and Research Institutions CA

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Unknown

2001:7c0:3100::202

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 2001:7c0:3100::202
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

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

Connection waterfall

DNS Lookup 171 ms TCP Connect 158 ms TLS Handshake 168 ms Server Processing 158 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