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

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
4 PASS 4 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.

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: 577 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 577 B Sitemaps referenced 0 User-agents Offline Explorer, Microsoft.URL.Control, EmailCollector, DataForSeoBot, *, WebReaper, WebCopier, HTTrack, penthesilea Blocking No — crawling allowed
# robots.txt zu http://www.uni-goettingen.de

User-agent: *
Disallow: /css/
Disallow: /js/
Disallow: /admin/bilder/
Disallow: /docs/
Disallow: /downloads/
Disallow: /storage/docs/
Disallow: /storage/downloads/
Disallow: /storage/pictures/
Disallow: /storage/upload/
Disallow: /storage/userdata/
Disallow: /error.php
Disallow: /index.php
Disallow: /verify.php

User-agent: WebReaper
User-agent: WebCopier
User-agent: Offline Explorer
User-agent: HTTrack
User-agent: Microsoft.URL.Control
User-agent: EmailCollector
User-agent: penthesilea
User-agent: DataForSeoBot
Disallow: /
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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-goettingen.de/
200https://uni-goettingen.de/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://uni-goettingen.de/ → https://uni-goettingen.de/

Consistent

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

Certificate validity

244
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, 42 ms lookup
PASS
1 A records, 42 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 134.76.18.234
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: dns1.gwdg.de, dns2.gwdg.de, dns3.gwdg.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
Info::
DNS resolution time: 42 ms
Got: 42 ms
A134.76.18.234
AAAA—
CNAME—
NSdns1.gwdg.de, dns2.gwdg.de, dns3.gwdg.de
MX
50 a1234.mx.srv.dfn.de
50 b1234.mx.srv.dfn.de
50 c1234.mx.srv.dfn.de
TXT
HARICA-DboSo0Xi6QaLoW718k0
MS=ms19247630
SPF v=spf1 include:_spf.webcontact.de mx ip4:134.76.10.0/23 ip4:134.76.26.0/24 ip4:1...
cisco-ci-domain-verification=508cb205c1630701f200c19d71038d283380468c1d6acd356d1...
mentimeter-99785aa2-2a75-4ef4-9d9e-6091d1bb9410
google-site-verification=RiGZhWSKYeRF__2VyTnHJ_qp6aSfdxwZM574w2f2c7U
google-site-verification=XLuHHDYYiuRkAjLrv8xqjsBz3F4ecobfK46Fh-j6AqA
ZOOM_verify_MKBxJcqXRQyiUA6tqVPXiw
google-site-verification=DArJdTKaaSqczRf87mXFIru-3BUAifor4FgUkVJCtkA
k9Wgo9044ZEiRe15EGdKzxQMmIpjRmf2ahI4UGiZcOZvnV89LQqgbc9FfgrFUrm2vq48W+JlPQlN0VXk...
CAALookup not available with standard resolver
Resolved in 42 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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://uni-goettingen.de

https://uni-goettingen.de

344 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://uni-goettingen.de200344 msHTTP/1.1nginx
A+
Domain Intelligence
uni-goettingen.de — hosted on GOENET, DE
PASS
uni-goettingen.de — hosted on GOENET, 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: GOENET, DE
Got: AS207592
Domain expiry

Unknown

SSL certificate

244 days

Issued by Hellenic Academic and Research Institutions CA

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

GOENET, DE

ASN AS207592

134.76.18.234

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 134.76.18.234
ASN AS207592 (GOENET, DE)
Provider GOENET, DE
Data source: whois (0.8s)

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 372 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
59 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.
45 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
372 ms
Total Time Total request time from DNS lookup through full response.
373 ms

Connection waterfall

DNS Lookup 59 ms TCP Connect 37 ms TLS Handshake 45 ms Server Processing 231 ms Content Transfer 1 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback