Hardenize Report: vliegherrie.nl

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.

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
lana.ns.cloudflare.com. PRIMARY 108.162.192.182 172.64.32.182 173.245.58.182 2606:4700:50::adf5:3ab6 2803:f800:50::6ca2:c0b6 2a06:98c1:50::ac40:20b6				REFERRAL NS SOA
rajeev.ns.cloudflare.com. 108.162.193.224 172.64.33.224 173.245.59.224 2606:4700:58::adf5:3be0 2803:f800:50::6ca2:c1e0 2a06:98c1:50::ac40:21e0				REFERRAL NS

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
108.162.192.182 PRIMARY lana.ns.cloudflare.com. PTR: lana.ns.cloudflare.com.	NAME	1232
108.162.193.224 rajeev.ns.cloudflare.com. PTR: rajeev.ns.cloudflare.com.	NAME	1232
172.64.32.182 PRIMARY lana.ns.cloudflare.com. PTR: lana.ns.cloudflare.com.	NAME	1232
172.64.33.224 rajeev.ns.cloudflare.com. PTR: rajeev.ns.cloudflare.com.	NAME	1232
173.245.58.182 PRIMARY lana.ns.cloudflare.com. PTR: lana.ns.cloudflare.com.	NAME	1232
173.245.59.224 rajeev.ns.cloudflare.com. PTR: rajeev.ns.cloudflare.com.	NAME	1232
2606:4700:50::adf5:3ab6 PRIMARY lana.ns.cloudflare.com. PTR: lana.ns.cloudflare.com.	NAME	1232
2606:4700:58::adf5:3be0 rajeev.ns.cloudflare.com. PTR: rajeev.ns.cloudflare.com.	NAME	1232
2803:f800:50::6ca2:c0b6 PRIMARY lana.ns.cloudflare.com. PTR: lana.ns.cloudflare.com.	NAME	1232
2803:f800:50::6ca2:c1e0 rajeev.ns.cloudflare.com. PTR: rajeev.ns.cloudflare.com.	NAME	1232
2a06:98c1:50::ac40:20b6 PRIMARY lana.ns.cloudflare.com. PTR: lana.ns.cloudflare.com.	NAME	1232
2a06:98c1:50::ac40:21e0 rajeev.ns.cloudflare.com. PTR: rajeev.ns.cloudflare.com.	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	lana.ns.cloudflare.com.
Email address of the persons responsible for this zone. Also known as RNAME.Admin email	dns.cloudflare.com.
Zone serial or version number.Serial number	-1955635994
The length of time secondary nameservers should wait before querying the primary for changes.Refresh interval	10,000 seconds (about 2 hours 46 minutes)
The length of time secondary nameservers should wait before querying an unresponsive primary again.Retry interval	2,400 seconds (about 40 minutes)
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	604,800 seconds (about 7 days)
TTL for purposes of negative response caching. Negative cache TTL	1,800 seconds (about 30 minutes)
Time To Live (TTL) indicates for how long a record remains valid. SOA record TTL	1,800 seconds (about 30 minutes)

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
vliegherrie.nl.	300	A	172.67.192.53
vliegherrie.nl.	300	A	104.21.65.203
www.vliegherrie.nl.	300	A	172.67.192.53
www.vliegherrie.nl.	300	A	104.21.65.203
vliegherrie.nl.	300	AAAA	2606:4700:3034:0:0:0:6815:41cb
vliegherrie.nl.	300	AAAA	2606:4700:3037:0:0:0:ac43:c035
www.vliegherrie.nl.	300	AAAA	2606:4700:3034:0:0:0:6815:41cb
www.vliegherrie.nl.	300	AAAA	2606:4700:3037:0:0:0:ac43:c035
vliegherrie.nl.	300	CAA	0 issue "pki.goog; cansignhttpexchanges=yes"
vliegherrie.nl.	300	CAA	0 issuewild "comodoca.com"
vliegherrie.nl.	300	CAA	0 issuewild "digicert.com; cansignhttpexchanges=yes"
vliegherrie.nl.	300	CAA	0 issuewild "letsencrypt.org"
vliegherrie.nl.	300	CAA	0 issuewild "pki.goog; cansignhttpexchanges=yes"
vliegherrie.nl.	300	CAA	0 issue "comodoca.com"
vliegherrie.nl.	300	CAA	0 issue "digicert.com; cansignhttpexchanges=yes"
vliegherrie.nl.	300	CAA	0 issue "globalsign.com"
vliegherrie.nl.	300	CAA	0 issue "letsencrypt.org"
vliegherrie.nl.	3600	DNSKEY	257 3 13 mdsswUyr3DPW132mOi8V9xESWE8jTo0dxCjjnopKl+GqJxpVXckHAeF+KkxLbxILfDLUT0rAK9iUzy1L53eKGQ==
vliegherrie.nl.	3600	DNSKEY	256 3 13 oJMRESz5E4gYzS/q6XDrvU1qMPYIjCWzJaOau8XNEZeqCYKD5ar0IRd8KqXXFJkqmVfRvMGPmM1x8fGAa2XhSA==
vliegherrie.nl.	300	HTTPS	1 . alpn=h3,h2 ipv4hint=104.21.65.203,172.67.192.53 ipv6hint=2606:4700:3034:0:0:0:6815:41cb,2606:4700:3037:0:0:0:ac43:c035
www.vliegherrie.nl.	300	HTTPS	1 . alpn=h3,h2 ipv4hint=104.21.65.203,172.67.192.53 ipv6hint=2606:4700:3034:0:0:0:6815:41cb,2606:4700:3037:0:0:0:ac43:c035
vliegherrie.nl.	300	MX	10 mx01.trustednetworks.nl.
vliegherrie.nl.	300	MX	20 mx01.trustednetworks.nl.
vliegherrie.nl.	86400	NS	lana.ns.cloudflare.com.
vliegherrie.nl.	86400	NS	rajeev.ns.cloudflare.com.
vliegherrie.nl.	1800	SOA	lana.ns.cloudflare.com. dns.cloudflare.com. 2339331302 10000 2400 604800 1800
vliegherrie.nl.	300	TXT	"google-site-verification=EvxeJwxzemzU1auEl_RGxtEEiMdlDWgxK0PALmMHYXA"
vliegherrie.nl.	300	TXT	"v=spf1 mx a include:amazonses.com -all"
_dmarc.vliegherrie.nl.	300	TXT	"v=DMARC1;p=quarantine;sp=quarantine;adkim=r;aspf=r;fo=1;rf=afrf;rua=mailto:dmarc@vliegherrie.nl;ruf=mailto:dmarc@vliegherrie.nl"
_mta-sts.vliegherrie.nl.	300	TXT	"v=STSv1; id=202107131544;"
_smtp._tls.vliegherrie.nl.	300	TXT	"v=TLSRPTv1;rua=mailto:ict@vliegherrie.nl"

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.

Test passed

Everything seems to be well configured. Well done.

CAA Policy Information

The DNS hostname where this policy is located.Policy host	vliegherrie.nl
The issuewild property has the same syntax and semantics as the issue property except that issuewild properties only grant authorization to issue certificates that specify a wildcard domain and issuewild properties take precedence over issue properties when specified.issuewild	digicert.com; cansignhttpexchanges=yes flags: 0
The issuewild property has the same syntax and semantics as the issue property except that issuewild properties only grant authorization to issue certificates that specify a wildcard domain and issuewild properties take precedence over issue properties when specified.issuewild	letsencrypt.org flags: 0
The issuewild property has the same syntax and semantics as the issue property except that issuewild properties only grant authorization to issue certificates that specify a wildcard domain and issuewild properties take precedence over issue properties when specified.issuewild	pki.goog; cansignhttpexchanges=yes flags: 0
The issue property tag is used to request that certificate issuers perform CAA issue restriction processing for the domain and to grant authorization to specific certificate issuers.issue	comodoca.com flags: 0
The issue property tag is used to request that certificate issuers perform CAA issue restriction processing for the domain and to grant authorization to specific certificate issuers.issue	digicert.com; cansignhttpexchanges=yes flags: 0
The issue property tag is used to request that certificate issuers perform CAA issue restriction processing for the domain and to grant authorization to specific certificate issuers.issue	globalsign.com flags: 0
The issue property tag is used to request that certificate issuers perform CAA issue restriction processing for the domain and to grant authorization to specific certificate issuers.issue	letsencrypt.org flags: 0
The issue property tag is used to request that certificate issuers perform CAA issue restriction processing for the domain and to grant authorization to specific certificate issuers.issue	pki.goog; cansignhttpexchanges=yes flags: 0
The issuewild property has the same syntax and semantics as the issue property except that issuewild properties only grant authorization to issue certificates that specify a wildcard domain and issuewild properties take precedence over issue properties when specified.issuewild	comodoca.com flags: 0

Analysis

CAA policy found

Good. This domain name uses CAA to restrict which CAs are allowed to issue certificates for it.

Policy doesn't use reporting

This policy doesn't use reporting, which means that there is no way to contact you when a violation is detected. The CAA RFC defines the iodef property that can be used for this purpose. Do note that you're not guaranteed to be notified, given that CAs generally don't support notifications yet.

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

mx01.trustednetworks.nl
2a03:b0c0:0:1010:0:0:30:6001
PTR: mx01.trustednetworks.nl

