Skip to content
https://infomaniak.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from Amsterdam, Netherlands
301 Moved Permanently
Checks
9
6 PASS 2 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
Redirect Chain
2 redirect(s), 267 ms total
REVIEW
2 redirect(s), 267 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://www.infomaniak.com/

https://infomaniak.com

92 ms · HTTP/1.1

301

https://www.infomaniak.com/

74 ms · HTTP/1.1

302

https://www.infomaniak.com/fr

101 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://infomaniak.com30192 msHTTP/1.1
2https://www.infomaniak.com/30274 msHTTP/1.1
3https://www.infomaniak.com/fr200101 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

B
TLS Certificate Expiry & Recommendations
309 days until leaf cert expires — 2 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
DNS Records
1 A records, 66 ms lookup
PASS
1 A records, 66 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 185.125.25.1
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:1600:0:aaaa::2:6
Info::
2 nameserver(s) configured
Got: ns1.infomaniak.ch, ns2.infomaniak.ch
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: 66 ms
Got: 66 ms
A185.125.25.1
AAAA2001:1600:0:aaaa::2:6
CNAME
NSns1.infomaniak.ch, ns2.infomaniak.ch
MX
5 mta-gw.infomaniak.ch
TXT
adojq6vxx4
_0456fl7j57k4hvo54iqoqdlagzhh0q8
_uqaz3lzwlwiyrfvt3hjimu3tlhkoe84
_vlslakjzuze9at8r1rl715byhxqhkfj
apple-domain-verification=Ey6vFr7DkisAJaSF
MS=A59978F0659511E0E80CC48E30ADDFD1F86E8801
amazonses:7hUjEK9TH/M+HXLYD8yA0dfU4jcVbNy3ZdGCsNByvEc=
google-site-verification=Ks5xAq1tM3zO_f80XerzZqoX16985FxihanzVeFOJa8
google-site-verification=S729C68oJjMTKpiIPMuRRhraZ6yk5RlC75M41nJ-Wws
google-site-verification=YE1h9_Az5_YBBZIzkwUqqgtlQYYIIG9RnZ0G2TlWi2o
google-site-verification=mx5B9z5DJj6DTz-eo_9gTAhPZ-JHJvwVwxdKuIZ9NQY
atlassian-domain-verification=lwrD2TOQhGSwjaugjMCBFRM4a89u0Geeyl6a3inzM9wBgc5ayP...
atlassian-domain-verification=qeCGHMahv9BJmcC4TSO8RNewSQOatfmucGX1AeOzbmCWndGItX...
SPF v=spf1 include:spf.infomaniak.ch include:_spf.mailrelay.rrpproxy.net ip4:164.128...
CAALookup not available with standard resolver
Resolved in 66 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+
IPv6 Readiness
IPv6 reachable (16 ms)
PASS
IPv6 reachable (16 ms)
Info::
IPv6 is configured and reachable at 2001:1600:0:aaaa::2:6
Got: 16 ms connect
IPv6 Ready
AAAA Records 2001:1600:0:aaaa::2:6 Connection Reachable (16 ms)
A+
Crawlability
robots.txt present, sitemap with 5 URLs
PASS
robots.txt present, sitemap with 5 URLs
Info::
robots.txt is present
Got: 235 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 235 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /
Disallow: /fr/etat-reseau
Disallow: /en/network-status
Disallow: /de/netzwerkstatus
Disallow: /it/stato-rete
Disallow: /es/estado-red
Disallow: /ip
Disallow: /api/
Sitemap: https://www.infomaniak.com/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)
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

302https://www.infomaniak.com/
200https://infomaniak.com/

Preferred variant: non-www

HTTP → HTTPS

308http://infomaniak.com/ https://infomaniak.com/

Use 301 (permanent) instead of 302 (temporary)

A
Domain Intelligence
infomaniak.com — via Infomaniak Network SA, 29 years, 3 months old
PASS
infomaniak.com — via Infomaniak Network SA, 29 years, 3 months old
Warning::
Domain expires in 47 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Jun 9, 2026
Info::
DNSSEC is enabled
Info::
Registrar: Infomaniak Network SA
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

EXPIRED

June 9, 2026

SSL certificate

309 days

Issued by Sectigo Limited

Domain age

29 years, 3 months

Registered June 10, 1997

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2001:1600:0:aaaa::2:6

Registrar

Infomaniak Network SA

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Domain has EXPIRED — renew immediately to avoid total site outage
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Infomaniak Network SA
Created June 10, 1997 (29 years, 3 months ago)
Expires June 9, 2026 (1 months)
Last Updated June 2, 2025
Name Servers ns1.infomaniak.ch, ns2.infomaniak.ch
DNSSEC Enabled
Hosting
IP Address 2001:1600:0:aaaa::2:6
Data source: rdap (0.1s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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+
HTTP Probe Timing
Total 74 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
23 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
16 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
20 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
75 ms
Total Time Total request time from DNS lookup through full response.
75 ms

Connection waterfall

DNS Lookup 23 ms TCP Connect 16 ms TLS Handshake 20 ms Server Processing 16 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback