Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
BRedirect Chain2 redirect(s), 769 ms totalREVIEW
https://rwth-aachen.de
230 ms · HTTP/1.1
https://rwth-aachen.de/go/id/a/?lidx=1
222 ms · HTTP/1.1
https://www.rwth-aachen.de/cms/~a/root/?...
317 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://rwth-aachen.de | 302 | 230 ms | HTTP/1.1 | |
| 2 | https://rwth-aachen.de/go/id/a/?lidx=1 | 301 | 222 ms | HTTP/1.1 | |
| 3 | https://www.rwth-aachen.de/cms/~a/root/?... | 200 | 317 ms | HTTP/1.1 |
See the visual redirect chain in the HTTP Probe tab →
Each redirect adds latency. Try to minimize the chain to 1 hop.
Redirect chain — each hop adds latency; combine into one redirect where possible.
Source: Google Search Central / web.dev
If permanent, use 301 instead.
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
BTLS Certificate Expiry & Recommendations170 days until leaf cert expires — 6 issues to addressREVIEW
Certificate validity
Recommended actions
- Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
- Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
- 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 Records1 A records, 36 ms lookupPASS
| A | 137.226.107.60 |
| AAAA | 2a00:8a60:450::107:60 |
| CNAME | — |
| NS | zs1.rz.rwth-aachen.de, zs2.rz.rwth-aachen.de, dns-1.dfn.de, dns-2.dfn.de |
| MX | 10 mx1.rz.rwth-aachen.de |
| TXT | SPF v=spf1 include:_spf.itc.rwth-aachen.de -all adobe-idp-site-verification=f776e93b43310d11ffce240aee50080562eb76f499439e8f27f9... google-gws-recovery-domain-verification=68268798 google-site-verification=MBo5UfSByZyIAyjv3TI4YpeIF3k9800b6R-0RuupVog |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
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.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
A+IPv6 ReadinessIPv6 reachable (29 ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 5484 URLsPASS
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
#custom
User-agent: *
Disallow:
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencerwth-aachen.dePASS
Unknown
170 days
Issued by Hellenic Academic and Research Institutions CA
Unknown
Status unknown
Protects against DNS spoofing
Unknown
2a00:8a60:450::107:60
Registrar unknown
Expiry timeline
Recommended actions
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
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.
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