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

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
2
REVIEW
2
PASS
5
INFO
0
Probed from Madrid, Spain
302 Found
Checks
9
5 PASS 2 REVIEW 2 FIX
D
Redirect Chain
Action
3 redirect(s), 457 ms total
FIX
3 redirect(s), 457 ms total
Warning::
3 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
HTTP to HTTPS redirect present
Info::
WWW normalization redirect
Warning::
3-hop chain could be reduced to 1 hop
Redirect directly from https://uni-frankfurt.de to https://www.uni-frankfurt.de/de
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://uni-frankfurt.de

https://uni-frankfurt.de

81 ms · HTTP/1.1

302

http://www.uni-frankfurt.de/

93 ms · HTTP/1.1

301

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

108 ms · HTTP/1.1

307

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

175 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://uni-frankfurt.de30281 msHTTP/1.1
2http://www.uni-frankfurt.de/30193 msHTTP/1.1
3https://www.uni-frankfurt.de/307108 msHTTP/1.1
4https://www.uni-frankfurt.de/de200175 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

Redirect directly from https://uni-frankfurt.de to https://www.uni-frankfurt.de/de

Why this matters

Redirect chain could be flattened to one hop — server config tweak removes intermediate latency.

Source: web.dev

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

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
218 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

218
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, 31 ms lookup
PASS
1 A records, 31 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 141.2.37.198
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: wattdenn.rz.uni-frankfurt.de, chaplin.rz.uni-frankfurt.de, dns-2.dfn.de
Info::
2 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: 31 ms
Got: 31 ms
A141.2.37.198
AAAA
CNAME
NSwattdenn.rz.uni-frankfurt.de, chaplin.rz.uni-frankfurt.de, dns-2.dfn.de
MX
10 mx1.uni-frankfurt.de
20 mx2.uni-frankfurt.de
TXT
apple-domain-verification=9O2ElvMkcA9WIJxP
docusign=428867fb-dc41-4edf-88df-bdcf41a0dca0
adobe-idp-site-verification=2bfe06eace1bc6cc8672ddc8b4c18c5ea775c59772d31774d04a...
SPF v=spf1 ip4:141.2.22.115 ip4:141.2.22.185 ip4:141.2.22.204 ip4:141.2.22.205 ip4:1...
MS=75E101694B17E7B7770B961A129D1C7E9D592778
CAALookup not available with standard resolver
Resolved in 31 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+
Crawlability
robots.txt present, sitemap with 6 URLs
PASS
robots.txt present, sitemap with 6 URLs
Info::
robots.txt is present
Got: 2225 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 6 entries
Info::
Sitemap index with 6 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 2225 B Sitemaps referenced 1 User-agents aranhabot, SEOkicks, serpstatbot, hgfAlphaXCrawl, NE Crawler, *, BLEXBot, WebPageTest.org, GeedoBot, crawler_eb_germany, CCBot, DotBot, MJ12bot, DataForSeoBot, FemtosearchBot, crawler_faq, MetaJobBot, VelenPublicWebCrawler, MegaIndex.ru, Barkrowler, FullStoryBot Blocking No — crawling allowed
# robots.txt von https://www.uni-frankfurt.de

# ID Bereiche
User-agent: *
Allow: /93095219
Allow: /51245042
Allow: /*?page=
Allow: /44662724
Allow: /99556206
Allow: /83792979
Allow: /75715457
Allow: /54233767
Allow: /49115505
Allow: /44292068
Allow: /41568540
Allow: /40805881
Allow: /39890622
Allow: /137432769
Allow: /112731403
Allow: /38298572
Allow: /37318133
Allow: /102672447
Allow: /91919538
Allow: /38298489
Allow: /36993027
Allow: /38072376
Allow: /38090278
Allow: /116578693
Allow: /88547476
Allow: /91919288
Allow: /139383707
Allow: /47549099
Allow: /40814056
Allow: /95150136
Allow: /104111268
Allow: /150872195
Allow: /151259015
Allow: /115901975
Allow: /39964695
Allow: /40155531
Allow: /54570072
Allow: /94748989
Allow: /94606296
Allow: /94436108
Allow: /76467309
Allow: /49561986
Allow: /44432397
Allow: /43668002
Allow: /43662564
Allow: /43662351
Allow: /43662305
Allow: /118963334
Allow: /60506908




# Gesperrte technische Bereiche & Parameter
User-agent: *
Disallow: /magnoliaAuthor/   
Disallow: /magnoliaPublic/   
Disallow: /admin/            
Disallow: /tools/            
Disallow: /login             
Disallow: /logout
Disallow: /rest/
Disallow: /ws/
Disallow: /docroot/
Disallow: /temp/
Disallow: /cgi-bin/
Disallow: /todo.html
Disallow: /international/doku/
Disallow: /org/ltg/admin/rewe/ba/Doku2/
Disallow: /fb/fb11/ifg/
Disallow: /fb/fb11/geoscience/
             
Disallow: /*&*   
Disallow: /*?filter=             
Disallow: /_next/
Disallow: /_next/image
Disallow: /1
Disallow: /2
Disallow: /3
Disallow: /4
Disallow: /5
Disallow: /6
Disallow: /7
Disallow: /8
Disallow: /9
Disallow: /0

# --- Crawler sperren ---
User-agent: MegaIndex.ru
User-agent: Barkrowler
User-agent: aranhabot
User-agent: SEOkicks
User-agent: DotBot
User-agent: BLEXBot
User-agent: MJ12bot
User-agent: DataForSeoBot
User-agent: FemtosearchBot
User-agent: serpstatbot
User-agent: WebPageTest.org
User-agent: crawler_faq
User-agent: GeedoBot
User-agent: crawler_eb_germany
User-agent: MetaJobBot
User-agent: CCBot
User-agent: VelenPublicWebCrawler
User-agent: hgfAlphaXCrawl
User-agent: FullStoryBot
User-agent: NE Crawler
Disallow: /
   
# --- Sitemap angeben ---
Sitemap: https://www.uni-frankfurt.de/sitemap-index.xml
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

307https://www.uni-frankfurt.de/
200https://uni-frankfurt.de/

HTTP → HTTPS

301http://uni-frankfurt.de/ https://uni-frankfurt.de/

Consistent

A+
Domain Intelligence
uni-frankfurt.de — hosted on UNIFFM-NET cords@rz.uni-frankfurt.de 20101227, DE
PASS
uni-frankfurt.de — hosted on UNIFFM-NET cords@rz.uni-frankfurt.de 20101227, 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.
Info::
Hosting: UNIFFM-NET cords@rz.uni-frankfurt.de 20101227, DE
Got: AS20633
Domain expiry

Unknown

SSL certificate

218 days

Issued by Hellenic Academic and Research Institutions CA

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

UNIFFM-NET cords@rz.uni-frankfurt.de 20101227, DE

ASN AS20633

141.2.37.198

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 141.2.37.198
ASN AS20633 (UNIFFM-NET cords@rz.uni-frankfurt.de 20101227, DE)
Provider UNIFFM-NET cords@rz.uni-frankfurt.de 20101227, DE
Data source: whois (0.9s)

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 113 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
30 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
26 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
30 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
113 ms
Total Time Total request time from DNS lookup through full response.
113 ms

Connection waterfall

DNS Lookup 30 ms TCP Connect 26 ms TLS Handshake 30 ms Server Processing 27 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