10

mx01.trustednetworks.nl
95.85.56.217
PTR: mx01.trustednetworks.nl

10

Analysis

Email servers match MTA-STS policy

Good. This host supports MTA-STS, which means that it restricts which MX servers can be used and how they are configured. We've verified that all MX servers listed here match the policy.

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: mx01.trustednetworks.nl (2a03:b0c0:0:1010:0:0:30:6001)

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.2 TLS v1.1 TLS v1.0
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.2 Unknown preference	Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA Suite ID: 0xc013 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 384 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA Suite ID: 0xc014 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA 256 bits (ECDHE 384 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 secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 128 bits (ECDHE 384 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 Suite ID: 0xc028 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 256 bits (ECDHE 384 bits) 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 secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 384 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 secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 384 bits) Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA Suite ID: 0x33 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: DHE_RSA Key exchange strength: 2048 bits Forward secrecy: Yes PRF: SHA TLS_DHE_RSA_WITH_AES_128_CBC_SHA 128 bits (DHE 2048 bits) Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA Suite ID: 0x39 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: DHE_RSA Key exchange strength: 2048 bits Forward secrecy: Yes PRF: SHA TLS_DHE_RSA_WITH_AES_256_CBC_SHA 256 bits (DHE 2048 bits) Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA256 Suite ID: 0x67 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: DHE_RSA Key exchange strength: 2048 bits Forward secrecy: Yes PRF: SHA256 TLS_DHE_RSA_WITH_AES_128_CBC_SHA256 128 bits (DHE 2048 bits) Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA256 Suite ID: 0x6b Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: DHE_RSA Key exchange strength: 2048 bits Forward secrecy: Yes PRF: SHA256 TLS_DHE_RSA_WITH_AES_256_CBC_SHA256 256 bits (DHE 2048 bits) Suite: TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0x9e Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: DHE_RSA Key exchange strength: 2048 bits Forward secrecy: Yes PRF: SHA256 TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (DHE 2048 bits) Suite: TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0x9f Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: DHE_RSA Key exchange strength: 2048 bits Forward secrecy: Yes PRF: SHA384 TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (DHE 2048 bits)
Shows cipher suite configuration for this protocol version.TLS v1.1 Unknown preference	Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA Suite ID: 0xc013 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 384 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA Suite ID: 0xc014 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA 256 bits (ECDHE 384 bits) Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA Suite ID: 0x33 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: DHE_RSA Key exchange strength: 2048 bits Forward secrecy: Yes PRF: SHA TLS_DHE_RSA_WITH_AES_128_CBC_SHA 128 bits (DHE 2048 bits) Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA Suite ID: 0x39 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: DHE_RSA Key exchange strength: 2048 bits Forward secrecy: Yes PRF: SHA TLS_DHE_RSA_WITH_AES_256_CBC_SHA 256 bits (DHE 2048 bits)
Shows cipher suite configuration for this protocol version.TLS v1.0 Unknown preference	Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA Suite ID: 0xc013 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 384 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA Suite ID: 0xc014 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA 256 bits (ECDHE 384 bits) Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA Suite ID: 0x33 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: DHE_RSA Key exchange strength: 2048 bits Forward secrecy: Yes PRF: SHA TLS_DHE_RSA_WITH_AES_128_CBC_SHA 128 bits (DHE 2048 bits) Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA Suite ID: 0x39 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: DHE_RSA Key exchange strength: 2048 bits Forward secrecy: Yes PRF: SHA TLS_DHE_RSA_WITH_AES_256_CBC_SHA 256 bits (DHE 2048 bits)

Analysis

Deprecated TLS 1.0 protocol supported

TLS 1.0 is a weak older protocol that should be phased out. Sites that aim at a wide audience might still need to support TLS 1.0 for the time being, because many older clients don't support newer protocol versions. Sites with a modern user base might be able to disable TLS 1.0 even now. We recommend that you enable logging of encryption parameters, after which you can examine your protocol usage and make decisions with confidence.

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.

Server doesn't enforce cipher suite preferences

Servers that don't enforce cipher suite preferences select the first cipher suite they support from the list provided by clients. This approach doesn't guarantee that best-possible cipher suite is negotiated.

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.

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.

DHE server parameter not reused

This server does not reuse the private value used for the Diffie-Hellman key exchange.

TLS Configuration: mx01.trustednetworks.nl (95.85.56.217)

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.2 TLS v1.1 TLS v1.0
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.2 Unknown preference	Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA Suite ID: 0xc013 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 384 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA Suite ID: 0xc014 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA 256 bits (ECDHE 384 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 secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 128 bits (ECDHE 384 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 Suite ID: 0xc028 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 256 bits (ECDHE 384 bits) 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 secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 384 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 secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 384 bits) Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA Suite ID: 0x33 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: DHE_RSA Key exchange strength: 2048 bits Forward secrecy: Yes PRF: SHA TLS_DHE_RSA_WITH_AES_128_CBC_SHA 128 bits (DHE 2048 bits) Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA Suite ID: 0x39 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: DHE_RSA Key exchange strength: 2048 bits Forward secrecy: Yes PRF: SHA TLS_DHE_RSA_WITH_AES_256_CBC_SHA 256 bits (DHE 2048 bits) Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA256 Suite ID: 0x67 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: DHE_RSA Key exchange strength: 2048 bits Forward secrecy: Yes PRF: SHA256 TLS_DHE_RSA_WITH_AES_128_CBC_SHA256 128 bits (DHE 2048 bits) Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA256 Suite ID: 0x6b Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: DHE_RSA Key exchange strength: 2048 bits Forward secrecy: Yes PRF: SHA256 TLS_DHE_RSA_WITH_AES_256_CBC_SHA256 256 bits (DHE 2048 bits) Suite: TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0x9e Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: DHE_RSA Key exchange strength: 2048 bits Forward secrecy: Yes PRF: SHA256 TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (DHE 2048 bits) Suite: TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0x9f Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: DHE_RSA Key exchange strength: 2048 bits Forward secrecy: Yes PRF: SHA384 TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (DHE 2048 bits)
Shows cipher suite configuration for this protocol version.TLS v1.1 Unknown preference	Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA Suite ID: 0xc013 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 384 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA Suite ID: 0xc014 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA 256 bits (ECDHE 384 bits) Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA Suite ID: 0x33 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: DHE_RSA Key exchange strength: 2048 bits Forward secrecy: Yes PRF: SHA TLS_DHE_RSA_WITH_AES_128_CBC_SHA 128 bits (DHE 2048 bits) Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA Suite ID: 0x39 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: DHE_RSA Key exchange strength: 2048 bits Forward secrecy: Yes PRF: SHA TLS_DHE_RSA_WITH_AES_256_CBC_SHA 256 bits (DHE 2048 bits)
Shows cipher suite configuration for this protocol version.TLS v1.0 Unknown preference	Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA Suite ID: 0xc013 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 384 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA Suite ID: 0xc014 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA 256 bits (ECDHE 384 bits) Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA Suite ID: 0x33 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: DHE_RSA Key exchange strength: 2048 bits Forward secrecy: Yes PRF: SHA TLS_DHE_RSA_WITH_AES_128_CBC_SHA 128 bits (DHE 2048 bits) Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA Suite ID: 0x39 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: DHE_RSA Key exchange strength: 2048 bits Forward secrecy: Yes PRF: SHA TLS_DHE_RSA_WITH_AES_256_CBC_SHA 256 bits (DHE 2048 bits)

Analysis

Deprecated TLS 1.0 protocol supported

TLS 1.0 is a weak older protocol that should be phased out. Sites that aim at a wide audience might still need to support TLS 1.0 for the time being, because many older clients don't support newer protocol versions. Sites with a modern user base might be able to disable TLS 1.0 even now. We recommend that you enable logging of encryption parameters, after which you can examine your protocol usage and make decisions with confidence.

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.

Server doesn't enforce cipher suite preferences

Servers that don't enforce cipher suite preferences select the first cipher suite they support from the list provided by clients. This approach doesn't guarantee that best-possible cipher suite is negotiated.

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.

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.

DHE server parameter not reused

This server does not reuse the private value used for the Diffie-Hellman key exchange.

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

mx01.trustednetworks.nl
Issuer: Let's Encrypt
Not Before: 07 Apr 2024 04:46:32 UTC
Not After: 06 Jul 2024 04:46:31 UTC (expires in 2 months 12 days)
Key: RSA 2048 bits
Signature: SHA256withRSA
View details

Names	mx01.trustednetworks.nl
Subject DN	CN=mx01.trustednetworks.nl
Subject Key Identifier	c4beff17218d39278721cc9746b90dbb3c477feb
Serial	4210e2567ac409132e594fafb5bc648ed37
Not Before	07 Apr 2024 04:46:32 UTC
Not After	06 Jul 2024 04:46:31 UTC
Validity period	90 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=R3, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:142eb317b75856cbae500940e61faf9d8b14c2c6
Parent Certificate	http://r3.i.lencr.org/
OCSP	http://r3.o.lencr.org
Certificate Transparency
Signed Certificate Timestamps	07 Apr 2024 05:46:32 UTC \| Let's Encrypt 'Oak2024H1' log \| Qualified 07 Apr 2024 05:46:32 UTC \| DigiCert Yeti2024 Log \| Qualified
Fingerprints
SHA1	ce2e09771d446f4018af9cc7561936e120a037e3
SHA256	6148220af39de83d474221f2dd21e4d663eb6401afbf675b5ca983f6716a3766
SPKI SHA256	7cc0c834adb35a9f0032176eade2870173e7a4a4951331f450974d8f96af9fbe

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

mx01.trustednetworks.nl | 6148220
Not After: 06 Jul 2024 04:46:31 UTC (expires in 2 months 12 days)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Names	mx01.trustednetworks.nl
Subject DN	CN=mx01.trustednetworks.nl
Subject Key Identifier	c4beff17218d39278721cc9746b90dbb3c477feb
Serial	4210e2567ac409132e594fafb5bc648ed37
Not Before	07 Apr 2024 04:46:32 UTC
Not After	06 Jul 2024 04:46:31 UTC
Validity period	90 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=R3, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:142eb317b75856cbae500940e61faf9d8b14c2c6
Parent Certificate	http://r3.i.lencr.org/
OCSP	http://r3.o.lencr.org
Certificate Transparency
Signed Certificate Timestamps	07 Apr 2024 05:46:32 UTC \| Let's Encrypt 'Oak2024H1' log \| Qualified 07 Apr 2024 05:46:32 UTC \| DigiCert Yeti2024 Log \| Qualified
Fingerprints
SHA1	ce2e09771d446f4018af9cc7561936e120a037e3
SHA256	6148220af39de83d474221f2dd21e4d663eb6401afbf675b5ca983f6716a3766
SPKI SHA256	7cc0c834adb35a9f0032176eade2870173e7a4a4951331f450974d8f96af9fbe

Intermediate certificate

R3 | 67add11
Not After: 15 Sep 2025 16:00:00 UTC (expires in 1 year 4 months)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Subject DN	CN=R3, O=Let's Encrypt, C=US
Subject Key Identifier	142eb317b75856cbae500940e61faf9d8b14c2c6
Serial	912b084acf0c18a753f6d62e25a75f5a
Not Before	04 Sep 2020 00:00:00 UTC
Not After	15 Sep 2025 16:00:00 UTC
Validity period	1838 days
Key Usage	digitalSignature, keyCertSign, cRLSign
Extended Key Usage	clientAuth, 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 0)
Fingerprints
SHA1	a053375bfe84e8b748782c7cee15827a6af5a405
SHA256	67add1166b020ae61b8f5fc96813c04c2aa589960796865572a3c7e737613dfd
SPKI SHA256	8d02536c887482bc34ff54e41d2ba659bf85b341a0a20afadb5813dcfbcf286d

Root certificate

ISRG Root X1 | 96bcec0
Not After: 04 Jun 2035 11:04:38 UTC (expires in 11 years 1 month)
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.

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

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	vliegherrie.nl
SPF version used by this policy.v	spf1
This mechanism matches if the sending IP address is one of the MX hosts for the domain name. mx
This mechanism matches if the sending IP address is one of the IP addresses that belong to the target domain name. Matches both IPv4 and IPv6 addresses. a
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

Analysis

SPF policy found

Policy text: v=spf1 mx a include:amazonses.com -all

Location: vliegherrie.nl

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: 3

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	52.82.172.0/22
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	54.240.64.0/19
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	54.240.96.0/19
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 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.vliegherrie.nl
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	quarantine
Requested mail receiver policy for all subdomains. Same format as for the p tag.sp	quarantine
Indicates whether strict or relaxed DKIM alignment mode is required.adkim	r
Indicates whether strict or relaxed SPF alignment mode is required.aspf	r
Configures failure reporting.fo	1
Specifies the format to be used when reporting failures.rf	afrf
Addresses to which aggregate feedback is to be sent.rua	mailto:dmarc@vliegherrie.nl
Addresses to which message-specific failure information is to be reported.ruf	mailto:dmarc@vliegherrie.nl

Analysis

DMARC policy found

Policy: v=DMARC1;p=quarantine;sp=quarantine;adkim=r;aspf=r;fo=1;rf=afrf;rua=mailto:dmarc@vliegherrie.nl;ruf=mailto:dmarc@vliegherrie.nl

Host: _dmarc.vliegherrie.nl

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.

Test passed

Everything seems to be well configured. Well done.

MTA-STS Policy Indicator

Location from which we retrieved the policy indicator.Location	_mta-sts.vliegherrie.nl
MTA-STS standard version used by this policy indicator.Version	STSv1
Unique policy identifier, whose value must change every time the underlying policy changes.ID	202107131544

Analysis

MTA-STS policy indicator valid

Good. Your MTA-STS policy indicator is valid.

MTA-STS Policy

The URL from which the policy was obtained.Location	https://mta-sts.vliegherrie.nl/.well-known/mta-sts.txt
Policy standard version.version	STSv1
Policy duration, which specifies how long the sending MTAs should remember and enforce the server policy for.max‑age	2,419,200 seconds (about 28 days)
Policy mode, which can be one of 'none', 'testing' and 'enforcing'. Guess which is best! :)mode	enforce
One 'mx' directive specifies one email server pattern that's allowed for this host.mx	mx01.trustednetworks.nl
One 'mx' directive specifies one email server pattern that's allowed for this host.mx	mx.trustednetworks.nl

Analysis

MTA-STS policy is valid

Good. Your MTA-STS policy is valid.

Policy host certificate is valid

Good. Your MTA-STS policy is delivered via a web server that has a valid publicly trusted certificate. This is a necessary condition for the policy to be recognized.

Policy HTTPS response information

Status code: 200

Length: 100 bytes

Content-Type: text/plain; charset=utf-8

Certificate: mta-sts.vliegherrie.nl

Leaf certificate

vliegherrie.nl
Issuer: Let's Encrypt
Not Before: 23 Apr 2024 03:12:51 UTC
Not After: 22 Jul 2024 03:12:50 UTC (expires in 2 months 28 days)
Key: EC 256 bits
Signature: SHA384withECDSA
View details

Names	*.vliegherrie.nl vliegherrie.nl
Subject DN	CN=vliegherrie.nl
Subject Key Identifier	85633fe6072462d31165fb8c6bffda9b08139a68
Serial	396056868b5c5a4e740853ff37971a9e002
Not Before	23 Apr 2024 03:12:51 UTC
Not After	22 Jul 2024 03:12:50 UTC
Validity period	90 days
Key Usage	digitalSignature
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=E1, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:5af3ed2bfc36c23779b95230ea546fcf55cb2eac
Parent Certificate	http://e1.i.lencr.org/
OCSP	http://e1.o.lencr.org
Certificate Transparency
Signed Certificate Timestamps	23 Apr 2024 04:12:51 UTC \| Google 'Argon2024' log \| Qualified 23 Apr 2024 04:12:51 UTC \| Sectigo 'Mammoth2024h2' \| Qualified
Fingerprints
SHA1	51a2b2dc7d0d02d507903d4ed5f246b7c503f99c
SHA256	b22ac184fb549b63264bc1c8cb54550f5c3e415b17521d986a1a2c0a2ad9b4f2
SPKI SHA256	0136430e10a7965e7f223210437b2988cc9115b7232b6a55302e5de12a4f8660

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

vliegherrie.nl | b22ac18
Not After: 22 Jul 2024 03:12:50 UTC (expires in 2 months 28 days)
Authentication: EC 256 bits (SHA384withECDSA)
View details

Names	*.vliegherrie.nl vliegherrie.nl
Subject DN	CN=vliegherrie.nl
Subject Key Identifier	85633fe6072462d31165fb8c6bffda9b08139a68
Serial	396056868b5c5a4e740853ff37971a9e002
Not Before	23 Apr 2024 03:12:51 UTC
Not After	22 Jul 2024 03:12:50 UTC
Validity period	90 days
Key Usage	digitalSignature
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=E1, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:5af3ed2bfc36c23779b95230ea546fcf55cb2eac
Parent Certificate	http://e1.i.lencr.org/
OCSP	http://e1.o.lencr.org
Certificate Transparency
Signed Certificate Timestamps	23 Apr 2024 04:12:51 UTC \| Google 'Argon2024' log \| Qualified 23 Apr 2024 04:12:51 UTC \| Sectigo 'Mammoth2024h2' \| Qualified
Fingerprints
SHA1	51a2b2dc7d0d02d507903d4ed5f246b7c503f99c
SHA256	b22ac184fb549b63264bc1c8cb54550f5c3e415b17521d986a1a2c0a2ad9b4f2
SPKI SHA256	0136430e10a7965e7f223210437b2988cc9115b7232b6a55302e5de12a4f8660

Intermediate certificate

E1 | 46494e3
Not After: 15 Sep 2025 16:00:00 UTC (expires in 1 year 4 months)
Authentication: EC 384 bits (SHA384withECDSA)
View details

Subject DN	CN=E1, O=Let's Encrypt, C=US
Subject Key Identifier	5af3ed2bfc36c23779b95230ea546fcf55cb2eac
Serial	b3bddff8a7845bbce903a04135b34a45
Not Before	04 Sep 2020 00:00:00 UTC
Not After	15 Sep 2025 16:00:00 UTC
Validity period	1838 days
Key Usage	digitalSignature, keyCertSign, cRLSign
Extended Key Usage	clientAuth, serverAuth
Issuer
Issuer DN	CN=ISRG Root X2, O=Internet Security Research Group, C=US
Certification Authority	Let's Encrypt
Validation Type	Not Applicable
Authority Key Identifier	keyid:7c4296aede4b483bfa92f89e8ccf6d8ba9723795
Parent Certificate	http://x2.i.lencr.org/
CRL	http://x2.c.lencr.org/
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	091e8ea1b256a312962af6c140c0fbf079a407b3
SHA256	46494e30379059df18be52124305e606fc59070e5b21076ce113954b60517cda
SPKI SHA256	276fe8a8c4ec7611565bf9fce6dcace9be320c1b5bea27596b2204071ed04f10

Intermediate certificate

ISRG Root X2 | 8b05b68
Not After: 15 Sep 2025 16:00:00 UTC (expires in 1 year 4 months)
Authentication: EC 384 bits (SHA256withRSA)
View details

Subject DN	CN=ISRG Root X2, O=Internet Security Research Group, C=US
Subject Key Identifier	7c4296aede4b483bfa92f89e8ccf6d8ba9723795
Serial	79e492886376fd40848c23fc631e463
Not Before	04 Sep 2020 00:00:00 UTC
Not After	15 Sep 2025 16:00:00 UTC
Validity period	1838 days
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	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	151682f5218c0a511c28f4060a73b9ca78ce9a53
SHA256	8b05b68cc659e5ed0fcb38f2c942fbfd200e6f2ff9f85d63c6994ef5e0b02701
SPKI SHA256	762195c225586ee6c0237456e2107dc54f1efc21f61a792ebd515913cce68332

Intermediate certificate

ISRG Root X1 | 6d99fb2
Not After: 30 Sep 2024 18:14:03 UTC (expires in 5 months 6 days)
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	4001772137d4e942b8ee76aa3c640ab7
Not Before	20 Jan 2021 19:14:03 UTC
Not After	30 Sep 2024 18:14:03 UTC
Validity period	1349 days
Key Usage	keyCertSign, cRLSign
Issuer
Issuer DN	CN=DST Root CA X3, O=Digital Signature Trust Co.
Certification Authority	IdenTrust Services, LLC
Validation Type	Not Applicable
Authority Key Identifier	keyid:c4a7b1a47b2c71fadbe14b9075ffc41560858910
Parent Certificate	http://apps.identrust.com/roots/dstrootcax3.p7c
CRL	http://crl.identrust.com/DSTROOTCAX3CRL.crl
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	933c6ddee95c9c41a40f9f50493d82be03ad87bf
SHA256	6d99fb265eb1c5b3744765fcbc648f3cd8e1bffafdc4c2f99b9d47cf7ff1c24f
SPKI SHA256	0b9fa5a59eed715c26c1020c711b4f6ec42d58b0015e14337a39dad301c5afc3

Root certificate

DST Root CA X3 | 0687260
Not After: 30 Sep 2021 14:01:15 UTC (expired 2 years 6 months ago)
Authentication: RSA 2048 bits (SHA1withRSA)
View details

Subject DN	CN=DST Root CA X3, O=Digital Signature Trust Co.
Subject Key Identifier	c4a7b1a47b2c71fadbe14b9075ffc41560858910
Serial	44afb080d6a327ba893039862ef8406b
Not Before	30 Sep 2000 21:12:19 UTC
Not After	30 Sep 2021 14:01:15 UTC (expired 2 years 6 months ago)
Key Usage	keyCertSign, cRLSign
Issuer
Issuer DN	CN=DST Root CA X3, O=Digital Signature Trust Co.
Certification Authority	IdenTrust Services, LLC
Validation Type	Self-signed
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	dac9024f54d8f6df94935fb1732638ca6ad77c13
SHA256	0687260331a72403d909f105e69bcf0d32e1bd2493ffc6d9206d11bcd6770739
SPKI SHA256	563b3caf8cfef34c2335caf560a7a95906e8488462eb75ac59784830df9e5b2b

Analysis

Certificate chain is correct

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

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.

Test passed

Everything seems to be well configured. Well done.

TLS-RPT Policy

Location from which we retrieved the policy indicator.Location	_smtp._tls.vliegherrie.nl
TLS-RPT standard version used by this policy indicator.Version	TLSRPTv1
Reporting endpoints specified in the policy.Reporting Endpoints	mailto:ict@vliegherrie.nl

Analysis

SMTP TLS-RPT policy valid

Good. Your TLS-RPT policy is valid. SMTP TLS Reporting is a young standard that is not yet widely supported, but support is probably going to increase over time.

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://vliegherrie.nl/

1

http://vliegherrie.nl/

HTTP/1.1 301 Moved Permanently

Date	Tue, 23 Apr 2024 20:18:55 GMT
Content-Type	text/html
Content-Length	167
Connection	keep-alive
Cache-Control	max-age=3600
Expires	Tue, 23 Apr 2024 21:18:55 GMT
Location	https://vliegherrie.nl/
Report-To	{"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v4?s=K5A6orUyMg%2BCNAIz4fiAMd6%2FmhMqGRp4MRbuw8Q7PuE11pvnCbEGr6TCjpriM7tPuihPVBeJ95aNba9bMIIglKPVtFhXVrRxJckwx1AS99T7g3Ak3Xt02hAVGaB78XKFIg%3D%3D"}],"group":"cf-nel","max_age":604800}
NEL	{"success_fraction":0,"report_to":"cf-nel","max_age":604800}
Vary	Accept-Encoding
X-Content-Type-Options	nosniff
Server	cloudflare
CF-RAY	87908ba768525962-IAD
alt-svc	h3=":443"; ma=86400

2

https://vliegherrie.nl/

HTTP/1.1 200 OK

Date	Tue, 23 Apr 2024 20:18:55 GMT
Content-Type	text/html; charset=utf-8
Transfer-Encoding	chunked
Connection	keep-alive
CF-Ray	87908ba7ea0e28ba-IAD
CF-Cache-Status	DYNAMIC
Cache-Control	public, max-age=3600
Content-Language	nl
Expires	Sun, 19 Nov 1978 05:00:00 GMT
Last-Modified	Tue, 23 Apr 2024 20:17:25 GMT
Link	<https://vliegherrie.nl/static/img/vtdark.jpg>; rel="image_src",<https://vliegherrie.nl/>; rel="canonical",<https://vliegherrie.nl/>; rel="shortlink"
Strict-Transport-Security	max-age=31536000; includeSubDomains; preload
Vary	Cookie,Accept-Encoding
Content-Security-Policy	upgrade-insecure-requests ; form-action vliegherrie.nl syndication.twitter.com platform.twitter.com www.paypal.com;
Feature-Policy	geolocation 'none'; microphone 'none'
Referrer-Policy	no-referrer-when-downgrade
X-Content-Type-Options	nosniff
X-Drupal-Cache	HIT
X-Frame-Options	SAMEORIGIN
X-Trace	2B692E467D2064D0B0BA12E0A6DC74335FA76A834B7C1E57E8E2BCB81E01
X-XSS-Protection	0
Report-To	{"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v4?s=IcRliYz3i3uYHKDgPuZ24U5oZwot%2BoatkDdv5PcN4nH4mDC1JYYWqFrZw8%2BA9s5H7gPLrfEi9JrofkqljZEgVP3Hyo9grq%2BQpbOk0kZaQ7BwPEP4F4r7NhXKU9M%2Br%2FikqQ%3D%3D"}],"group":"cf-nel","max_age":604800}
NEL	{"success_fraction":0,"report_to":"cf-nel","max_age":604800}
Server	cloudflare
alt-svc	h3=":443"; ma=86400

Analysis

HTTP redirects to HTTPS

Good. This plaintext HTTP server redirects to HTTPS.

URL: http://www.vliegherrie.nl/

1

http://www.vliegherrie.nl/

HTTP/1.1 301 Moved Permanently

Date	Tue, 23 Apr 2024 20:18:55 GMT
Content-Type	text/html
Content-Length	167
Connection	keep-alive
Cache-Control	max-age=3600
Expires	Tue, 23 Apr 2024 21:18:55 GMT
Location	https://www.vliegherrie.nl/
Report-To	{"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v4?s=2qST9PjyDZE%2FbDfMpOaBjR1Ue79YzAMnzvowxrPAiKL0rXLCmDgZikhKnc06fDlGUH%2BySmybibMjF1jAH4TTX%2BQHHiqjwcABlqpNB6YNJVZfuGr2uv6D9AUbvSJpsoyiK%2F%2FXVog%3D"}],"group":"cf-nel","max_age":604800}
NEL	{"success_fraction":0,"report_to":"cf-nel","max_age":604800}
Vary	Accept-Encoding
X-Content-Type-Options	nosniff
Server	cloudflare
CF-RAY	87908baa3efe5716-IAD
alt-svc	h3=":443"; ma=86400

2

https://www.vliegherrie.nl/

HTTP/1.1 301 Moved Permanently

Date	Tue, 23 Apr 2024 20:18:56 GMT
Content-Type	text/html; charset=iso-8859-1
Transfer-Encoding	chunked
Connection	keep-alive
Location	https://vliegherrie.nl/
CF-Ray	87908baabbe007b7-IAD
CF-Cache-Status	DYNAMIC
Cache-Control	max-age=864000
Expires	Fri, 03 May 2024 20:18:56 GMT
Strict-Transport-Security	max-age=31536000; includeSubDomains; preload
Content-Security-Policy	upgrade-insecure-requests ; form-action vliegherrie.nl syndication.twitter.com platform.twitter.com www.paypal.com;
Feature-Policy	geolocation 'none'; microphone 'none'
Referrer-Policy	no-referrer-when-downgrade
X-Content-Type-Options	nosniff
X-Frame-Options	SAMEORIGIN
X-XSS-Protection	0
Report-To	{"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v4?s=ZFVkGSZExt1Vzuj6rX4zuE5%2Fr2jpzuYlTcqloHnRBEd7ruICaGbHvUo%2F%2FyAz1tfh4fxjwCaeIVdRS4TemVi8OYs8xbhlXaD74Jjn6khb8XrCCVvCM8YxeP0cfGQ%2FhADdnMv6MKc%3D"}],"group":"cf-nel","max_age":604800}
NEL	{"success_fraction":0,"report_to":"cf-nel","max_age":604800}
Vary	Accept-Encoding
Server	cloudflare
alt-svc	h3=":443"; ma=86400

3

https://vliegherrie.nl/

HTTP/1.1 200 OK

Date	Tue, 23 Apr 2024 20:18:56 GMT
Content-Type	text/html; charset=utf-8
Transfer-Encoding	chunked
Connection	keep-alive
CF-Ray	87908bad980e9c5b-IAD
CF-Cache-Status	DYNAMIC
Cache-Control	public, max-age=3600
Content-Language	nl
Expires	Sun, 19 Nov 1978 05:00:00 GMT
Last-Modified	Tue, 23 Apr 2024 20:17:25 GMT
Link	<https://vliegherrie.nl/static/img/vtdark.jpg>; rel="image_src",<https://vliegherrie.nl/>; rel="canonical",<https://vliegherrie.nl/>; rel="shortlink"
Strict-Transport-Security	max-age=31536000; includeSubDomains; preload
Vary	Cookie,Accept-Encoding
Content-Security-Policy	upgrade-insecure-requests ; form-action vliegherrie.nl syndication.twitter.com platform.twitter.com www.paypal.com;
Feature-Policy	geolocation 'none'; microphone 'none'
Referrer-Policy	no-referrer-when-downgrade
X-Content-Type-Options	nosniff
X-Drupal-Cache	HIT
X-Frame-Options	SAMEORIGIN
X-Trace	2B4D2A0A428BD80F82C52FEFA125543A6BE5D6D545E2DC5C0D37BBB1B301
X-XSS-Protection	0
Report-To	{"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v4?s=5Q1eW4OEDSdGh0J%2BW0BFmDPNDI8JmJEsnSmFZQwY30OJ6b%2F0OJnDBFXzb8IT5%2Fe1hxzhjP486hm1BJWQUmz9Rtj8NNq1AbJBze4G%2Bj2ywkKqYu0hlWEEydDFW7EHN6Yzgd%2Bb%2FYN9nNSAAzIjoA%3D%3D"}],"group":"cf-nel","max_age":604800}
NEL	{"success_fraction":0,"report_to":"cf-nel","max_age":604800}
Server	cloudflare
alt-svc	h3=":443"; ma=86400

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://vliegherrie.nl/

1

https://vliegherrie.nl/

HTTP/1.1 200 OK

Date	Tue, 23 Apr 2024 20:18:57 GMT
Content-Type	text/html; charset=utf-8
Transfer-Encoding	chunked
Connection	keep-alive
CF-Ray	87908bb0f8f12429-IAD
CF-Cache-Status	DYNAMIC
Cache-Control	public, max-age=3600
Content-Language	nl
Expires	Sun, 19 Nov 1978 05:00:00 GMT
Last-Modified	Tue, 23 Apr 2024 20:17:25 GMT
Link	<https://vliegherrie.nl/static/img/vtdark.jpg>; rel="image_src",<https://vliegherrie.nl/>; rel="canonical",<https://vliegherrie.nl/>; rel="shortlink"
Strict-Transport-Security	max-age=31536000; includeSubDomains; preload
Vary	Cookie,Accept-Encoding
Content-Security-Policy	upgrade-insecure-requests ; form-action vliegherrie.nl syndication.twitter.com platform.twitter.com www.paypal.com;
Feature-Policy	geolocation 'none'; microphone 'none'
Referrer-Policy	no-referrer-when-downgrade
X-Content-Type-Options	nosniff
X-Drupal-Cache	HIT
X-Frame-Options	SAMEORIGIN
X-Trace	2B691DFD3EB77AB1F0E7BB79B3B50D59365F4CFB35F8125C46F222F1C701
X-XSS-Protection	0
Report-To	{"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v4?s=SoVV9vUTUyrmclgYe66ia55genslCMbAk%2FlnJH4BcLA7f7q%2FfEbqus66F34ktNc9b4aNL5GPaRfQxict%2F58ft30C%2FCbWie7KLSA2jyp%2BLIAikr%2BiqhhuuN%2FQEM%2Fy8IguYw%3D%3D"}],"group":"cf-nel","max_age":604800}
NEL	{"success_fraction":0,"report_to":"cf-nel","max_age":604800}
Server	cloudflare
alt-svc	h3=":443"; ma=86400

URL: https://www.vliegherrie.nl/

1

https://www.vliegherrie.nl/

HTTP/1.1 301 Moved Permanently

Date	Tue, 23 Apr 2024 20:18:57 GMT
Content-Type	text/html; charset=iso-8859-1
Transfer-Encoding	chunked
Connection	keep-alive
Location	https://vliegherrie.nl/
CF-Ray	87908bb3de0a07e0-IAD
CF-Cache-Status	DYNAMIC
Cache-Control	max-age=864000
Expires	Fri, 03 May 2024 20:18:57 GMT
Strict-Transport-Security	max-age=31536000; includeSubDomains; preload
Content-Security-Policy	upgrade-insecure-requests ; form-action vliegherrie.nl syndication.twitter.com platform.twitter.com www.paypal.com;
Feature-Policy	geolocation 'none'; microphone 'none'
Referrer-Policy	no-referrer-when-downgrade
X-Content-Type-Options	nosniff
X-Frame-Options	SAMEORIGIN
X-XSS-Protection	0
Report-To	{"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v4?s=1jMrTEfEpByY42qXFkQjZeWZUovMw8wDeOxsU2RZDG8dZmhKQaFG1awQN938Yz7uVxUTsdZ0x0Au6OZGSpneD6MWsFhaB4IMm8Q3Z504t0SPD0Xg72MsrGovgetDksM3lhkbKgo%3D"}],"group":"cf-nel","max_age":604800}
NEL	{"success_fraction":0,"report_to":"cf-nel","max_age":604800}
Vary	Accept-Encoding
Server	cloudflare
alt-svc	h3=":443"; ma=86400

2

https://vliegherrie.nl/

HTTP/1.1 200 OK

