Skip to content
https://e-recht24.de

Infrastructure

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

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
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.e-recht24.de/
200https://e-recht24.de/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://e-recht24.de/ https://www.e-recht24.de/

Consistent

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

Certificate validity

300
days left
0d 30d 60d 90d+

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • 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, 35 ms lookup
PASS
1 A records, 35 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 159.69.70.50
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: ns54.domaincontrol.com, ns53.domaincontrol.com
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: 35 ms
Got: 35 ms
A159.69.70.50
AAAA
CNAME
NSns54.domaincontrol.com, ns53.domaincontrol.com
MX
100 mx0.webpack.hosteurope.de
TXT
DKT6TTBBQNI1KE4FUK5S4LA192
Dl/DKvQdqlfdeqrAP4re5wEwE49KQYfQDSHCErkg/xA=
apple-domain-verification=rk3cayRcQ8bwa6u5
google-site-verification=znVYtvLWmXQ6wQksbthP6p-q9byQS-85142HgFc0Sxw
google-site-verification=5D_J2I7gUbdh8pFaosx0Ha72g3Ory5x-DeOQf3lZqE8
SPF v=spf1 a mx include:spf.server-he.de include:spf.brevo.com ~all
brevo-code:4a9473c4106fa5c902fe7e200fce59dd
google-site-verification=2q2p6btpNSem4eCOAsBcUjc-BsXGnkBIs2y6FAGlNH4
google-site-verification=d8LNW9P1xjc93BcJ6qapeaqy-pjfRP__i7b0LK3_-Ic
CAALookup not available with standard resolver
Resolved in 35 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
1 redirect(s), 307 ms total
PASS
1 redirect(s), 307 ms total
Info::
Single redirect
Got: https://e-recht24.de → https://www.e-recht24.de/ (301)
Info::
WWW normalization redirect

https://e-recht24.de

134 ms · HTTP/1.1

301

https://www.e-recht24.de/

173 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://e-recht24.de301134 msHTTP/1.1LiteSpeed
2https://www.e-recht24.de/200173 msHTTP/1.1LiteSpeed

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 1411 URLs
PASS
robots.txt present, sitemap with 1411 URLs
Info::
robots.txt is present
Got: 1257 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 1411 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1257 B Sitemaps referenced 1 User-agents *, newspaper/0.2.8, wget, webzip, webmirror, webcopy, magpie-crawler Blocking No — crawling allowed
# If the Joomla site is installed within a folder such as at
# e.g. www.example.com/joomla/ the robots.txt file MUST be
# moved to the site root at e.g. www.example.com/robots.txt
# AND the joomla folder name MUST be prefixed to the disallowed
# path, e.g. the Disallow rule for the /administrator/ folder
# MUST be changed to read Disallow: /joomla/administrator/
#
# For more information about the robots.txt standard, see:
# http://www.robotstxt.org/orig.html
#
# For syntax checking, see:
# http://tool.motoricerca.info/robots-checker.phtml

User-agent: *
Allow: /*.js*
Allow: /*.css*
Allow: /*.png*
Allow: /*.jpg*
Allow: /*.gif*

Allow: /*.js
Allow: /*.css
Allow: /*.png
Allow: /*.jpg
Allow: /*.gif
Allow: /*.svg
Allow: /*.woff
Allow: /*.woff2
Allow: /*.eot

Disallow: /administrator/
Disallow: /bin/
Disallow: /cache/
Disallow: /cli/
Disallow: /includes/
Disallow: /installation/
Disallow: /language/
Disallow: /libraries/
Disallow: /logs/
Disallow: /tmp/

User-agent: newspaper/0.2.8
Disallow: /

# Massendownloader fernhalten
User-agent: wget
User-agent: webzip
User-agent: webmirror
User-agent: webcopy
User-agent: magpie-crawler
Disallow: /

# JSitemap entries
Sitemap: https://www.e-recht24.de/index.php?option=com_jmap&view=sitemap&format=gnews

A+
Domain Intelligence
e-recht24.de — hosted on Hetzner
PASS
e-recht24.de — hosted on Hetzner
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: Hetzner
Got: AS24940
Domain expiry

Unknown

SSL certificate

300 days

Issued by Starfield Technologies, Inc.

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Hetzner

ASN AS24940

159.69.70.50

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

Connection waterfall

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