Hardenize Report: libraesva.com

Web Security Overview

HTTPS

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

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.
There are issues with this site's HSTS configuration.

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
clark.ns.cloudflare.com. PRIMARY 108.162.193.87 172.64.33.87 173.245.59.87 2606:4700:58::adf5:3b57 2803:f800:50::6ca2:c157 2a06:98c1:50::ac40:2157				SOA REFERRAL NS
heather.ns.cloudflare.com. 108.162.192.161 172.64.32.161 173.245.58.161 2606:4700:50::adf5:3aa1 2803:f800:50::6ca2:c0a1 2a06:98c1:50::ac40:20a1				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.161 heather.ns.cloudflare.com. PTR: heather.ns.cloudflare.com.	NAME, GLUE	1232
108.162.193.87 PRIMARY clark.ns.cloudflare.com. PTR: clark.ns.cloudflare.com.	NAME, GLUE	1232
172.64.32.161 heather.ns.cloudflare.com. PTR: heather.ns.cloudflare.com.	NAME, GLUE	1232
172.64.33.87 PRIMARY clark.ns.cloudflare.com. PTR: clark.ns.cloudflare.com.	NAME, GLUE	1232
173.245.58.161 heather.ns.cloudflare.com. PTR: heather.ns.cloudflare.com.	NAME, GLUE	1232
173.245.59.87 PRIMARY clark.ns.cloudflare.com. PTR: clark.ns.cloudflare.com.	NAME, GLUE	1232
2606:4700:50::adf5:3aa1 heather.ns.cloudflare.com. PTR: heather.ns.cloudflare.com.	NAME, GLUE	1232
2606:4700:58::adf5:3b57 PRIMARY clark.ns.cloudflare.com. PTR: clark.ns.cloudflare.com.	NAME, GLUE	1232
2803:f800:50::6ca2:c0a1 heather.ns.cloudflare.com. PTR: heather.ns.cloudflare.com.	NAME, GLUE	1232
2803:f800:50::6ca2:c157 PRIMARY clark.ns.cloudflare.com. PTR: clark.ns.cloudflare.com.	NAME, GLUE	1232
2a06:98c1:50::ac40:20a1 heather.ns.cloudflare.com. PTR: heather.ns.cloudflare.com.	NAME, GLUE	1232
2a06:98c1:50::ac40:2157 PRIMARY clark.ns.cloudflare.com. PTR: clark.ns.cloudflare.com.	NAME, GLUE	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	clark.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	-1891106522
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
libraesva.com.	300	A	172.67.170.172
libraesva.com.	300	A	104.21.63.123
www.libraesva.com.	300	A	104.21.63.123
www.libraesva.com.	300	A	172.67.170.172
libraesva.com.	300	AAAA	2606:4700:3037:0:0:0:6815:3f7b
libraesva.com.	300	AAAA	2606:4700:3030:0:0:0:ac43:aaac
www.libraesva.com.	300	AAAA	2606:4700:3030:0:0:0:ac43:aaac
www.libraesva.com.	300	AAAA	2606:4700:3037:0:0:0:6815:3f7b
libraesva.com.	300	CAA	0 issuewild "pki.goog; cansignhttpexchanges=yes"
libraesva.com.	300	CAA	0 issuewild "ssl.com"
libraesva.com.	300	CAA	0 iodef "mailto:devel@libraesva.com"
libraesva.com.	300	CAA	0 issue "comodoca.com"
libraesva.com.	300	CAA	0 issue "digicert.com; cansignhttpexchanges=yes"
libraesva.com.	300	CAA	0 issue "letsencrypt.org"
libraesva.com.	300	CAA	0 issue "pki.goog; cansignhttpexchanges=yes"
libraesva.com.	300	CAA	0 issue "ssl.com"
libraesva.com.	300	CAA	0 issuewild "comodoca.com"
libraesva.com.	300	CAA	0 issuewild "digicert.com; cansignhttpexchanges=yes"
libraesva.com.	300	CAA	0 issuewild "letsencrypt.org"
libraesva.com.	300	HTTPS	1 . alpn=h3,h2 ipv4hint=104.21.63.123,172.67.170.172 ech=AEX+DQBBMgAgACBcV/I+GKhpqHDnumV7xytwAS2gO1WqXx0ZADYw1Oy9SgAEAAEAAQASY2xvdWRmbGFyZS1lY2guY29tAAA= ipv6hint=2606:4700:3030:0:0:0:ac43:aaac,2606:4700:3037:0:0:0:6815:3f7b
www.libraesva.com.	300	HTTPS	1 . alpn=h3,h2 ipv4hint=104.21.63.123,172.67.170.172 ech=AEX+DQBBMgAgACBcV/I+GKhpqHDnumV7xytwAS2gO1WqXx0ZADYw1Oy9SgAEAAEAAQASY2xvdWRmbGFyZS1lY2guY29tAAA= ipv6hint=2606:4700:3030:0:0:0:ac43:aaac,2606:4700:3037:0:0:0:6815:3f7b
libraesva.com.	60	MX	0 mail.libraesva.com.
libraesva.com.	60	MX	0 mail2.libraesva.com.
libraesva.com.	86400	NS	clark.ns.cloudflare.com.
libraesva.com.	86400	NS	heather.ns.cloudflare.com.
libraesva.com.	1800	SOA	clark.ns.cloudflare.com. dns.cloudflare.com. 2403860774 10000 2400 604800 1800
libraesva.com.	300	TXT	"v=spf1 redirect=80216bdbea2363da2a2d11665d2352630509c68bcb4e67331d8c7293.eu.rspf.letsdmarc.com"
libraesva.com.	300	TXT	"MS=AE9AFCD7835723CF24980B0A7C9386DF43EB89B4"
libraesva.com.	300	TXT	"google-site-verification=iFDPJDtcyRUK75TuTBrxi7yobtkJ9Fl5tRbAXMG5xoY"
libraesva.com.	300	TXT	"linkedin-site-verification=efc87161-1707-4a44-87f7-e71a7a622c9f"
libraesva.com.	300	TXT	"mistral-domain-verification=9c4411dbe6645aefbf6ffa22af44f6d5878e556f"
_dmarc.libraesva.com.	300	TXT	"v=DMARC1; p=reject; sp=reject; adkim=r; aspf=r; pct=100; fo=1; rua=mailto:rua_bce5fccccb02f488@eu.report.letsdmarc.com; ruf=mailto:ruf_bce5fccccb02f488@eu.report.letsdmarc.com,mailto:dmarc-reports@libraesva.com"
_mta-sts.libraesva.com.	300	TXT	"v=spf1 a -all"
_smtp._tls.libraesva.com.	300	TXT	"v=TLSRPTv1;rua=mailto:rua_a8b8e38cadc4b190@eu.report.letsdmarc.com"

Backing DNS Queries

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

	ID	Server	Question Name	Type	Status

DNSSEC

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

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

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	libraesva.com
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	ssl.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	ssl.com 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	digicert.com; cansignhttpexchanges=yes flags: 0
The iodef property specifies a means of reporting certificate issue requests or cases of certificate issue for the corresponding domain that violate the security policy of the issuer or the domain name holder.iodef	mailto:devel@libraesva.com 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	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	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	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	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	digicert.com; cansignhttpexchanges=yes flags: 0

Analysis

Issuance of S/MIME certificates not restricted

This policy doesn't restrict the issuance of S/MIME certificates. Consider using the `issuemail` directive to restrict which CAs, if any, can issue.

Issuance of BIMI not restricted

This policy doesn't restrict issuance of BIMI certificates. Consider using the `issuevmc` directive to restrict which CAs, if any, can issue.

CAA policy restricts issuance

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

Policy uses reporting

Good. This policy uses reporting, which means that your contact information is available should someone need to contact you about a CAA violation. 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

mail.libraesva.com
185.91.71.80
PTR: mail.libraesva.com

0

mail2.libraesva.com
109.168.30.140
PTR: mail2.libraesva.com

