Hardenize Report: infomaniak.com

Web Security Overview

HTTPS

Web sites need to use encryption to help their visitors know they're in the right place, as well as provide confidentiality and content integrity. Sites that don't support HTTPS may expose sensitive data and have their pages modified and subverted.
There are issues with this site's HTTPS configuration.

For all sites VERY IMPORTANT medium EFFORT

HTTPS Redirection

To deploy HTTPS properly, web sites must redirect all unsafe (plaintext) traffic to the encrypted variant. This approach ensures that no sensitive data is exposed and that further security technologies can be activated.

For all sites VERY IMPORTANT low EFFORT

HTTP Strict Transport Security

HTTP Strict Transport Security (HSTS) is an HTTPS extension that instructs browsers to remember sites that use encryption and enforce strict security requirements. Without HSTS, active network attacks are easy to carry out.

For important sites VERY IMPORTANT medium EFFORT

HSTS Preloaded

HSTS Preloading is informing browsers in advance about a site's use of HSTS, which means that strict security can be enforced even on the first visit. This approach provides best HTTPS security available today.

For important sites VERY IMPORTANT medium EFFORT

Content Security Policy

Content Security Policy (CSP) is an additional security layer that enables web sites to control browser behavior, creating a safety net that can counter attacks such as cross-site scripting.

For important sites IMPORTANT high EFFORT

Email Security Overview

STARTTLS

All hosts that receive email need encryption to ensure confidentiality of email messages. Email servers thus need to support STARTTLS, as well as provide decent TLS configuration and correct certificates.

For all sites VERY IMPORTANT low EFFORT

SPF

Sender Policy Framework (SPF) enables organizations to designate servers that are allowed to send email messages on their behalf. With SPF in place, spam is easier to identify.

For important sites IMPORTANT low EFFORT

DMARC

Domain-based Message Authentication, Reporting, and Conformance (DMARC) is a mechanism that allows organizations to specify how unauthenticated email (identified using SPF and DKIM) should be handled.

For important sites IMPORTANT low EFFORT

DNS Zone

The global DNS infrastructure is organized as a series of hierarchical DNS zones. The root zone hosts a number of global and country TLDs, which in turn host further zones that are delegated to their customers. Each organization that controls a zone can delegate parts of its namespace to other zones. In this test we perform detailed inspection of a DNS zone, but only if the host being tested matches the zone.

Test passed

Everything seems to be well configured. Well done.

Nameserver Names

Nameservers can be referred to by name and by address. In this section we show the names, which can appear in the NS records, the referrals from the parent zone, and the SOA record. In some situations, servers from the parent zone respond authoritatively, in which case we will include them in the list as well.

Nameserver	Operational	IPv4	IPv6	Sources
ns1.infomaniak.ch. PRIMARY 84.16.66.66 2001:1600:0:aaaa::a				NS SOA REFERRAL
ns2.infomaniak.ch. 84.16.67.66 2001:1600:0:aaaa::b				NS REFERRAL

Nameserver Addresses

This section shows the configuration of all discovered nameservers by their IP address. To find all applicable nameservers, we inspect the parent zone nameservers for names and glue and then the tested zone nameservers for NS records. We then resolve all discovered names to IP addresses. Finally, we test each address individually.

Nameserver	Sources	Payload Size
84.16.66.66 PRIMARY ns1.infomaniak.ch. PTR: ns1.infomaniak.ch.	NAME	1232
84.16.67.66 ns2.infomaniak.ch. PTR: ns2.infomaniak.ch.	NAME	1232
2001:1600:0:aaaa::a PRIMARY ns1.infomaniak.ch. PTR: ns1.infomaniak.ch.	NAME	1232
2001:1600:0:aaaa::b ns2.infomaniak.ch. PTR: ns2.infomaniak.ch.	NAME	1232

Start of Authority (SOA) Record

Start of Authority (SOA) records contain administrative information pertaining to one DNS zone, especially the configuration that's used for zone transfers between the primary nameserver and the secondaries. Only one SOA record should exist, with all nameservers providing the same information.

The domain name of the primary nameserver for the zone. Also known as MNAME.Primary nameserver	ns1.infomaniak.ch.
Email address of the persons responsible for this zone. Also known as RNAME.Admin email	hostmaster.infomaniak.ch.
Zone serial or version number.Serial number	2026100289
The length of time secondary nameservers should wait before querying the primary for changes.Refresh interval	10,800 seconds (about 3 hours)
The length of time secondary nameservers should wait before querying an unresponsive primary again.Retry interval	3,600 seconds (about 1 hour)
The length of time after which secondary nameservers should stop responding to queries for a zone, assuming no updates were obtained from the primary.Expire interval	605,800 seconds (about 7 days 16 minutes)
TTL for purposes of negative response caching. Negative cache TTL	3,600 seconds (about 1 hour)
Time To Live (TTL) indicates for how long a record remains valid. SOA record TTL	3,600 seconds (about 1 hour)

Analysis

No problems detected with the zone configuration

Excellent. This DNS zone is in a good working order. No problems detected.

Backing DNS Queries

Below are all DNS queries we submitted during the zone inspection.

	ID	Server	Transport	Question Name	Type	Status

DNS Records

Correctly functioning name servers are necessary to hold and distribute information that's necessary for your domain name to operate correctly. Examples include converting names to IP addresses, determining where email should go, and so on. More recently, the DNS is being used to communicate email and other security policies.

Test passed

Everything seems to be well configured. Well done.

DNS Records

These are the results of individual DNS queries against your nameserver for common resource record types.

Name	TTL	Type	Data
infomaniak.com.	300	A	185.125.25.1
www.infomaniak.com.	300	A	185.125.25.1
infomaniak.com.	300	AAAA	2001:1600:0:aaaa:0:0:2:6
www.infomaniak.com.	300	AAAA	2001:1600:0:aaaa:0:0:2:6
infomaniak.com.	60	DNSKEY	257 3 13 T3tuKNsZlLkMya1c+ubWmny7L6wVw/Qpd1j4bsvar1FNVJsmGXcZFgkIYr8sT+htrv6IfWVlXYyO6Neoi0hMWw==
infomaniak.com.	60	DNSKEY	256 3 13 YoACjyGzsqVPayDAaphwDu0FLGjFVtMF2okF+C7Le3VdQmeEWBXttIrpDMk1jqppahhNuWkJEZDeoqu7qFwEag==
infomaniak.com.	3600	MX	5 mta-gw.infomaniak.ch.
infomaniak.com.	3600	NS	ns2.infomaniak.ch.
infomaniak.com.	3600	NS	ns1.infomaniak.ch.
infomaniak.com.	3600	SOA	ns1.infomaniak.ch. hostmaster.infomaniak.ch. 2026100289 10800 3600 605800 3600
infomaniak.com.	3600	TXT	"apple-domain-verification=Ey6vFr7DkisAJaSF"
infomaniak.com.	3600	TXT	"v=spf1 include:spf.infomaniak.ch include:_spf.mailrelay.rrpproxy.net ip4:164.128.163.164 ip4:164.128.163.167 ip4:164.128.163.171 include:mailgun.org -all"
infomaniak.com.	3600	TXT	"_vlslakjzuze9at8r1rl715byhxqhkfj"
infomaniak.com.	3600	TXT	"google-site-verification=mx5B9z5DJj6DTz-eo_9gTAhPZ-JHJvwVwxdKuIZ9NQY"
infomaniak.com.	3600	TXT	"adojq6vxx4"
infomaniak.com.	3600	TXT	"google-site-verification=S729C68oJjMTKpiIPMuRRhraZ6yk5RlC75M41nJ-Wws"
infomaniak.com.	3600	TXT	"google-site-verification=YE1h9_Az5_YBBZIzkwUqqgtlQYYIIG9RnZ0G2TlWi2o"
infomaniak.com.	3600	TXT	"_uqaz3lzwlwiyrfvt3hjimu3tlhkoe84"
infomaniak.com.	3600	TXT	"atlassian-domain-verification=qeCGHMahv9BJmcC4TSO8RNewSQOatfmucGX1AeOzbmCWndGItXdLFBxrmmLr38HB"
infomaniak.com.	3600	TXT	"MS=A59978F0659511E0E80CC48E30ADDFD1F86E8801"
infomaniak.com.	3600	TXT	"amazonses:7hUjEK9TH/M+HXLYD8yA0dfU4jcVbNy3ZdGCsNByvEc="
infomaniak.com.	3600	TXT	"atlassian-domain-verification=lwrD2TOQhGSwjaugjMCBFRM4a89u0Geeyl6a3inzM9wBgc5ayPOtAoKEPFYxOdyC"
infomaniak.com.	3600	TXT	"_0456fl7j57k4hvo54iqoqdlagzhh0q8"
infomaniak.com.	3600	TXT	"google-site-verification=Ks5xAq1tM3zO_f80XerzZqoX16985FxihanzVeFOJa8"
_dmarc.infomaniak.com.	300	TXT	"v=DMARC1;p=reject;sp=reject;rua=mailto:dmarc-report@infomaniak.com;ruf=mailto:dmarc-report@infomaniak.com"

Backing DNS Queries

Below are all DNS queries we submitted while inspecting the resource records.

	ID	Server	Question Name	Type	Status

DNSSEC

DNSSEC is an extension of the DNS protocol that provides cryptographic assurance of the authenticity and integrity of responses; it's intended as a defense against network attackers who are able to manipulate DNS to redirect their victims to servers of their choice. DNSSEC is controversial, with the industry split largely between those who think it's essential and those who believe that it's problematic and unnecessary.

Test passed

Everything seems to be well configured. Well done.

Analysis

DNSSEC is well configured

Good. This domain name has well-configured DNSSEC.

Useful DNSSEC Tools

Certification Authority Authorization

CAA (RFC 8659) is a new standard that allows domain name owners to restrict which CAs are allowed to issue certificates for their domains. This can help to reduce the chance of misissuance, either accidentally or maliciously. In September 2017, CAA became mandatory for CAs to implement.

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

Analysis

There is no CAA policy on this domain

CAA policies can be used to restrict which CAs are allowed to issue certificates for a hostname. As such, CAA can be used to enforce an organization-wide policy and to prevent issuance of unauthorized certificates. The CA/Browser forum requires CAs to consult CAA configuration during certificate issuance from September 2017.

Email (SMTP)

An internet hostname can be served by zero or more mail servers, as specified by MX (mail exchange) DNS resource records. Each server can further resolve to multiple IP addresses, for example to handle IPv4 and IPv6 clients. Thus, in practice, hosts that wish to receive email reliably are supported by many endpoint.

Test passed

Everything seems to be well configured. Well done.

Server

Preference

Operational

STARTTLS

TLS

PKI

DNSSEC

DANE

mta-gw.infomaniak.ch
83.166.143.57
PTR: mx01.infomaniak.ch

5

Analysis

Limited testing of third-party SMTP servers

We employ limited testing of third-party SMTP servers because they tend to be used by a great many domain names. Because we also continuously test a great many domain names, we want to avoid sending too many near-identical connections to these SMTP servers. It doesn't serve a practical purpose and also tends to get us on their bad side. TLS protocol testing, in particular, requires a lot of connections, which mean that we're often treated like spammers, even though we don't send any email. When testing third-party servers we may check only IP address per SMTP destination. When this is the case, the list of IP addresses shown here may not be complete. Further, in some situations with top services, we may show only the TLS configuration from a representative sample of their servers.

Some SMTP server assessments contain partial information

Comprehensive TLS assessments require many connections, which is exactly what many SMTP servers don't like. We implement a two-tier assessment approach. To give you some results as fast as possible, we perform shallow assessments that use only one connection per SMTP server. We then have a background process that performs complete assessments slowly, trying to accommodate each server individually. The results presented here contain partial information. If you come back later we may be able to provide complete assessment results.

Email TLS (SMTP)

Transport Layer Security (TLS) is the most widely used encryption protocol on the Internet. In combination with valid certificates, servers can establish trusted communication channels even with users who have never visited them before. Network attackers can't uncover what is being communicated, even when they can see all the traffic.

Test passed

Everything seems to be well configured. Well done.

TLS Configuration: mta-gw.infomaniak.ch (83.166.143.57)

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.3 TLS v1.2
Shows cipher suite configuration for this protocol version.TLS v1.3	Suite: TLS_AES_256_GCM_SHA384 Suite ID: 0x1302 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2	Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits)

Analysis

TLS 1.2 supported

Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.

Strong key exchange detected

Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.

Partial results shown

SMTP assessments usually take a long time. To get you some results faster, we initially perform shallow checks. If you come back later we may be able to show you complete results.

Relaxed TLS assessment criteria applied to SMTP on port 25

We apply relaxed assessment criteria when evaluating TLS configuration of SMTP servers on port 25. This is because most delivery agents fall back to delivering via plaintext on failure to negotiate encryption. Some configuration elements that can be abused to attack other ports and protocols (e.g., SSLv2 and export cipher suites) are penalized in the same way as for other protocols. We will review this policy in the future.

Email Certificates (SMTP)

A certificate is a digital document that contains a public key, some information about the entity associated with it, and a digital signature from the certificate issuer. It’s a mechanism that enables us to exchange, store, and use public keys. Being able to reliably verify the identity of a remote server is crucial in order to achieve secure encrypted communication.

Test passed

Everything seems to be well configured. Well done.

Certificate #1

Leaf certificate

mta-gw.infomaniak.ch
Issuer: Let's Encrypt
Not Before: 15 Aug 2026 21:45:51 UTC
Not After: 13 Nov 2026 21:45:50 UTC (expires in 1 month 11 days)
Key: RSA 2048 bits
Signature: SHA256withRSA
View details

Names	mta-gw.infomaniak.ch mx.infomaniak.com
Subject DN	CN=mta-gw.infomaniak.ch
Subject Key Identifier	0bcd9e344488f574b5234ade2a2bc777628b5d86
Serial	06dcd4421d82d1fc83771f10b6a544fd4845
Not Before	15 Aug 2026 21:45:51 UTC
Not After	13 Nov 2026 21:45:50 UTC
Validity period	90 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth
Must Staple	No
Issuer
Issuer DN	CN=YR2, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:40152d2679ed32209edf9a721dd6321f810c810c
Parent Certificate	http://yr2.i.lencr.org/
CRL	http://yr2.c.lencr.org/70.crl
Certificate Transparency
Signed Certificate Timestamps	15 Aug 2026 22:44:21 UTC \| Google 'Xenon2026h2' log \| Qualified 15 Aug 2026 22:44:22 UTC \| Let's Encrypt 'Willow2026h2' \| Qualified
Fingerprints
SHA1	e43c04be8299badea6dfed6c340ea04652b2526b
SHA256	4a7f65b62e1bf0ed10d9494e0f7a10a40ae6cf2b5f5b78188755c09a03ecd91a
SPKI SHA256	01bbbc3a65e5f2067aa43dbab107583e1a14567ed2569c63445d21e1de556926

Analysis

Strong private key

Good. The private key associated with this certificate is secure.

Strong signature algorithm

Good. This certificate uses a strong signature algorithm.

Certificate matches hostname

Good. The provided certificate matches the expected hostnames.

Certificate dates match

Good. The certificate is valid for use at this point of time.

Certificate has not been revoked

Good. This certificate has not been revoked.

Certificate satisfies Apple's CT compliance requirements

Good. This certificate satisfies Apple's CT requirements at present.

Certificate Chain

Leaf certificate

mta-gw.infomaniak.ch | 4a7f65b
Not After: 13 Nov 2026 21:45:50 UTC (expires in 1 month 11 days)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Names	mta-gw.infomaniak.ch mx.infomaniak.com
Subject DN	CN=mta-gw.infomaniak.ch
Subject Key Identifier	0bcd9e344488f574b5234ade2a2bc777628b5d86
Serial	06dcd4421d82d1fc83771f10b6a544fd4845
Not Before	15 Aug 2026 21:45:51 UTC
Not After	13 Nov 2026 21:45:50 UTC
Validity period	90 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth
Must Staple	No
Issuer
Issuer DN	CN=YR2, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:40152d2679ed32209edf9a721dd6321f810c810c
Parent Certificate	http://yr2.i.lencr.org/
CRL	http://yr2.c.lencr.org/70.crl
Certificate Transparency
Signed Certificate Timestamps	15 Aug 2026 22:44:21 UTC \| Google 'Xenon2026h2' log \| Qualified 15 Aug 2026 22:44:22 UTC \| Let's Encrypt 'Willow2026h2' \| Qualified
Fingerprints
SHA1	e43c04be8299badea6dfed6c340ea04652b2526b
SHA256	4a7f65b62e1bf0ed10d9494e0f7a10a40ae6cf2b5f5b78188755c09a03ecd91a
SPKI SHA256	01bbbc3a65e5f2067aa43dbab107583e1a14567ed2569c63445d21e1de556926

Intermediate certificate

YR2 | 238b85a
Not After: 02 Sep 2028 23:59:59 UTC (expires in 1 year 11 months)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Subject DN	CN=YR2, O=Let's Encrypt, C=US
Subject Key Identifier	40152d2679ed32209edf9a721dd6321f810c810c
Serial	4ebd24947e24d394802d84a52fd5b319
Not Before	03 Sep 2025 00:00:00 UTC
Not After	02 Sep 2028 23:59:59 UTC
Validity period	1096 days
Key Usage	digitalSignature, keyCertSign, cRLSign
Extended Key Usage	serverAuth
Issuer
Issuer DN	CN=Root YR, O=ISRG, C=US
Certification Authority	Let's Encrypt
Validation Type	Not Applicable
Authority Key Identifier	keyid:dee75b60d0226d40287d3f0d01fea4b552b45194
Parent Certificate	http://yr.i.lencr.org/
CRL	http://yr.c.lencr.org/
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	2d74d6dfd96eea55ad7baafa0d3c6552b2dadc37
SHA256	238b85a0099c65b970477d5724f1a1d475ce5058cffe4efa8733899bdb863c47
SPKI SHA256	9d637b3d27a9e570d07607b9ccadb80a70915c7af72afce12841b1b1da825fd1

Intermediate certificate

Root YR | 072639d
Not After: 02 Sep 2032 23:59:59 UTC (expires in 5 years 11 months)
Authentication: RSA 4096 bits (SHA256withRSA)
View details

Subject DN	CN=Root YR, O=ISRG, C=US
Subject Key Identifier	dee75b60d0226d40287d3f0d01fea4b552b45194
Serial	f24b6d17f9d9ad7cb1c9fea78782699f
Not Before	13 May 2026 00:00:00 UTC
Not After	02 Sep 2032 23:59:59 UTC
Validity period	2305 days
Key Usage	keyCertSign, cRLSign
Extended Key Usage	serverAuth
Issuer
Issuer DN	CN=ISRG Root X1, O=Internet Security Research Group, C=US
Certification Authority	Let's Encrypt
Validation Type	Not Applicable
Authority Key Identifier	keyid:79b459e67bb6e5e40173800888c81a58f6e99b6e
Parent Certificate	http://x1.i.lencr.org/
CRL	http://x1.c.lencr.org/
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	ab9d0263244dd0326eb67015705a667e79cfe998
SHA256	072639d0b140d5bffae16ad9c3f6cc6086040621f51ee61a6d46a8915c07cf76
SPKI SHA256	7e4e8838a8add6295de7ae3b047d3aba3488ab95db0a0aa56d897a00d8618bcf

Root certificate

ISRG Root X1 | 96bcec0
Not After: 04 Jun 2035 11:04:38 UTC (expires in 8 years 8 months)
Authentication: RSA 4096 bits (SHA256withRSA)
View details

Subject DN	CN=ISRG Root X1, O=Internet Security Research Group, C=US
Subject Key Identifier	79b459e67bb6e5e40173800888c81a58f6e99b6e
Serial	8210cfb0d240e3594463e0bb63828b00
Not Before	04 Jun 2015 11:04:38 UTC
Not After	04 Jun 2035 11:04:38 UTC
Key Usage	keyCertSign, cRLSign
Issuer
Issuer DN	CN=ISRG Root X1, O=Internet Security Research Group, C=US
Certification Authority	Let's Encrypt
Validation Type	Self-signed
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	cabd2a79a1076a31f21d253635cb039d4329a5e8
SHA256	96bcec06264976f37460779acf28c5a7cfe8a3c0aae11a8ffcee05c0bddf08c6
SPKI SHA256	0b9fa5a59eed715c26c1020c711b4f6ec42d58b0015e14337a39dad301c5afc3

Analysis

Certificate chain is correct

Good. This chain contains all the right certificates and in the right order.

Email DANE (SMTP)

DNS-based Authentication of Named Entities (DANE) is a bridge between DNSSEC and TLS. In one possible scenario, DANE can be used for public key pinning, building on an existing publicly-trusted certificate. In another approach, it can be used to completely bypass the CA ecosystem and establish trust using DNSSEC alone.

Test passed

Everything seems to be well configured. Well done.

DANE: mta-gw.infomaniak.ch (83.166.143.57)

Specifies which certificate in the chain is being pinned and how validation should be performed.Certificate Usage	Domain-issued certificate / DANE-EE (3)
Determines if the association is made with a certificate or with a public key (via its SPKI structure).Selector	SPKI structure (1)
Determines how matching is done; directly or via a hash. Matching Type	SHA2-256 (1)
Contains the data necessary to perform the matching. Data	01bbbc3a65e5f2067aa43dbab107583e1a14567ed2569c63445d21e1de556926 Leaf certificate: RSA 2048 bits Subject: CN=mta-gw.infomaniak.ch Issuer: CN=YR2, O=Let's Encrypt, C=US mta-gw.infomaniak.ch (RSA 2048 bits)

Analysis

Valid DANE configuration

Excellent. Your DANE configuration matches the certificate chain(s) provided by the service. Your TLS configuration enjoys the additional benefit of DANE validation.

SPF

Sender Policy Framework (SPF) is a protocol that allows domain name owners to control which internet hosts are allowed to send email on their behalf. This simple mechanism can be used to reduce the effect of email spoofing and cut down on spam.

Test passed

Everything seems to be well configured. Well done.

SPF Policy Information Main policy

Host where this policy is located.Location	infomaniak.com
SPF version used by this policy.v	spf1
Evaluates SPF policy specified in another DNS location. This directive is typically used to allow hosts controlled by another organization. include	spf.infomaniak.ch
Evaluates SPF policy specified in another DNS location. This directive is typically used to allow hosts controlled by another organization. include	_spf.mailrelay.rrpproxy.net
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	164.128.163.164
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	164.128.163.167
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	164.128.163.171
Evaluates SPF policy specified in another DNS location. This directive is typically used to allow hosts controlled by another organization. include	mailgun.org
This policy element always matches. It's normally used at the end of a policy to specify the handling of hosts that don't match earlier mechanisms. -all

Analysis

SPF policy found

Policy text: v=spf1 include:spf.infomaniak.ch include:_spf.mailrelay.rrpproxy.net ip4:164.128.163.164 ip4:164.128.163.167 ip4:164.128.163.171 include:mailgun.org -all

Location: infomaniak.com

SPF policy is valid

Good. Your SPF policy is syntactically valid.

Policy uses default fail

Excellent. This policy fails hosts that are not allowed to send email for this domain name.

Policy DNS lookups under limit

Good. Your policy stays under the limit of up to 10 DNS queries. The SPF specification Section 4.6.4. requires implementations to limit the total number of DNS queries. Policies that exceed the limit should not be used and may not work in practice.

Lookups: 10

SPF Policy Information Included policy

Host where this policy is located.Location	spf.infomaniak.ch
SPF version used by this policy.v	spf1
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	45.157.188.8/29
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	185.125.25.8/29
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	83.166.143.168/29
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	84.16.66.168/29
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	128.65.197.100
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	128.65.197.101
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	185.125.25.16/29
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	45.157.188.16/29
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	84.16.66.176/29
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	83.166.143.176/29
This mechanism tests whether the IP address being tested is contained within a given IPv6 network. ip6	2001:1600:19::/48
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	84.16.69.64/31
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	128.65.197.2/31
Evaluates SPF policy specified in another DNS location. This directive is typically used to allow hosts controlled by another organization. include	newsletter.infomaniak.com
This policy element always matches. It's normally used at the end of a policy to specify the handling of hosts that don't match earlier mechanisms. -all

SPF Policy Information Included policy

Host where this policy is located.Location	newsletter.infomaniak.com
SPF version used by this policy.v	spf1
Evaluates SPF policy specified in another DNS location. This directive is typically used to allow hosts controlled by another organization. include	amazonses.com
This policy element always matches. It's normally used at the end of a policy to specify the handling of hosts that don't match earlier mechanisms. ?all

SPF Policy Information Included policy

Host where this policy is located.Location	amazonses.com
SPF version used by this policy.v	spf1
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	199.255.192.0/22
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	199.127.232.0/22
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	54.240.0.0/18
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	69.169.224.0/20
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	23.249.208.0/20
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	23.251.224.0/19
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	76.223.176.0/20
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	54.240.64.0/18
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	76.223.128.0/19
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	216.221.160.0/19
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	206.55.144.0/20
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	24.110.64.0/18
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	98.77.0.0/16
This policy element always matches. It's normally used at the end of a policy to specify the handling of hosts that don't match earlier mechanisms. -all

SPF Policy Information Included policy

Host where this policy is located.Location	_spf.mailrelay.rrpproxy.net
SPF version used by this policy.v	spf1
Evaluates SPF policy specified in another DNS location. This directive is typically used to allow hosts controlled by another organization. include	spf.key-systems.net
This policy element always matches. It's normally used at the end of a policy to specify the handling of hosts that don't match earlier mechanisms. ~all

SPF Policy Information Included policy

Host where this policy is located.Location	spf.key-systems.net
SPF version used by this policy.v	spf1
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	109.234.111.22
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	109.234.111.38
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	109.234.111.46
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	109.234.104.246
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	109.234.104.254
This policy element always matches. It's normally used at the end of a policy to specify the handling of hosts that don't match earlier mechanisms. ~all

SPF Policy Information Included policy

Host where this policy is located.Location	mailgun.org
SPF version used by this policy.v	spf1
Evaluates SPF policy specified in another DNS location. This directive is typically used to allow hosts controlled by another organization. include	_spf.mailgun.org
Evaluates SPF policy specified in another DNS location. This directive is typically used to allow hosts controlled by another organization. include	_spf.eu.mailgun.org
This policy element always matches. It's normally used at the end of a policy to specify the handling of hosts that don't match earlier mechanisms. -all

SPF Policy Information Included policy

Host where this policy is located.Location	_spf.mailgun.org
SPF version used by this policy.v	spf1
Evaluates SPF policy specified in another DNS location. This directive is typically used to allow hosts controlled by another organization. include	_spf1.mailgun.org
Evaluates SPF policy specified in another DNS location. This directive is typically used to allow hosts controlled by another organization. include	_spf2.mailgun.org
This policy element always matches. It's normally used at the end of a policy to specify the handling of hosts that don't match earlier mechanisms. ~all

SPF Policy Information Included policy

Host where this policy is located.Location	_spf1.mailgun.org
SPF version used by this policy.v	spf1
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	159.135.224.0/20
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	69.72.32.0/20
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	204.220.90.0/23
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	204.220.92.0/22
This policy element always matches. It's normally used at the end of a policy to specify the handling of hosts that don't match earlier mechanisms. ~all

SPF Policy Information Included policy

Host where this policy is located.Location	_spf2.mailgun.org
SPF version used by this policy.v	spf1
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	161.38.192.0/20
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	143.55.224.0/21
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	143.55.232.0/22
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	159.112.240.0/20
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	198.244.48.0/20
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	204.220.168.0/21
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	204.220.176.0/20
This policy element always matches. It's normally used at the end of a policy to specify the handling of hosts that don't match earlier mechanisms. ~all

SPF Policy Information Included policy

Host where this policy is located.Location	_spf.eu.mailgun.org
SPF version used by this policy.v	spf1
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	141.193.32.0/23
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	159.135.140.80/29
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	159.135.132.128/25
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	161.38.204.0/22
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	87.253.232.0/21
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	185.189.236.0/22
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	185.211.120.0/22
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	185.250.236.0/22
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	143.55.236.0/22
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	198.244.60.0/22
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	204.220.160.0/20
This policy element always matches. It's normally used at the end of a policy to specify the handling of hosts that don't match earlier mechanisms. ~all

DMARC

Domain-based Message Authentication, Reporting, and Conformance (DMARC) is a scalable mechanism by which a mail-originating organization can express domain-level policies and preferences for message validation, disposition, and reporting, that a mail-receiving organization can use to improve mail handling.

Test passed

Everything seems to be well configured. Well done.

DMARC Policy Information

The location from which we obtained this policy.Policy location	_dmarc.infomaniak.com
DMARC version used by this policy.v	DMARC1
Indicates the policy to be enacted by the receiver at the request of the domain owner. Possible values are: none, quarantine, and reject.p	reject
Requested mail receiver policy for all subdomains. Same format as for the p tag.sp	reject
Addresses to which aggregate feedback is to be sent.rua	mailto:dmarc-report@infomaniak.com
Addresses to which message-specific failure information is to be reported.ruf	mailto:dmarc-report@infomaniak.com

Analysis

DMARC policy found

Policy: v=DMARC1;p=reject;sp=reject;rua=mailto:dmarc-report@infomaniak.com;ruf=mailto:dmarc-report@infomaniak.com

Host: _dmarc.infomaniak.com

Policy is valid

Good. You have a valid DMARC policy.

MTA Strict Transport Security

SMTP Mail Transfer Agent Strict Transport Security (MTA-STS) is a mechanism enabling mail service providers to declare their ability to receive Transport Layer Security (TLS) secure SMTP connections, and to specify whether sending SMTP servers should refuse to deliver to MX hosts that do not offer TLS with a trusted server certificate.

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

SMTP TLS Reporting

SMTP TLS Reporting (RFC 8460), or TLS-RPT for short, describes a reporting mechanism and format by which systems sending email can share statistics and specific information about potential failures with recipient domains. Recipient domains can then use this information to both detect potential attacks and diagnose unintentional misconfigurations. TLS-RPT can be used with DANE or MTA-STS.

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

HTTP (80)

To observe your HTTP implementation, we submit a request to the homepage of your site on port 80, follow all redirections (even when they take us to other domain names), and record the returned HTTP headers.

Test passed

Everything seems to be well configured. Well done.

URL: http://infomaniak.com/

1

http://infomaniak.com/

HTTP/1.1 308 Permanent Redirect

content-length	0
location	https://infomaniak.com/
x-request-id

2

https://infomaniak.com/

HTTP/1.1 301 Moved Permanently

content-length	0
location	https://www.infomaniak.com/
strict-transport-security	max-age=63072000;
x-request-id	a64238b9-fc8a-4f77-ad99-c575a5b1a910

3

https://www.infomaniak.com/

HTTP/1.1 302 Found

date	Fri, 02 Oct 2026 12:49:54 GMT
content-type	text/html; charset=iso-8859-1
content-length	253
set-cookie	ingress-site-infomaniak=1790945395.118.639.524436\|dac64a6785aa6904b0236e5d0464075f; Max-Age=3600; Path=/; HttpOnly
x-content-type-options	nosniff
location	https://www.infomaniak.com/en
cache-control	max-age=172800
expires	Sun, 04 Oct 2026 12:49:54 GMT
strict-transport-security	max-age=63072000;
x-request-id	12776709-b5d7-428e-9f54-925fb3d1dd69

4

https://www.infomaniak.com/en

HTTP/1.1 200 OK

date	Fri, 02 Oct 2026 12:49:54 GMT
content-type	text/html; charset=utf-8
transfer-encoding	chunked
x-content-type-options	nosniff
set-cookie	STATIC_CURRENCY=CHF; expires=Sat, 02 Oct 2027 12:49:54 GMT; Max-Age=31536000; path=/
set-cookie	STATIC_COUNTRY=US; expires=Sat, 03 Oct 2026 12:49:54 GMT; Max-Age=86400; path=/
cache-control	no-cache, private, max-age=172800
vary	X-Inertia,Accept-Encoding
x-content-type-options	nosniff
referrer-policy	strict-origin-when-cross-origin
permissions-policy	camera=(), microphone=(), geolocation=(self), browsing-topics=()
cross-origin-opener-policy	same-origin
x-frame-options	SAMEORIGIN
content-security-policy-report-only	default-src; script-src https://.infomaniak.com 'self' blob: data: https://infomaniak.com https://www.google.com https://www.gstatic.com https://maps.googleapis.com https://cdn.trustindex.io 'nonce-Gt8bR8vz3zpEgdFKG82OZqTh4fd6wbpL0A6mEoDO'; script-src-elem https://.infomaniak.com 'self' blob: data: https://infomaniak.com https://www.google.com https://www.gstatic.com https://maps.googleapis.com https://cdn.trustindex.io 'nonce-Gt8bR8vz3zpEgdFKG82OZqTh4fd6wbpL0A6mEoDO'; style-src https://.infomaniak.com 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src https://.infomaniak.com 'self' data: https://fonts.gstatic.com; img-src https://.infomaniak.com 'self' data: blob: android-webview-video-poster https://.infomaniak.ch; connect-src https://.infomaniak.com 'self' wss://.infomaniak.com:* https://infomaniak.com https://www.google.com https://maps.googleapis.com https://.trustindex.io; child-src https://.infomaniak.com https://www.google.com https://www.youtube.com; frame-src https://.infomaniak.com https://www.google.com https://www.youtube.com; worker-src https://.infomaniak.com 'self' blob:; object-src 'none'; base-uri 'self'; frame-ancestors 'self'; form-action https://.infomaniak.com 'self' https://.infomaniak.ch; upgrade-insecure-requests; report-uri /api/csp-report;
set-cookie	XSRF-TOKEN=eyJpdiI6IkxIS0lLcFlRc1pTb2pRVHJ5VlB5T1E9PSIsInZhbHVlIjoiMlgwcytBMVBEcm5qdklsMDlmVzBlS2pZNHlkZjVLckpIam54SnNNT2lXQll6Tzc1QjZWNytlcm9qaHp1RkgzaERoV3NySVlHbnNWTU14dkcreHpsTTZuTmlxQ2ZtaEFnMzNWWHh6enBUU2ltcUdrSmRlVzZjK1kra0JndGx2WFkiLCJtYWMiOiIxYmVkYzczN2NhYTg1MzJlYTdiOWIxN2YzMTJmMDg1NThlNjdkMzFhNmY0ZGFjMjBiY2VmMTkyZDY5N2VjMjc3IiwidGFnIjoiIn0%3D; expires=Fri, 02 Oct 2026 14:49:54 GMT; Max-Age=7200; path=/; secure; samesite=lax
set-cookie	site_infomaniak_session=eyJpdiI6IjcxaXNJRHpoZ1duK3hJQ3FpMUtXN3c9PSIsInZhbHVlIjoiS2RmU2RXdUFQUmxvUFZWdVpvcCtza2txU1g0MWNWSm1vMXlRVUhtZFkvZTVJRHRTODkzcENtclFVN3ZKZ3QyTUZpb1RqMmxHYXRoOTlMK2txWnFYUzczWFNjTHhVQU5aL3Mza05xT0Q5YlU4SFJqSTNBbEc5WkprWWhDVldJSWwiLCJtYWMiOiIxM2Y5MGNmODI1MmMwN2Q2MTJkN2EyMTg0ODE4OWQ0MDFjMTdmMTUxMTAzZDAzZDZlOGJkMGUxMTlkMDIyZDc5IiwidGFnIjoiIn0%3D; expires=Fri, 02 Oct 2026 14:49:54 GMT; Max-Age=7200; path=/; secure; httponly; samesite=lax
set-cookie	locale=eyJpdiI6ImowTVFxWXh5ZW1xcklxWG9jbjhyUGc9PSIsInZhbHVlIjoic0JWUUtBRkxKMHZEYTVuRjNPSXlxTkljZkVyR29kV3pGVkYrWEx4Q0s1QUt3clhZT043SXB0ck5lYnd5QndjcSIsIm1hYyI6ImM3ZmQ4MTg3YjMwYmFhNWRlNDEyNDU2MTIyMzNjYTU3NmU1M2ZkZDNhMWRkMDkwMmY0NGU2ZjdmY2U0Y2QyYTkiLCJ0YWciOiIifQ%3D%3D; expires=Sun, 01 Nov 2026 12:49:54 GMT; Max-Age=2592000; path=/; secure; httponly; samesite=lax
set-cookie	mDR1Bd0zdDm3ijrmuslSHKkyfhoMH3cgBqVvmo3r=eyJpdiI6IjM3aGt0L0tzSkt5dHFEMjlydGJ3TkE9PSIsInZhbHVlIjoicVk5MzNld2FGRGZ1MEE0OVpDdGswVjh2QUNxTWJwWlhYUHFyd3NvY2huNXJMTWdCSmNzNS9NUVJiNk5IdG5vTCtHYjFxRzRXc2twd2wxMWJQOHNFdkd6WmNHL05KK0VuT0JrQkpjUHo5OVM1Wjg1bk5tNzJDRzlpQXJpZGwxR0FZT0EvRjNOOCtUOXJXWVBidytlS2lSekIvRDFJNGV6VGs3R3Y2KzI5bmRKWHBVaFNYQTVTdHZOVEc4Zm5mMm5CZmRtdTduZmg2ejVsdE1tY3dSL1I1bUs4TWpTNHJubEJEMGhXa2sycTk0eTZwRmV5QVdvUTdsMUx5c0NUdWlZdktSQVNsWDhXdDlHalFGU0xyelpUVEFuVWJmQjlVbW9nMnR4bHdYTlN5eUJ5T3A0VkhUZGhZbjVPV0RMc1cyaGxNMTgvek44Y3gvTFlnQTBxNXVMWm0xZ0xYOGs1TUdNTC94Rk9xR0hDb3lISFJ0aEhaRXJJSnNlb1RtaDFDMjNoN1lEeWIzbWpWVDJaV1p2bUtlZ1BwY2tkQmdNZVE1bGY2QXN1akE0RkZ5S3JwYU9sTitoS21sOE9lMXVkZG4rZSIsIm1hYyI6ImI5ZGQ3MTVhM2RiOTA3ZTM4NzlkNTgxNGQzNGNjYmRmYTkwZTQ0NGJlZGEzZjE1YjcxZTNlYTllMjNjNGVlMWQiLCJ0YWciOiIifQ%3D%3D; expires=Fri, 02 Oct 2026 14:49:54 GMT; Max-Age=7200; path=/; secure; httponly; samesite=lax
expires	Sun, 04 Oct 2026 12:49:54 GMT
strict-transport-security	max-age=63072000;
x-request-id	36a2a540-a36f-48a8-835f-67a763599b2b

Analysis

HTTP redirects to HTTPS

Good. This plaintext HTTP server redirects to HTTPS.

URL: http://www.infomaniak.com/

1

http://www.infomaniak.com/

HTTP/1.1 308 Permanent Redirect

content-length	0
location	https://www.infomaniak.com/
x-request-id

2

https://www.infomaniak.com/

HTTP/1.1 302 Found

date	Fri, 02 Oct 2026 12:49:55 GMT
content-type	text/html; charset=iso-8859-1
content-length	253
set-cookie	ingress-site-infomaniak=1790945396.854.618.777253\|dac64a6785aa6904b0236e5d0464075f; Max-Age=3600; Path=/; HttpOnly
x-content-type-options	nosniff
location	https://www.infomaniak.com/en
cache-control	max-age=172800
expires	Sun, 04 Oct 2026 12:49:55 GMT
strict-transport-security	max-age=63072000;
x-request-id	1521fdda-5506-4547-aca0-4804b39e002a

3

https://www.infomaniak.com/en

HTTP/1.1 200 OK

date	Fri, 02 Oct 2026 12:49:56 GMT
content-type	text/html; charset=utf-8
transfer-encoding	chunked
x-content-type-options	nosniff
set-cookie	STATIC_CURRENCY=CHF; expires=Sat, 02 Oct 2027 12:49:56 GMT; Max-Age=31536000; path=/
set-cookie	STATIC_COUNTRY=US; expires=Sat, 03 Oct 2026 12:49:56 GMT; Max-Age=86400; path=/
cache-control	no-cache, private, max-age=172800
vary	X-Inertia,Accept-Encoding
x-content-type-options	nosniff
referrer-policy	strict-origin-when-cross-origin
permissions-policy	camera=(), microphone=(), geolocation=(self), browsing-topics=()
cross-origin-opener-policy	same-origin
x-frame-options	SAMEORIGIN
content-security-policy-report-only	default-src; script-src https://.infomaniak.com 'self' blob: data: https://infomaniak.com https://www.google.com https://www.gstatic.com https://maps.googleapis.com https://cdn.trustindex.io 'nonce-UlOhuz6lTYBzQlzXrIpxFU5ZvscEjjjBoJgLEGML'; script-src-elem https://.infomaniak.com 'self' blob: data: https://infomaniak.com https://www.google.com https://www.gstatic.com https://maps.googleapis.com https://cdn.trustindex.io 'nonce-UlOhuz6lTYBzQlzXrIpxFU5ZvscEjjjBoJgLEGML'; style-src https://.infomaniak.com 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src https://.infomaniak.com 'self' data: https://fonts.gstatic.com; img-src https://.infomaniak.com 'self' data: blob: android-webview-video-poster https://.infomaniak.ch; connect-src https://.infomaniak.com 'self' wss://.infomaniak.com:* https://infomaniak.com https://www.google.com https://maps.googleapis.com https://.trustindex.io; child-src https://.infomaniak.com https://www.google.com https://www.youtube.com; frame-src https://.infomaniak.com https://www.google.com https://www.youtube.com; worker-src https://.infomaniak.com 'self' blob:; object-src 'none'; base-uri 'self'; frame-ancestors 'self'; form-action https://.infomaniak.com 'self' https://.infomaniak.ch; upgrade-insecure-requests; report-uri /api/csp-report;
set-cookie	XSRF-TOKEN=eyJpdiI6Im1OVHJpZ2gwZEw0aTdkN2s3Ykxvb0E9PSIsInZhbHVlIjoiNVhUNStYcE9pNllpeFRpdGlJNVlWYXlEZHZzR2ZzSktIOUcybDlwV2U2emlqZnRMVEhzWmkvYWVKeU9HWjVacVBpd1kwZnF5L1NBcGs0R3d5WFQ5T3U2Uy9VR2RNVlR2QXVOK1lLUG1iVmdDenA5enY4NytMQ3VCT2FBN0Z2STgiLCJtYWMiOiJkOWY5MGEzZDlmMDA1MTM1NGFiZGY2NDZhODFiMjRmM2UxOTUyZmMyMDVmODIyZGI2MDhmMDNmYTU2YjJjMzg3IiwidGFnIjoiIn0%3D; expires=Fri, 02 Oct 2026 14:49:56 GMT; Max-Age=7200; path=/; secure; samesite=lax
set-cookie	site_infomaniak_session=eyJpdiI6Im1KMk1zV0lKYW1Gb2U2K1dlNVNEK3c9PSIsInZhbHVlIjoiNFdoWEozbVd3c1k3U2IvUGlLUTNlaGJpWnIyWmFKbXRzWk5ZVGRYYkRWMHo3cURqKzlYMVhVWTU5ckhUcnp4bUNpS1VjbVdhR2gxd2VZc0Z1KzRiNjlBeWt4UHFSa3U2MlpMY3prd2g4SFYxcVR0TGNQVjJ5ZzR3azJhVTU0VjUiLCJtYWMiOiIyYWUyYjhmMjQwNTk2MTE5ZjQ0MDBmNzRhZTg2MTMzMTczZTY1MzA3NjNhZTBjZjVmOTcyN2M3MjUwNTJmNGFhIiwidGFnIjoiIn0%3D; expires=Fri, 02 Oct 2026 14:49:56 GMT; Max-Age=7200; path=/; secure; httponly; samesite=lax
set-cookie	locale=eyJpdiI6IkpyVWc4MjU5N2YvcGlTZUZXWHRna2c9PSIsInZhbHVlIjoiRXZvYnp6YjBuc2JMYzdobDkyNUMyOERpWFpIWjBKQlppZ2VqVlEzNjd2UjV2SEpxU2gweTJodktSWFkzQmttayIsIm1hYyI6Ijc1NzFjZjVhZjEzNTU2NTcxYjkyYTk4NDEwNTg0NmFlMWY5MGNiN2U5MjM0MjU3ODEyOGI3ODFlZDk2YjU5ODAiLCJ0YWciOiIifQ%3D%3D; expires=Sun, 01 Nov 2026 12:49:56 GMT; Max-Age=2592000; path=/; secure; httponly; samesite=lax
set-cookie	7wDm2aFk7QvDPzoQHwuCPbyZONkDQzLIbzImMJCG=eyJpdiI6InBvZ25LY3ZDYllBcHFFYndJVkc0dUE9PSIsInZhbHVlIjoieW1tcEFOZ0xjRlo5NUt0bGxSMWtaUXYyOU5tR3lIZnQrN3ZKU24wNnBOQ0RyTldnK0NmOEtDOEdLUVVUejFhRjlJZ0tYOEg2Nnh6V0Z0QVNXelVGd1pBWmpRSzBGWjB4SHdGVlJPZDQ2c3dQTzJRb29jU09pQSs1NEx2UDRacERQOWpKbEdWWUNaNmJZdlpKbHJZWG1YTGExLy9hYmZiR3BnUjR3bWdmc1JlVFIzakkwaTN5K2pKSnBPMVJZVWZheUh6RmZuOEVzY2JNc3c3V3BCakx5Z2lsR0xKNEJHLytBeEE1S0huS0RzWkJmaEk5Z3dSUkFBdXoyRmNKazF2RlpEYjEraVBFRmNTT0xlVDZGZytQOGZZa29GNjdZK0FLaTdMc0cxUmtyajRiK2JyTEZCenpieU9UL29TY1Awdm1JYVNFNnQ0dmk3VjliWGxvcHhCdU5RQ3lBdWVZTlVsUTVKbWVab2Zia3dXdHhESmovOGxYdUx5SXN5QkdwZS9QZ1pPNXA0UmtoVEdHaFBhZjR6T1V2N3krODI4aUJPdGpoSksvOFdvM2lrbkh5bEZMTFowZTF3L0hNZGVzUTg2YSIsIm1hYyI6IjNlN2RjNzdkOTNlMGNiYzY2NzRmNTliZjA1MjBjMTZhMmY4ODQ4M2I0Mjk4ZDQxNWRiNDU1ZmFlMjJhOGFiYWQiLCJ0YWciOiIifQ%3D%3D; expires=Fri, 02 Oct 2026 14:49:56 GMT; Max-Age=7200; path=/; secure; httponly; samesite=lax
expires	Sun, 04 Oct 2026 12:49:56 GMT
strict-transport-security	max-age=63072000;
x-request-id	a96783c6-cebc-4331-bea8-cab39254e5b1

Analysis

HTTP redirects to HTTPS

Good. This plaintext HTTP server redirects to HTTPS.

HTTP (443)

To observe your HTTPS implementation, we submit a request to the homepage of your site on port 443, follow all redirections (even when they take us to other domain names), and record the returned HTTP headers. We use the most recent set of headers returned from the tested hostname for further tests such as HSTS and HPKP.

Test passed

Everything seems to be well configured. Well done.

URL: https://infomaniak.com/

1

https://infomaniak.com/

HTTP/1.1 301 Moved Permanently

content-length	0
location	https://www.infomaniak.com/
strict-transport-security	max-age=63072000;
x-request-id	72a79384-f510-4275-be9b-ea6e7e88ef90

2

https://www.infomaniak.com/

HTTP/1.1 302 Found

date	Fri, 02 Oct 2026 12:49:57 GMT
content-type	text/html; charset=iso-8859-1
content-length	253
set-cookie	ingress-site-infomaniak=1790945398.83.579.301672\|dac64a6785aa6904b0236e5d0464075f; Max-Age=3600; Path=/; HttpOnly
x-content-type-options	nosniff
location	https://www.infomaniak.com/en
cache-control	max-age=172800
expires	Sun, 04 Oct 2026 12:49:57 GMT
strict-transport-security	max-age=63072000;
x-request-id	97cb9cbf-d40c-404c-b7c6-2872079064f6

3

https://www.infomaniak.com/en

HTTP/1.1 200 OK

date	Fri, 02 Oct 2026 12:49:58 GMT
content-type	text/html; charset=utf-8
transfer-encoding	chunked
x-content-type-options	nosniff
set-cookie	STATIC_CURRENCY=CHF; expires=Sat, 02 Oct 2027 12:49:58 GMT; Max-Age=31536000; path=/
set-cookie	STATIC_COUNTRY=US; expires=Sat, 03 Oct 2026 12:49:58 GMT; Max-Age=86400; path=/
cache-control	no-cache, private, max-age=172800
vary	X-Inertia,Accept-Encoding
x-content-type-options	nosniff
referrer-policy	strict-origin-when-cross-origin
permissions-policy	camera=(), microphone=(), geolocation=(self), browsing-topics=()
cross-origin-opener-policy	same-origin
x-frame-options	SAMEORIGIN
content-security-policy-report-only	default-src; script-src https://.infomaniak.com 'self' blob: data: https://infomaniak.com https://www.google.com https://www.gstatic.com https://maps.googleapis.com https://cdn.trustindex.io 'nonce-gA3jv66uzXIRMGhvO7CS6s9E1If4E9R2gasiu42U'; script-src-elem https://.infomaniak.com 'self' blob: data: https://infomaniak.com https://www.google.com https://www.gstatic.com https://maps.googleapis.com https://cdn.trustindex.io 'nonce-gA3jv66uzXIRMGhvO7CS6s9E1If4E9R2gasiu42U'; style-src https://.infomaniak.com 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src https://.infomaniak.com 'self' data: https://fonts.gstatic.com; img-src https://.infomaniak.com 'self' data: blob: android-webview-video-poster https://.infomaniak.ch; connect-src https://.infomaniak.com 'self' wss://.infomaniak.com:* https://infomaniak.com https://www.google.com https://maps.googleapis.com https://.trustindex.io; child-src https://.infomaniak.com https://www.google.com https://www.youtube.com; frame-src https://.infomaniak.com https://www.google.com https://www.youtube.com; worker-src https://.infomaniak.com 'self' blob:; object-src 'none'; base-uri 'self'; frame-ancestors 'self'; form-action https://.infomaniak.com 'self' https://.infomaniak.ch; upgrade-insecure-requests; report-uri /api/csp-report;
set-cookie	XSRF-TOKEN=eyJpdiI6Im9IYXovSGgyMGVKcTQ2QWNpd0MxSHc9PSIsInZhbHVlIjoiY2VPdXRhOXdsVGQyd2VHTklnRkN3cTZuSWF0b3ZWUEpCREh5YnkzK0w1WVpLMGdkc2hVbFFSbUp6R2lyOUMxeHVUWGRONE13YXg1TkdYbU13dWhydWU2NTY5U0dtUkVRVzRZbUZGWXJRQ1E0RjFjNDlvbGZ2MEZ4MFlCQ3NwWVEiLCJtYWMiOiJkM2E5ZmNjNmFjNjA0ZThlNzA0ODU5YzM1OWNiOTgwNzUxYWM2ZmE3NzY1NWJiMTNmMDdiZjM0MzUwNmY3NDhhIiwidGFnIjoiIn0%3D; expires=Fri, 02 Oct 2026 14:49:58 GMT; Max-Age=7200; path=/; secure; samesite=lax
set-cookie	site_infomaniak_session=eyJpdiI6IlpBcitwMXRUS01NdXpsYjZiRHVMMlE9PSIsInZhbHVlIjoiS3I1YU9BZFAxeWJrWng0V21EZWFENmo5SzRuY2wxdWFrNnhFcFZGWHhpYWVjZkhPR0dQVFQvaWdrQnNlS05BQjZlL0tJenU3ZTBWSExRaGJwZmp1WXhHM1RZV3lJMGI4YjVRdjZQVDZFY3ozMy9BOUJmMWRKNEFpYm5ndXVLYnoiLCJtYWMiOiJjNjhkNTEyNjMzZWM5NjExNGU2MDhhODhiZDVlZjE5NTYxNmQyZTVjNDY2MjY3OTYwY2VjMjUwMjlkNDUzYzc4IiwidGFnIjoiIn0%3D; expires=Fri, 02 Oct 2026 14:49:58 GMT; Max-Age=7200; path=/; secure; httponly; samesite=lax
set-cookie	locale=eyJpdiI6IlNNbFhNcFcwU2ptNzVxNE0vd1BtdkE9PSIsInZhbHVlIjoiMVRCeW5SYzRlOGJGelV5M3Rmakh1Sm5TNnFEQldrS1hjbkdJeW40Sml4dzR6bXFxcStLQUtGSXh0eHk3MHhuWCIsIm1hYyI6ImNjNjRmYTMzNzkzMzQ0NzgyYWYxNDg1MDAxZmJlNjA0YmJiZTMyMzg3NmMxYTVkMTk5MTJmZTUzZWQ3MGEwN2MiLCJ0YWciOiIifQ%3D%3D; expires=Sun, 01 Nov 2026 12:49:58 GMT; Max-Age=2592000; path=/; secure; httponly; samesite=lax
set-cookie	TBdknaTHBeMTLwknLuvqaAFqrfJhy5SxPGXksPrW=eyJpdiI6IlRKN25LT1BORy8zaklDbndRVitSNnc9PSIsInZhbHVlIjoidjFNUVU4TjlOK0lvRUgyc2k5WTFhVHVabWlEZDdmZkxEVlhxMEd0NjRXN2dkK3hSYk1mMGZoeW5YWG8wQ3pxM1phcGZXRUtkejlUL1JDSUhhWEdHUzZ2NVY5YmpSN2pHVUFqTi9DM25PTTZmV3hwTWFNNFR0UGNicnFVb0lRZFZyOGdaZUxGZEhpcElRZE9LV3pmQWNYV3hEUnUwVnpwdnFqeGUvSXhjQXNRR0w4QjFBelBvQWUzeHQ5bk40SDN2aDNXV1pZZUp3NVhreTRNSGltMGlWTmxGQmM4QXJWdzZnQ0l2V1VaNDkvZ1ZTMXNwbFplNUNuZFBZaGF2TjRmeHB0RUsvVERteE5Qc1VUSk5TbEV6S1RJc2ZWenJvdUNseXliRmNrV2hGeFFkdktvM3Z1UzVrbldkUVcyczVORkJRQzl1NXYzZC9URG1UTWhaYWgzVHN1elU5N0d1dndoQVovM3FtNzJnTmcyejNXRTRBRGs5WkU4aG15ZjdFTVdNemJIR0FWUW1oMjEyVzBERjlUclMrQkROSGREZXl4c0kvSkFxMGJBYjBRVWV5aTdEdUhnTWcxTE1FSFM5RjRYOCIsIm1hYyI6IjhlZTI5MjE1ODY1ZjI4NDJkMzUwOWY1NmRlNzkwNzUwNzQ3NzdiY2YxNjU4ZmI2YjA3ZjFjZTkzYzMzODBjNzUiLCJ0YWciOiIifQ%3D%3D; expires=Fri, 02 Oct 2026 14:49:58 GMT; Max-Age=7200; path=/; secure; httponly; samesite=lax
expires	Sun, 04 Oct 2026 12:49:58 GMT
strict-transport-security	max-age=63072000;
x-request-id	6c9ef54c-58de-43fd-8e29-c8296046ca18

URL: https://www.infomaniak.com/

1

https://www.infomaniak.com/

HTTP/1.1 302 Found

date	Fri, 02 Oct 2026 12:49:59 GMT
content-type	text/html; charset=iso-8859-1
content-length	253
set-cookie	ingress-site-infomaniak=1790945400.366.618.963773\|dac64a6785aa6904b0236e5d0464075f; Max-Age=3600; Path=/; HttpOnly
x-content-type-options	nosniff
location	https://www.infomaniak.com/en
cache-control	max-age=172800
expires	Sun, 04 Oct 2026 12:49:59 GMT
strict-transport-security	max-age=63072000;
x-request-id	7434d6f9-95c7-473a-88da-b051ad6cf0f6

2

https://www.infomaniak.com/en

HTTP/1.1 200 OK

