Skip to content
https://gesafe-hennel.de

Infrastructure

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

B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
B
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
B
Reverse DNS
0/2 IPs match cert SAN
REVIEW
0/2 IPs match cert SAN
Info::
PTR for 217.160.0.224 does not match any cert SAN: 217-160-0-224.elastic-ssl.ui-r.com
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 2001:8d8:100f:f000::200 does not match any cert SAN: 2001-08d8-100f-f000-0000-0000-0000-0200.elastic-ssl.ui-r.com
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 200 Expected: 301 redirect to HTTPS

www / non-www

500https://www.gesafe-hennel.de/
200https://gesafe-hennel.de/

HTTP → HTTPS

200http://gesafe-hennel.de/

HTTP version does not redirect to HTTPS

B
HTTP Probe Timing
Total 1346 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
35 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
34 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
38 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.32 s
Total Time Total request time from DNS lookup through full response.
1.35 s

Connection waterfall

DNS Lookup 35 ms TCP Connect 34 ms TLS Handshake 38 ms Server Processing 1.21 s Content Transfer 27 ms
B
TLS Certificate Expiry & Recommendations
145 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

145
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
B
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
No CDN cache-status headers in the response
Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: connection error, /ping: 404, /status: connection error.
A+
DNS Records
1 A records, 48 ms lookup
PASS
1 A records, 48 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 217.160.0.224
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2001:8d8:100f:f000::200
Info::
4 nameserver(s) configured
Got: ns1065.ui-dns.de, ns1095.ui-dns.org, ns1071.ui-dns.biz, ns1095.ui-dns.com
Info::
2 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 48 ms
Got: 48 ms
A217.160.0.224
AAAA2001:8d8:100f:f000::200
CNAME—
NSns1065.ui-dns.de, ns1095.ui-dns.org, ns1071.ui-dns.biz, ns1095.ui-dns.com
MX
10 mx01.ionos.de
10 mx00.ionos.de
TXT
SPF v=spf1 include:_spf-eu.ionos.com ~all
CAALookup not available with standard resolver
Resolved in 48 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

A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Multi-Resolver DNS Speed
Mean 21ms across 3 resolvers (spread 36ms)
PASS
Mean 21ms across 3 resolvers (spread 36ms)
Info::
Quad9: 0ms
Got: 0ms via 9.9.9.9:53
Info::
Google: 27ms
Got: 27ms via 8.8.8.8:53
Info::
Cloudflare: 36ms
Got: 36ms via 1.1.1.1:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://gesafe-hennel.de

https://gesafe-hennel.de

1244 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://gesafe-hennel.de2001244 msHTTP/1.1Apache
A+
IPv6 Readiness
IPv6 reachable (33 ms)
PASS
IPv6 reachable (33 ms)
Info::
IPv6 is configured and reachable at 2001:8d8:100f:f000::200
Got: 33 ms connect
IPv6 Ready
AAAA Records 2001:8d8:100f:f000::200 Connection Reachable (33 ms)
A+
Crawlability
robots.txt present, sitemap with 3001 URLs
PASS
robots.txt present, sitemap with 3001 URLs
Info::
robots.txt is present
Got: 273 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 3001 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 273 B Sitemaps referenced 5 User-agents * Blocking No — crawling allowed
User-agent: *

Allow: /

sitemap: https://gesafe-hennel.de/sitemap301.xml

sitemap: https://gesafe-hennel.de/sitemap647.xml

sitemap: https://gesafe-hennel.de/sitemap356.xml

sitemap: https://gesafe-hennel.de/sitemap244.xml

sitemap: https://gesafe-hennel.de/sitemap867.xml
sitemap.xml 200 OK
Type URL Set URLs 3001 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
gesafe-hennel.de
PASS
gesafe-hennel.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.
Domain expiry

Unknown

SSL certificate

145 days

Issued by Sectigo Limited

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Unknown

2001:8d8:100f:f000::200

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 2001:8d8:100f:f000::200
Data source: whois (0.5s)

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