0

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: mail.libraesva.com (185.91.71.80)

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_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) 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_128_CCM_SHA256 Suite ID: 0x1304 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_CCM_SHA256 128 bits (ECDHE 256 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2 Server preference	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_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: 4096 bits Forward secrecy: Yes PRF: SHA384 TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (DHE 4096 bits) Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 384 bits) Suite: TLS_DHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xccaa Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: DHE_RSA Key exchange strength: 4096 bits Forward secrecy: Yes PRF: SHA256 TLS_DHE_RSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (DHE 4096 bits) Suite: TLS_DHE_RSA_WITH_AES_256_CCM_8 Suite ID: 0xc0a3 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: DHE_RSA Key exchange strength: 4096 bits Forward secrecy: Yes PRF: SHA256 TLS_DHE_RSA_WITH_AES_256_CCM_8 256 bits (DHE 4096 bits) Suite: TLS_DHE_RSA_WITH_AES_256_CCM Suite ID: 0xc09f Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: DHE_RSA Key exchange strength: 4096 bits Forward secrecy: Yes PRF: SHA256 TLS_DHE_RSA_WITH_AES_256_CCM 256 bits (DHE 4096 bits) Suite: TLS_ECDHE_RSA_WITH_ARIA_256_GCM_SHA384 Suite ID: 0xc061 Cipher name: ARIA 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_ARIA_256_GCM_SHA384 256 bits (ECDHE 384 bits) Suite: TLS_DHE_RSA_WITH_ARIA_256_GCM_SHA384 Suite ID: 0xc053 Cipher name: ARIA Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: DHE_RSA Key exchange strength: 4096 bits Forward secrecy: Yes PRF: SHA384 TLS_DHE_RSA_WITH_ARIA_256_GCM_SHA384 256 bits (DHE 4096 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_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: 4096 bits Forward secrecy: Yes PRF: SHA256 TLS_DHE_RSA_WITH_AES_256_CBC_SHA256 256 bits (DHE 4096 bits) Suite: TLS_ECDHE_RSA_WITH_CAMELLIA_256_CBC_SHA384 Suite ID: 0xc077 Cipher name: CAMELLIA 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_CAMELLIA_256_CBC_SHA384 256 bits (ECDHE 384 bits) Suite: TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA256 Suite ID: 0xc4 Cipher name: CAMELLIA Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: DHE_RSA Key exchange strength: 4096 bits Forward secrecy: Yes PRF: SHA256 TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA256 256 bits (DHE 4096 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_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: 4096 bits Forward secrecy: Yes PRF: SHA TLS_DHE_RSA_WITH_AES_256_CBC_SHA 256 bits (DHE 4096 bits) Suite: TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA Suite ID: 0x88 Cipher name: CAMELLIA Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: DHE_RSA Key exchange strength: 4096 bits Forward secrecy: Yes PRF: SHA TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA 256 bits (DHE 4096 bits) Suite: TLS_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0x9d Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 4096 bits Forward secrecy: No (WEAK) PRF: SHA384 TLS_RSA_WITH_AES_256_GCM_SHA384 256 bits Suite: TLS_RSA_WITH_AES_256_CCM_8 Suite ID: 0xc0a1 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 4096 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_256_CCM_8 256 bits Suite: TLS_RSA_WITH_AES_256_CCM Suite ID: 0xc09d Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 4096 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_256_CCM 256 bits Suite: TLS_RSA_WITH_ARIA_256_GCM_SHA384 Suite ID: 0xc051 Cipher name: ARIA Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 4096 bits Forward secrecy: No (WEAK) PRF: SHA384 TLS_RSA_WITH_ARIA_256_GCM_SHA384 256 bits Suite: TLS_RSA_WITH_AES_256_CBC_SHA256 Suite ID: 0x3d Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 4096 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_256_CBC_SHA256 256 bits Suite: TLS_RSA_WITH_CAMELLIA_256_CBC_SHA256 Suite ID: 0xc0 Cipher name: CAMELLIA Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 4096 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_CAMELLIA_256_CBC_SHA256 256 bits Suite: TLS_RSA_WITH_AES_256_CBC_SHA Suite ID: 0x35 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 4096 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_256_CBC_SHA 256 bits Suite: TLS_RSA_WITH_CAMELLIA_256_CBC_SHA Suite ID: 0x84 Cipher name: CAMELLIA Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 4096 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_CAMELLIA_256_CBC_SHA 256 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_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: 4096 bits Forward secrecy: Yes PRF: SHA256 TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (DHE 4096 bits) Suite: TLS_DHE_RSA_WITH_AES_128_CCM_8 Suite ID: 0xc0a2 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: DHE_RSA Key exchange strength: 4096 bits Forward secrecy: Yes PRF: SHA256 TLS_DHE_RSA_WITH_AES_128_CCM_8 128 bits (DHE 4096 bits) Suite: TLS_DHE_RSA_WITH_AES_128_CCM Suite ID: 0xc09e Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: DHE_RSA Key exchange strength: 4096 bits Forward secrecy: Yes PRF: SHA256 TLS_DHE_RSA_WITH_AES_128_CCM 128 bits (DHE 4096 bits) Suite: TLS_ECDHE_RSA_WITH_ARIA_128_GCM_SHA256 Suite ID: 0xc060 Cipher name: ARIA 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_ARIA_128_GCM_SHA256 128 bits (ECDHE 384 bits) Suite: TLS_DHE_RSA_WITH_ARIA_128_GCM_SHA256 Suite ID: 0xc052 Cipher name: ARIA Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: DHE_RSA Key exchange strength: 4096 bits Forward secrecy: Yes PRF: SHA256 TLS_DHE_RSA_WITH_ARIA_128_GCM_SHA256 128 bits (DHE 4096 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_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: 4096 bits Forward secrecy: Yes PRF: SHA256 TLS_DHE_RSA_WITH_AES_128_CBC_SHA256 128 bits (DHE 4096 bits) Suite: TLS_ECDHE_RSA_WITH_CAMELLIA_128_CBC_SHA256 Suite ID: 0xc076 Cipher name: CAMELLIA 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_CAMELLIA_128_CBC_SHA256 128 bits (ECDHE 384 bits) Suite: TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA256 Suite ID: 0xbe Cipher name: CAMELLIA Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: DHE_RSA Key exchange strength: 4096 bits Forward secrecy: Yes PRF: SHA256 TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA256 128 bits (DHE 4096 bits) 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_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: 4096 bits Forward secrecy: Yes PRF: SHA TLS_DHE_RSA_WITH_AES_128_CBC_SHA 128 bits (DHE 4096 bits) Suite: TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA Suite ID: 0x45 Cipher name: CAMELLIA Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: DHE_RSA Key exchange strength: 4096 bits Forward secrecy: Yes PRF: SHA TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA 128 bits (DHE 4096 bits) Suite: TLS_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0x9c Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 4096 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_128_GCM_SHA256 128 bits Suite: TLS_RSA_WITH_AES_128_CCM_8 Suite ID: 0xc0a0 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 4096 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_128_CCM_8 128 bits Suite: TLS_RSA_WITH_AES_128_CCM Suite ID: 0xc09c Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 4096 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_128_CCM 128 bits Suite: TLS_RSA_WITH_ARIA_128_GCM_SHA256 Suite ID: 0xc050 Cipher name: ARIA Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 4096 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_ARIA_128_GCM_SHA256 128 bits Suite: TLS_RSA_WITH_AES_128_CBC_SHA256 Suite ID: 0x3c Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 4096 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_128_CBC_SHA256 128 bits Suite: TLS_RSA_WITH_CAMELLIA_128_CBC_SHA256 Suite ID: 0xba Cipher name: CAMELLIA Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 4096 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_CAMELLIA_128_CBC_SHA256 128 bits Suite: TLS_RSA_WITH_AES_128_CBC_SHA Suite ID: 0x2f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 4096 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_128_CBC_SHA 128 bits Suite: TLS_RSA_WITH_CAMELLIA_128_CBC_SHA Suite ID: 0x41 Cipher name: CAMELLIA Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 4096 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_CAMELLIA_128_CBC_SHA 128 bits Suite: TLS_DHE_RSA_WITH_SEED_CBC_SHA Suite ID: 0x9a Cipher name: SEED Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: DHE_RSA Key exchange strength: 4096 bits Forward secrecy: Yes PRF: SHA TLS_DHE_RSA_WITH_SEED_CBC_SHA 128 bits (DHE 4096 bits) Suite: TLS_RSA_WITH_SEED_CBC_SHA Suite ID: 0x96 Cipher name: SEED Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 4096 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_SEED_CBC_SHA 128 bits

Analysis

TLS 1.2 supported

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

Server enforces cipher suite preferences

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

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: mail2.libraesva.com (109.168.30.140)

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_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) 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_128_CCM_SHA256 Suite ID: 0x1304 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_CCM_SHA256 128 bits (ECDHE 256 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2 Server preference	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_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: 4096 bits Forward secrecy: Yes PRF: SHA384 TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (DHE 4096 bits) Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 384 bits) Suite: TLS_DHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xccaa Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: DHE_RSA Key exchange strength: 4096 bits Forward secrecy: Yes PRF: SHA256 TLS_DHE_RSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (DHE 4096 bits) Suite: TLS_DHE_RSA_WITH_AES_256_CCM_8 Suite ID: 0xc0a3 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: DHE_RSA Key exchange strength: 4096 bits Forward secrecy: Yes PRF: SHA256 TLS_DHE_RSA_WITH_AES_256_CCM_8 256 bits (DHE 4096 bits) Suite: TLS_DHE_RSA_WITH_AES_256_CCM Suite ID: 0xc09f Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: DHE_RSA Key exchange strength: 4096 bits Forward secrecy: Yes PRF: SHA256 TLS_DHE_RSA_WITH_AES_256_CCM 256 bits (DHE 4096 bits) Suite: TLS_ECDHE_RSA_WITH_ARIA_256_GCM_SHA384 Suite ID: 0xc061 Cipher name: ARIA 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_ARIA_256_GCM_SHA384 256 bits (ECDHE 384 bits) Suite: TLS_DHE_RSA_WITH_ARIA_256_GCM_SHA384 Suite ID: 0xc053 Cipher name: ARIA Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: DHE_RSA Key exchange strength: 4096 bits Forward secrecy: Yes PRF: SHA384 TLS_DHE_RSA_WITH_ARIA_256_GCM_SHA384 256 bits (DHE 4096 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_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: 4096 bits Forward secrecy: Yes PRF: SHA256 TLS_DHE_RSA_WITH_AES_256_CBC_SHA256 256 bits (DHE 4096 bits) Suite: TLS_ECDHE_RSA_WITH_CAMELLIA_256_CBC_SHA384 Suite ID: 0xc077 Cipher name: CAMELLIA 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_CAMELLIA_256_CBC_SHA384 256 bits (ECDHE 384 bits) Suite: TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA256 Suite ID: 0xc4 Cipher name: CAMELLIA Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: DHE_RSA Key exchange strength: 4096 bits Forward secrecy: Yes PRF: SHA256 TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA256 256 bits (DHE 4096 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_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: 4096 bits Forward secrecy: Yes PRF: SHA TLS_DHE_RSA_WITH_AES_256_CBC_SHA 256 bits (DHE 4096 bits) Suite: TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA Suite ID: 0x88 Cipher name: CAMELLIA Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: DHE_RSA Key exchange strength: 4096 bits Forward secrecy: Yes PRF: SHA TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA 256 bits (DHE 4096 bits) Suite: TLS_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0x9d Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 4096 bits Forward secrecy: No (WEAK) PRF: SHA384 TLS_RSA_WITH_AES_256_GCM_SHA384 256 bits Suite: TLS_RSA_WITH_AES_256_CCM_8 Suite ID: 0xc0a1 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 4096 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_256_CCM_8 256 bits Suite: TLS_RSA_WITH_AES_256_CCM Suite ID: 0xc09d Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 4096 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_256_CCM 256 bits Suite: TLS_RSA_WITH_ARIA_256_GCM_SHA384 Suite ID: 0xc051 Cipher name: ARIA Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 4096 bits Forward secrecy: No (WEAK) PRF: SHA384 TLS_RSA_WITH_ARIA_256_GCM_SHA384 256 bits Suite: TLS_RSA_WITH_AES_256_CBC_SHA256 Suite ID: 0x3d Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 4096 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_256_CBC_SHA256 256 bits Suite: TLS_RSA_WITH_CAMELLIA_256_CBC_SHA256 Suite ID: 0xc0 Cipher name: CAMELLIA Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 4096 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_CAMELLIA_256_CBC_SHA256 256 bits Suite: TLS_RSA_WITH_AES_256_CBC_SHA Suite ID: 0x35 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 4096 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_256_CBC_SHA 256 bits Suite: TLS_RSA_WITH_CAMELLIA_256_CBC_SHA Suite ID: 0x84 Cipher name: CAMELLIA Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 4096 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_CAMELLIA_256_CBC_SHA 256 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_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: 4096 bits Forward secrecy: Yes PRF: SHA256 TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (DHE 4096 bits) Suite: TLS_DHE_RSA_WITH_AES_128_CCM_8 Suite ID: 0xc0a2 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: DHE_RSA Key exchange strength: 4096 bits Forward secrecy: Yes PRF: SHA256 TLS_DHE_RSA_WITH_AES_128_CCM_8 128 bits (DHE 4096 bits) Suite: TLS_DHE_RSA_WITH_AES_128_CCM Suite ID: 0xc09e Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: DHE_RSA Key exchange strength: 4096 bits Forward secrecy: Yes PRF: SHA256 TLS_DHE_RSA_WITH_AES_128_CCM 128 bits (DHE 4096 bits) Suite: TLS_ECDHE_RSA_WITH_ARIA_128_GCM_SHA256 Suite ID: 0xc060 Cipher name: ARIA 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_ARIA_128_GCM_SHA256 128 bits (ECDHE 384 bits) Suite: TLS_DHE_RSA_WITH_ARIA_128_GCM_SHA256 Suite ID: 0xc052 Cipher name: ARIA Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: DHE_RSA Key exchange strength: 4096 bits Forward secrecy: Yes PRF: SHA256 TLS_DHE_RSA_WITH_ARIA_128_GCM_SHA256 128 bits (DHE 4096 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_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: 4096 bits Forward secrecy: Yes PRF: SHA256 TLS_DHE_RSA_WITH_AES_128_CBC_SHA256 128 bits (DHE 4096 bits) Suite: TLS_ECDHE_RSA_WITH_CAMELLIA_128_CBC_SHA256 Suite ID: 0xc076 Cipher name: CAMELLIA 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_CAMELLIA_128_CBC_SHA256 128 bits (ECDHE 384 bits) Suite: TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA256 Suite ID: 0xbe Cipher name: CAMELLIA Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: DHE_RSA Key exchange strength: 4096 bits Forward secrecy: Yes PRF: SHA256 TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA256 128 bits (DHE 4096 bits) 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_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: 4096 bits Forward secrecy: Yes PRF: SHA TLS_DHE_RSA_WITH_AES_128_CBC_SHA 128 bits (DHE 4096 bits) Suite: TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA Suite ID: 0x45 Cipher name: CAMELLIA Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: DHE_RSA Key exchange strength: 4096 bits Forward secrecy: Yes PRF: SHA TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA 128 bits (DHE 4096 bits) Suite: TLS_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0x9c Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 4096 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_128_GCM_SHA256 128 bits Suite: TLS_RSA_WITH_AES_128_CCM_8 Suite ID: 0xc0a0 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 4096 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_128_CCM_8 128 bits Suite: TLS_RSA_WITH_AES_128_CCM Suite ID: 0xc09c Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 4096 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_128_CCM 128 bits Suite: TLS_RSA_WITH_ARIA_128_GCM_SHA256 Suite ID: 0xc050 Cipher name: ARIA Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 4096 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_ARIA_128_GCM_SHA256 128 bits Suite: TLS_RSA_WITH_AES_128_CBC_SHA256 Suite ID: 0x3c Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 4096 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_128_CBC_SHA256 128 bits Suite: TLS_RSA_WITH_CAMELLIA_128_CBC_SHA256 Suite ID: 0xba Cipher name: CAMELLIA Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 4096 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_CAMELLIA_128_CBC_SHA256 128 bits Suite: TLS_RSA_WITH_AES_128_CBC_SHA Suite ID: 0x2f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 4096 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_128_CBC_SHA 128 bits Suite: TLS_RSA_WITH_CAMELLIA_128_CBC_SHA Suite ID: 0x41 Cipher name: CAMELLIA Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 4096 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_CAMELLIA_128_CBC_SHA 128 bits Suite: TLS_DHE_RSA_WITH_SEED_CBC_SHA Suite ID: 0x9a Cipher name: SEED Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: DHE_RSA Key exchange strength: 4096 bits Forward secrecy: Yes PRF: SHA TLS_DHE_RSA_WITH_SEED_CBC_SHA 128 bits (DHE 4096 bits) Suite: TLS_RSA_WITH_SEED_CBC_SHA Suite ID: 0x96 Cipher name: SEED Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 4096 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_SEED_CBC_SHA 128 bits

Analysis

TLS 1.2 supported

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

Server enforces cipher suite preferences

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

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

mail.libraesva.com
Issuer: Let's Encrypt
Not Before: 31 Mar 2026 23:29:03 UTC
Not After: 29 Jun 2026 23:29:02 UTC (expires in 1 month 14 days)
Key: RSA 4096 bits
Signature: SHA256withRSA
View details

Names	mail.libraesva.com
Subject DN	CN=mail.libraesva.com
Subject Key Identifier	3fdac83139c9999eab26aa10ee244a1e9890189c
Serial	06287e05dada32575576a10d8193ac431258
Not Before	31 Mar 2026 23:29:03 UTC
Not After	29 Jun 2026 23:29:02 UTC
Validity period	90 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth
Must Staple	No
Issuer
Issuer DN	CN=R13, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:e7ab9f0f2c33a053d35e4f78c8b2840e3bd69233
Parent Certificate	http://r13.i.lencr.org/
CRL	http://r13.c.lencr.org/89.crl
Certificate Transparency
Signed Certificate Timestamps	01 Apr 2026 00:27:33 UTC \| Let's Encrypt 'Sycamore2026h2' \| Qualified 01 Apr 2026 00:27:33 UTC \| Google 'Xenon2026h1' log \| Qualified
Fingerprints
SHA1	309f1ebc4692579932c848e82958334c9dddb538
SHA256	697197ee3ff96fc4e673249d9ade59474d5d04977082eae9a9c022351ea689ac
SPKI SHA256	d566f06725769bd23eb14f963b2e70d28386705544a9a7821057502d8dd98eb0

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

mail.libraesva.com | 697197e
Not After: 29 Jun 2026 23:29:02 UTC (expires in 1 month 14 days)
Authentication: RSA 4096 bits (SHA256withRSA)
View details

Names	mail.libraesva.com
Subject DN	CN=mail.libraesva.com
Subject Key Identifier	3fdac83139c9999eab26aa10ee244a1e9890189c
Serial	06287e05dada32575576a10d8193ac431258
Not Before	31 Mar 2026 23:29:03 UTC
Not After	29 Jun 2026 23:29:02 UTC
Validity period	90 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth
Must Staple	No
Issuer
Issuer DN	CN=R13, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:e7ab9f0f2c33a053d35e4f78c8b2840e3bd69233
Parent Certificate	http://r13.i.lencr.org/
CRL	http://r13.c.lencr.org/89.crl
Certificate Transparency
Signed Certificate Timestamps	01 Apr 2026 00:27:33 UTC \| Let's Encrypt 'Sycamore2026h2' \| Qualified 01 Apr 2026 00:27:33 UTC \| Google 'Xenon2026h1' log \| Qualified
Fingerprints
SHA1	309f1ebc4692579932c848e82958334c9dddb538
SHA256	697197ee3ff96fc4e673249d9ade59474d5d04977082eae9a9c022351ea689ac
SPKI SHA256	d566f06725769bd23eb14f963b2e70d28386705544a9a7821057502d8dd98eb0

Intermediate certificate

R13 | d3b1282
Not After: 12 Mar 2027 23:59:59 UTC (expires in 9 months 25 days)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Subject DN	CN=R13, O=Let's Encrypt, C=US
Subject Key Identifier	e7ab9f0f2c33a053d35e4f78c8b2840e3bd69233
Serial	5a00f212d8d4b480f3924157ea298305
Not Before	13 Mar 2024 00:00:00 UTC
Not After	12 Mar 2027 23:59:59 UTC
Validity period	1095 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	22ff89586561fc2d52f77491e9f1eff1b80be33e
SHA256	d3b128216a843f8ef1321501f5df52a5df52939ee2c19297712cd3de4d419354
SPKI SHA256	025490860b498ab73c6a12f27a49ad5fe230fafe3ac8f6112c9b7d0aad46941d

Root certificate

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

Certificate #2

Leaf certificate

mail2.libraesva.com
Issuer: Let's Encrypt
Not Before: 31 Mar 2026 23:29:13 UTC
Not After: 29 Jun 2026 23:29:12 UTC (expires in 1 month 14 days)
Key: RSA 4096 bits
Signature: SHA256withRSA
View details

Names	mail2.libraesva.com
Subject DN	CN=mail2.libraesva.com
Subject Key Identifier	237de2f6ca3c7f21dea1cbbc6d2cae876947a1a6
Serial	05d86142fa8f46bea081d700807768821bba
Not Before	31 Mar 2026 23:29:13 UTC
Not After	29 Jun 2026 23:29:12 UTC
Validity period	90 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth
Must Staple	No
Issuer
Issuer DN	CN=R12, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:00b529f22d8e6f31e89b4cad783efadce90cd1d2
Parent Certificate	http://r12.i.lencr.org/
CRL	http://r12.c.lencr.org/59.crl
Certificate Transparency
Signed Certificate Timestamps	01 Apr 2026 00:27:43 UTC \| Sectigo 'Tiger2026h1' \| Qualified 01 Apr 2026 00:27:44 UTC \| IPng Networks 'Gouda2026h1' \| Qualified
Fingerprints
SHA1	c76d67c29b8c98a1e1e224a6493bba677691cc43
SHA256	f50e2ce2bffa002fdffd622f4fd78eddeacc258677e7659fafd3bb9da1b11d45
SPKI SHA256	1e6278f8a00f2f8815f251720974b6a5ce4871a1da7d75180f6779699f0de74d

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

mail2.libraesva.com | f50e2ce
Not After: 29 Jun 2026 23:29:12 UTC (expires in 1 month 14 days)
Authentication: RSA 4096 bits (SHA256withRSA)
View details

Names	mail2.libraesva.com
Subject DN	CN=mail2.libraesva.com
Subject Key Identifier	237de2f6ca3c7f21dea1cbbc6d2cae876947a1a6
Serial	05d86142fa8f46bea081d700807768821bba
Not Before	31 Mar 2026 23:29:13 UTC
Not After	29 Jun 2026 23:29:12 UTC
Validity period	90 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth
Must Staple	No
Issuer
Issuer DN	CN=R12, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:00b529f22d8e6f31e89b4cad783efadce90cd1d2
Parent Certificate	http://r12.i.lencr.org/
CRL	http://r12.c.lencr.org/59.crl
Certificate Transparency
Signed Certificate Timestamps	01 Apr 2026 00:27:43 UTC \| Sectigo 'Tiger2026h1' \| Qualified 01 Apr 2026 00:27:44 UTC \| IPng Networks 'Gouda2026h1' \| Qualified
Fingerprints
SHA1	c76d67c29b8c98a1e1e224a6493bba677691cc43
SHA256	f50e2ce2bffa002fdffd622f4fd78eddeacc258677e7659fafd3bb9da1b11d45
SPKI SHA256	1e6278f8a00f2f8815f251720974b6a5ce4871a1da7d75180f6779699f0de74d

Intermediate certificate

R12 | 131fce7
Not After: 12 Mar 2027 23:59:59 UTC (expires in 9 months 25 days)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Subject DN	CN=R12, O=Let's Encrypt, C=US
Subject Key Identifier	00b529f22d8e6f31e89b4cad783efadce90cd1d2
Serial	c212324b70a9b49171dc40f7e285263c
Not Before	13 Mar 2024 00:00:00 UTC
Not After	12 Mar 2027 23:59:59 UTC
Validity period	1095 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	ee44782835d8fb31394da5ceb840dc93849bcf5a
SHA256	131fce7784016899a5a00203a9efc80f18ebbd75580717edc1553580930836ec
SPKI SHA256	919c0df7a787b597ed056ace654b1de9c0387acf349f73734a4fd7b58cf612a4

Root certificate

ISRG Root X1 | 96bcec0
Not After: 04 Jun 2035 11:04:38 UTC (expires in 9 years 19 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	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	libraesva.com
SPF version used by this policy.v	spf1
This modifier is intended for consolidating both authorizations and policy into a common set to be shared within a single administrative domain. redirect	80216bdbea2363da2a2d11665d2352630509c68bcb4e67331d8c7293.eu.rspf.letsdmarc.com

Analysis

SPF policy found

Policy text: v=spf1 redirect=80216bdbea2363da2a2d11665d2352630509c68bcb4e67331d8c7293.eu.rspf.letsdmarc.com

Location: libraesva.com

SPF policy is valid

Good. Your SPF policy is syntactically valid.

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	80216bdbea2363da2a2d11665d2352630509c68bcb4e67331d8c7293.eu.rspf.letsdmarc.com
SPF version used by this policy.v	spf1
This mechanism is used to construct an arbitrary domain name that is used for a DNS A record query. It allows for complicated schemes involving arbitrary parts of the mail envelope to determine what is permitted. exists	%{ir}.80216bdbea2363da2a2d11665d2352630509c68bcb4e67331d8c7293.eu.spf.letsdmarc.com
This mechanism is used to construct an arbitrary domain name that is used for a DNS A record query. It allows for complicated schemes involving arbitrary parts of the mail envelope to determine what is permitted. exists	%{ir}.spf-esvacloud.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

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.libraesva.com
DMARC version used by this policy.v	DMARC1
Indicates the policy to be enacted by the receiver at the request of the domain owner. Possible values are: none, quarantine, and reject.p	reject
Requested mail receiver policy for all subdomains. Same format as for the p tag.sp	reject
Indicates whether strict or relaxed DKIM alignment mode is required.adkim	r
Indicates whether strict or relaxed SPF alignment mode is required.aspf	r
Percentage of messages from mail stream to which the DMARC policy is to be applied.pct	100
Configures failure reporting.fo	1
Addresses to which aggregate feedback is to be sent.rua	mailto:rua_bce5fccccb02f488@eu.report.letsdmarc.com
Addresses to which message-specific failure information is to be reported.ruf	mailto:ruf_bce5fccccb02f488@eu.report.letsdmarc.com,mailto:dmarc-reports@libraesva.com

Analysis

DMARC policy found

Policy: v=DMARC1; p=reject; sp=reject; adkim=r; aspf=r; pct=100; fo=1; rua=mailto:rua_bce5fccccb02f488@eu.report.letsdmarc.com; ruf=mailto:ruf_bce5fccccb02f488@eu.report.letsdmarc.com,mailto:dmarc-reports@libraesva.com

Host: _dmarc.libraesva.com

Valid external destination

Permission record location: libraesva.com._report._dmarc.eu.report.letsdmarc.com

External destination: mailto:rua_bce5fccccb02f488@eu.report.letsdmarc.com

Permission record contents: v=DMARC1;

Policy is valid

Good. You have a valid DMARC policy.

MTA Strict Transport Security

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

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

SMTP TLS Reporting

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

Test passed

Everything seems to be well configured. Well done.

TLS-RPT Policy

Location from which we retrieved the policy indicator.Location	_smtp._tls.libraesva.com
TLS-RPT standard version used by this policy indicator.Version	TLSRPTv1
Reporting endpoints specified in the policy.Reporting Endpoints	mailto:rua_a8b8e38cadc4b190@eu.report.letsdmarc.com

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://libraesva.com/

1

http://libraesva.com/

HTTP/1.1 301 Moved Permanently

Date	Fri, 15 May 2026 17:29:14 GMT
Content-Type	text/html; charset=UTF-8
Transfer-Encoding	chunked
Connection	keep-alive
Server-Timing	cfEdge;dur=22,cfOrigin;dur=0
Location	https://libraesva.com/
Speculation-Rules	"/cdn-cgi/speculation"
Report-To	{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=AnymfOMaDNbQCUMgEUyikeePAtGDp7z1yMh6zjh8tQQcvCpNtOOwT%2F%2FD3vtEG7GDZ5CLbXishnIiBAWHsc8tou2CSKvJNOgnE%2B84nv7p5kKu9e0mPko1KHqeRM43ojWt"}]}
Nel	{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Server	cloudflare
CF-RAY	9fc3dd179e4c82ed-IAD
alt-svc	h3=":443"; ma=86400

2

https://libraesva.com/

HTTP/1.1 301 Moved Permanently

Date	Fri, 15 May 2026 17:29:14 GMT
Content-Type	text/html; charset=UTF-8
Transfer-Encoding	chunked
Connection	keep-alive
Location	https://www.libraesva.com/
CF-Ray	9fc3dd18187ad6e5-IAD
CF-Cache-Status	DYNAMIC
Access-Control-Allow-Origin	*
Cache-Control	max-age=3600
Expires	Fri, 15 May 2026 18:29:14 GMT
Server	cloudflare
Strict-Transport-Security	max-age=31536000; includeSubDomains; preload;
Content-Security-Policy-Report-Only	default-src 'self' https://s0.wp.com https://fonts.googleapis.com https://fonts.gstatic.com data:; frame-src 'self' data: blob: https://www.youtube.com https://player.vimeo.com https://wp-themes.com; img-src * data:; media-src * data:; style-src 'self' https://fonts.googleapis.com data: 'unsafe-inline'; script-src https://wp-themes.com 'self' data: 'unsafe-inline' 'unsafe-eval'; worker-src 'self'; frame-ancestors 'self' https://hub.libraesva.com; report-uri https://sentry.libraesva.com/api/16/security/?sentry_key=ec35ea3e850202bb70633fcd5d55c698
X-Redirect-By	WordPress
referrer-policy	strict-origin
x-content-type-options	nosniff
x-xss-protection	1; mode=block
Speculation-Rules	"/cdn-cgi/speculation"
Server-Timing	cfCacheStatus;desc="DYNAMIC"
Server-Timing	cfEdge;dur=668,cfOrigin;dur=0
Report-To	{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=tYBDE0kKhnuLIGlK3VWwo0QV9NJIcvNO15Wd8HtzOQsNQ1xfk1wMAtRj25Xq8bo%2FNxe5Z8Iz8VEwj%2BWrUVxyFfFNEMo2KLVjFKgBVqSVz58es8pZ9YmlhCdm%2F%2Bk4eIXm"}]}
Nel	{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
alt-svc	h3=":443"; ma=86400

3

https://www.libraesva.com/

HTTP/1.1 200 OK

Date	Fri, 15 May 2026 17:29:15 GMT
Content-Type	text/html; charset=UTF-8
Transfer-Encoding	chunked
Connection	keep-alive
CF-Ray	9fc3dd1ca95ed65f-IAD
CF-Cache-Status	DYNAMIC
Access-Control-Allow-Origin	*
Server	cloudflare
Strict-Transport-Security	max-age=31536000; includeSubDomains; preload;
Vary	accept-encoding
Content-Security-Policy-Report-Only	default-src 'self' https://s0.wp.com https://fonts.googleapis.com https://fonts.gstatic.com data:; frame-src 'self' data: blob: https://www.youtube.com https://player.vimeo.com https://wp-themes.com; img-src * data:; media-src * data:; style-src 'self' https://fonts.googleapis.com data: 'unsafe-inline'; script-src https://wp-themes.com 'self' data: 'unsafe-inline' 'unsafe-eval'; worker-src 'self'; frame-ancestors 'self' https://hub.libraesva.com; report-uri https://sentry.libraesva.com/api/16/security/?sentry_key=ec35ea3e850202bb70633fcd5d55c698
referrer-policy	strict-origin
x-content-type-options	nosniff
x-xss-protection	1; mode=block
Speculation-Rules	"/cdn-cgi/speculation"
Server-Timing	cfCacheStatus;desc="DYNAMIC"
Server-Timing	cfEdge;dur=983,cfOrigin;dur=0
Report-To	{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=atpqmYTQe9riDuZfzbhVYh0nUrZRIZGXSUkayTks9JKN7%2B3oPzQTY%2FRAFn%2Fi8cHhUU91%2FZr9NKDEwqLXxtbbN%2B4%2BQf6JbTh3I13%2BOzGKvUD9Tw8JCh25zm2h02jG1RqkvHgxmbL69PlibEsIMSGwOQ%3D%3D"}]}
Nel	{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
alt-svc	h3=":443"; ma=86400

Analysis

HTTP redirects to HTTPS

Good. This plaintext HTTP server redirects to HTTPS.

URL: http://www.libraesva.com/

1

http://www.libraesva.com/

HTTP/1.1 301 Moved Permanently

Date	Fri, 15 May 2026 17:29:16 GMT
Content-Type	text/html; charset=UTF-8
Transfer-Encoding	chunked
Connection	keep-alive
Server-Timing	cfEdge;dur=24,cfOrigin;dur=0
Location	https://www.libraesva.com/
Speculation-Rules	"/cdn-cgi/speculation"
Report-To	{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=iEWWrYWddUGQAMEqEB2fjHeMLOTjMO9xAqrTqddtYZ7gaAb7OSCGNI4QqqBRm%2B0Cy96lLAhvnc59AqNovx1i6cpX7d39bcuVpxSnDFfuNNm%2BbdtGdNy%2B6oobqy4gQW1kT7KBbQ%3D%3D"}]}
Nel	{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Server	cloudflare
CF-RAY	9fc3dd22ee7b0808-IAD
alt-svc	h3=":443"; ma=86400

2

https://www.libraesva.com/

HTTP/1.1 200 OK

Date	Fri, 15 May 2026 17:29:16 GMT
Content-Type	text/html; charset=UTF-8
Transfer-Encoding	chunked
Connection	keep-alive
CF-Ray	9fc3dd236d19553b-IAD
CF-Cache-Status	DYNAMIC
Access-Control-Allow-Origin	*
Server	cloudflare
Strict-Transport-Security	max-age=31536000; includeSubDomains; preload;
Vary	accept-encoding
Content-Security-Policy-Report-Only	default-src 'self' https://s0.wp.com https://fonts.googleapis.com https://fonts.gstatic.com data:; frame-src 'self' data: blob: https://www.youtube.com https://player.vimeo.com https://wp-themes.com; img-src * data:; media-src * data:; style-src 'self' https://fonts.googleapis.com data: 'unsafe-inline'; script-src https://wp-themes.com 'self' data: 'unsafe-inline' 'unsafe-eval'; worker-src 'self'; frame-ancestors 'self' https://hub.libraesva.com; report-uri https://sentry.libraesva.com/api/16/security/?sentry_key=ec35ea3e850202bb70633fcd5d55c698
referrer-policy	strict-origin
x-content-type-options	nosniff
x-xss-protection	1; mode=block
Speculation-Rules	"/cdn-cgi/speculation"
Server-Timing	cfCacheStatus;desc="DYNAMIC"
Server-Timing	cfEdge;dur=910,cfOrigin;dur=0
Report-To	{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=l3IhFx4eT6GRVvlz1hnRcOwiCKwdJ29VTYxQrpXuQmKDk0FSAy%2Bed5GgFWUZgp4Zg1m9qu8U5hYF4I1Cm9ROjoX1EaP35PIqrehwR2vhqtA1OIGkVo7qPVY1MNnfJxh%2FWFMlrw%3D%3D"}]}
Nel	{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
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://libraesva.com/

1

https://libraesva.com/

HTTP/1.1 301 Moved Permanently

Date	Fri, 15 May 2026 17:29:17 GMT
Content-Type	text/html; charset=UTF-8
Transfer-Encoding	chunked
Connection	keep-alive
Location	https://www.libraesva.com/
CF-Ray	9fc3dd298e640592-IAD
CF-Cache-Status	DYNAMIC
Access-Control-Allow-Origin	*
Cache-Control	max-age=3600
Expires	Fri, 15 May 2026 18:29:17 GMT
Server	cloudflare
Strict-Transport-Security	max-age=31536000; includeSubDomains; preload;
Content-Security-Policy-Report-Only	default-src 'self' https://s0.wp.com https://fonts.googleapis.com https://fonts.gstatic.com data:; frame-src 'self' data: blob: https://www.youtube.com https://player.vimeo.com https://wp-themes.com; img-src * data:; media-src * data:; style-src 'self' https://fonts.googleapis.com data: 'unsafe-inline'; script-src https://wp-themes.com 'self' data: 'unsafe-inline' 'unsafe-eval'; worker-src 'self'; frame-ancestors 'self' https://hub.libraesva.com; report-uri https://sentry.libraesva.com/api/16/security/?sentry_key=ec35ea3e850202bb70633fcd5d55c698
X-Redirect-By	WordPress
referrer-policy	strict-origin
x-content-type-options	nosniff
x-xss-protection	1; mode=block
Speculation-Rules	"/cdn-cgi/speculation"
Server-Timing	cfCacheStatus;desc="DYNAMIC"
Server-Timing	cfEdge;dur=651,cfOrigin;dur=0
Report-To	{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=0J23hN%2Bzve33Av2o9USkT4ZKe2GjBwP9qB5RIrYf15RwgHnIg0XFFyIOiDsqr6XjGMVyu5xw%2BzSKfRcad48T7Q2suLKh9yjvjcerU%2F4a3%2BpG4v0omc2uVA7uS5MULjKY"}]}
Nel	{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
alt-svc	h3=":443"; ma=86400

2

https://www.libraesva.com/

HTTP/1.1 200 OK

Date	Fri, 15 May 2026 17:29:18 GMT
Content-Type	text/html; charset=UTF-8
Transfer-Encoding	chunked
Connection	keep-alive
CF-Ray	9fc3dd2e0f90ff28-IAD
CF-Cache-Status	DYNAMIC
Access-Control-Allow-Origin	*
Server	cloudflare
Strict-Transport-Security	max-age=31536000; includeSubDomains; preload;
Vary	accept-encoding
Content-Security-Policy-Report-Only	default-src 'self' https://s0.wp.com https://fonts.googleapis.com https://fonts.gstatic.com data:; frame-src 'self' data: blob: https://www.youtube.com https://player.vimeo.com https://wp-themes.com; img-src * data:; media-src * data:; style-src 'self' https://fonts.googleapis.com data: 'unsafe-inline'; script-src https://wp-themes.com 'self' data: 'unsafe-inline' 'unsafe-eval'; worker-src 'self'; frame-ancestors 'self' https://hub.libraesva.com; report-uri https://sentry.libraesva.com/api/16/security/?sentry_key=ec35ea3e850202bb70633fcd5d55c698
referrer-policy	strict-origin
x-content-type-options	nosniff
x-xss-protection	1; mode=block
Speculation-Rules	"/cdn-cgi/speculation"
Server-Timing	cfCacheStatus;desc="DYNAMIC"
Server-Timing	cfEdge;dur=921,cfOrigin;dur=0
Report-To	{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=XE8WfpJJlEdaMv%2FDHHY6FQtyr6Al7M2CNG%2BFp41GSYxUM4kHTccvCV%2FcUKM2XwtBM9%2BD%2BqHVQmgqtcPSq6whyhEYWdYCEv06Tr744E8F1JTcp4BsmWfF48YdvYKy%2BMvArWN%2FldLHP9BaNnEujLPgrQ%3D%3D"}]}
Nel	{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
alt-svc	h3=":443"; ma=86400

URL: https://www.libraesva.com/

1

https://www.libraesva.com/

HTTP/1.1 200 OK

Date	Fri, 15 May 2026 17:29:19 GMT
Content-Type	text/html; charset=UTF-8
Transfer-Encoding	chunked
Connection	keep-alive
CF-Ray	9fc3dd34292b8e53-IAD
CF-Cache-Status	DYNAMIC
Access-Control-Allow-Origin	*
Server	cloudflare
Strict-Transport-Security	max-age=31536000; includeSubDomains; preload;
Vary	accept-encoding
Content-Security-Policy-Report-Only	default-src 'self' https://s0.wp.com https://fonts.googleapis.com https://fonts.gstatic.com data:; frame-src 'self' data: blob: https://www.youtube.com https://player.vimeo.com https://wp-themes.com; img-src * data:; media-src * data:; style-src 'self' https://fonts.googleapis.com data: 'unsafe-inline'; script-src https://wp-themes.com 'self' data: 'unsafe-inline' 'unsafe-eval'; worker-src 'self'; frame-ancestors 'self' https://hub.libraesva.com; report-uri https://sentry.libraesva.com/api/16/security/?sentry_key=ec35ea3e850202bb70633fcd5d55c698
referrer-policy	strict-origin
x-content-type-options	nosniff
x-xss-protection	1; mode=block
Speculation-Rules	"/cdn-cgi/speculation"
Server-Timing	cfCacheStatus;desc="DYNAMIC"
Server-Timing	cfEdge;dur=900,cfOrigin;dur=0
Report-To	{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=kgDij9LviGQlPNMdM9bImnkJ4PTPlvW0UO8IOPjVwDlotCPuyM%2BwebCaD4PJbyjPLTIsgfgtBuao4SzC9Wog9i5y0Ike9Kgqij7hzTgKoZdmBiBOmMAgzNWTaTODg%2Bo4Pt%2Bx4g%3D%3D"}]}
Nel	{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
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: libraesva.com (2606:4700:3037:0:0:0:6815:3f7b)

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.3 TLS v1.2
Servers should always enforce their own cipher suite preference, as that is the only approach that guarantees that the best possible suite is selected.Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3 Server preference	Suite: TLS_CHACHA20_POLY1305_SHA256 Suite ID: 0x1303 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: X25519MLKEM768 Key exchange strength: Hybrid PQ X25519MLKEM768 (9472 bits) Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (Hybrid PQ 9472 bits) Suite: TLS_AES_128_GCM_SHA256 Suite ID: 0x1301 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: X25519MLKEM768 Key exchange strength: Hybrid PQ X25519MLKEM768 (9472 bits) Forward secrecy: Yes PRF: SHA256 TLS_AES_128_GCM_SHA256 128 bits (Hybrid PQ 9472 bits) Suite: TLS_AES_256_GCM_SHA384 Suite ID: 0x1302 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: X25519MLKEM768 Key exchange strength: Hybrid PQ X25519MLKEM768 (9472 bits) Forward secrecy: Yes PRF: SHA384 TLS_AES_256_GCM_SHA384 256 bits (Hybrid PQ 9472 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2 Server preference	Suite: TLS_ECDHE_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 setting enables negotiation of best security.

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

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

SCT transports: CERT

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

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

SCT transports: CERT

Post-quantum key exchange supported

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

Algorithm: X25519MLKEM768

DHE suites not supported

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

TLS Configuration: libraesva.com (2606:4700:3030:0:0:0:ac43:aaac)

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.3 TLS v1.2
Servers should always enforce their own cipher suite preference, as that is the only approach that guarantees that the best possible suite is selected.Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3 Server preference	Suite: TLS_CHACHA20_POLY1305_SHA256 Suite ID: 0x1303 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: X25519MLKEM768 Key exchange strength: Hybrid PQ X25519MLKEM768 (9472 bits) Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (Hybrid PQ 9472 bits) Suite: TLS_AES_128_GCM_SHA256 Suite ID: 0x1301 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: X25519MLKEM768 Key exchange strength: Hybrid PQ X25519MLKEM768 (9472 bits) Forward secrecy: Yes PRF: SHA256 TLS_AES_128_GCM_SHA256 128 bits (Hybrid PQ 9472 bits) Suite: TLS_AES_256_GCM_SHA384 Suite ID: 0x1302 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: X25519MLKEM768 Key exchange strength: Hybrid PQ X25519MLKEM768 (9472 bits) Forward secrecy: Yes PRF: SHA384 TLS_AES_256_GCM_SHA384 256 bits (Hybrid PQ 9472 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2 Server preference	Suite: TLS_ECDHE_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 setting enables negotiation of best security.

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

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

SCT transports: CERT

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

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

SCT transports: CERT

Post-quantum key exchange supported

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

Algorithm: X25519MLKEM768

DHE suites not supported

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

TLS Configuration: libraesva.com (104.21.63.123)

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.3 TLS v1.2
Servers should always enforce their own cipher suite preference, as that is the only approach that guarantees that the best possible suite is selected.Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3 Server preference	Suite: TLS_CHACHA20_POLY1305_SHA256 Suite ID: 0x1303 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: X25519MLKEM768 Key exchange strength: Hybrid PQ X25519MLKEM768 (9472 bits) Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (Hybrid PQ 9472 bits) Suite: TLS_AES_128_GCM_SHA256 Suite ID: 0x1301 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: X25519MLKEM768 Key exchange strength: Hybrid PQ X25519MLKEM768 (9472 bits) Forward secrecy: Yes PRF: SHA256 TLS_AES_128_GCM_SHA256 128 bits (Hybrid PQ 9472 bits) Suite: TLS_AES_256_GCM_SHA384 Suite ID: 0x1302 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: X25519MLKEM768 Key exchange strength: Hybrid PQ X25519MLKEM768 (9472 bits) Forward secrecy: Yes PRF: SHA384 TLS_AES_256_GCM_SHA384 256 bits (Hybrid PQ 9472 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2 Server preference	Suite: TLS_ECDHE_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 setting enables negotiation of best security.

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

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

SCT transports: CERT

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

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

SCT transports: CERT

Post-quantum key exchange supported

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

Algorithm: X25519MLKEM768

DHE suites not supported

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

TLS Configuration: www.libraesva.com (2606:4700:3037:0:0:0:6815:3f7b)

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.3 TLS v1.2
Servers should always enforce their own cipher suite preference, as that is the only approach that guarantees that the best possible suite is selected.Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3 Server preference	Suite: TLS_CHACHA20_POLY1305_SHA256 Suite ID: 0x1303 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: X25519MLKEM768 Key exchange strength: Hybrid PQ X25519MLKEM768 (9472 bits) Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (Hybrid PQ 9472 bits) Suite: TLS_AES_128_GCM_SHA256 Suite ID: 0x1301 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: X25519MLKEM768 Key exchange strength: Hybrid PQ X25519MLKEM768 (9472 bits) Forward secrecy: Yes PRF: SHA256 TLS_AES_128_GCM_SHA256 128 bits (Hybrid PQ 9472 bits) Suite: TLS_AES_256_GCM_SHA384 Suite ID: 0x1302 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: X25519MLKEM768 Key exchange strength: Hybrid PQ X25519MLKEM768 (9472 bits) Forward secrecy: Yes PRF: SHA384 TLS_AES_256_GCM_SHA384 256 bits (Hybrid PQ 9472 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2 Server preference	Suite: TLS_ECDHE_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 setting enables negotiation of best security.

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

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

SCT transports: CERT

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

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

SCT transports: CERT

Post-quantum key exchange supported

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

Algorithm: X25519MLKEM768

DHE suites not supported

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

TLS Configuration: libraesva.com (172.67.170.172)

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.3 TLS v1.2
Servers should always enforce their own cipher suite preference, as that is the only approach that guarantees that the best possible suite is selected.Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3 Server preference	Suite: TLS_CHACHA20_POLY1305_SHA256 Suite ID: 0x1303 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: X25519MLKEM768 Key exchange strength: Hybrid PQ X25519MLKEM768 (9472 bits) Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (Hybrid PQ 9472 bits) Suite: TLS_AES_128_GCM_SHA256 Suite ID: 0x1301 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: X25519MLKEM768 Key exchange strength: Hybrid PQ X25519MLKEM768 (9472 bits) Forward secrecy: Yes PRF: SHA256 TLS_AES_128_GCM_SHA256 128 bits (Hybrid PQ 9472 bits) Suite: TLS_AES_256_GCM_SHA384 Suite ID: 0x1302 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: X25519MLKEM768 Key exchange strength: Hybrid PQ X25519MLKEM768 (9472 bits) Forward secrecy: Yes PRF: SHA384 TLS_AES_256_GCM_SHA384 256 bits (Hybrid PQ 9472 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2 Server preference	Suite: TLS_ECDHE_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 setting enables negotiation of best security.

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

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

SCT transports: CERT

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

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

SCT transports: CERT

Post-quantum key exchange supported

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

Algorithm: X25519MLKEM768

DHE suites not supported

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

TLS Configuration: www.libraesva.com (2606:4700:3030:0:0:0:ac43:aaac)

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.3 TLS v1.2
Servers should always enforce their own cipher suite preference, as that is the only approach that guarantees that the best possible suite is selected.Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3 Server preference	Suite: TLS_CHACHA20_POLY1305_SHA256 Suite ID: 0x1303 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: X25519MLKEM768 Key exchange strength: Hybrid PQ X25519MLKEM768 (9472 bits) Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (Hybrid PQ 9472 bits) Suite: TLS_AES_128_GCM_SHA256 Suite ID: 0x1301 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: X25519MLKEM768 Key exchange strength: Hybrid PQ X25519MLKEM768 (9472 bits) Forward secrecy: Yes PRF: SHA256 TLS_AES_128_GCM_SHA256 128 bits (Hybrid PQ 9472 bits) Suite: TLS_AES_256_GCM_SHA384 Suite ID: 0x1302 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: X25519MLKEM768 Key exchange strength: Hybrid PQ X25519MLKEM768 (9472 bits) Forward secrecy: Yes PRF: SHA384 TLS_AES_256_GCM_SHA384 256 bits (Hybrid PQ 9472 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2 Server preference	Suite: TLS_ECDHE_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 setting enables negotiation of best security.

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

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

SCT transports: CERT

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

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

SCT transports: CERT

Post-quantum key exchange supported

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

Algorithm: X25519MLKEM768

DHE suites not supported

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

TLS Configuration: www.libraesva.com (172.67.170.172)

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.3 TLS v1.2
Servers should always enforce their own cipher suite preference, as that is the only approach that guarantees that the best possible suite is selected.Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3 Server preference	Suite: TLS_CHACHA20_POLY1305_SHA256 Suite ID: 0x1303 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: X25519MLKEM768 Key exchange strength: Hybrid PQ X25519MLKEM768 (9472 bits) Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (Hybrid PQ 9472 bits) Suite: TLS_AES_128_GCM_SHA256 Suite ID: 0x1301 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: X25519MLKEM768 Key exchange strength: Hybrid PQ X25519MLKEM768 (9472 bits) Forward secrecy: Yes PRF: SHA256 TLS_AES_128_GCM_SHA256 128 bits (Hybrid PQ 9472 bits) Suite: TLS_AES_256_GCM_SHA384 Suite ID: 0x1302 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: X25519MLKEM768 Key exchange strength: Hybrid PQ X25519MLKEM768 (9472 bits) Forward secrecy: Yes PRF: SHA384 TLS_AES_256_GCM_SHA384 256 bits (Hybrid PQ 9472 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2 Server preference	Suite: TLS_ECDHE_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 setting enables negotiation of best security.

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

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

SCT transports: CERT

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

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

SCT transports: CERT

Post-quantum key exchange supported

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

Algorithm: X25519MLKEM768

DHE suites not supported

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

TLS Configuration: www.libraesva.com (104.21.63.123)

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.3 TLS v1.2
Servers should always enforce their own cipher suite preference, as that is the only approach that guarantees that the best possible suite is selected.Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3 Server preference	Suite: TLS_CHACHA20_POLY1305_SHA256 Suite ID: 0x1303 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: X25519MLKEM768 Key exchange strength: Hybrid PQ X25519MLKEM768 (9472 bits) Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (Hybrid PQ 9472 bits) Suite: TLS_AES_128_GCM_SHA256 Suite ID: 0x1301 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: X25519MLKEM768 Key exchange strength: Hybrid PQ X25519MLKEM768 (9472 bits) Forward secrecy: Yes PRF: SHA256 TLS_AES_128_GCM_SHA256 128 bits (Hybrid PQ 9472 bits) Suite: TLS_AES_256_GCM_SHA384 Suite ID: 0x1302 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: X25519MLKEM768 Key exchange strength: Hybrid PQ X25519MLKEM768 (9472 bits) Forward secrecy: Yes PRF: SHA384 TLS_AES_256_GCM_SHA384 256 bits (Hybrid PQ 9472 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2 Server preference	Suite: TLS_ECDHE_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 setting enables negotiation of best security.

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

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

SCT transports: CERT

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

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

SCT transports: CERT

Post-quantum key exchange supported

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

Algorithm: X25519MLKEM768

DHE suites not supported

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

WWW Certificates

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

Test passed

Everything seems to be well configured. Well done.

Certificate: www.libraesva.com

Leaf certificate

libraesva.com
Issuer: Google Trust Services LLC
Not Before: 03 May 2026 00:53:36 UTC
Not After: 01 Aug 2026 01:53:33 UTC (expires in 2 months 16 days)
Key: EC 256 bits
Signature: SHA256withECDSA
View details

Names	libraesva.com *.libraesva.com
Subject DN	CN=libraesva.com
Subject Key Identifier	4c8baccff48066bd6f06324d7a7e2cae5904ef5e
Serial	b076882f048e600b115c690c4fa20a86
Not Before	03 May 2026 00:53:36 UTC
Not After	01 Aug 2026 01:53:33 UTC
Validity period	91 days
Key Usage	digitalSignature
Extended Key Usage	serverAuth
Must Staple	No
Issuer
Issuer DN	CN=WE1, O=Google Trust Services, C=US
Certification Authority	Google Trust Services LLC
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:9077923567c4ffa8cca9e67bd980797bcc93f938
Parent Certificate	http://i.pki.goog/we1.crt
CRL	http://c.pki.goog/we1/hxWfeVec_R4.crl
OCSP	http://o.pki.goog/s/we1/sHY
Certificate Transparency
Signed Certificate Timestamps	03 May 2026 01:53:37 UTC \| Google 'Xenon2026h2' log \| Qualified 03 May 2026 01:53:37 UTC \| Sectigo 'Tiger2026h2' \| Qualified
Fingerprints
SHA1	1e9d58f9ee4b653be4457e1c9760430ee6b124e9
SHA256	760c2ba3067b96cdb6c4b8d174e3e2ea6c0372e644a3c55b9d66cb4aaee426ea
SPKI SHA256	af8cb959c4a220861aedee3cd8303d53b5d4808d45b17b5a1e577518e73ac019

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

libraesva.com | 760c2ba
Not After: 01 Aug 2026 01:53:33 UTC (expires in 2 months 16 days)
Authentication: EC 256 bits (SHA256withECDSA)
View details

Names	libraesva.com *.libraesva.com
Subject DN	CN=libraesva.com
Subject Key Identifier	4c8baccff48066bd6f06324d7a7e2cae5904ef5e
Serial	b076882f048e600b115c690c4fa20a86
Not Before	03 May 2026 00:53:36 UTC
Not After	01 Aug 2026 01:53:33 UTC
Validity period	91 days
Key Usage	digitalSignature
Extended Key Usage	serverAuth
Must Staple	No
Issuer
Issuer DN	CN=WE1, O=Google Trust Services, C=US
Certification Authority	Google Trust Services LLC
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:9077923567c4ffa8cca9e67bd980797bcc93f938
Parent Certificate	http://i.pki.goog/we1.crt
CRL	http://c.pki.goog/we1/hxWfeVec_R4.crl
OCSP	http://o.pki.goog/s/we1/sHY
Certificate Transparency
Signed Certificate Timestamps	03 May 2026 01:53:37 UTC \| Google 'Xenon2026h2' log \| Qualified 03 May 2026 01:53:37 UTC \| Sectigo 'Tiger2026h2' \| Qualified
Fingerprints
SHA1	1e9d58f9ee4b653be4457e1c9760430ee6b124e9
SHA256	760c2ba3067b96cdb6c4b8d174e3e2ea6c0372e644a3c55b9d66cb4aaee426ea
SPKI SHA256	af8cb959c4a220861aedee3cd8303d53b5d4808d45b17b5a1e577518e73ac019

Intermediate certificate

WE1 | 1dfc160
Not After: 20 Feb 2029 14:00:00 UTC (expires in 2 years 9 months)
Authentication: EC 256 bits (SHA384withECDSA)
View details

Subject DN	CN=WE1, O=Google Trust Services, C=US
Subject Key Identifier	9077923567c4ffa8cca9e67bd980797bcc93f938
Serial	7ff31977972c224a76155d13b6d685e3
Not Before	13 Dec 2023 09:00:00 UTC
Not After	20 Feb 2029 14:00:00 UTC
Validity period	1897 days
Key Usage	digitalSignature, keyCertSign, cRLSign
Extended Key Usage	serverAuth, clientAuth
Issuer
Issuer DN	CN=GTS Root R4, O=Google Trust Services LLC, C=US
Certification Authority	Google Trust Services LLC
Validation Type	Not Applicable
Authority Key Identifier	keyid:804cd6eb74ff4936a3d5d8fcb53ec56af0941d8c
Parent Certificate	http://i.pki.goog/r4.crt
CRL	http://c.pki.goog/r/r4.crl
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	108fbf794e18ec5347a414e4370cc4506c297ab2
SHA256	1dfc1605fbad358d8bc844f76d15203fac9ca5c1a79fd4857ffaf2864fbebf96
SPKI SHA256	908769e8d34477cc2cba0632c88605b22d7294c0840f78596d247c645b1afc0e

Intermediate certificate

GTS Root R4 | 76b27b8
Not After: 28 Jan 2028 00:00:42 UTC (expires in 1 year 8 months)
Authentication: EC 384 bits (SHA256withRSA)
View details

Subject DN	CN=GTS Root R4, O=Google Trust Services LLC, C=US
Subject Key Identifier	804cd6eb74ff4936a3d5d8fcb53ec56af0941d8c
Serial	7fe530bf331343bedd821610493d8a1b
Not Before	15 Nov 2023 03:43:21 UTC
Not After	28 Jan 2028 00:00:42 UTC
Validity period	1535 days
Key Usage	digitalSignature, keyCertSign, cRLSign
Extended Key Usage	serverAuth, clientAuth
Issuer
Issuer DN	CN=GlobalSign Root CA, OU=Root CA, O=GlobalSign nv-sa, C=BE
Certification Authority	Google Trust Services LLC
Validation Type	Not Applicable
Authority Key Identifier	keyid:607b661a450d97ca89502f7d04cd34a8fffcfd4b
Parent Certificate	http://i.pki.goog/gsr1.crt
CRL	http://c.pki.goog/r/gsr1.crl
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	932bed339aa69212c89375b79304b475490b89a0
SHA256	76b27b80a58027dc3cf1da68dac17010ed93997d0b603e2fadbe85012493b5a7
SPKI SHA256	9847e5653e5e9e847516e5cb818606aa7544a19be67fd7366d506988e8d84347

Root certificate

GlobalSign Root CA | ebd4104
Not After: 28 Jan 2028 12:00:00 UTC (expires in 1 year 8 months)
Authentication: RSA 2048 bits (SHA1withRSA)
View details

Subject DN	CN=GlobalSign Root CA, OU=Root CA, O=GlobalSign nv-sa, C=BE
Subject Key Identifier	607b661a450d97ca89502f7d04cd34a8fffcfd4b
Serial	040000000001154b5ac394
Not Before	01 Sep 1998 12:00:00 UTC
Not After	28 Jan 2028 12:00:00 UTC
Key Usage	keyCertSign, cRLSign
Issuer
Issuer DN	CN=GlobalSign Root CA, OU=Root CA, O=GlobalSign nv-sa, C=BE
Certification Authority	Google Trust Services LLC
Validation Type	Self-signed
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	b1bc968bd4f49d622aa89a81f2150152a41d829c
SHA256	ebd41040e4bb3ec742c9e381d31ef2a41a48b6685c96e7cef3c1df6cd4331c99
SPKI SHA256	2bcee858158cf5465fc9d76f0dfa312fef25a4dca8501da9b46b67d1fbfa1b64

Analysis

Certificate chain is correct

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

Certificate: libraesva.com

Leaf certificate

libraesva.com
Issuer: Google Trust Services LLC
Not Before: 03 May 2026 00:53:36 UTC
Not After: 01 Aug 2026 01:53:33 UTC (expires in 2 months 16 days)
Key: EC 256 bits
Signature: SHA256withECDSA
View details

Names	libraesva.com *.libraesva.com
Subject DN	CN=libraesva.com
Subject Key Identifier	4c8baccff48066bd6f06324d7a7e2cae5904ef5e
Serial	b076882f048e600b115c690c4fa20a86
Not Before	03 May 2026 00:53:36 UTC
Not After	01 Aug 2026 01:53:33 UTC
Validity period	91 days
Key Usage	digitalSignature
Extended Key Usage	serverAuth
Must Staple	No
Issuer
Issuer DN	CN=WE1, O=Google Trust Services, C=US
Certification Authority	Google Trust Services LLC
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:9077923567c4ffa8cca9e67bd980797bcc93f938
Parent Certificate	http://i.pki.goog/we1.crt
CRL	http://c.pki.goog/we1/hxWfeVec_R4.crl
OCSP	http://o.pki.goog/s/we1/sHY
Certificate Transparency
Signed Certificate Timestamps	03 May 2026 01:53:37 UTC \| Google 'Xenon2026h2' log \| Qualified 03 May 2026 01:53:37 UTC \| Sectigo 'Tiger2026h2' \| Qualified
Fingerprints
SHA1	1e9d58f9ee4b653be4457e1c9760430ee6b124e9
SHA256	760c2ba3067b96cdb6c4b8d174e3e2ea6c0372e644a3c55b9d66cb4aaee426ea
SPKI SHA256	af8cb959c4a220861aedee3cd8303d53b5d4808d45b17b5a1e577518e73ac019

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

libraesva.com | 760c2ba
Not After: 01 Aug 2026 01:53:33 UTC (expires in 2 months 16 days)
Authentication: EC 256 bits (SHA256withECDSA)
View details

Names	libraesva.com *.libraesva.com
Subject DN	CN=libraesva.com
Subject Key Identifier	4c8baccff48066bd6f06324d7a7e2cae5904ef5e
Serial	b076882f048e600b115c690c4fa20a86
Not Before	03 May 2026 00:53:36 UTC
Not After	01 Aug 2026 01:53:33 UTC
Validity period	91 days
Key Usage	digitalSignature
Extended Key Usage	serverAuth
Must Staple	No
Issuer
Issuer DN	CN=WE1, O=Google Trust Services, C=US
Certification Authority	Google Trust Services LLC
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:9077923567c4ffa8cca9e67bd980797bcc93f938
Parent Certificate	http://i.pki.goog/we1.crt
CRL	http://c.pki.goog/we1/hxWfeVec_R4.crl
OCSP	http://o.pki.goog/s/we1/sHY
Certificate Transparency
Signed Certificate Timestamps	03 May 2026 01:53:37 UTC \| Google 'Xenon2026h2' log \| Qualified 03 May 2026 01:53:37 UTC \| Sectigo 'Tiger2026h2' \| Qualified
Fingerprints
SHA1	1e9d58f9ee4b653be4457e1c9760430ee6b124e9
SHA256	760c2ba3067b96cdb6c4b8d174e3e2ea6c0372e644a3c55b9d66cb4aaee426ea
SPKI SHA256	af8cb959c4a220861aedee3cd8303d53b5d4808d45b17b5a1e577518e73ac019

Intermediate certificate

WE1 | 1dfc160
Not After: 20 Feb 2029 14:00:00 UTC (expires in 2 years 9 months)
Authentication: EC 256 bits (SHA384withECDSA)
View details

Subject DN	CN=WE1, O=Google Trust Services, C=US
Subject Key Identifier	9077923567c4ffa8cca9e67bd980797bcc93f938
Serial	7ff31977972c224a76155d13b6d685e3
Not Before	13 Dec 2023 09:00:00 UTC
Not After	20 Feb 2029 14:00:00 UTC
Validity period	1897 days
Key Usage	digitalSignature, keyCertSign, cRLSign
Extended Key Usage	serverAuth, clientAuth
Issuer
Issuer DN	CN=GTS Root R4, O=Google Trust Services LLC, C=US
Certification Authority	Google Trust Services LLC
Validation Type	Not Applicable
Authority Key Identifier	keyid:804cd6eb74ff4936a3d5d8fcb53ec56af0941d8c
Parent Certificate	http://i.pki.goog/r4.crt
CRL	http://c.pki.goog/r/r4.crl
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	108fbf794e18ec5347a414e4370cc4506c297ab2
SHA256	1dfc1605fbad358d8bc844f76d15203fac9ca5c1a79fd4857ffaf2864fbebf96
SPKI SHA256	908769e8d34477cc2cba0632c88605b22d7294c0840f78596d247c645b1afc0e

Intermediate certificate

GTS Root R4 | 76b27b8
Not After: 28 Jan 2028 00:00:42 UTC (expires in 1 year 8 months)
Authentication: EC 384 bits (SHA256withRSA)
View details

Subject DN	CN=GTS Root R4, O=Google Trust Services LLC, C=US
Subject Key Identifier	804cd6eb74ff4936a3d5d8fcb53ec56af0941d8c
Serial	7fe530bf331343bedd821610493d8a1b
Not Before	15 Nov 2023 03:43:21 UTC
Not After	28 Jan 2028 00:00:42 UTC
Validity period	1535 days
Key Usage	digitalSignature, keyCertSign, cRLSign
Extended Key Usage	serverAuth, clientAuth
Issuer
Issuer DN	CN=GlobalSign Root CA, OU=Root CA, O=GlobalSign nv-sa, C=BE
Certification Authority	Google Trust Services LLC
Validation Type	Not Applicable
Authority Key Identifier	keyid:607b661a450d97ca89502f7d04cd34a8fffcfd4b
Parent Certificate	http://i.pki.goog/gsr1.crt
CRL	http://c.pki.goog/r/gsr1.crl
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	932bed339aa69212c89375b79304b475490b89a0
SHA256	76b27b80a58027dc3cf1da68dac17010ed93997d0b603e2fadbe85012493b5a7
SPKI SHA256	9847e5653e5e9e847516e5cb818606aa7544a19be67fd7366d506988e8d84347

Root certificate

GlobalSign Root CA | ebd4104
Not After: 28 Jan 2028 12:00:00 UTC (expires in 1 year 8 months)
Authentication: RSA 2048 bits (SHA1withRSA)
View details

Subject DN	CN=GlobalSign Root CA, OU=Root CA, O=GlobalSign nv-sa, C=BE
Subject Key Identifier	607b661a450d97ca89502f7d04cd34a8fffcfd4b
Serial	040000000001154b5ac394
Not Before	01 Sep 1998 12:00:00 UTC
Not After	28 Jan 2028 12:00:00 UTC
Key Usage	keyCertSign, cRLSign
Issuer
Issuer DN	CN=GlobalSign Root CA, OU=Root CA, O=GlobalSign nv-sa, C=BE
Certification Authority	Google Trust Services LLC
Validation Type	Self-signed
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	b1bc968bd4f49d622aa89a81f2150152a41d829c
SHA256	ebd41040e4bb3ec742c9e381d31ef2a41a48b6685c96e7cef3c1df6cd4331c99
SPKI SHA256	2bcee858158cf5465fc9d76f0dfa312fef25a4dca8501da9b46b67d1fbfa1b64

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.

HTML Content

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

Test passed

Everything seems to be well configured. Well done.

Encryption of Embedded Resources

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

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

Status	Link
Encrypted	https://www.libraesva.com/...ontend/js/gcm.min.js
Encrypted	https://cdn-cookieyes.com/...0d5634390e/script.js
Encrypted	https://www.libraesva.com/...ontend/js/wca.min.js
Encrypted	https://www.libraesva.com/...lot/dist/front-js.js
Encrypted	https://ajax.googleapis.com/.../3.7.1/jquery.min.js
Encrypted	https://maps.googleapis.com/maps/api/js
Encrypted	https://cdn.jsdelivr.net/...swiper-bundle.min.js
Encrypted	https://cdn.jsdelivr.net/...p@3/dist/gsap.min.js
Encrypted	https://cdn.jsdelivr.net/...ScrollTrigger.min.js
Encrypted	https://www.libraesva.com/...esva/dist/js/main.js
Encrypted	https://cdn-app.pathfactory.com/...s/overlay/overlay.js

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

Status	Link
Encrypted	https://cdn.jsdelivr.net/...wiper-bundle.min.css
Encrypted	https://fonts.googleapis.com/css2
Encrypted	https://www.libraesva.com/...st/css/front-css.css
Encrypted	https://www.libraesva.com/...st/css/new-flags.css
Encrypted	https://www.libraesva.com/...a/dist/css/style.css
Encrypted	https://www.libraesva.com/...ial-share-public.css
Encrypted	https://cdn-app.pathfactory.com/.../overlay/overlay.css

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

Encryption of Outbound Links

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

0 link(s)
0 out of 0 are encrypted

HTTP Strict Transport Security

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

Test passed, but there are warnings

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

HSTS Policy Main host

URL from which this policy was obtained.Location	https://www.libraesva.com/
Specifies policy duration. Once activated, HSTS stays in force until this time lapses. Browsers update policy cache duration every time they receive a new HSTS header from a site.max‑age	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.

HSTS Policy Apex host

URL from which this policy was obtained.Location	https://libraesva.com/
Specifies policy duration. Once activated, HSTS stays in force until this time lapses. Browsers update policy cache duration every time they receive a new HSTS header from a site.max‑age	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 not preloaded

When hostname is preloaded, that means that browsers embed your HSTS policy and apply it even to the first request sent to your web site. This server indicates preloading in its policy, but the domain name isn't actually preloaded. We classify this as a warning because it's a common problem to place the 'preload' keyword in the policy even though the infrastructure is not ready for preloading. This is dangerous because, in this situation, anyone can submit this domain name for preloading just by visiting hstspreload.org. We recommend that you either preload this domain name yourself—if it's ready—or remove the preloading indicator from the policy until it is ready.

HTTP Public Key Pinning

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

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

Content Security Policy

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

Test passed

Everything seems to be well configured. Well done.

Content-Security-Policy-Report-Only

default-src	'self' https://s0.wp.com https://fonts.googleapis.com https://fonts.gstatic.com data:
frame-src	'self' data: blob: https://www.youtube.com https://player.vimeo.com https://wp-themes.com
img-src	data: *
media-src	data: *
style-src	'self' https://fonts.googleapis.com data: This parameter shouldn't be used because it reenables insecure behavior that CSP disables by default.'unsafe-inline'
script-src	https://wp-themes.com 'self' data: This parameter shouldn't be used because it reenables insecure behavior that CSP disables by default.'unsafe-inline' This parameter shouldn't be used because it reenables insecure behavior that CSP disables by default.'unsafe-eval'
worker-src	'self'
frame-ancestors	'self' https://hub.libraesva.com
report-uri	https://sentry.libraesva.com/api/16/security/

Analysis

Inline scripts are allowed

By default, CSP doesn't allow inline script execution, but this policy overrides that behavior by specifying 'unsafe-inline' in the 'script-src' directive. As a result, all XSS defenses provided by CSP are significantly weakened.

Inline styles are allowed

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

Dynamic code execution is allowed

By default, CSP doesn't allow dynamic script execution via eval and friends, but this policy overrides that behavior by specifyin 'unsafe-eval' in the 'script-src' directive. As a result, XSS defenses provided by CSP are significantly weakened.

Mixed content not blocked

This CSP policy doesn't use any of the directives designed to handle mixed content. Consider using the 'block-all-mixed-content' and 'upgrade-insecure-requests' directives as appropriate to ensure that no mixed content is allowed.

Form targets not restricted

The 'form-action' directive is not explicitly set. Because this directive doesn't fall back to default sources, this means that all targets are allowed.

Analysis

CSP report-only policy detected

Header: Content-Security-Policy-Report-Only

Value: default-src 'self' https://s0.wp.com https://fonts.googleapis.com https://fonts.gstatic.com data:; frame-src 'self' data: blob: https://www.youtube.com https://player.vimeo.com https://wp-themes.com; img-src * data:; media-src * data:; style-src 'self' https://fonts.googleapis.com data: 'unsafe-inline'; script-src https://wp-themes.com 'self' data: 'unsafe-inline' 'unsafe-eval'; worker-src 'self'; frame-ancestors 'self' https://hub.libraesva.com; report-uri https://sentry.libraesva.com/api/16/security/?sentry_key=ec35ea3e850202bb70633fcd5d55c698

Location: https://www.libraesva.com/

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.

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

11 script(s)
4 out of 11 are secure

https://ajax.googleapis.com/.../3.7.1/jquery.min.js

https://cdn-app.pathfactory.com/...s/overlay/overlay.js

https://cdn-cookieyes.com/...0d5634390e/script.js

https://cdn.jsdelivr.net/...ScrollTrigger.min.js

https://cdn.jsdelivr.net/...p@3/dist/gsap.min.js

https://cdn.jsdelivr.net/...swiper-bundle.min.js

https://maps.googleapis.com/maps/api/js

View all

Status	Link
Remote	https://ajax.googleapis.com/ajax/libs/jquery/3.7.1/jquery.min.js?ver=3.7.1
Remote	https://cdn-app.pathfactory.com/libraries/overlay/overlay.js
Remote	https://cdn-cookieyes.com/client_data/3a1ade222ca8130d5634390e/script.js
Remote	https://cdn.jsdelivr.net/npm/gsap@3/dist/ScrollTrigger.min.js?ver=6.9.4
Remote	https://cdn.jsdelivr.net/npm/gsap@3/dist/gsap.min.js?ver=6.9.4
Remote	https://cdn.jsdelivr.net/npm/swiper@11/swiper-bundle.min.js?ver=6.9.4
Remote	https://maps.googleapis.com/maps/api/js?key=AIzaSyA96CbnrUHVrypZUMF1WbyAkPpkt6tzwlo&callback=Function.prototype&ver=6.9.4
Local	https://www.libraesva.com/wp-content/plugins/cookie-law-info/lite/frontend/js/gcm.min.js
Local	https://www.libraesva.com/wp-content/plugins/cookie-law-info/lite/frontend/js/wca.min.js?ver=3.4.2
Local	https://www.libraesva.com/wp-content/plugins/weglot/dist/front-js.js?ver=5.5
Local	https://www.libraesva.com/wp-content/themes/libraesva/dist/js/main.js?ver=1.0.0

7 CSS file(s)
4 out of 7 are secure

https://cdn-app.pathfactory.com/.../overlay/overlay.css

https://cdn.jsdelivr.net/...wiper-bundle.min.css

https://fonts.googleapis.com/css2

View all

Status	Link
Remote	https://cdn-app.pathfactory.com/libraries/overlay/overlay.css
Remote	https://cdn.jsdelivr.net/npm/swiper@11/swiper-bundle.min.css
Remote	https://fonts.googleapis.com/css2?family=Roboto:ital,wght@0,100..900;1,100..900&display=swap
Local	https://www.libraesva.com/wp-content/plugins/sassy-social-share/public/css/sassy-social-share-public.css?ver=3.3.79
Local	https://www.libraesva.com/wp-content/plugins/weglot/dist/css/front-css.css?ver=5.5
Local	https://www.libraesva.com/wp-content/plugins/weglot/dist/css/new-flags.css?ver=5.5
Local	https://www.libraesva.com/wp-content/themes/libraesva/dist/css/style.css?ver=1.0.0

Analysis

SRI required

This page contains remote resources that are under the control of third parties. Deploy SRI to protect them from modification.

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.

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

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, but there are warnings

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

Analysis

Header information

Name: x-xss-protection

Value: 1; mode=block

XSS auditor blocking is dangerous

Your configuration requests blocking when XSS attacks are detected, which is potentially dangerous as it allows attackers to selectively disable portions of JavaScript code. The only safe approach is to explicitly disable browser-based XSS protection.

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 | libraesva.com

libraesva.com

Domain Name System

Email

WWW

DNS Zone

Nameserver Names

Nameserver Addresses

Start of Authority (SOA) Record

Analysis

Backing DNS Queries

DNS Records

DNS Records

Backing DNS Queries

DNSSEC

Useful DNSSEC Tools

Certification Authority Authorization

CAA Policy Information

Analysis

Email (SMTP)

Email TLS (SMTP)

TLS Configuration: mail.libraesva.com (185.91.71.80)

Analysis

TLS Configuration: mail2.libraesva.com (109.168.30.140)

Analysis

Email Certificates (SMTP)

Certificate #1

Analysis

Certificate Chain

Analysis

Certificate #2

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

SMTP TLS Reporting

TLS-RPT Policy

Analysis

HTTP (80)

URL: http://libraesva.com/

Analysis

URL: http://www.libraesva.com/

Analysis

HTTP (443)

URL: https://libraesva.com/

URL: https://www.libraesva.com/

WWW TLS

TLS Configuration: libraesva.com (2606:4700:3037:0:0:0:6815:3f7b)

Analysis

TLS Configuration: libraesva.com (2606:4700:3030:0:0:0:ac43:aaac)

Analysis

TLS Configuration: libraesva.com (104.21.63.123)

Analysis

TLS Configuration: www.libraesva.com (2606:4700:3037:0:0:0:6815:3f7b)

Analysis

TLS Configuration: libraesva.com (172.67.170.172)

Analysis

TLS Configuration: www.libraesva.com (2606:4700:3030:0:0:0:ac43:aaac)

Analysis

TLS Configuration: www.libraesva.com (172.67.170.172)

Analysis

TLS Configuration: www.libraesva.com (104.21.63.123)

Analysis

WWW Certificates

Certificate: www.libraesva.com

Analysis

Certificate Trust

Certificate Chain

Analysis

Certificate: libraesva.com

Analysis

Certificate Trust