date	Fri, 02 Oct 2026 12:49:59 GMT
content-type	text/html; charset=utf-8
transfer-encoding	chunked
x-content-type-options	nosniff
set-cookie	STATIC_CURRENCY=CHF; expires=Sat, 02 Oct 2027 12:49:59 GMT; Max-Age=31536000; path=/
set-cookie	STATIC_COUNTRY=US; expires=Sat, 03 Oct 2026 12:49:59 GMT; Max-Age=86400; path=/
cache-control	no-cache, private, max-age=172800
vary	X-Inertia,Accept-Encoding
x-content-type-options	nosniff
referrer-policy	strict-origin-when-cross-origin
permissions-policy	camera=(), microphone=(), geolocation=(self), browsing-topics=()
cross-origin-opener-policy	same-origin
x-frame-options	SAMEORIGIN
content-security-policy-report-only	default-src; script-src https://.infomaniak.com 'self' blob: data: https://infomaniak.com https://www.google.com https://www.gstatic.com https://maps.googleapis.com https://cdn.trustindex.io 'nonce-ts23ekE2GSUcoAzY7LJnyOkp2IFzBg53OHpgH7KG'; script-src-elem https://.infomaniak.com 'self' blob: data: https://infomaniak.com https://www.google.com https://www.gstatic.com https://maps.googleapis.com https://cdn.trustindex.io 'nonce-ts23ekE2GSUcoAzY7LJnyOkp2IFzBg53OHpgH7KG'; style-src https://.infomaniak.com 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src https://.infomaniak.com 'self' data: https://fonts.gstatic.com; img-src https://.infomaniak.com 'self' data: blob: android-webview-video-poster https://.infomaniak.ch; connect-src https://.infomaniak.com 'self' wss://.infomaniak.com:* https://infomaniak.com https://www.google.com https://maps.googleapis.com https://.trustindex.io; child-src https://.infomaniak.com https://www.google.com https://www.youtube.com; frame-src https://.infomaniak.com https://www.google.com https://www.youtube.com; worker-src https://.infomaniak.com 'self' blob:; object-src 'none'; base-uri 'self'; frame-ancestors 'self'; form-action https://.infomaniak.com 'self' https://.infomaniak.ch; upgrade-insecure-requests; report-uri /api/csp-report;
set-cookie	XSRF-TOKEN=eyJpdiI6ImFCL3pYL1NDdnRZQ1M3UFFoRWFVTlE9PSIsInZhbHVlIjoiZnc2UVY3VEU1YTY2NFZ3RDliSHhhQjBQelErZXMvRWswWFBuSFNvNFdlTlNkQkoxeGR1UEQ5SStFZFN6V3gvbVQ2VVU5bTA5NTlNR1dFU3U5NHVpT2tud3hWb1Rzd0lVS1FLSE55NXRXbFdWQzJ5V0xRdlFLT1JjQXhJczVOWU4iLCJtYWMiOiI0Y2YxNTE2N2Y5ZDE1NjE5ODQ5OWE0OGVmMTI1ZDhjOWRjYWViOGMxM2NkZGViNDdjNzBmMGQwZDk1MzE5NmNlIiwidGFnIjoiIn0%3D; expires=Fri, 02 Oct 2026 14:49:59 GMT; Max-Age=7200; path=/; secure; samesite=lax
set-cookie	site_infomaniak_session=eyJpdiI6ImJPMWQ4TGxGV1lodnVvQ2llVENoQ1E9PSIsInZhbHVlIjoiTmJiVmY2aHhrV0Vyd0N1NXhMNk05M3pvVDNpSzREcXgzT3gwaGJMaW1JcjBaR2ZoaEdkSnNVZU05WCt4aWlZaU1kQ1NET3lTTDMwbnFodzR2aUdJdytzN1Rod0hKZm5hWHRNU1dWN242U2FtZkh3WFBLOGV4dllNOEpXWitlZ28iLCJtYWMiOiJhNjdjMDU2Yzk2MTI0YzhjZmJjY2U0MTk4NTk1ZGIyNTYzOWE2MTRjY2FjNDAxNWI1ZmYzYzA2NzY3OTU3M2Y0IiwidGFnIjoiIn0%3D; expires=Fri, 02 Oct 2026 14:49:59 GMT; Max-Age=7200; path=/; secure; httponly; samesite=lax
set-cookie	locale=eyJpdiI6IkxGcjJSamNBOXVwTGpkT3Y0MGhiMFE9PSIsInZhbHVlIjoiSDJ2cXd6VGNLbU4relZ4T2RHUURNQTBFWWJPWjk2dlpCWENZa0wrNUJ3eVdmYzlkbDRMNGFxWCs3M1JOOEdpTyIsIm1hYyI6IjRkMmQyNDIwNzZkYzE5MTQ5MDY5ZTgyNDJmOTNmMzFjYTIxNWRlZTlmYWQ3ZjdhMDRkMWNmZGRiYWIxYWQ2OWQiLCJ0YWciOiIifQ%3D%3D; expires=Sun, 01 Nov 2026 12:49:59 GMT; Max-Age=2592000; path=/; secure; httponly; samesite=lax
set-cookie	JQjGNaIPH534NypDfdpq8wsdtVhM2DSY2xBkxb6C=eyJpdiI6IlpqblNIYWkrcDlKL2dtQjVFb0Z5OGc9PSIsInZhbHVlIjoiR0JnbHRxSnZGeTUwYm5oMTliTlY4WTUzTDIzMUpLczBoRE93ZDBWaVF6cmxIZmZJVWF1ODl4R2hhcGZ4MExtR3VCNm11M3RYV1phNXBqaXUzY2dLTVI1WEdpQm1xTXVwYkYwSlZHVzNBYUFESDVYdXYzSVZiUnAxS0xscVc4bEJkQ0JUYkFIVjRka3V2b1lDTlFXWXVSM3lJdFdUeHdQcVFVMWRFWGdoeEJqb05Ga0dhbE51RjNlSnFLVkxua3lrbitvMHVFNlMwZ0VIT0hEcHo5b053NlF0MjFSQmRQdjh2Qk5NRWFaT2NaVmRkaW9QYThNOWlxQ0ZmcS9pUm1TVllUVWdOd1FEN2ZOd3hxOWNoZEVJa0NjV2wxMEJmemc5UDB2ZStkdndSdU1UVHYyR3BSSzNXYkRwM054MUNpKzMrZVcyMVRveWFQWDNRRmpVdHdlbzN0NWhvVENnMWtjYk5EbzV0ek90SUFnckIrT3JjY3NubTI1Q2g4eEQzUERmM2kzemJLZTR3cjF0NnVSVjZFd05ZT0pxMGJNMkpoQjR5WDhtUmQwYkk5KzJ1bUJDT1V0NS9YSlR1dTBRMkR4LyIsIm1hYyI6ImIxNDA1ZGQ4MWU3MGEyNTc2NDkzMDIwMDE5NDAyNGNlMWNkMDA0OWJlODQyMmFhZDBlOWMzMTM5ZGJhOGQ2YzAiLCJ0YWciOiIifQ%3D%3D; expires=Fri, 02 Oct 2026 14:49:59 GMT; Max-Age=7200; path=/; secure; httponly; samesite=lax
expires	Sun, 04 Oct 2026 12:49:59 GMT
strict-transport-security	max-age=63072000;
x-request-id	bb89140f-a675-441c-8068-877ec8aa9c18

WWW TLS

Transport Layer Security (TLS) is the most widely used encryption protocol on the Internet. In combination with valid certificates, servers can establish trusted communication channels even with users who have never visited them before. Network attackers can't uncover what is being communicated, even when they can see all the traffic.

Test passed

Everything seems to be well configured. Well done.

TLS Configuration: infomaniak.com (2001:1600:0:aaaa:0:0:2:6)

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.3 TLS v1.2
Servers should always enforce their own cipher suite preference, as that is the only approach that guarantees that the best possible suite is selected.Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3 Server preference	Suite: TLS_CHACHA20_POLY1305_SHA256 Suite ID: 0x1303 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: X25519MLKEM768 Key exchange strength: Hybrid PQ X25519MLKEM768 (9472 bits) Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (Hybrid PQ 9472 bits) Suite: TLS_AES_128_GCM_SHA256 Suite ID: 0x1301 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: X25519MLKEM768 Key exchange strength: Hybrid PQ X25519MLKEM768 (9472 bits) Forward secrecy: Yes PRF: SHA256 TLS_AES_128_GCM_SHA256 128 bits (Hybrid PQ 9472 bits) Suite: TLS_AES_256_GCM_SHA384 Suite ID: 0x1302 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: X25519MLKEM768 Key exchange strength: Hybrid PQ X25519MLKEM768 (9472 bits) Forward secrecy: Yes PRF: SHA384 TLS_AES_256_GCM_SHA384 256 bits (Hybrid PQ 9472 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2 Server preference	Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 Suite ID: 0xc027 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 128 bits (ECDHE 256 bits)

Analysis

TLS 1.3 supported

Excellent. This server supports TLS 1.3, which is the latest revision of the TLS protocol and a significant improvement over earlier versions. Developed over a period of several years and extensively analyzed prior to the release, TLS 1.3 removed insecure features, and improved both security and performance.

TLS 1.2 supported

Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.

Deprecated protocols not supported

Excellent. This server doesn't support any of the deprecated protocol (TLS 1.1 and earlier).

Strong key exchange detected

Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.

Server prefers forward secrecy and authenticated encryption suites

Excellent. Not only does this server enforce its server preference, but it also has at the top of the list suites that support both forward secrecy and authenticated encryption. This is the best TLS 1.2 can offer.

Server enforces cipher suite preferences

Excellent. This server enforces server cipher suite preference, which means that it is able to select the best suite from the options submitted by clients. Combined with a well-designed list of supported cipher suites, this setting enables negotiation of best security.

All TLS connections with this server satisfy Apple's CT requirements

All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

All TLS connections with this server satisfy Chrome's CT requirements

All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

Post-quantum key exchange supported

Excellent. This server supports post-quantum cryptography (PQC) and uses it for key exchange. PQC is still in the process of being standardized and deployed. Protecting the key exchange against future quantum computers is considered to be one of the more pressing tasks.

Algorithm: X25519MLKEM768

DHE suites not supported

This server doesn't support the Diffie-Hellman (DH) key exchange.

TLS Configuration: infomaniak.com (185.125.25.1)

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.3 TLS v1.2
Servers should always enforce their own cipher suite preference, as that is the only approach that guarantees that the best possible suite is selected.Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3 Server preference	Suite: TLS_CHACHA20_POLY1305_SHA256 Suite ID: 0x1303 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: X25519MLKEM768 Key exchange strength: Hybrid PQ X25519MLKEM768 (9472 bits) Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (Hybrid PQ 9472 bits) Suite: TLS_AES_128_GCM_SHA256 Suite ID: 0x1301 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: X25519MLKEM768 Key exchange strength: Hybrid PQ X25519MLKEM768 (9472 bits) Forward secrecy: Yes PRF: SHA256 TLS_AES_128_GCM_SHA256 128 bits (Hybrid PQ 9472 bits) Suite: TLS_AES_256_GCM_SHA384 Suite ID: 0x1302 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: X25519MLKEM768 Key exchange strength: Hybrid PQ X25519MLKEM768 (9472 bits) Forward secrecy: Yes PRF: SHA384 TLS_AES_256_GCM_SHA384 256 bits (Hybrid PQ 9472 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2 Server preference	Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 Suite ID: 0xc027 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 128 bits (ECDHE 256 bits)

Analysis

TLS 1.3 supported

Excellent. This server supports TLS 1.3, which is the latest revision of the TLS protocol and a significant improvement over earlier versions. Developed over a period of several years and extensively analyzed prior to the release, TLS 1.3 removed insecure features, and improved both security and performance.

TLS 1.2 supported

Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.

Deprecated protocols not supported

Excellent. This server doesn't support any of the deprecated protocol (TLS 1.1 and earlier).

Strong key exchange detected

Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.

Server prefers forward secrecy and authenticated encryption suites

Excellent. Not only does this server enforce its server preference, but it also has at the top of the list suites that support both forward secrecy and authenticated encryption. This is the best TLS 1.2 can offer.

Server enforces cipher suite preferences

Excellent. This server enforces server cipher suite preference, which means that it is able to select the best suite from the options submitted by clients. Combined with a well-designed list of supported cipher suites, this setting enables negotiation of best security.

All TLS connections with this server satisfy Apple's CT requirements

All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

All TLS connections with this server satisfy Chrome's CT requirements

All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

Post-quantum key exchange supported

Excellent. This server supports post-quantum cryptography (PQC) and uses it for key exchange. PQC is still in the process of being standardized and deployed. Protecting the key exchange against future quantum computers is considered to be one of the more pressing tasks.

Algorithm: X25519MLKEM768

DHE suites not supported

This server doesn't support the Diffie-Hellman (DH) key exchange.

TLS Configuration: www.infomaniak.com (2001:1600:0:aaaa:0:0:2:6)

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.3 TLS v1.2
Servers should always enforce their own cipher suite preference, as that is the only approach that guarantees that the best possible suite is selected.Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3 Server preference	Suite: TLS_CHACHA20_POLY1305_SHA256 Suite ID: 0x1303 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: X25519MLKEM768 Key exchange strength: Hybrid PQ X25519MLKEM768 (9472 bits) Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (Hybrid PQ 9472 bits) Suite: TLS_AES_128_GCM_SHA256 Suite ID: 0x1301 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: X25519MLKEM768 Key exchange strength: Hybrid PQ X25519MLKEM768 (9472 bits) Forward secrecy: Yes PRF: SHA256 TLS_AES_128_GCM_SHA256 128 bits (Hybrid PQ 9472 bits) Suite: TLS_AES_256_GCM_SHA384 Suite ID: 0x1302 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: X25519MLKEM768 Key exchange strength: Hybrid PQ X25519MLKEM768 (9472 bits) Forward secrecy: Yes PRF: SHA384 TLS_AES_256_GCM_SHA384 256 bits (Hybrid PQ 9472 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2 Server preference	Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 Suite ID: 0xc027 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 128 bits (ECDHE 256 bits)

Analysis

TLS 1.3 supported

Excellent. This server supports TLS 1.3, which is the latest revision of the TLS protocol and a significant improvement over earlier versions. Developed over a period of several years and extensively analyzed prior to the release, TLS 1.3 removed insecure features, and improved both security and performance.

TLS 1.2 supported

Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.

Deprecated protocols not supported

Excellent. This server doesn't support any of the deprecated protocol (TLS 1.1 and earlier).

Strong key exchange detected

Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.

Server prefers forward secrecy and authenticated encryption suites

Excellent. Not only does this server enforce its server preference, but it also has at the top of the list suites that support both forward secrecy and authenticated encryption. This is the best TLS 1.2 can offer.

Server enforces cipher suite preferences

Excellent. This server enforces server cipher suite preference, which means that it is able to select the best suite from the options submitted by clients. Combined with a well-designed list of supported cipher suites, this setting enables negotiation of best security.

All TLS connections with this server satisfy Apple's CT requirements

All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

All TLS connections with this server satisfy Chrome's CT requirements

All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

Post-quantum key exchange supported

Excellent. This server supports post-quantum cryptography (PQC) and uses it for key exchange. PQC is still in the process of being standardized and deployed. Protecting the key exchange against future quantum computers is considered to be one of the more pressing tasks.

Algorithm: X25519MLKEM768

DHE suites not supported

This server doesn't support the Diffie-Hellman (DH) key exchange.

TLS Configuration: www.infomaniak.com (185.125.25.1)

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.3 TLS v1.2
Servers should always enforce their own cipher suite preference, as that is the only approach that guarantees that the best possible suite is selected.Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3 Server preference	Suite: TLS_CHACHA20_POLY1305_SHA256 Suite ID: 0x1303 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: X25519MLKEM768 Key exchange strength: Hybrid PQ X25519MLKEM768 (9472 bits) Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (Hybrid PQ 9472 bits) Suite: TLS_AES_128_GCM_SHA256 Suite ID: 0x1301 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: X25519MLKEM768 Key exchange strength: Hybrid PQ X25519MLKEM768 (9472 bits) Forward secrecy: Yes PRF: SHA256 TLS_AES_128_GCM_SHA256 128 bits (Hybrid PQ 9472 bits) Suite: TLS_AES_256_GCM_SHA384 Suite ID: 0x1302 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: X25519MLKEM768 Key exchange strength: Hybrid PQ X25519MLKEM768 (9472 bits) Forward secrecy: Yes PRF: SHA384 TLS_AES_256_GCM_SHA384 256 bits (Hybrid PQ 9472 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2 Server preference	Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 Suite ID: 0xc027 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 128 bits (ECDHE 256 bits)

Analysis

TLS 1.3 supported

Excellent. This server supports TLS 1.3, which is the latest revision of the TLS protocol and a significant improvement over earlier versions. Developed over a period of several years and extensively analyzed prior to the release, TLS 1.3 removed insecure features, and improved both security and performance.

TLS 1.2 supported

Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.

Deprecated protocols not supported

Excellent. This server doesn't support any of the deprecated protocol (TLS 1.1 and earlier).

Strong key exchange detected

Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.

Server prefers forward secrecy and authenticated encryption suites

Excellent. Not only does this server enforce its server preference, but it also has at the top of the list suites that support both forward secrecy and authenticated encryption. This is the best TLS 1.2 can offer.

Server enforces cipher suite preferences

Excellent. This server enforces server cipher suite preference, which means that it is able to select the best suite from the options submitted by clients. Combined with a well-designed list of supported cipher suites, this setting enables negotiation of best security.

All TLS connections with this server satisfy Apple's CT requirements

All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

All TLS connections with this server satisfy Chrome's CT requirements

All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

Post-quantum key exchange supported

Excellent. This server supports post-quantum cryptography (PQC) and uses it for key exchange. PQC is still in the process of being standardized and deployed. Protecting the key exchange against future quantum computers is considered to be one of the more pressing tasks.

Algorithm: X25519MLKEM768

DHE suites not supported

This server doesn't support the Diffie-Hellman (DH) key exchange.

WWW Certificates

A certificate is a digital document that contains a public key, some information about the entity associated with it, and a digital signature from the certificate issuer. It’s a mechanism that enables us to exchange, store, and use public keys. Being able to reliably verify the identity of a remote server is crucial in order to achieve secure encrypted communication.

Test passed

Everything seems to be well configured. Well done.

Certificate: infomaniak.com

Leaf certificate

*.infomaniak.com
Issuer: Sectigo
Not Before: 12 Feb 2026 00:00:00 UTC
Not After: 25 Feb 2027 23:59:59 UTC (expires in 4 months 23 days)
Key: RSA 2048 bits
Signature: SHA256withRSA
View details

Names	*.infomaniak.com infomaniak.com
Subject DN	CN=*.infomaniak.com
Subject Key Identifier	9357b8058825889707f04771f552a7e5f2485e67
Serial	b616945d86796323ff2392a73293ca07
Not Before	12 Feb 2026 00:00:00 UTC
Not After	25 Feb 2027 23:59:59 UTC
Validity period	379 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth
Must Staple	No
Issuer
Issuer DN	CN=Sectigo Public Server Authentication CA DV R36, O=Sectigo Limited, C=GB
Certification Authority	Sectigo
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:68c01216180eafcef687a63257a346515dcb0727
Parent Certificate	http://crt.sectigo.com/SectigoPublicServerAuthenticationCADVR36.crt
OCSP	http://ocsp.sectigo.com
Certificate Transparency
Signed Certificate Timestamps	12 Feb 2026 03:21:23 UTC \| Sectigo 'Elephant2027h1' \| Qualified 12 Feb 2026 03:21:23 UTC \| Let's Encrypt 'Sycamore2027h1' \| Qualified 12 Feb 2026 03:21:23 UTC \| Geomys 'Tuscolo2027h1' \| Qualified
Fingerprints
SHA1	161b657d15901696cc8dc35789245e911274e3f0
SHA256	90bd9188ef09ef9333c9f7a8fa2b14af2b0765cfc0ceb48171ba9a0bc7bde807
SPKI SHA256	4ac77f8c7189dcea8483afcaea26358849f6d3514a487ebb5961cbe62767629f

Analysis

Strong private key

Good. The private key associated with this certificate is secure.

Strong signature algorithm

Good. This certificate uses a strong signature algorithm.

Certificate matches hostname

Good. The provided certificate matches the expected hostnames.

Certificate dates match

Good. The certificate is valid for use at this point of time.

Certificate has not been revoked

Good. This certificate has not been revoked.

Certificate satisfies Apple's CT compliance requirements

Good. This certificate satisfies Apple's CT requirements at present.

Certificate Trust

Determining whether a certificate is considered valid is a complicated process that depends on the exact configuration of the validating party. For trust to be established, the certificate must form a chain that ends with a trusted root. In this section we evaluate the server's certificate against major root stores.

Platform	Trusted
Apple
Google AOSP
Microsoft
Mozilla

Certificate Chain

For a server certificate to be valid, it must be presented as part of a complete and valid certificate chain. The last certificate in the chain should be the root and is usually not included in the configuration.

Leaf certificate

*.infomaniak.com | 90bd918
Not After: 25 Feb 2027 23:59:59 UTC (expires in 4 months 23 days)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Names	*.infomaniak.com infomaniak.com
Subject DN	CN=*.infomaniak.com
Subject Key Identifier	9357b8058825889707f04771f552a7e5f2485e67
Serial	b616945d86796323ff2392a73293ca07
Not Before	12 Feb 2026 00:00:00 UTC
Not After	25 Feb 2027 23:59:59 UTC
Validity period	379 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth
Must Staple	No
Issuer
Issuer DN	CN=Sectigo Public Server Authentication CA DV R36, O=Sectigo Limited, C=GB
Certification Authority	Sectigo
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:68c01216180eafcef687a63257a346515dcb0727
Parent Certificate	http://crt.sectigo.com/SectigoPublicServerAuthenticationCADVR36.crt
OCSP	http://ocsp.sectigo.com
Certificate Transparency
Signed Certificate Timestamps	12 Feb 2026 03:21:23 UTC \| Sectigo 'Elephant2027h1' \| Qualified 12 Feb 2026 03:21:23 UTC \| Let's Encrypt 'Sycamore2027h1' \| Qualified 12 Feb 2026 03:21:23 UTC \| Geomys 'Tuscolo2027h1' \| Qualified
Fingerprints
SHA1	161b657d15901696cc8dc35789245e911274e3f0
SHA256	90bd9188ef09ef9333c9f7a8fa2b14af2b0765cfc0ceb48171ba9a0bc7bde807
SPKI SHA256	4ac77f8c7189dcea8483afcaea26358849f6d3514a487ebb5961cbe62767629f

Intermediate certificate

Sectigo Public Server Authentication CA DV R36 | 8c54c33
Not After: 21 Mar 2036 23:59:59 UTC (expires in 9 years 5 months)
Authentication: RSA 3072 bits (SHA384withRSA)
View details

Subject DN	CN=Sectigo Public Server Authentication CA DV R36, O=Sectigo Limited, C=GB
Subject Key Identifier	68c01216180eafcef687a63257a346515dcb0727
Serial	397a66cc2756362e0daa87ca6eabe3b1
Not Before	22 Mar 2021 00:00:00 UTC
Not After	21 Mar 2036 23:59:59 UTC
Validity period	5479 days
Key Usage	digitalSignature, keyCertSign, cRLSign
Extended Key Usage	serverAuth, clientAuth
Issuer
Issuer DN	CN=Sectigo Public Server Authentication Root R46, O=Sectigo Limited, C=GB
Certification Authority	Sectigo
Validation Type	Not Applicable
Authority Key Identifier	keyid:5673586495f9921ab0122a046279a14015882149
Parent Certificate	http://crt.sectigo.com/SectigoPublicServerAuthenticationRootR46.p7c
CRL	http://crl.sectigo.com/SectigoPublicServerAuthenticationRootR46.crl
OCSP	http://ocsp.sectigo.com
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	dd55b4520291e276588f0dd02fafd83a7368e0fa
SHA256	8c54c334b66ba4e426772af4a3f9136c19a1aec729fdb28c535c07a5a4ef22e0
SPKI SHA256	6bd9212ce649c659c9cabc6cb60fcffac7a20c29be61fdceb2b5f2168701688d

Intermediate certificate

Sectigo Public Server Authentication Root R46 | 92f351b
Not After: 18 Jan 2038 23:59:59 UTC (expires in 11 years 3 months)
Authentication: RSA 4096 bits (SHA384withRSA)
View details

Subject DN	CN=Sectigo Public Server Authentication Root R46, O=Sectigo Limited, C=GB
Subject Key Identifier	5673586495f9921ab0122a046279a14015882149
Serial	d27fbbc1de359e5216ad6149586099c4
Not Before	22 Mar 2021 00:00:00 UTC
Not After	18 Jan 2038 23:59:59 UTC
Validity period	6147 days
Key Usage	digitalSignature, keyCertSign, cRLSign
Extended Key Usage	serverAuth, clientAuth
Issuer
Issuer DN	CN=USERTrust RSA Certification Authority, O=The USERTRUST Network, L=Jersey City, ST=New Jersey, C=US
Certification Authority	Sectigo
Validation Type	Not Applicable
Authority Key Identifier	keyid:5379bf5aaa2b4acf5480e1d89bc09df2b20366cb
CRL	http://crl.usertrust.com/USERTrustRSACertificationAuthority.crl
OCSP	http://ocsp.usertrust.com
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	2b18947a6a9fc7764fd8b5fb18a863b0c6dac24f
SHA256	92f351bf3d54164dfa8dd8f9e1139d3150349786485d2b9eecd00e2971c1e6c5
SPKI SHA256	0e8bb18bbeefb381be21bfc1a206d317298462ad104855f04a0542699708d3d4

Root certificate

USERTrust RSA Certification Authority | e793c9b
Not After: 18 Jan 2038 23:59:59 UTC (expires in 11 years 3 months)
Authentication: RSA 4096 bits (SHA384withRSA)
View details

Subject DN	CN=USERTrust RSA Certification Authority, O=The USERTRUST Network, L=Jersey City, ST=New Jersey, C=US
Subject Key Identifier	5379bf5aaa2b4acf5480e1d89bc09df2b20366cb
Serial	01fd6d30fca3ca51a81bbc640e35032d
Not Before	01 Feb 2010 00:00:00 UTC
Not After	18 Jan 2038 23:59:59 UTC
Key Usage	keyCertSign, cRLSign
Issuer
Issuer DN	CN=USERTrust RSA Certification Authority, O=The USERTRUST Network, L=Jersey City, ST=New Jersey, C=US
Certification Authority	Sectigo
Validation Type	Self-signed
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	2b8f1b57330dbba2d07a6c51f70ee90ddab9ad8e
SHA256	e793c9b02fd8aa13e21c31228accb08119643b749c898964b1746d46c3d4cbd2
SPKI SHA256	c784333d20bcd742b9fdc3236f4e509b8937070e73067e254dd3bf9c45bf4dde

Analysis

Certificate chain is correct

Good. This chain contains all the right certificates and in the right order.

Certificate: www.infomaniak.com

Leaf certificate

www.infomaniak.com
Issuer: Sectigo
Not Before: 25 Sep 2026 00:00:00 UTC
Not After: 11 Apr 2027 23:59:59 UTC (expires in 6 months 9 days)
Key: RSA 2048 bits
Signature: SHA256withRSA
View details

Names	www.infomaniak.com infomaniak.com news.infomaniak.com
Subject DN	CN=www.infomaniak.com, O=Infomaniak Network SA, ST=Genève, C=CH, OID.2.5.4.15=Private Organization, OID.1.3.6.1.4.1.311.60.2.1.3=CH, SERIALNUMBER=CHE-103.167.648
Subject Key Identifier	a839ecfb0bd1b5a874744eb9757a4a92a26be416
Serial	13eb54edd0960a987c8edbdf825abd74
Not Before	25 Sep 2026 00:00:00 UTC
Not After	11 Apr 2027 23:59:59 UTC
Validity period	199 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth
Must Staple	No
Issuer
Issuer DN	CN=Sectigo Public Server Authentication CA EV R36, O=Sectigo Limited, C=GB
Certification Authority	Sectigo
Validation Type	Extended Validation (EV)
Authority Key Identifier	keyid:982d5e1e8feb54f4b9ff5595ad4cc77ea498ae7b
Parent Certificate	http://crt.sectigo.com/SectigoPublicServerAuthenticationCAEVR36.crt
CRL	http://crl.sectigo.com/SectigoPublicServerAuthenticationCAEVR36.crl
OCSP	http://ocsp.sectigo.com
Certificate Transparency
Signed Certificate Timestamps	25 Sep 2026 13:21:48 UTC \| Cloudflare 'Nimbus2027' \| Qualified 25 Sep 2026 13:21:48 UTC \| TrustAsia 'HETU2027' \| Qualified 25 Sep 2026 13:21:49 UTC \| Geomys 'Tuscolo2027h1' \| Qualified
Fingerprints
SHA1	715952173db2560f5bdd30fbdb7cd52a78601daf
SHA256	a42cd9cb81f2217c086ed006ebf2c816943d5a6a9a8310eb7b1a4725ce22185d
SPKI SHA256	30ddbd130b94f890d4eb27656d3d9bac25f88604c4ad33a55152071412b4cd61

Analysis

Strong private key

Good. The private key associated with this certificate is secure.

Strong signature algorithm

Good. This certificate uses a strong signature algorithm.

Certificate matches hostname

Good. The provided certificate matches the expected hostnames.

Certificate dates match

Good. The certificate is valid for use at this point of time.

Certificate has not been revoked

Good. This certificate has not been revoked.

Certificate satisfies Apple's CT compliance requirements

Good. This certificate satisfies Apple's CT requirements at present.

Certificate Trust

Determining whether a certificate is considered valid is a complicated process that depends on the exact configuration of the validating party. For trust to be established, the certificate must form a chain that ends with a trusted root. In this section we evaluate the server's certificate against major root stores.

Platform	Trusted
Apple
Google AOSP
Microsoft
Mozilla

Certificate Chain

For a server certificate to be valid, it must be presented as part of a complete and valid certificate chain. The last certificate in the chain should be the root and is usually not included in the configuration.

Leaf certificate

www.infomaniak.com | a42cd9c
Not After: 11 Apr 2027 23:59:59 UTC (expires in 6 months 9 days)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Names	www.infomaniak.com infomaniak.com news.infomaniak.com
Subject DN	CN=www.infomaniak.com, O=Infomaniak Network SA, ST=Genève, C=CH, OID.2.5.4.15=Private Organization, OID.1.3.6.1.4.1.311.60.2.1.3=CH, SERIALNUMBER=CHE-103.167.648
Subject Key Identifier	a839ecfb0bd1b5a874744eb9757a4a92a26be416
Serial	13eb54edd0960a987c8edbdf825abd74
Not Before	25 Sep 2026 00:00:00 UTC
Not After	11 Apr 2027 23:59:59 UTC
Validity period	199 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth
Must Staple	No
Issuer
Issuer DN	CN=Sectigo Public Server Authentication CA EV R36, O=Sectigo Limited, C=GB
Certification Authority	Sectigo
Validation Type	Extended Validation (EV)
Authority Key Identifier	keyid:982d5e1e8feb54f4b9ff5595ad4cc77ea498ae7b
Parent Certificate	http://crt.sectigo.com/SectigoPublicServerAuthenticationCAEVR36.crt
CRL	http://crl.sectigo.com/SectigoPublicServerAuthenticationCAEVR36.crl
OCSP	http://ocsp.sectigo.com
Certificate Transparency
Signed Certificate Timestamps	25 Sep 2026 13:21:48 UTC \| Cloudflare 'Nimbus2027' \| Qualified 25 Sep 2026 13:21:48 UTC \| TrustAsia 'HETU2027' \| Qualified 25 Sep 2026 13:21:49 UTC \| Geomys 'Tuscolo2027h1' \| Qualified
Fingerprints
SHA1	715952173db2560f5bdd30fbdb7cd52a78601daf
SHA256	a42cd9cb81f2217c086ed006ebf2c816943d5a6a9a8310eb7b1a4725ce22185d
SPKI SHA256	30ddbd130b94f890d4eb27656d3d9bac25f88604c4ad33a55152071412b4cd61

Intermediate certificate

Sectigo Public Server Authentication CA EV R36 | 7a1a242
Not After: 21 Mar 2036 23:59:59 UTC (expires in 9 years 5 months)
Authentication: RSA 3072 bits (SHA384withRSA)
View details

Subject DN	CN=Sectigo Public Server Authentication CA EV R36, O=Sectigo Limited, C=GB
Subject Key Identifier	982d5e1e8feb54f4b9ff5595ad4cc77ea498ae7b
Serial	6d4f7cad335377c8c6e001dde2e2c88e
Not Before	22 Mar 2021 00:00:00 UTC
Not After	21 Mar 2036 23:59:59 UTC
Validity period	5479 days
Key Usage	digitalSignature, keyCertSign, cRLSign
Extended Key Usage	serverAuth, clientAuth
Issuer
Issuer DN	CN=Sectigo Public Server Authentication Root R46, O=Sectigo Limited, C=GB
Certification Authority	Sectigo
Validation Type	Not Applicable
Authority Key Identifier	keyid:5673586495f9921ab0122a046279a14015882149
Parent Certificate	http://crt.sectigo.com/SectigoPublicServerAuthenticationRootR46.p7c
CRL	http://crl.sectigo.com/SectigoPublicServerAuthenticationRootR46.crl
OCSP	http://ocsp.sectigo.com
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	9924ca1790c918ab1a43b7ad9b4fa16006fbaedc
SHA256	7a1a24285e25e94df27ce8b344b1bb6b32f0254ff0d7b5ab6e856ae90cfde55c
SPKI SHA256	d117d70df71c36a444b03cd15eb69e76bfa93df69603c7cca651c2537d31625a

Intermediate certificate

Sectigo Public Server Authentication Root R46 | 92f351b
Not After: 18 Jan 2038 23:59:59 UTC (expires in 11 years 3 months)
Authentication: RSA 4096 bits (SHA384withRSA)
View details

Subject DN	CN=Sectigo Public Server Authentication Root R46, O=Sectigo Limited, C=GB
Subject Key Identifier	5673586495f9921ab0122a046279a14015882149
Serial	d27fbbc1de359e5216ad6149586099c4
Not Before	22 Mar 2021 00:00:00 UTC
Not After	18 Jan 2038 23:59:59 UTC
Validity period	6147 days
Key Usage	digitalSignature, keyCertSign, cRLSign
Extended Key Usage	serverAuth, clientAuth
Issuer
Issuer DN	CN=USERTrust RSA Certification Authority, O=The USERTRUST Network, L=Jersey City, ST=New Jersey, C=US
Certification Authority	Sectigo
Validation Type	Not Applicable
Authority Key Identifier	keyid:5379bf5aaa2b4acf5480e1d89bc09df2b20366cb
CRL	http://crl.usertrust.com/USERTrustRSACertificationAuthority.crl
OCSP	http://ocsp.usertrust.com
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	2b18947a6a9fc7764fd8b5fb18a863b0c6dac24f
SHA256	92f351bf3d54164dfa8dd8f9e1139d3150349786485d2b9eecd00e2971c1e6c5
SPKI SHA256	0e8bb18bbeefb381be21bfc1a206d317298462ad104855f04a0542699708d3d4

Root certificate

USERTrust RSA Certification Authority | e793c9b
Not After: 18 Jan 2038 23:59:59 UTC (expires in 11 years 3 months)
Authentication: RSA 4096 bits (SHA384withRSA)
View details

Subject DN	CN=USERTrust RSA Certification Authority, O=The USERTRUST Network, L=Jersey City, ST=New Jersey, C=US
Subject Key Identifier	5379bf5aaa2b4acf5480e1d89bc09df2b20366cb
Serial	01fd6d30fca3ca51a81bbc640e35032d
Not Before	01 Feb 2010 00:00:00 UTC
Not After	18 Jan 2038 23:59:59 UTC
Key Usage	keyCertSign, cRLSign
Issuer
Issuer DN	CN=USERTrust RSA Certification Authority, O=The USERTRUST Network, L=Jersey City, ST=New Jersey, C=US
Certification Authority	Sectigo
Validation Type	Self-signed
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	2b8f1b57330dbba2d07a6c51f70ee90ddab9ad8e
SHA256	e793c9b02fd8aa13e21c31228accb08119643b749c898964b1746d46c3d4cbd2
SPKI SHA256	c784333d20bcd742b9fdc3236f4e509b8937070e73067e254dd3bf9c45bf4dde

Analysis

Certificate chain is correct

Good. This chain contains all the right certificates and in the right order.

DANE (443)

DNS-based Authentication of Named Entities (DANE) is a bridge between DNSSEC and TLS. In one possible scenario, DANE can be used for public key pinning, building on an existing publicly-trusted certificate. In another approach, it can be used to completely bypass the CA ecosystem and establish trust using DNSSEC alone.

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

Cookies

Cookies are small chunks of text that are sent between your browser and a website. They are often essential to the operation of the site and sometimes contain sensitive information. Session cookies sent from secure sites must be explicitly marked as secure to prevent being obtained by active network attackers.

Test passed, but there are warnings

Some aspect of your site's configuration require your attention.

HTTP Cookie: STATIC_CURRENCY

Cookie value. As far as the cookie RFC is concerned, the value is an opaque string which only the application should interpret.Value	CHF
Cookie domain. When domain is implied (not explicitly set in a cookie), most browsers (but not IE) treat the cookie as host-only, meaning that no other server can overwrite it.Domain	Implied (www.infomaniak.com)
Cookie path. This field can't be used as security measure, but it could be of use to avoid cookie name collision in non-adversarial contexts.Path	/
Cookies are designed to always expire. Session cookies are truly ephemeral and remain cached until the browser is closed. The Expires and Max-Age cookie attributes can be used to specify that a cookie should stay alive for longer.Expires	Sat Oct 02 12:50:00 UTC 2027 (11 months 29 days)
The HttpOnly flag prevents the cookie from being accessed from JavaScript, thus making them more difficult to obtain after a successful XSS attack.HttpOnly
The Secure flag signals to browsers that the cookie should be transmitted only over an encrypted channel.Secure
Normally, when a browser makes a request to a web site, it sends all associated cookies. This is not always desirable, because it might allow third-party sites to perform site actions under the identity of the user. This attack is known as Cross-Site Request Forgery. With SameSite cookies (still in development, but already supported in some browsers), you can choose to be more strict. The possible values are 'lax' and 'strict'.SameSite

Analysis

Cookie is not secure

This cookie, which has been sent over an encrypted channel, doesn't have the secure flag set. As a result, an active network attacker can easily recover it.

HTTP Cookie: STATIC_COUNTRY

Cookie value. As far as the cookie RFC is concerned, the value is an opaque string which only the application should interpret.Value	US
Cookie domain. When domain is implied (not explicitly set in a cookie), most browsers (but not IE) treat the cookie as host-only, meaning that no other server can overwrite it.Domain	Implied (www.infomaniak.com)
Cookie path. This field can't be used as security measure, but it could be of use to avoid cookie name collision in non-adversarial contexts.Path	/
Cookies are designed to always expire. Session cookies are truly ephemeral and remain cached until the browser is closed. The Expires and Max-Age cookie attributes can be used to specify that a cookie should stay alive for longer.Expires	Sat Oct 03 12:50:00 UTC 2026 (23 hours 59 minutes)
The HttpOnly flag prevents the cookie from being accessed from JavaScript, thus making them more difficult to obtain after a successful XSS attack.HttpOnly
The Secure flag signals to browsers that the cookie should be transmitted only over an encrypted channel.Secure
Normally, when a browser makes a request to a web site, it sends all associated cookies. This is not always desirable, because it might allow third-party sites to perform site actions under the identity of the user. This attack is known as Cross-Site Request Forgery. With SameSite cookies (still in development, but already supported in some browsers), you can choose to be more strict. The possible values are 'lax' and 'strict'.SameSite

Analysis

Cookie is not secure

This cookie, which has been sent over an encrypted channel, doesn't have the secure flag set. As a result, an active network attacker can easily recover it.

HTTP Cookie: XSRF-TOKEN

Cookie value. As far as the cookie RFC is concerned, the value is an opaque string which only the application should interpret.Value	eyJpdiI6ImFCL3pYL1NDdnRZQ1M3UFFoRWFVTlE9PSIsInZhbHVlIjoiZnc2UVY3VEU1YTY2NFZ3RDliSHhhQjBQelErZXMvRWswWFBuSFNvNFdlTlNkQkoxeGR1UEQ5SStFZFN6V3gvbVQ2VVU5bTA5NTlNR1dFU3U5NHVpT2tud3hWb1Rzd0lVS1FLSE55NXRXbFdWQzJ5V0xRdlFLT1JjQXhJczVOWU4iLCJtYWMiOiI0Y2YxNTE2N2Y5ZDE1NjE5ODQ5OWE0OGVmMTI1ZDhjOWRjYWViOGMxM2NkZGViNDdjNzBmMGQwZDk1MzE5NmNlIiwidGFnIjoiIn0%3D
Cookie domain. When domain is implied (not explicitly set in a cookie), most browsers (but not IE) treat the cookie as host-only, meaning that no other server can overwrite it.Domain	Implied (www.infomaniak.com)
Cookie path. This field can't be used as security measure, but it could be of use to avoid cookie name collision in non-adversarial contexts.Path	/
Cookies are designed to always expire. Session cookies are truly ephemeral and remain cached until the browser is closed. The Expires and Max-Age cookie attributes can be used to specify that a cookie should stay alive for longer.Expires	Fri Oct 02 14:50:00 UTC 2026 (1 hour 59 minutes)
The HttpOnly flag prevents the cookie from being accessed from JavaScript, thus making them more difficult to obtain after a successful XSS attack.HttpOnly
The Secure flag signals to browsers that the cookie should be transmitted only over an encrypted channel.Secure
Normally, when a browser makes a request to a web site, it sends all associated cookies. This is not always desirable, because it might allow third-party sites to perform site actions under the identity of the user. This attack is known as Cross-Site Request Forgery. With SameSite cookies (still in development, but already supported in some browsers), you can choose to be more strict. The possible values are 'lax' and 'strict'.SameSite	lax

Analysis

Cookie is secure

Good. This cookie is marked secure, which means that it won't ever be transmitted over plaintext. As such, it's not vulnerable to the Sidejacking attack.

HTTP Cookie: site_infomaniak_session Session cookie

Cookie value. As far as the cookie RFC is concerned, the value is an opaque string which only the application should interpret.Value	eyJpdiI6ImJPMWQ4TGxGV1lodnVvQ2llVENoQ1E9PSIsInZhbHVlIjoiTmJiVmY2aHhrV0Vyd0N1NXhMNk05M3pvVDNpSzREcXgzT3gwaGJMaW1JcjBaR2ZoaEdkSnNVZU05WCt4aWlZaU1kQ1NET3lTTDMwbnFodzR2aUdJdytzN1Rod0hKZm5hWHRNU1dWN242U2FtZkh3WFBLOGV4dllNOEpXWitlZ28iLCJtYWMiOiJhNjdjMDU2Yzk2MTI0YzhjZmJjY2U0MTk4NTk1ZGIyNTYzOWE2MTRjY2FjNDAxNWI1ZmYzYzA2NzY3OTU3M2Y0IiwidGFnIjoiIn0%3D
Cookie domain. When domain is implied (not explicitly set in a cookie), most browsers (but not IE) treat the cookie as host-only, meaning that no other server can overwrite it.Domain	Implied (www.infomaniak.com)
Cookie path. This field can't be used as security measure, but it could be of use to avoid cookie name collision in non-adversarial contexts.Path	/
Cookies are designed to always expire. Session cookies are truly ephemeral and remain cached until the browser is closed. The Expires and Max-Age cookie attributes can be used to specify that a cookie should stay alive for longer.Expires	Fri Oct 02 14:50:00 UTC 2026 (1 hour 59 minutes)
The HttpOnly flag prevents the cookie from being accessed from JavaScript, thus making them more difficult to obtain after a successful XSS attack.HttpOnly
The Secure flag signals to browsers that the cookie should be transmitted only over an encrypted channel.Secure
Normally, when a browser makes a request to a web site, it sends all associated cookies. This is not always desirable, because it might allow third-party sites to perform site actions under the identity of the user. This attack is known as Cross-Site Request Forgery. With SameSite cookies (still in development, but already supported in some browsers), you can choose to be more strict. The possible values are 'lax' and 'strict'.SameSite	lax

Analysis

Name prefix not used

Cookie name prefixes are a recent improvement that enable web application developers to opt-in into a more secure type of cookies. Virtually all cookies would benefit from using either the '__Secure-' or the '__Host-' prefix. The former ensures that a plaintext cookie can't overwrite a secure cookie. The latter ensures that the cookie is sent back only to the host that issued it.

SameSite attribute deployed

Great. This cookie uses the new "SameSite" attribute to increase security and defend against Cross-Site Request Forgery (CSRF) attacks. Unlike normal cookies, same-site cookies are not always sent on cross-origin requests.

Session cookie is secure

Good. This session cookie is marked secure, which means that it won't ever be transmitted over plaintext. As such, it's not vulnerable to the Sidejacking attack.

Session cookie is HttpOnly

Good. This session cookie is marked as HttpOnly, which means that it can't be accessed from JavaScript. Such cookies are more difficult to obtain after a successful XSS attack.

HTTP Cookie: locale

Cookie value. As far as the cookie RFC is concerned, the value is an opaque string which only the application should interpret.Value	eyJpdiI6IkxGcjJSamNBOXVwTGpkT3Y0MGhiMFE9PSIsInZhbHVlIjoiSDJ2cXd6VGNLbU4relZ4T2RHUURNQTBFWWJPWjk2dlpCWENZa0wrNUJ3eVdmYzlkbDRMNGFxWCs3M1JOOEdpTyIsIm1hYyI6IjRkMmQyNDIwNzZkYzE5MTQ5MDY5ZTgyNDJmOTNmMzFjYTIxNWRlZTlmYWQ3ZjdhMDRkMWNmZGRiYWIxYWQ2OWQiLCJ0YWciOiIifQ%3D%3D
Cookie domain. When domain is implied (not explicitly set in a cookie), most browsers (but not IE) treat the cookie as host-only, meaning that no other server can overwrite it.Domain	Implied (www.infomaniak.com)
Cookie path. This field can't be used as security measure, but it could be of use to avoid cookie name collision in non-adversarial contexts.Path	/
Cookies are designed to always expire. Session cookies are truly ephemeral and remain cached until the browser is closed. The Expires and Max-Age cookie attributes can be used to specify that a cookie should stay alive for longer.Expires	Sun Nov 01 12:50:00 UTC 2026 (29 days 23 hours)
The HttpOnly flag prevents the cookie from being accessed from JavaScript, thus making them more difficult to obtain after a successful XSS attack.HttpOnly
The Secure flag signals to browsers that the cookie should be transmitted only over an encrypted channel.Secure
Normally, when a browser makes a request to a web site, it sends all associated cookies. This is not always desirable, because it might allow third-party sites to perform site actions under the identity of the user. This attack is known as Cross-Site Request Forgery. With SameSite cookies (still in development, but already supported in some browsers), you can choose to be more strict. The possible values are 'lax' and 'strict'.SameSite	lax

Analysis

Cookie is secure

Good. This cookie is marked secure, which means that it won't ever be transmitted over plaintext. As such, it's not vulnerable to the Sidejacking attack.

HTTP Cookie: JQjGNaIPH534NypDfdpq8wsdtVhM2DSY2xBkxb6C

Cookie value. As far as the cookie RFC is concerned, the value is an opaque string which only the application should interpret.Value	eyJpdiI6IlpqblNIYWkrcDlKL2dtQjVFb0Z5OGc9PSIsInZhbHVlIjoiR0JnbHRxSnZGeTUwYm5oMTliTlY4WTUzTDIzMUpLczBoRE93ZDBWaVF6cmxIZmZJVWF1ODl4R2hhcGZ4MExtR3VCNm11M3RYV1phNXBqaXUzY2dLTVI1WEdpQm1xTXVwYkYwSlZHVzNBYUFESDVYdXYzSVZiUnAxS0xscVc4bEJkQ0JUYkFIVjRka3V2b1lDTlFXWXVSM3lJdFdUeHdQcVFVMWRFWGdoeEJqb05Ga0dhbE51RjNlSnFLVkxua3lrbitvMHVFNlMwZ0VIT0hEcHo5b053NlF0MjFSQmRQdjh2Qk5NRWFaT2NaVmRkaW9QYThNOWlxQ0ZmcS9pUm1TVllUVWdOd1FEN2ZOd3hxOWNoZEVJa0NjV2wxMEJmemc5UDB2ZStkdndSdU1UVHYyR3BSSzNXYkRwM054MUNpKzMrZVcyMVRveWFQWDNRRmpVdHdlbzN0NWhvVENnMWtjYk5EbzV0ek90SUFnckIrT3JjY3NubTI1Q2g4eEQzUERmM2kzemJLZTR3cjF0NnVSVjZFd05ZT0pxMGJNMkpoQjR5WDhtUmQwYkk5KzJ1bUJDT1V0NS9YSlR1dTBRMkR4LyIsIm1hYyI6ImIxNDA1ZGQ4MWU3MGEyNTc2NDkzMDIwMDE5NDAyNGNlMWNkMDA0OWJlODQyMmFhZDBlOWMzMTM5ZGJhOGQ2YzAiLCJ0YWciOiIifQ%3D%3D
Cookie domain. When domain is implied (not explicitly set in a cookie), most browsers (but not IE) treat the cookie as host-only, meaning that no other server can overwrite it.Domain	Implied (www.infomaniak.com)
Cookie path. This field can't be used as security measure, but it could be of use to avoid cookie name collision in non-adversarial contexts.Path	/
Cookies are designed to always expire. Session cookies are truly ephemeral and remain cached until the browser is closed. The Expires and Max-Age cookie attributes can be used to specify that a cookie should stay alive for longer.Expires	Fri Oct 02 14:50:00 UTC 2026 (1 hour 59 minutes)
The HttpOnly flag prevents the cookie from being accessed from JavaScript, thus making them more difficult to obtain after a successful XSS attack.HttpOnly
The Secure flag signals to browsers that the cookie should be transmitted only over an encrypted channel.Secure
Normally, when a browser makes a request to a web site, it sends all associated cookies. This is not always desirable, because it might allow third-party sites to perform site actions under the identity of the user. This attack is known as Cross-Site Request Forgery. With SameSite cookies (still in development, but already supported in some browsers), you can choose to be more strict. The possible values are 'lax' and 'strict'.SameSite	lax

Analysis

Cookie is secure

Good. This cookie is marked secure, which means that it won't ever be transmitted over plaintext. As such, it's not vulnerable to the Sidejacking attack.

HTML Content

On virtually all web sites, HTML markup, images, style sheets, JavaScript, and other page resources arrive not only over multiple connections but possibly from multiple servers and sites spread across the entire Internet. For a page to be properly encrypted, it’s necessary that all the content is retrieved over HTTPS. In practice, that’s very often not the case, leading to mixed content security problems.

Test passed

Everything seems to be well configured. Well done.

Encryption of Embedded Resources

In this section we look at the transport security of all embedded resources. Mixed active content occurs when there are unprotected scripts or styles embedded in a page. This is typically not allowed by modern browsers. Mixed passive content (images, videos and such) are typically allowed, but shouldn't be present.

0 script(s)
0 out of 0 are secure

0 CSS file(s)
0 out of 0 are secure

0 media file(s)
0 out of 0 are secure

Encryption of Outbound Links

Ideally, an encrypted page should only have links that lead to other encrypted pages. If plaintext links are used, passive network attackers can see where people go after they visit your web site. It's also possible that some sensitive information is leaked in the Referer header.

0 link(s)
0 out of 0 are encrypted

HTTP Strict Transport Security

HTTP Strict Transport Security (HSTS) vastly improves security of the network encryption layer. With HSTS enabled, browsers no longer allow clicking through certificate warnings errors, which are typically trivial to exploit. Additionally, they will no longer submit insecure (plaintext) requests to the site in question, even if asked.

Test passed

Everything seems to be well configured. Well done.

HSTS Policy Main host

URL from which this policy was obtained.Location	https://www.infomaniak.com/
Specifies policy duration. Once activated, HSTS stays in force until this time lapses. Browsers update policy cache duration every time they receive a new HSTS header from a site.max‑age	63,072,000 seconds (about 2 years)
When present, this directive forces HSTS activation on allsubdomains. For best security, HSTS should be deployed on the bare domain name (e.g., example.com) and all its subdomains.includeSubDomains
Presence of this directive indicates that a web site wishes to permanently use HSTS and that its policy information should be preloaded (embedded in browsers).preload

Analysis

No parent protection

This host could benefit from further protection if the apex hostname would be configured with a HSTS policy that uses 'includeSubDomains'. Enabling HSTS on an entire domain name is the only approach that provides robust security.

Long policy age

Your HSTS policy has a long max-age value, which offers better protection.

Preload directive has no effect here

This policy doesn't enable preloading, but that's all right. The preload directive doesn't have any effect unless it's used on an apex hostname.

No subdomains

This HSTS policy doesn't cover subdomains. Without full coverage, HSTS can't protect from certain cookie attacks that typically allow active network attackers to inject cookies into an application. Additionally, subdomain coverage is one of the requirements to allow preloading.

Policy is valid

OK. Your HSTS policy uses correct syntax.

Redirection from HTTP to HTTPS to the same host

Good. The redirection from HTTP to HTTPS is to the same host. This approach ensures that HSTS is activated on the hostname when it's accessed via plaintext.

HSTS Policy Apex host

URL from which this policy was obtained.Location	https://infomaniak.com/
Specifies policy duration. Once activated, HSTS stays in force until this time lapses. Browsers update policy cache duration every time they receive a new HSTS header from a site.max‑age	63,072,000 seconds (about 2 years)
When present, this directive forces HSTS activation on allsubdomains. For best security, HSTS should be deployed on the bare domain name (e.g., example.com) and all its subdomains.includeSubDomains
Presence of this directive indicates that a web site wishes to permanently use HSTS and that its policy information should be preloaded (embedded in browsers).preload

Analysis

Long policy age

Your HSTS policy has a long max-age value, which offers better protection.

Preloading not enabled

This policy doesn't give browsers permission to embed it and provide protection even to the first request to the web site. Sites that wish to use preloading can apply at hstspreload.org.

No subdomains

This HSTS policy doesn't cover subdomains. Without full coverage, HSTS can't protect from certain cookie attacks that typically allow active network attackers to inject cookies into an application. Additionally, subdomain coverage is one of the requirements to allow preloading.

Policy is valid

OK. Your HSTS policy uses correct syntax.

Redirection from HTTP to HTTPS to the same host

Good. The redirection from HTTP to HTTPS is to the same host. This approach ensures that HSTS is activated on the hostname when it's accessed via plaintext.

HTTP Public Key Pinning

HTTP Public Key Pinning (HPKP) enables site operators to restrict which certificates are considered valid for their domain names. With a valid HPKP configuration, sites can defeat man in the middle (MITM) attacks using fraudulent or misissued certificates. HPKP is an advanced feature, suitable for use by only high-profile web sites.

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

Content Security Policy

Content Security Policy (CSP) is a security mechanism that allows web sites control how browsers process their pages. In essence, sites can restrict what types of resources are loaded and from where. CSP policies can be used to defend against cross-site scripting, prevent mixed content issues, as well as report violations for investigation.

Test passed

Everything seems to be well configured. Well done.

content-security-policy-report-only

default-src	'none'
script-src	https://*.infomaniak.com 'self' blob: data: https://infomaniak.com https://www.google.com https://www.gstatic.com https://maps.googleapis.com https://cdn.trustindex.io 'nonce-ts23ekE2GSUcoAzY7LJnyOkp2IFzBg53OHpgH7KG'
style-src	https://*.infomaniak.com 'self' This parameter shouldn't be used because it reenables insecure behavior that CSP disables by default.'unsafe-inline' https://fonts.googleapis.com
font-src	https://*.infomaniak.com 'self' data: https://fonts.gstatic.com
img-src	https://.infomaniak.com 'self' data: blob: android-webview-video-poster https://.infomaniak.ch
connect-src	https://.infomaniak.com 'self' wss://.infomaniak.com:* https://infomaniak.com https://www.google.com https://maps.googleapis.com https://*.trustindex.io
child-src	https://*.infomaniak.com https://www.google.com https://www.youtube.com
worker-src	https://*.infomaniak.com 'self' blob:
base-uri	'self'
frame-ancestors	'self'
form-action	https://.infomaniak.com 'self' https://.infomaniak.ch
upgrade-insecure-requests
report-uri	https://www.infomaniak.com/api/csp-report

Analysis

Inline styles are allowed

This policy allows inline styles. Although they are not as bad as inline scripts in terms of security, an injection bug in script area would allow the attacker to modify page appearance.

Mixed content upgraded

Good. This CSP policy instructs browsers to seamlessly upgrade plaintext resources to encryption.

Analysis

CSP report-only policy detected

Header: content-security-policy-report-only

Value: default-src; script-src https://*.infomaniak.com 'self' blob: data: https://infomaniak.com https://www.google.com https://www.gstatic.com https://maps.googleapis.com https://cdn.trustindex.io 'nonce-ts23ekE2GSUcoAzY7LJnyOkp2IFzBg53OHpgH7KG'; script-src-elem https://*.infomaniak.com 'self' blob: data: https://infomaniak.com https://www.google.com https://www.gstatic.com https://maps.googleapis.com https://cdn.trustindex.io 'nonce-ts23ekE2GSUcoAzY7LJnyOkp2IFzBg53OHpgH7KG'; style-src https://*.infomaniak.com 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src https://*.infomaniak.com 'self' data: https://fonts.gstatic.com; img-src https://*.infomaniak.com 'self' data: blob: android-webview-video-poster https://*.infomaniak.ch; connect-src https://*.infomaniak.com 'self' wss://*.infomaniak.com:* https://infomaniak.com https://www.google.com https://maps.googleapis.com https://*.trustindex.io; child-src https://*.infomaniak.com https://www.google.com https://www.youtube.com; frame-src https://*.infomaniak.com https://www.google.com https://www.youtube.com; worker-src https://*.infomaniak.com 'self' blob:; object-src 'none'; base-uri 'self'; frame-ancestors 'self'; form-action https://*.infomaniak.com 'self' https://*.infomaniak.ch; upgrade-insecure-requests; report-uri /api/csp-report;

Location: https://www.infomaniak.com/en

Subresource Integrity

Subresource Integrity (SRI) is a new standard that enables browsers to verify the integrity of embedded page resources (e.g., scripts and stylesheets) when they are loaded from third-party web sites. With SRI deployed, remote resources can be used safely, without fear of them being modified by malicious parties.

Test passed

Everything seems to be well configured. Well done.

No external scripts
SRI not needed

No external stylesheets
SRI not needed

Analysis

No remote resources

The homepage of this site doesn't contain any remote resources so SRI is not needed.

Expect CT

Expect-CT is a deprecated response HTTP header designed to enable web sites to monitor problems related to their Certificate Transparency (CT) compliance. Should any CT issues arise, browsers that supported this header will submit reports to the specified reporting endpoint. Chrome was the browser that introduced support for this response header, but later deprecated it and removed it in version 107.

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

Analysis

Deploy Expect-CT to enable reporting

An Expect-CT policy enables web sites to monitor for any problems related to their Expect-CT compliance, detecting potentially serious issues quickly. When issues arise, compliant browsers will submit reports to the specified reporting endpoints. Before CT became required for all public certificates the Expect-CT was also used to require CT, but that use case no longer applies.

Frame Options

The X-Frame-Options header controls page framing, which occurs when a page is incorporated into some other page, possibly on a different site. If framing is allowed, attackers can employ clever tricks to make victims perform arbitrary actions on your site; they do this by showing their web site while forwarding the victim's clicks to yours.

Test passed

Everything seems to be well configured. Well done.

Analysis

Header information

Name: x-frame-options

Value: SAMEORIGIN

Framing allowed from the same origin only

OK. Your site allows page framing only from itself. This should generally be safe, except maybe on sites that host user content.

XSS Protection

Some browsers ship with so-called XSS Auditors, built-in defenses against XSS. Although these defenses work against simple reflective XSS attacks, they can be abused by skillful attackers to add weaknesses to otherwise secure web sites. These dangers are present in both filtering and blocking modes. At this time, the Safari browser ships with its XSS defenses enabled by default. For this reason, the best approach is to explicitly disable this functionality.

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

Analysis

Explicitly disable browser XSS protection

For best security, every web site should explicitly disable browser-based XSS protection. This is because this type of functionality can be used to introduce vulnerabilities into otherwise error-free web sites.

Content Type Options

Some browsers use a technique called content sniffing to override response MIME types provided by HTTP servers and interpret responses as something else (usually HTML). This behavior, which could potentially lead to security issues, should be disabled by attaching an X-Content-Type-Options header to all responses.

Test failed

We've detected serious problems that require your immediate attention.

Analysis

Header information

Name: x-content-type-options

Value: nosniff

Multiple headers

Multiple X-Content-Type-Options headers are not allowed.

Location: https://www.infomaniak.com/en

Public Report | infomaniak.com

infomaniak.com

Domain Name System

Email

WWW

DNS Zone

Nameserver Names

Nameserver Addresses

Start of Authority (SOA) Record

Analysis

Backing DNS Queries

DNS Records

DNS Records

Backing DNS Queries

DNSSEC

Analysis

Useful DNSSEC Tools

Certification Authority Authorization

Analysis

Email (SMTP)

Analysis

Email TLS (SMTP)

TLS Configuration: mta-gw.infomaniak.ch (83.166.143.57)

Analysis

Email Certificates (SMTP)

Certificate #1

Analysis

Certificate Chain

Analysis

Email DANE (SMTP)

DANE: mta-gw.infomaniak.ch (83.166.143.57)

Analysis

SPF

SPF Policy Information Main policy

Analysis

SPF Policy Information Included policy

SPF Policy Information Included policy

SPF Policy Information Included policy

SPF Policy Information Included policy

SPF Policy Information Included policy

SPF Policy Information Included policy

SPF Policy Information Included policy

SPF Policy Information Included policy

SPF Policy Information Included policy

SPF Policy Information Included policy

DMARC

DMARC Policy Information

Analysis

MTA Strict Transport Security

SMTP TLS Reporting

HTTP (80)

URL: http://infomaniak.com/

Analysis

URL: http://www.infomaniak.com/

Analysis

HTTP (443)

URL: https://infomaniak.com/

URL: https://www.infomaniak.com/

WWW TLS

TLS Configuration: infomaniak.com (2001:1600:0:aaaa:0:0:2:6)

Analysis

TLS Configuration: infomaniak.com (185.125.25.1)

Analysis

TLS Configuration: www.infomaniak.com (2001:1600:0:aaaa:0:0:2:6)

Analysis

TLS Configuration: www.infomaniak.com (185.125.25.1)

Analysis

WWW Certificates

Certificate: infomaniak.com

Analysis

Certificate Trust

Certificate Chain

Analysis

Certificate: www.infomaniak.com

Analysis

Certificate Trust

Certificate Chain

Analysis

DANE (443)

Cookies