Skip to content
https://www.gesundheitswelt.de

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
83
GRADE
B
FIX
0
REVIEW
10
PASS
7
INFO
0
Probed from Santa Clara, United States
200 OK
Checks
17
7 PASS 10 REVIEW
B
DNS Records
1 A records, 590 ms lookup
REVIEW
1 A records, 590 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 162.159.135.42
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: gesundheitswelt.de
Info::
2 nameserver(s) configured
Got: ns1.ns-serve.net, ns2.ns-serve.net
Info::
3 mail exchanger(s) configured
Info::
SPF record present in TXT
Warning::
DNS resolution is slow (590 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 590 ms
A162.159.135.42
AAAA—
CNAMEgesundheitswelt.de
NSns1.ns-serve.net, ns2.ns-serve.net
MX
10 mx1.gesundheitswelt.de
20 mx2.gesundheitswelt.de
30 mx3.gesundheitswelt.de
TXT
brevo-code:e0598ec6f259c349e0934673997ec4f1
Sendinblue-code:ec6cc7d786ff96d3f769828ef7a78bc9
atlassian-domain-verification=9xSBngfGgY30/mOJHaMlYNACIqnjwnpj1ksSunXEOJkVbVpFTQ...
SPF v=spf1 include:spf1.gesundheitswelt.de include:_spf.rexx-suite.com include:spf.s...
apple-domain-verification=a9tsp4NYtMYOC2NE
sendinblue-code:495221fca79a0d0941cb66232f181627
MS=ms49581311
CAALookup not available with standard resolver
Resolved in 590 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 CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more ▾

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

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.
C
Reverse DNS
Action
0/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR lookup failed for 162.159.135.42: lookup 162.159.135.42: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
C
Multi-Resolver DNS Speed
Action
Mean 310ms across 3 resolvers (spread 14ms)
REVIEW
Mean 310ms across 3 resolvers (spread 14ms)
Info::
Google: 304ms
Got: 304ms via 8.8.8.8:53
Info::
Cloudflare: 308ms
Got: 308ms via 1.1.1.1:53
Info::
Quad9: 318ms
Got: 318ms via 9.9.9.9:53
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 1190 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
467 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
3 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
8 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.05 s
Total Time Total request time from DNS lookup through full response.
1.19 s

Connection waterfall

DNS Lookup 467 ms TCP Connect 3 ms TLS Handshake 8 ms Server Processing 567 ms Content Transfer 146 ms
B
TLS Certificate Expiry & Recommendations
75 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • 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
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: 404, /ping: 404, /status: 404.
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
CNAME does not point at a known takeover-able service
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.gesundheitswelt.de

https://www.gesundheitswelt.de

1088 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.gesundheitswelt.de2001088 msHTTP/1.1cloudflare
A+
Crawlability
robots.txt present, sitemap with 5 URLs
PASS
robots.txt present, sitemap with 5 URLs
Info::
robots.txt is present
Got: 180 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 5 entries
Info::
Sitemap index with 5 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 180 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
# START YOAST BLOCK
# ---------------------------
User-agent: *
Disallow:

Sitemap: https://www.gesundheitswelt.de/sitemap_index.xml
# ---------------------------
# END YOAST BLOCK
sitemap.xml 200 OK
Type Sitemap Index URLs 5 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: www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.gesundheitswelt.de/
301https://gesundheitswelt.de/

Preferred variant: www

HTTP → HTTPS

301http://www.gesundheitswelt.de/ → https://www.gesundheitswelt.de/

Consistent

A+
Domain Intelligence
gesundheitswelt.de — hosted on Cloudflare
PASS
gesundheitswelt.de — hosted on Cloudflare
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: Cloudflare
Got: AS13335
Domain expiry

Unknown

SSL certificate

75 days

Issued by Google Trust Services

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

162.159.135.42

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 162.159.135.42
ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)
Provider Cloudflare
Data source: whois (0.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

A
CDN & Delivery
Cloudflare (DYNAMIC)
PASS
Cloudflare (DYNAMIC)
Info::
Site is served via Cloudflare CDN (edge: SJC)
Got: cf-ray: 9f9eb88f9d48f457-SJC
Info::
CDN cache status: DYNAMIC
CDN Detected: Cloudflare
Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: 9f9eb88f9d48f457-SJC
A+
CDN Cache Observability
Cache state: DYNAMIC
PASS
Cache state: DYNAMIC
Info::
CDN cache state observable via 1 header(s)
Got: cf-cache-status=DYNAMIC
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback