Skip to content
https://dlr.de

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
82
GRADE
B
FIX
2
REVIEW
3
PASS
4
INFO
0
Probed from Singapore, Singapore
301 Moved Permanently
Checks
9
4 PASS 3 REVIEW 2 FIX
D
Redirect Chain
Action
2 redirect(s), 3424 ms total
FIX
2 redirect(s), 3424 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://WWW.DLR.DE/
Warning::
Redirect overhead: 3424 ms total
Got: 3424 ms

https://dlr.de

1103 ms · HTTP/1.1

301

https://WWW.DLR.DE/

1101 ms · HTTP/1.1

302

https://WWW.DLR.DE/de

1221 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://dlr.de3011103 msHTTP/1.1
2https://WWW.DLR.DE/3021101 msHTTP/1.1
3https://WWW.DLR.DE/de2001221 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

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

Connection waterfall

DNS Lookup 179 ms TCP Connect 180 ms TLS Handshake 371 ms Server Processing 194 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
196 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

196
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, 196 ms lookup
PASS
1 A records, 196 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 194.94.201.30
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
5 nameserver(s) configured
Got: ns4.dlr.de, dns-2.dfn.de, ns3.dlr.de, dns-1.dfn.de, dns-3.dfn.de
Info::
1 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: 196 ms
Got: 196 ms
A194.94.201.30
AAAA—
CNAME—
NSns4.dlr.de, dns-2.dfn.de, ns3.dlr.de, dns-1.dfn.de, dns-3.dfn.de
MX
10 mailin.dlr.de
TXT
google-site-verification=Qygvkz5D16bz6MgHFShwReH95oxmzqR1nSVKEk106s8
SPF v=spf1 mx ~all
zone-ownership-verification-7093224593846186e0ae328b3c6d6c5f6a8cce2dc6eda3d8cf0f...
MS=ms99685526
MS=ms32953597
HARICA-tyNT5a7DBeOPJ4Urq7E
google-site-verification=wHkXyYZAbPzHPSE3panC81CYJnYFGaXCWpw_KQuJeWQ
google-gws-recovery-domain-verification=52485859
MS=E9410EC7E6BA177C32F2456EF80EDF52DC65EED5
zone-ownership-verification-0ba214405c9835dfe8a1c16c266f865616dd69e1dbd3c31c6dd4...
apple-domain-verification=9OdBZwFC9B8H4QhP
apple-domain-verification=k5TjvcoYmt5Bfejc
OSSRH-53474
CAALookup not available with standard resolver
Resolved in 196 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 31 URLs
PASS
robots.txt present, sitemap with 31 URLs
Info::
robots.txt is present
Got: 314 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 31 entries
Info::
Sitemap index with 31 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 314 B Sitemaps referenced 1 User-agents *, Googlebot Blocking No — crawling allowed
Sitemap: https://WWW.DLR.DE/sitemap-index.xml


# Define access-restrictions for robots/spiders

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




# By default we allow robots to access all areas of our site

# already accessible to anonymous users


User-agent: *

Disallow:


User-Agent: Googlebot

Disallow:
sitemap.xml 200 OK
Type Sitemap Index URLs 31 entries Valid XML Yes
Child Sitemaps:
A
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

302https://www.dlr.de/
200https://dlr.de/

Preferred variant: non-www

HTTP → HTTPS

302http://dlr.de/ → https://dlr.de/

Use 301 (permanent) instead of 302 (temporary)

A+
Domain Intelligence
dlr.de — hosted on DFN Verein zur Foerderung eines Deutschen Forschungsnetzes e.V., DE
PASS
dlr.de — hosted on DFN Verein zur Foerderung eines Deutschen Forschungsnetzes e.V., 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: DFN Verein zur Foerderung eines Deutschen Forschungsnetzes e.V., DE
Got: AS680
Domain expiry

Unknown

SSL certificate

196 days

Issued by Hellenic Academic and Research Institutions CA

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

DFN Verein zur Foerderung eines Deutschen Forschungsnetzes e.V., DE

ASN AS680

194.94.201.30

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 194.94.201.30
ASN AS680 (DFN Verein zur Foerderung eines Deutschen Forschungsnetzes e.V., DE)
Provider DFN Verein zur Foerderung eines Deutschen Forschungsnetzes e.V., DE
Data source: whois (1.7s)

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback