Skip to content
https://willysfood.ch

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
0
REVIEW
7
PASS
9
INFO
1
Probed from Madrid, Spain
200 OK
Checks
17
9 PASS 7 REVIEW
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/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR for 185.158.133.1 does not match any cert SAN: lovable-app-cd-1-4.p.l5e.io
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.
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
TLS Certificate Expiry & Recommendations
71 days until leaf cert expires — 2 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • 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
CDN & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: a0c2f5c5280ec6ae-CDG
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: a0c2f5c5280ec6ae-CDG
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.
A+
DNS Records
1 A records, 55 ms lookup
PASS
1 A records, 55 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 185.158.133.1
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: nsany2.infomaniak.com, nsany1.infomaniak.com
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 55 ms
Got: 55 ms
A185.158.133.1
AAAA
CNAME
NSnsany2.infomaniak.com, nsany1.infomaniak.com
MX
5 mta-gw.infomaniak.ch
TXT
google-site-verification=BDjcZiP7x8hyP7z-xEppGb6hqCrYE88CQTWtQwu_x50
SPF v=spf1 include:spf.infomaniak.ch -all
CAALookup not available with standard resolver
Resolved in 55 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+
DNSSEC
Signed and validating
PASS
Signed and validating
Info::
DNSSEC fully signed and chain validates (ECDSAP256SHA256)
A
Multi-Resolver DNS Speed
Mean 57ms across 3 resolvers (spread 64ms)
PASS
Mean 57ms across 3 resolvers (spread 64ms)
Info::
Quad9: 33ms
Got: 33ms via 9.9.9.9:53
Info::
Cloudflare: 43ms
Got: 43ms via 1.1.1.1:53
Info::
Google: 97ms
Got: 97ms via 8.8.8.8:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://willysfood.ch

https://willysfood.ch

120 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://willysfood.ch200120 msHTTP/1.1cloudflare
A+
Crawlability
robots.txt present, sitemap with 8 URLs
PASS
robots.txt present, sitemap with 8 URLs
Info::
robots.txt is present
Got: 757 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 8 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 757 B Sitemaps referenced 1 User-agents PerplexityBot, GoogleOther, SemrushBot, Twitterbot, LinkedInBot, Applebot, ClaudeBot, MJ12bot, *, Bingbot, facebookexternalhit, GPTBot, DotBot, WhatsApp, AhrefsBot, Googlebot Blocking No — crawling allowed
# Willy's — robots.txt

User-agent: Googlebot
Allow: /
Disallow: /admin

User-agent: Bingbot
Allow: /
Disallow: /admin

User-agent: Twitterbot
Allow: /

User-agent: facebookexternalhit
Allow: /

User-agent: WhatsApp
Allow: /

User-agent: LinkedInBot
Allow: /

User-agent: Applebot
Allow: /

User-agent: ClaudeBot
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: GPTBot
Allow: /

User-agent: GoogleOther
Allow: /

# Aggressive SEO crawlers — throttle
User-agent: SemrushBot
Crawl-delay: 30

User-agent: AhrefsBot
Crawl-delay: 30

User-agent: MJ12bot
Crawl-delay: 30

User-agent: DotBot
Crawl-delay: 30

# Default
User-agent: *
Allow: /
Disallow: /admin
Disallow: /order-success
Disallow: /unsubscribe

Sitemap: https://willysfood.ch/sitemap.xml

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)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

302https://www.willysfood.ch/
200https://willysfood.ch/

Preferred variant: non-www

HTTP → HTTPS

301http://willysfood.ch/ https://willysfood.ch/

Consistent

A+
HTTP Probe Timing
Total 293 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
51 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
17 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
23 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
292 ms
Total Time Total request time from DNS lookup through full response.
293 ms

Connection waterfall

DNS Lookup 51 ms TCP Connect 17 ms TLS Handshake 23 ms Server Processing 201 ms Content Transfer 1 ms
A+
Health Check Endpoint
Health endpoint at https://willysfood.ch/health (HTTP 200)
PASS
Health endpoint at https://willysfood.ch/health (HTTP 200)
Info::
Public health endpoint at https://willysfood.ch/health
Got: https://willysfood.ch/health
Domain Intelligence
Domain intelligence data not available
INFO
Domain intelligence data not available

RDAP and WHOIS lookup both failed

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

Send Feedback