Skip to content
https://puretechleman.ch

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
91
GRADE
A
FIX
0
REVIEW
3
PASS
5
INFO
1
Probed from Madrid, Spain
200 OK
Checks
9
5 PASS 3 REVIEW
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
86 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

86
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
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
B
CDN & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: 9f70921c9de8d0c0-CDG
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9f70921c9de8d0c0-CDG
A+
DNS Records
1 A records, 45 ms lookup
PASS
1 A records, 45 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::
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: 45 ms
Got: 45 ms
A185.158.133.1
AAAA—
CNAME—
NSnsany2.infomaniak.com, nsany1.infomaniak.com
MX
5 mta-gw.infomaniak.ch
TXT
SPF v=spf1 include:spf.infomaniak.ch -all
google-site-verification=iGSV6Uzduby1N-lqsxTOfmv6cjOsKSApcqd-TWfWMxQ
google-site-verification=mJNblggbc_os8WO2sL4y2db35f92SkRspl6PBvsVRAk
CAALookup not available with standard resolver
Resolved in 45 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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://puretechleman.ch

https://puretechleman.ch

394 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://puretechleman.ch200394 msHTTP/1.1cloudflare
A+
Crawlability
robots.txt present, sitemap with 24 URLs
PASS
robots.txt present, sitemap with 24 URLs
Info::
robots.txt is present
Got: 69 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 24 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 69 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /
Sitemap: https://puretechleman.ch/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 24 entries Valid XML Yes
Sample URLs:
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.puretechleman.ch/
200https://puretechleman.ch/

Preferred variant: non-www

HTTP → HTTPS

301http://puretechleman.ch/ → https://puretechleman.ch/

Consistent

A
HTTP Probe Timing
Total 528 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
42 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.
525 ms
Total Time Total request time from DNS lookup through full response.
528 ms

Connection waterfall

DNS Lookup 42 ms TCP Connect 17 ms TLS Handshake 23 ms Server Processing 444 ms Content Transfer 3 ms
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