Infrastructure - https://leancure.com BeaverCheck Audit

B

DNSSEC

Unsigned (DNSSEC not deployed)

REVIEW

Unsigned (DNSSEC not deployed)

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)

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/1 IPs match cert SAN

REVIEW

0/1 IPs match cert SAN

PTR for 109.234.162.57 does not match any cert SAN: 109-234-162-57.reverse.odns.fr

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

Redirect Chain

1 redirect(s), 4961 ms total

REVIEW

1 redirect(s), 4961 ms total

Single redirect

Got: https://leancure.com → https://www.leancure.com/ (301)

WWW normalization redirect

Redirect overhead: 4961 ms total

Got: 4961 ms

https://leancure.com

1595 ms · HTTP/1.1

301

https://www.leancure.com/

3366 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://leancure.com	301	1595 ms	HTTP/1.1	o2switch-PowerBoost-v3
2	https://www.leancure.com/	200	3366 ms	HTTP/1.1	o2switch-PowerBoost-v3

See the visual redirect chain in the HTTP Probe tab →

C

IPv6 Readiness

Action

No IPv6 support

REVIEW

No IPv6 support

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

Both www and non-www versions serve content

Got: Both variants return 200 Expected: One variant 301-redirects to the other

HTTP correctly redirects to HTTPS permanently

Got: HTTP 301

www / non-www

200https://www.leancure.com/

200https://leancure.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://leancure.com/ → https://leancure.com/

Consistent

C

HTTP Probe Timing

Action

Total 1785 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

REVIEW

DNS Lookup

37 ms

TCP Connect

23 ms

TLS Handshake

29 ms

Time to First Byte

1.78 s

Total Time

1.79 s

Connection waterfall

DNS Lookup 37 ms TCP Connect 23 ms TLS Handshake 29 ms Server Processing 1.70 s Content Transfer 1 ms

B

TLS Certificate Expiry & Recommendations

88 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

88

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

C

CDN & Delivery

Action

Assets on Cloudflare (host cdnjs.cloudflare.com, 4 assets); document served directly from origin

REVIEW

Assets on Cloudflare (host cdnjs.cloudflare.com, 4 assets); document served directly from origin

Document not behind existing CDN (Cloudflare serves the assets)

The page's subresources are delivered by Cloudflare (cdnjs.cloudflare.com, 4 assets), but the HTML document itself comes straight from the origin. Routing the document through the CDN already in use is the cheapest latency win available here -- the provider relationship, the certificate and the config already exist. A short edge TTL with stale-while-revalidate suits HTML that changes often; if the response is genuinely per-user, edge TLS termination alone still removes a full round trip from every visitor's first byte.

Got: cf-ray: a54ea89e6ead4fe6-CDG

Assets on Cloudflare: cdnjs.cloudflare.com (assets: 4), cache HIT

Got: cf-ray: a54ea89e6ead4fe6-CDG

Assets on a CDN, document is not: Cloudflare

Document origin not attributed

Asset hosts on a CDN

cdnjs.cloudflare.com — Cloudflare · assets: 4 · Cache Status: HIT

Other asset hosts

o2swit.ch — assets: 4 · not attributed

The heavy static files already ride an edge network, but every visitor still waits on the origin for the HTML itself. Routing the document through the same CDN is usually a config change rather than a migration: a short edge TTL with stale-while-revalidate for cacheable HTML, or edge TLS termination alone when the response is per-user.

B

CDN Cache Observability

No CDN cache-status headers in the response

REVIEW

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

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

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: connection error, /health: connection error, /healthz: connection error, /ping: connection error, /status: connection error.

A+

DNS Records

1 A records, 41 ms lookup

PASS

1 A records, 41 ms lookup

Resolves to 1 IPv4 address(es)

Got: 109.234.162.57

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

No IPv6 (AAAA) records

4 nameserver(s) configured

Got: ns1047.ui-dns.com, ns1045.ui-dns.org, ns1091.ui-dns.de, ns1045.ui-dns.biz

5 mail exchanger(s) configured

SPF record present in TXT

DNS resolution time: 41 ms

Got: 41 ms

A	109.234.162.57
AAAA	—
CNAME	—
NS	ns1047.ui-dns.com, ns1045.ui-dns.org, ns1091.ui-dns.de, ns1045.ui-dns.biz
MX	1 aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com 10 alt3.aspmx.l.google.com 10 alt4.aspmx.l.google.com
TXT	google-site-verification=ib0dbiNhl9_IxH3J5uWaHN_EZE0MimDNnWWd_Pl3Ehc SPF v=spf1 include:_spf.google.com include:_spf-eu.ionos.com ~all
CAA	Lookup not available with standard resolver

Resolved in 41 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

No CNAME record present

A+

Multi-Resolver DNS Speed

Mean 31ms across 3 resolvers (spread 40ms)

PASS

Mean 31ms across 3 resolvers (spread 40ms)

Cloudflare: 17ms

Got: 17ms via 1.1.1.1:53

Google: 20ms

Got: 20ms via 8.8.8.8:53

Quad9: 57ms

Got: 57ms via 9.9.9.9:53

A+

Crawlability

robots.txt present, sitemap with 4 URLs

PASS

robots.txt present, sitemap with 4 URLs

robots.txt is present

Got: 199 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 4 entries

Sitemap index with 4 child sitemaps

robots.txt references sitemap

robots.txt 200 OK

Size 199 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed

# START YOAST BLOCK
# ---------------------------
User-agent: *
Disallow:

Sitemap: https://www.leancure.com/sitemap_index.xml
# ---------------------------
# END YOAST BLOCK<!-- Génération CSS -->

sitemap.xml 200 OK

Type Sitemap Index URLs 4 entries Valid XML Yes

Child Sitemaps:

A+

Domain Intelligence

leancure.com — via IONOS SE, 11 years, 11 months old, hosted on O2SWITCH - O2SWITCH SAS, FR

PASS

leancure.com — via IONOS SE, 11 years, 11 months old, hosted on O2SWITCH - O2SWITCH SAS, FR

Domain registered until Feb 3, 2027 (3 months remaining)

DNSSEC is not enabled

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Registrar: IONOS SE

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.

Hosting: O2SWITCH - O2SWITCH SAS, FR

Got: AS50474

Domain expiry

87 days

February 3, 2027

SSL certificate

88 days

Issued by Let's Encrypt

Domain age

11 years, 11 months

Registered February 3, 2015

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

O2SWITCH - O2SWITCH SAS, FR

ASN AS50474

109.234.162.57

Registrar

IONOS SE

Unlocked 4 NS records

Expiry timeline

Today

+1 year

Domain expiry SSL expiry Danger zone (≤30 days)

Recommended actions

Renew the domain or enable auto-renewal to prevent accidental expiry
Enable DNSSEC to protect visitors from DNS spoofing
Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers

Registrar IONOS SE

Created February 3, 2015 (11 years, 11 months ago)

Expires February 3, 2027 (3 months)

Last Updated February 4, 2026

Name Servers ns1045.ui-dns.biz, ns1045.ui-dns.org, ns1047.ui-dns.com, ns1091.ui-dns.de

DNSSEC Not enabled

Hosting

IP Address 109.234.162.57

ASN AS50474 (O2SWITCH - O2SWITCH SAS, FR)

Provider O2SWITCH - O2SWITCH SAS, FR

Data source: rdap (0.4s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more ▾

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

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