Date	Tue, 23 Apr 2024 20:18:57 GMT
Content-Type	text/html; charset=utf-8
Transfer-Encoding	chunked
Connection	keep-alive
CF-Ray	87908bb61a5d0819-IAD
CF-Cache-Status	DYNAMIC
Cache-Control	public, max-age=3600
Content-Language	nl
Expires	Sun, 19 Nov 1978 05:00:00 GMT
Last-Modified	Tue, 23 Apr 2024 20:17:25 GMT
Link	<https://vliegherrie.nl/static/img/vtdark.jpg>; rel="image_src",<https://vliegherrie.nl/>; rel="canonical",<https://vliegherrie.nl/>; rel="shortlink"
Strict-Transport-Security	max-age=31536000; includeSubDomains; preload
Vary	Cookie,Accept-Encoding
Content-Security-Policy	upgrade-insecure-requests ; form-action vliegherrie.nl syndication.twitter.com platform.twitter.com www.paypal.com;
Feature-Policy	geolocation 'none'; microphone 'none'
Referrer-Policy	no-referrer-when-downgrade
X-Content-Type-Options	nosniff
X-Drupal-Cache	HIT
X-Frame-Options	SAMEORIGIN
X-Trace	2B85320F85BB7180693516B6DA1250CADA3AADFF35097B11156AF4677201
X-XSS-Protection	0
Report-To	{"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v4?s=eUYN8n995nnTcWz3EAhiqz2hhPEocuW5bbUTZ7u3hTxSK27IfvVmZ6bMAYLbvZ5wyU6fl37918hkVIxe0A9DW6qLwujXbJQNv8l4KRhGAcu2tbuN3hC3ZAYVgfXyBfAUDAvASmehXfl1jlL4ig%3D%3D"}],"group":"cf-nel","max_age":604800}
NEL	{"success_fraction":0,"report_to":"cf-nel","max_age":604800}
Server	cloudflare
alt-svc	h3=":443"; ma=86400

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: vliegherrie.nl (2606:4700:3034:0:0:0:6815:41cb)

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: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 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: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_AES_128_GCM_SHA256 128 bits (ECDHE 256 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: 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 Server preference	Suite: AGL_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcc14 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 AGL_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca9 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02b Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA Suite ID: 0xc009 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc02c Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA Suite ID: 0xc00a Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 Suite ID: 0xc023 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 Suite ID: 0xc024 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 256 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 settings 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

DHE suites not supported

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

TLS Configuration: www.vliegherrie.nl (2606:4700:3034:0:0:0:6815:41cb)

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: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 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: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_AES_128_GCM_SHA256 128 bits (ECDHE 256 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: 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 Server preference	Suite: AGL_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcc14 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 AGL_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca9 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02b Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA Suite ID: 0xc009 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc02c Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA Suite ID: 0xc00a Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 Suite ID: 0xc023 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 Suite ID: 0xc024 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 256 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 settings 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

DHE suites not supported

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

TLS Configuration: www.vliegherrie.nl (2606:4700:3037:0:0:0:ac43:c035)

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: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 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: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_AES_128_GCM_SHA256 128 bits (ECDHE 256 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: 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 Server preference	Suite: AGL_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcc14 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 AGL_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca9 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02b Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA Suite ID: 0xc009 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc02c Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA Suite ID: 0xc00a Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 Suite ID: 0xc023 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 Suite ID: 0xc024 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 256 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 settings 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

DHE suites not supported

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

TLS Configuration: vliegherrie.nl (2606:4700:3037:0:0:0:ac43:c035)

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: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 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: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_AES_128_GCM_SHA256 128 bits (ECDHE 256 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: 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 Server preference	Suite: AGL_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcc14 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 AGL_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca9 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02b Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA Suite ID: 0xc009 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc02c Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA Suite ID: 0xc00a Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 Suite ID: 0xc023 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 Suite ID: 0xc024 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 256 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 settings 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

DHE suites not supported

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

TLS Configuration: www.vliegherrie.nl (104.21.65.203)

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: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 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: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_AES_128_GCM_SHA256 128 bits (ECDHE 256 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: 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 Server preference	Suite: AGL_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcc14 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 AGL_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca9 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02b Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA Suite ID: 0xc009 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc02c Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA Suite ID: 0xc00a Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 Suite ID: 0xc023 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 Suite ID: 0xc024 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 256 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 settings 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

DHE suites not supported

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

TLS Configuration: www.vliegherrie.nl (172.67.192.53)

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: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 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: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_AES_128_GCM_SHA256 128 bits (ECDHE 256 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: 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 Server preference	Suite: AGL_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcc14 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 AGL_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca9 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02b Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA Suite ID: 0xc009 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc02c Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA Suite ID: 0xc00a Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 Suite ID: 0xc023 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 Suite ID: 0xc024 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 256 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 settings 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

DHE suites not supported

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

TLS Configuration: vliegherrie.nl (172.67.192.53)

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: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 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: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_AES_128_GCM_SHA256 128 bits (ECDHE 256 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: 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 Server preference	Suite: AGL_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcc14 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 AGL_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca9 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02b Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA Suite ID: 0xc009 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc02c Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA Suite ID: 0xc00a Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 Suite ID: 0xc023 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 Suite ID: 0xc024 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 256 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 settings 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

DHE suites not supported

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

TLS Configuration: vliegherrie.nl (104.21.65.203)

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: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 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: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_AES_128_GCM_SHA256 128 bits (ECDHE 256 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: 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 Server preference	Suite: AGL_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcc14 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 AGL_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca9 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02b Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA Suite ID: 0xc009 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc02c Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA Suite ID: 0xc00a Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 Suite ID: 0xc023 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 Suite ID: 0xc024 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 256 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 settings 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

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: vliegherrie.nl

Leaf certificate

vliegherrie.nl
Issuer: Let's Encrypt
Not Before: 23 Apr 2024 03:12:51 UTC
Not After: 22 Jul 2024 03:12:50 UTC (expires in 2 months 28 days)
Key: EC 256 bits
Signature: SHA384withECDSA
View details

Names	*.vliegherrie.nl vliegherrie.nl
Subject DN	CN=vliegherrie.nl
Subject Key Identifier	85633fe6072462d31165fb8c6bffda9b08139a68
Serial	396056868b5c5a4e740853ff37971a9e002
Not Before	23 Apr 2024 03:12:51 UTC
Not After	22 Jul 2024 03:12:50 UTC
Validity period	90 days
Key Usage	digitalSignature
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=E1, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:5af3ed2bfc36c23779b95230ea546fcf55cb2eac
Parent Certificate	http://e1.i.lencr.org/
OCSP	http://e1.o.lencr.org
Certificate Transparency
Signed Certificate Timestamps	23 Apr 2024 04:12:51 UTC \| Google 'Argon2024' log \| Qualified 23 Apr 2024 04:12:51 UTC \| Sectigo 'Mammoth2024h2' \| Qualified
Fingerprints
SHA1	51a2b2dc7d0d02d507903d4ed5f246b7c503f99c
SHA256	b22ac184fb549b63264bc1c8cb54550f5c3e415b17521d986a1a2c0a2ad9b4f2
SPKI SHA256	0136430e10a7965e7f223210437b2988cc9115b7232b6a55302e5de12a4f8660

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

vliegherrie.nl | b22ac18
Not After: 22 Jul 2024 03:12:50 UTC (expires in 2 months 28 days)
Authentication: EC 256 bits (SHA384withECDSA)
View details

Names	*.vliegherrie.nl vliegherrie.nl
Subject DN	CN=vliegherrie.nl
Subject Key Identifier	85633fe6072462d31165fb8c6bffda9b08139a68
Serial	396056868b5c5a4e740853ff37971a9e002
Not Before	23 Apr 2024 03:12:51 UTC
Not After	22 Jul 2024 03:12:50 UTC
Validity period	90 days
Key Usage	digitalSignature
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=E1, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:5af3ed2bfc36c23779b95230ea546fcf55cb2eac
Parent Certificate	http://e1.i.lencr.org/
OCSP	http://e1.o.lencr.org
Certificate Transparency
Signed Certificate Timestamps	23 Apr 2024 04:12:51 UTC \| Google 'Argon2024' log \| Qualified 23 Apr 2024 04:12:51 UTC \| Sectigo 'Mammoth2024h2' \| Qualified
Fingerprints
SHA1	51a2b2dc7d0d02d507903d4ed5f246b7c503f99c
SHA256	b22ac184fb549b63264bc1c8cb54550f5c3e415b17521d986a1a2c0a2ad9b4f2
SPKI SHA256	0136430e10a7965e7f223210437b2988cc9115b7232b6a55302e5de12a4f8660

Intermediate certificate

E1 | 46494e3
Not After: 15 Sep 2025 16:00:00 UTC (expires in 1 year 4 months)
Authentication: EC 384 bits (SHA384withECDSA)
View details

Subject DN	CN=E1, O=Let's Encrypt, C=US
Subject Key Identifier	5af3ed2bfc36c23779b95230ea546fcf55cb2eac
Serial	b3bddff8a7845bbce903a04135b34a45
Not Before	04 Sep 2020 00:00:00 UTC
Not After	15 Sep 2025 16:00:00 UTC
Validity period	1838 days
Key Usage	digitalSignature, keyCertSign, cRLSign
Extended Key Usage	clientAuth, serverAuth
Issuer
Issuer DN	CN=ISRG Root X2, O=Internet Security Research Group, C=US
Certification Authority	Let's Encrypt
Validation Type	Not Applicable
Authority Key Identifier	keyid:7c4296aede4b483bfa92f89e8ccf6d8ba9723795
Parent Certificate	http://x2.i.lencr.org/
CRL	http://x2.c.lencr.org/
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	091e8ea1b256a312962af6c140c0fbf079a407b3
SHA256	46494e30379059df18be52124305e606fc59070e5b21076ce113954b60517cda
SPKI SHA256	276fe8a8c4ec7611565bf9fce6dcace9be320c1b5bea27596b2204071ed04f10

Intermediate certificate

ISRG Root X2 | 8b05b68
Not After: 15 Sep 2025 16:00:00 UTC (expires in 1 year 4 months)
Authentication: EC 384 bits (SHA256withRSA)
View details

Subject DN	CN=ISRG Root X2, O=Internet Security Research Group, C=US
Subject Key Identifier	7c4296aede4b483bfa92f89e8ccf6d8ba9723795
Serial	79e492886376fd40848c23fc631e463
Not Before	04 Sep 2020 00:00:00 UTC
Not After	15 Sep 2025 16:00:00 UTC
Validity period	1838 days
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	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	151682f5218c0a511c28f4060a73b9ca78ce9a53
SHA256	8b05b68cc659e5ed0fcb38f2c942fbfd200e6f2ff9f85d63c6994ef5e0b02701
SPKI SHA256	762195c225586ee6c0237456e2107dc54f1efc21f61a792ebd515913cce68332

Intermediate certificate

ISRG Root X1 | 6d99fb2
Not After: 30 Sep 2024 18:14:03 UTC (expires in 5 months 6 days)
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	4001772137d4e942b8ee76aa3c640ab7
Not Before	20 Jan 2021 19:14:03 UTC
Not After	30 Sep 2024 18:14:03 UTC
Validity period	1349 days
Key Usage	keyCertSign, cRLSign
Issuer
Issuer DN	CN=DST Root CA X3, O=Digital Signature Trust Co.
Certification Authority	IdenTrust Services, LLC
Validation Type	Not Applicable
Authority Key Identifier	keyid:c4a7b1a47b2c71fadbe14b9075ffc41560858910
Parent Certificate	http://apps.identrust.com/roots/dstrootcax3.p7c
CRL	http://crl.identrust.com/DSTROOTCAX3CRL.crl
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	933c6ddee95c9c41a40f9f50493d82be03ad87bf
SHA256	6d99fb265eb1c5b3744765fcbc648f3cd8e1bffafdc4c2f99b9d47cf7ff1c24f
SPKI SHA256	0b9fa5a59eed715c26c1020c711b4f6ec42d58b0015e14337a39dad301c5afc3

Root certificate

DST Root CA X3 | 0687260
Not After: 30 Sep 2021 14:01:15 UTC (expired 2 years 6 months ago)
Authentication: RSA 2048 bits (SHA1withRSA)
View details

Subject DN	CN=DST Root CA X3, O=Digital Signature Trust Co.
Subject Key Identifier	c4a7b1a47b2c71fadbe14b9075ffc41560858910
Serial	44afb080d6a327ba893039862ef8406b
Not Before	30 Sep 2000 21:12:19 UTC
Not After	30 Sep 2021 14:01:15 UTC (expired 2 years 6 months ago)
Key Usage	keyCertSign, cRLSign
Issuer
Issuer DN	CN=DST Root CA X3, O=Digital Signature Trust Co.
Certification Authority	IdenTrust Services, LLC
Validation Type	Self-signed
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	dac9024f54d8f6df94935fb1732638ca6ad77c13
SHA256	0687260331a72403d909f105e69bcf0d32e1bd2493ffc6d9206d11bcd6770739
SPKI SHA256	563b3caf8cfef34c2335caf560a7a95906e8488462eb75ac59784830df9e5b2b

Analysis

Certificate chain is correct

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

Certificate: www.vliegherrie.nl

Leaf certificate

vliegherrie.nl
Issuer: Let's Encrypt
Not Before: 23 Apr 2024 03:12:51 UTC
Not After: 22 Jul 2024 03:12:50 UTC (expires in 2 months 28 days)
Key: EC 256 bits
Signature: SHA384withECDSA
View details

Names	*.vliegherrie.nl vliegherrie.nl
Subject DN	CN=vliegherrie.nl
Subject Key Identifier	85633fe6072462d31165fb8c6bffda9b08139a68
Serial	396056868b5c5a4e740853ff37971a9e002
Not Before	23 Apr 2024 03:12:51 UTC
Not After	22 Jul 2024 03:12:50 UTC
Validity period	90 days
Key Usage	digitalSignature
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=E1, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:5af3ed2bfc36c23779b95230ea546fcf55cb2eac
Parent Certificate	http://e1.i.lencr.org/
OCSP	http://e1.o.lencr.org
Certificate Transparency
Signed Certificate Timestamps	23 Apr 2024 04:12:51 UTC \| Google 'Argon2024' log \| Qualified 23 Apr 2024 04:12:51 UTC \| Sectigo 'Mammoth2024h2' \| Qualified
Fingerprints
SHA1	51a2b2dc7d0d02d507903d4ed5f246b7c503f99c
SHA256	b22ac184fb549b63264bc1c8cb54550f5c3e415b17521d986a1a2c0a2ad9b4f2
SPKI SHA256	0136430e10a7965e7f223210437b2988cc9115b7232b6a55302e5de12a4f8660

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

vliegherrie.nl | b22ac18
Not After: 22 Jul 2024 03:12:50 UTC (expires in 2 months 28 days)
Authentication: EC 256 bits (SHA384withECDSA)
View details

Names	*.vliegherrie.nl vliegherrie.nl
Subject DN	CN=vliegherrie.nl
Subject Key Identifier	85633fe6072462d31165fb8c6bffda9b08139a68
Serial	396056868b5c5a4e740853ff37971a9e002
Not Before	23 Apr 2024 03:12:51 UTC
Not After	22 Jul 2024 03:12:50 UTC
Validity period	90 days
Key Usage	digitalSignature
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=E1, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:5af3ed2bfc36c23779b95230ea546fcf55cb2eac
Parent Certificate	http://e1.i.lencr.org/
OCSP	http://e1.o.lencr.org
Certificate Transparency
Signed Certificate Timestamps	23 Apr 2024 04:12:51 UTC \| Google 'Argon2024' log \| Qualified 23 Apr 2024 04:12:51 UTC \| Sectigo 'Mammoth2024h2' \| Qualified
Fingerprints
SHA1	51a2b2dc7d0d02d507903d4ed5f246b7c503f99c
SHA256	b22ac184fb549b63264bc1c8cb54550f5c3e415b17521d986a1a2c0a2ad9b4f2
SPKI SHA256	0136430e10a7965e7f223210437b2988cc9115b7232b6a55302e5de12a4f8660

Intermediate certificate

E1 | 46494e3
Not After: 15 Sep 2025 16:00:00 UTC (expires in 1 year 4 months)
Authentication: EC 384 bits (SHA384withECDSA)
View details

Subject DN	CN=E1, O=Let's Encrypt, C=US
Subject Key Identifier	5af3ed2bfc36c23779b95230ea546fcf55cb2eac
Serial	b3bddff8a7845bbce903a04135b34a45
Not Before	04 Sep 2020 00:00:00 UTC
Not After	15 Sep 2025 16:00:00 UTC
Validity period	1838 days
Key Usage	digitalSignature, keyCertSign, cRLSign
Extended Key Usage	clientAuth, serverAuth
Issuer
Issuer DN	CN=ISRG Root X2, O=Internet Security Research Group, C=US
Certification Authority	Let's Encrypt
Validation Type	Not Applicable
Authority Key Identifier	keyid:7c4296aede4b483bfa92f89e8ccf6d8ba9723795
Parent Certificate	http://x2.i.lencr.org/
CRL	http://x2.c.lencr.org/
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	091e8ea1b256a312962af6c140c0fbf079a407b3
SHA256	46494e30379059df18be52124305e606fc59070e5b21076ce113954b60517cda
SPKI SHA256	276fe8a8c4ec7611565bf9fce6dcace9be320c1b5bea27596b2204071ed04f10

Intermediate certificate

ISRG Root X2 | 8b05b68
Not After: 15 Sep 2025 16:00:00 UTC (expires in 1 year 4 months)
Authentication: EC 384 bits (SHA256withRSA)
View details

Subject DN	CN=ISRG Root X2, O=Internet Security Research Group, C=US
Subject Key Identifier	7c4296aede4b483bfa92f89e8ccf6d8ba9723795
Serial	79e492886376fd40848c23fc631e463
Not Before	04 Sep 2020 00:00:00 UTC
Not After	15 Sep 2025 16:00:00 UTC
Validity period	1838 days
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	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	151682f5218c0a511c28f4060a73b9ca78ce9a53
SHA256	8b05b68cc659e5ed0fcb38f2c942fbfd200e6f2ff9f85d63c6994ef5e0b02701
SPKI SHA256	762195c225586ee6c0237456e2107dc54f1efc21f61a792ebd515913cce68332

Intermediate certificate

ISRG Root X1 | 6d99fb2
Not After: 30 Sep 2024 18:14:03 UTC (expires in 5 months 6 days)
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	4001772137d4e942b8ee76aa3c640ab7
Not Before	20 Jan 2021 19:14:03 UTC
Not After	30 Sep 2024 18:14:03 UTC
Validity period	1349 days
Key Usage	keyCertSign, cRLSign
Issuer
Issuer DN	CN=DST Root CA X3, O=Digital Signature Trust Co.
Certification Authority	IdenTrust Services, LLC
Validation Type	Not Applicable
Authority Key Identifier	keyid:c4a7b1a47b2c71fadbe14b9075ffc41560858910
Parent Certificate	http://apps.identrust.com/roots/dstrootcax3.p7c
CRL	http://crl.identrust.com/DSTROOTCAX3CRL.crl
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	933c6ddee95c9c41a40f9f50493d82be03ad87bf
SHA256	6d99fb265eb1c5b3744765fcbc648f3cd8e1bffafdc4c2f99b9d47cf7ff1c24f
SPKI SHA256	0b9fa5a59eed715c26c1020c711b4f6ec42d58b0015e14337a39dad301c5afc3

Root certificate

DST Root CA X3 | 0687260
Not After: 30 Sep 2021 14:01:15 UTC (expired 2 years 6 months ago)
Authentication: RSA 2048 bits (SHA1withRSA)
View details

Subject DN	CN=DST Root CA X3, O=Digital Signature Trust Co.
Subject Key Identifier	c4a7b1a47b2c71fadbe14b9075ffc41560858910
Serial	44afb080d6a327ba893039862ef8406b
Not Before	30 Sep 2000 21:12:19 UTC
Not After	30 Sep 2021 14:01:15 UTC (expired 2 years 6 months ago)
Key Usage	keyCertSign, cRLSign
Issuer
Issuer DN	CN=DST Root CA X3, O=Digital Signature Trust Co.
Certification Authority	IdenTrust Services, LLC
Validation Type	Self-signed
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	dac9024f54d8f6df94935fb1732638ca6ad77c13
SHA256	0687260331a72403d909f105e69bcf0d32e1bd2493ffc6d9206d11bcd6770739
SPKI SHA256	563b3caf8cfef34c2335caf560a7a95906e8488462eb75ac59784830df9e5b2b

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

Everything seems to be well configured. Well done.

Mixed 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.

Embedded Resources

In this section we look at the 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.

9 script(s)
9 out of 9 are secure View all

Status	Link
Encrypted	https://vliegherrie.nl/...WDkcyYrPTIrXDSON0.js
Encrypted	https://vliegherrie.nl/...FC-RuqypZZ6Zxez-o.js
Encrypted	https://vliegherrie.nl/...45Qtx34UMM3DrZpjs.js
Encrypted	https://vliegherrie.nl/...zLft2SSt_SMOEPRNs.js
Encrypted	https://vliegherrie.nl/.../js/bootstrap.min.js
Encrypted	https://vliegherrie.nl/...mxYMSavQZXjbE3uHI.js
Encrypted	https://vliegherrie.nl/...uery.meanmenu.min.js
Encrypted	https://vliegherrie.nl/...EZ4Kvv2DfTKq1gYoI.js
Encrypted	https://vliegherrie.nl/...rocket-loader.min.js

5 CSS file(s)
5 out of 5 are secure View all

Status	Link
Encrypted	https://vliegherrie.nl/...font-awesome.min.css
Encrypted	https://vliegherrie.nl/...ss/bootstrap.min.css
Encrypted	https://vliegherrie.nl/.../fonts/lato-font.css
Encrypted	https://vliegherrie.nl/...urcecodepro-font.css
Encrypted	https://vliegherrie.nl/...-blockquote-font.css

4 media file(s)
4 out of 4 are secure View all

Status	Link
Encrypted	https://vliegherrie.nl/.../vliegherrie-w50.png
Encrypted	https://www.googletagmanager.com/ns.html
Encrypted	https://vliegherrie.nl/...static/icon/info.gif
Encrypted	https://static.vliegherrie.nl/maps/last.png

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.

24 link(s)
24 out of 24 are encrypted View all

Status	Link
Encrypted	https://schipholwatch.nl/nieuwsbrief
Encrypted	https://schipholwatch.nl/...et-snel-veel-opener/
Encrypted	https://useplink.com/...iPdwPAPiVhtgMz0xJLh/
Encrypted	https://schipholwatch.nl
Encrypted	https://milieudefensie.nl/
Encrypted	https://www.greenpeace.org/nl/
Encrypted	https://www.partijvoordedieren.nl/
Encrypted	https://extinctionrebellion.nl/
Encrypted	https://satl-lelystad.nl/
Encrypted	https://aalsmeer.groenlinks.nl/home
Encrypted	https://haarlemmermeer.groenlinks.nl/
Encrypted	https://www.btv-rotterdam.nl/
Encrypted	https://www.vlieghinder.nl/
Encrypted	https://www.toekomstluchtvaart.nl/
Encrypted	https://www.vliegoverlast.nl/
Encrypted	https://www.wvb.nu/
Encrypted	https://veenendaal.sp.nl/
Encrypted	https://stichtingswab.nl/
Encrypted	https://ozv.nu/
Encrypted	https://redgelderland.nl/
Encrypted	https://www.stichtingreddeveluwe.nl/
Encrypted	https://www.sos-zaanstreek.nl/
Encrypted	https://www.beschermingtegenvliegtuighinder.nl/
Encrypted	https://www.floriandetegengeluid.nl/

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.vliegherrie.nl/
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	31,536,000 seconds (about 1 year)
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

Policy is valid

OK. Your HSTS policy uses correct syntax.

Long policy age

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

Policy covers subdomains

When subdomains are included, network attackers are unable to manufacture arbitrary subdomains to manipulate cookies and trick users.

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.

Policy preloaded

Excellent. This host is covered by a preloaded HSTS policy.

Preloaded host: vliegherrie.nl; includeSubDomains=true

HSTS Policy Apex host

URL from which this policy was obtained.Location	https://vliegherrie.nl/
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	31,536,000 seconds (about 1 year)
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

Policy is valid

OK. Your HSTS policy uses correct syntax.

Long policy age

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

Policy covers subdomains

When subdomains are included, network attackers are unable to manufacture arbitrary subdomains to manipulate cookies and trick users.

Preload intent declared

Good. With the preload directive set, browsers have a green light to embed the HSTS policy.

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.

Policy preloaded

Excellent. This host is covered by a preloaded HSTS policy.

Preloaded host: vliegherrie.nl; includeSubDomains=true

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

upgrade-insecure-requests
form-action	vliegherrie.nl syndication.twitter.com platform.twitter.com www.paypal.com

Analysis

Mixed content upgraded

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

Analysis

CSP policy detected

Header: Content-Security-Policy

Value: upgrade-insecure-requests ; form-action vliegherrie.nl syndication.twitter.com platform.twitter.com www.paypal.com;

Location: https://vliegherrie.nl/

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.

9 script(s)
9 out of 9 are secure View all

Status	Link
Local	https://vliegherrie.nl/sites/default/files/js/js_Pt6OpwTd6jcHLRIjrE-eSPLWMxWDkcyYrPTIrXDSON0.js
Local	https://vliegherrie.nl/sites/default/files/js/js_onbE0n0cQY6KTDQtHO_E27UBymFC-RuqypZZ6Zxez-o.js
Local	https://vliegherrie.nl/sites/default/files/js/js_GutTEDHvNAf0s4BFEqaXyMS8Gs45Qtx34UMM3DrZpjs.js
Local	https://vliegherrie.nl/sites/default/files/js/js_5kWT5A9PbnPtnMS1cOU-27JhIKzLft2SSt_SMOEPRNs.js
Local	https://vliegherrie.nl/sites/default/files/cef/maxcdn.bootstrapcdn.com/bootstrap/3.3.2/js/bootstrap.min.js
Local	https://vliegherrie.nl/sites/default/files/js/js_5SkfKOrrNKw0Bk-WuoEk-r0k87mxYMSavQZXjbE3uHI.js
Local	https://vliegherrie.nl/sites/all/themes/vliegherrie/js/meanmenu/jquery.meanmenu.min.js?scewb8
Local	https://vliegherrie.nl/sites/default/files/js/js_QY8nSvNGr8l2erNSTUrY9Hu99CEZ4Kvv2DfTKq1gYoI.js
Local	/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js

5 CSS file(s)
5 out of 5 are secure View all

Status	Link
Local	https://vliegherrie.nl/sites/default/files/cef/maxcdn.bootstrapcdn.com/font-awesome/4.2.0/css/font-awesome.min.css
Local	https://vliegherrie.nl/sites/default/files/cef/maxcdn.bootstrapcdn.com/bootstrap/3.3.2/css/bootstrap.min.css
Local	https://vliegherrie.nl/sites/all/themes/vliegherrie/fonts/lato-font.css?scewb8
Local	https://vliegherrie.nl/sites/all/themes/vliegherrie/fonts/sourcecodepro-font.css?scewb8
Local	https://vliegherrie.nl/sites/all/themes/vliegherrie/fonts/ptserif-blockquote-font.css?scewb8

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.

Test passed

Everything seems to be well configured. Well done.

Analysis

Header information

Name: X-XSS-Protection

Value: 0

Browser XSS protection disabled

Great. XSS protection is explicitly disabled, making this web site safe even with browsers that have this functionality enabled by default.

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 passed

Everything seems to be well configured. Well done.

Analysis

Header information

Name: X-Content-Type-Options

Value: nosniff

Valid configuration

Good. Your configuration is valid. This means that browsers won't try to guess file MIME type on this web site.

Public Report | vliegherrie.nl

vliegherrie.nl

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

CAA Policy Information

Analysis

Email (SMTP)

Analysis

Email TLS (SMTP)

TLS Configuration: mx01.trustednetworks.nl (2a03:b0c0:0:1010:0:0:30:6001)

Analysis

TLS Configuration: mx01.trustednetworks.nl (95.85.56.217)

Analysis

Email Certificates (SMTP)

Certificate #1

Analysis

Certificate Chain

Analysis

Email DANE (SMTP)

SPF

SPF Policy Information Main policy

Analysis

SPF Policy Information Included policy

DMARC

DMARC Policy Information

Analysis

MTA Strict Transport Security

MTA-STS Policy Indicator

Analysis

MTA-STS Policy

Analysis

Certificate: mta-sts.vliegherrie.nl

Analysis

Certificate Chain

Analysis

SMTP TLS Reporting

TLS-RPT Policy

Analysis

HTTP (80)

URL: http://vliegherrie.nl/

Analysis

URL: http://www.vliegherrie.nl/

Analysis

HTTP (443)

URL: https://vliegherrie.nl/

URL: https://www.vliegherrie.nl/

WWW TLS

TLS Configuration: vliegherrie.nl (2606:4700:3034:0:0:0:6815:41cb)

Analysis

TLS Configuration: www.vliegherrie.nl (2606:4700:3034:0:0:0:6815:41cb)

Analysis

TLS Configuration: www.vliegherrie.nl (2606:4700:3037:0:0:0:ac43:c035)

Analysis

TLS Configuration: vliegherrie.nl (2606:4700:3037:0:0:0:ac43:c035)

Analysis

TLS Configuration: www.vliegherrie.nl (104.21.65.203)

Analysis

TLS Configuration: www.vliegherrie.nl (172.67.192.53)

Analysis

TLS Configuration: vliegherrie.nl (172.67.192.53)

Analysis

TLS Configuration: vliegherrie.nl (104.21.65.203)

Analysis

WWW Certificates

Certificate: vliegherrie.nl

Analysis