Hardenize Report: turva.dev

Web Security Overview

HTTPS

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

For all sites VERY IMPORTANT medium EFFORT

HTTPS Redirection

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

For all sites VERY IMPORTANT low EFFORT

HTTP Strict Transport Security

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

For important sites VERY IMPORTANT medium EFFORT

HSTS Preloaded

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

For important sites VERY IMPORTANT medium EFFORT

Content Security Policy

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

For important sites IMPORTANT high EFFORT

Email Security Overview

STARTTLS

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

For all sites VERY IMPORTANT low EFFORT

SPF

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

For important sites IMPORTANT low EFFORT

DMARC

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

For important sites IMPORTANT low EFFORT

DNS Zone

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

Test passed

Everything seems to be well configured. Well done.

Nameserver Names

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

Nameserver	Operational	IPv4	IPv6	Sources
lennox.ns.cloudflare.com. PRIMARY 108.162.195.214 162.159.44.214 172.64.35.214 2606:4700:58::a29f:2cd6 2803:f800:50::6ca2:c3d6 2a06:98c1:50::ac40:23d6				NS SOA REFERRAL
luciane.ns.cloudflare.com. 108.162.194.120 162.159.38.120 172.64.34.120 2606:4700:50::a29f:2678 2803:f800:50::6ca2:c278 2a06:98c1:50::ac40:2278				NS REFERRAL

Nameserver Addresses

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

Nameserver	Sources	Payload Size
108.162.194.120 luciane.ns.cloudflare.com. PTR: luciane.ns.cloudflare.com.	NAME	1232
108.162.195.214 PRIMARY lennox.ns.cloudflare.com. PTR: lennox.ns.cloudflare.com.	NAME	1232
162.159.38.120 luciane.ns.cloudflare.com. PTR: luciane.ns.cloudflare.com.	NAME	1232
162.159.44.214 PRIMARY lennox.ns.cloudflare.com. PTR: lennox.ns.cloudflare.com.	NAME	1232
172.64.34.120 luciane.ns.cloudflare.com. PTR: luciane.ns.cloudflare.com.	NAME	1232
172.64.35.214 PRIMARY lennox.ns.cloudflare.com. PTR: lennox.ns.cloudflare.com.	NAME	1232
2606:4700:50::a29f:2678 luciane.ns.cloudflare.com. PTR: luciane.ns.cloudflare.com.	NAME	1232
2606:4700:58::a29f:2cd6 PRIMARY lennox.ns.cloudflare.com. PTR: lennox.ns.cloudflare.com.	NAME	1232
2803:f800:50::6ca2:c278 luciane.ns.cloudflare.com. PTR: luciane.ns.cloudflare.com.	NAME	1232
2803:f800:50::6ca2:c3d6 PRIMARY lennox.ns.cloudflare.com. PTR: lennox.ns.cloudflare.com.	NAME	1232
2a06:98c1:50::ac40:2278 luciane.ns.cloudflare.com. PTR: luciane.ns.cloudflare.com.	NAME	1232
2a06:98c1:50::ac40:23d6 PRIMARY lennox.ns.cloudflare.com. PTR: lennox.ns.cloudflare.com.	NAME	1232

Start of Authority (SOA) Record

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

The domain name of the primary nameserver for the zone. Also known as MNAME.Primary nameserver	lennox.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	-1883263109
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
turva.dev.	300	A	172.67.72.212
turva.dev.	300	A	104.26.1.140
turva.dev.	300	A	104.26.0.140
www.turva.dev.	300	A	172.67.72.212
www.turva.dev.	300	A	104.26.1.140
www.turva.dev.	300	A	104.26.0.140
turva.dev.	300	AAAA	2606:4700:20:0:0:0:ac43:48d4
turva.dev.	300	AAAA	2606:4700:20:0:0:0:681a:8c
turva.dev.	300	AAAA	2606:4700:20:0:0:0:681a:18c
www.turva.dev.	300	AAAA	2606:4700:20:0:0:0:ac43:48d4
www.turva.dev.	300	AAAA	2606:4700:20:0:0:0:681a:18c
www.turva.dev.	300	AAAA	2606:4700:20:0:0:0:681a:8c
turva.dev.	300	CAA	0 issuewild "pki.goog; cansignhttpexchanges=yes"
turva.dev.	300	CAA	0 issuewild "ssl.com"
turva.dev.	300	CAA	0 iodef " mailto:info@turva.dev"
turva.dev.	300	CAA	0 issue "comodoca.com"
turva.dev.	300	CAA	0 issue "digicert.com; cansignhttpexchanges=yes"
turva.dev.	300	CAA	0 issue "letsencrypt.org"
turva.dev.	300	CAA	0 issue "pki.goog; cansignhttpexchanges=yes"
turva.dev.	300	CAA	0 issue "ssl.com"
turva.dev.	300	CAA	0 issuewild "comodoca.com"
turva.dev.	300	CAA	0 issuewild "digicert.com; cansignhttpexchanges=yes"
turva.dev.	300	CAA	0 issuewild "letsencrypt.org"
turva.dev.	3600	DNSKEY	257 3 13 mdsswUyr3DPW132mOi8V9xESWE8jTo0dxCjjnopKl+GqJxpVXckHAeF+KkxLbxILfDLUT0rAK9iUzy1L53eKGQ==
turva.dev.	3600	DNSKEY	256 3 13 oJMRESz5E4gYzS/q6XDrvU1qMPYIjCWzJaOau8XNEZeqCYKD5ar0IRd8KqXXFJkqmVfRvMGPmM1x8fGAa2XhSA==
turva.dev.	300	HTTPS	1 . alpn=h3,h2 ipv4hint=104.26.0.140,104.26.1.140,172.67.72.212 ech=AEX+DQBBZwAgACBaz6aLb5mF7c/51IaCUfKO7zm3qmnq4IxVhbIVQk02OAAEAAEAAQASY2xvdWRmbGFyZS1lY2guY29tAAA= ipv6hint=2606:4700:20:0:0:0:681a:8c,2606:4700:20:0:0:0:681a:18c,2606:4700:20:0:0:0:ac43:48d4
www.turva.dev.	300	HTTPS	1 . alpn=h3,h2 ipv4hint=104.26.0.140,104.26.1.140,172.67.72.212 ech=AEX+DQBBZwAgACBaz6aLb5mF7c/51IaCUfKO7zm3qmnq4IxVhbIVQk02OAAEAAEAAQASY2xvdWRmbGFyZS1lY2guY29tAAA= ipv6hint=2606:4700:20:0:0:0:681a:8c,2606:4700:20:0:0:0:681a:18c,2606:4700:20:0:0:0:ac43:48d4
turva.dev.	300	MX	30 mxext3.mailbox.org.
turva.dev.	300	MX	40 mxext4.mailbox.org.
turva.dev.	300	MX	10 mxext1.mailbox.org.
turva.dev.	300	MX	20 mxext2.mailbox.org.
turva.dev.	86400	NS	lennox.ns.cloudflare.com.
turva.dev.	86400	NS	luciane.ns.cloudflare.com.
turva.dev.	1800	SOA	lennox.ns.cloudflare.com. dns.cloudflare.com. 2411704187 10000 2400 604800 1800
turva.dev.	300	TXT	"google-site-verification=eDp4p_qeDRH-Ew9aBvXwQhJZopwtKaFCMDHZjrFDAtM"
turva.dev.	300	TXT	"v=spf1 include:mailbox.org ~all"
turva.dev.	300	TXT	"_m1z4s7ppywsrkcmswq3yizm378kaecj"
_dmarc.turva.dev.	300	TXT	"v=DMARC1; p=quarantine; pct=100; adkim=s; aspf=s; rua=mailto:re+gr4dh7urmxz@dmarc.postmarkapp.com"
_mta-sts.turva.dev.	300	TXT	"v=STSv1; id=20260804163000"
_smtp._tls.turva.dev.	300	TXT	"v=TLSRPTv1; rua=mailto:info@turva.dev"

Backing DNS Queries

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

	ID	Server	Question Name	Type	Status

DNSSEC

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

Test passed

Everything seems to be well configured. Well done.

Analysis

DNSSEC is well configured

Good. This domain name has well-configured DNSSEC.

Useful DNSSEC Tools

Certification Authority Authorization

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

Test passed

Everything seems to be well configured. Well done.

CAA Policy Information

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

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
mxext1.mailbox.org 80.241.60.212 PTR: mx1.mailbox.org	10
mxext2.mailbox.org 80.241.60.215 PTR: mx2.mailbox.org	20
mxext3.mailbox.org 80.241.60.216 PTR: mx3.mailbox.org	30
mxext4.mailbox.org 80.241.60.217 PTR: mx4.mailbox.org	40

Analysis

Email servers match MTA-STS policy

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

Limited testing of third-party SMTP servers

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

Some SMTP server assessments contain partial information

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

Email TLS (SMTP)

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

Test passed

Everything seems to be well configured. Well done.

TLS Configuration: mxext1.mailbox.org (80.241.60.212)

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

Analysis

TLS 1.2 supported

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

Strong key exchange detected

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

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

Partial results shown

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

Relaxed TLS assessment criteria applied to SMTP on port 25

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

TLS Configuration: mxext2.mailbox.org (80.241.60.215)

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

Analysis

TLS 1.2 supported

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

Strong key exchange detected

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

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

Partial results shown

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

Relaxed TLS assessment criteria applied to SMTP on port 25

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

TLS Configuration: mxext3.mailbox.org (80.241.60.216)

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

Analysis

TLS 1.2 supported

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

Strong key exchange detected

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

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

Partial results shown

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

Relaxed TLS assessment criteria applied to SMTP on port 25

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

TLS Configuration: mxext4.mailbox.org (80.241.60.217)

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

Analysis

TLS 1.2 supported

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

Strong key exchange detected

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

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

Partial results shown

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

Relaxed TLS assessment criteria applied to SMTP on port 25

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

Email Certificates (SMTP)

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

Test passed

Everything seems to be well configured. Well done.

Certificate #1

Leaf certificate

*.mailbox.org
Issuer: DigiCert
Not Before: 18 May 2026 00:00:00 UTC
Not After: 02 Dec 2026 23:59:59 UTC (expires in 3 months 21 days)
Key: RSA 4096 bits
Signature: SHA256withRSA
View details

Names	*.mailbox.org mailbox.org
Subject DN	CN=*.mailbox.org
Subject Key Identifier	67757539e587ffbbfa1396e908a1b555c861aa08
Serial	03b96bdce4eef71dd8ac45c23fe5347b
Not Before	18 May 2026 00:00:00 UTC
Not After	02 Dec 2026 23:59:59 UTC
Validity period	199 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=Thawte TLS RSA CA G1, OU=www.digicert.com, O=DigiCert Inc, C=US
Certification Authority	DigiCert
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:a58cfe32cceb0f2cd419c608b80024885dc3c5b7
Parent Certificate	http://cacerts.thawte.com/ThawteTLSRSACAG1.crt
CRL	http://cdp.thawte.com/ThawteTLSRSACAG1.crl
OCSP	http://status.thawte.com
Certificate Transparency
Signed Certificate Timestamps	18 May 2026 10:42:09 UTC \| DigiCert 'Wyvern2026h2' \| Qualified 18 May 2026 10:42:09 UTC \| Google 'Xenon2026h2' log \| Qualified 18 May 2026 10:42:09 UTC \| DigiCert 'Sphinx2026h2' \| Qualified
Fingerprints
SHA1	8284599483cb73137e68c9061256a9d5424c98c2
SHA256	6dcc7ccad5875f926c0ecd35da5da977509555f61d189329c5c0015236baeb53
SPKI SHA256	996ad31d65e03f038b8ec950f6f26611529da03e3a283e4400cba2edd04b8a88

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

*.mailbox.org | 6dcc7cc
Not After: 02 Dec 2026 23:59:59 UTC (expires in 3 months 21 days)
Authentication: RSA 4096 bits (SHA256withRSA)
View details

Names	*.mailbox.org mailbox.org
Subject DN	CN=*.mailbox.org
Subject Key Identifier	67757539e587ffbbfa1396e908a1b555c861aa08
Serial	03b96bdce4eef71dd8ac45c23fe5347b
Not Before	18 May 2026 00:00:00 UTC
Not After	02 Dec 2026 23:59:59 UTC
Validity period	199 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=Thawte TLS RSA CA G1, OU=www.digicert.com, O=DigiCert Inc, C=US
Certification Authority	DigiCert
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:a58cfe32cceb0f2cd419c608b80024885dc3c5b7
Parent Certificate	http://cacerts.thawte.com/ThawteTLSRSACAG1.crt
CRL	http://cdp.thawte.com/ThawteTLSRSACAG1.crl
OCSP	http://status.thawte.com
Certificate Transparency
Signed Certificate Timestamps	18 May 2026 10:42:09 UTC \| DigiCert 'Wyvern2026h2' \| Qualified 18 May 2026 10:42:09 UTC \| Google 'Xenon2026h2' log \| Qualified 18 May 2026 10:42:09 UTC \| DigiCert 'Sphinx2026h2' \| Qualified
Fingerprints
SHA1	8284599483cb73137e68c9061256a9d5424c98c2
SHA256	6dcc7ccad5875f926c0ecd35da5da977509555f61d189329c5c0015236baeb53
SPKI SHA256	996ad31d65e03f038b8ec950f6f26611529da03e3a283e4400cba2edd04b8a88

Intermediate certificate

Thawte TLS RSA CA G1 | 4bcc5e2
Not After: 02 Nov 2027 12:24:25 UTC (expires in 1 year 2 months)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Subject DN	CN=Thawte TLS RSA CA G1, OU=www.digicert.com, O=DigiCert Inc, C=US
Subject Key Identifier	a58cfe32cceb0f2cd419c608b80024885dc3c5b7
Serial	090ee8c5de5bfa62d2ae2ff7097c4857
Not Before	02 Nov 2017 12:24:25 UTC
Not After	02 Nov 2027 12:24:25 UTC
Key Usage	digitalSignature, keyCertSign, cRLSign
Extended Key Usage	serverAuth, clientAuth
Issuer
Issuer DN	CN=DigiCert Global Root G2, OU=www.digicert.com, O=DigiCert Inc, C=US
Certification Authority	DigiCert
Validation Type	Not Applicable
Authority Key Identifier	keyid:4e2254201895e6e36ee60ffafab912ed06178f39
CRL	http://crl3.digicert.com/DigiCertGlobalRootG2.crl
OCSP	http://ocsp.digicert.com
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	c9fefc763d9548b487696f047acba0abe45c7bc1
SHA256	4bcc5e234fe81ede4eaf883aa19c31335b0b26e85e066b9945e4cb6153eb20c2
SPKI SHA256	e366fd44d3a7c9bded942d0a62d34f03728aa4996eb24c94e9a1be0a2a5499a3

Root certificate

DigiCert Global Root G2 | cb3ccbb
Not After: 15 Jan 2038 12:00:00 UTC (expires in 11 years 5 months)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Subject DN	CN=DigiCert Global Root G2, OU=www.digicert.com, O=DigiCert Inc, C=US
Subject Key Identifier	4e2254201895e6e36ee60ffafab912ed06178f39
Serial	033af1e6a711a9a0bb2864b11d09fae5
Not Before	01 Aug 2013 12:00:00 UTC
Not After	15 Jan 2038 12:00:00 UTC
Key Usage	digitalSignature, keyCertSign, cRLSign
Issuer
Issuer DN	CN=DigiCert Global Root G2, OU=www.digicert.com, O=DigiCert Inc, C=US
Certification Authority	DigiCert
Validation Type	Self-signed
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	df3c24f9bfd666761b268073fe06d1cc8d4f82a4
SHA256	cb3ccbb76031e5e0138f8dd39a23f9de47ffc35e43c1144cea27d46a5ab1cb5f
SPKI SHA256	8bb593a93be1d0e8a822bb887c547890c3e706aad2dab76254f97fb36b82fc26

Analysis

Certificate chain is correct

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

Email DANE (SMTP)

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

Test passed

Everything seems to be well configured. Well done.

DANE: mxext1.mailbox.org (80.241.60.212)

Specifies which certificate in the chain is being pinned and how validation should be performed.Certificate Usage	Domain-issued certificate / DANE-EE (3)
Determines if the association is made with a certificate or with a public key (via its SPKI structure).Selector	SPKI structure (1)
Determines how matching is done; directly or via a hash. Matching Type	SHA2-256 (1)
Contains the data necessary to perform the matching. Data	996ad31d65e03f038b8ec950f6f26611529da03e3a283e4400cba2edd04b8a88 Leaf certificate: RSA 4096 bits Subject: CN=.mailbox.org Issuer: CN=Thawte TLS RSA CA G1, OU=www.digicert.com, O=DigiCert Inc, C=US .mailbox.org (RSA 4096 bits)

Specifies which certificate in the chain is being pinned and how validation should be performed.Certificate Usage	Domain-issued certificate / DANE-EE (3)
Determines if the association is made with a certificate or with a public key (via its SPKI structure).Selector	SPKI structure (1)
Determines how matching is done; directly or via a hash. Matching Type	SHA2-256 (1)
Contains the data necessary to perform the matching. Data	4758af6f02dfb5dc8795fa402e77a8a0486af5e85d2ca60c294476aadc40b220

Specifies which certificate in the chain is being pinned and how validation should be performed.Certificate Usage	Domain-issued certificate / DANE-EE (3)
Determines if the association is made with a certificate or with a public key (via its SPKI structure).Selector	SPKI structure (1)
Determines how matching is done; directly or via a hash. Matching Type	SHA2-256 (1)
Contains the data necessary to perform the matching. Data	e41cc7633029afdba53744d7e5fc31ef507e592de9dfb33557bf3b9a79239446

Analysis

Valid DANE configuration

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

DANE: mxext2.mailbox.org (80.241.60.215)

Specifies which certificate in the chain is being pinned and how validation should be performed.Certificate Usage	Domain-issued certificate / DANE-EE (3)
Determines if the association is made with a certificate or with a public key (via its SPKI structure).Selector	SPKI structure (1)
Determines how matching is done; directly or via a hash. Matching Type	SHA2-256 (1)
Contains the data necessary to perform the matching. Data	e41cc7633029afdba53744d7e5fc31ef507e592de9dfb33557bf3b9a79239446

Specifies which certificate in the chain is being pinned and how validation should be performed.Certificate Usage	Domain-issued certificate / DANE-EE (3)
Determines if the association is made with a certificate or with a public key (via its SPKI structure).Selector	SPKI structure (1)
Determines how matching is done; directly or via a hash. Matching Type	SHA2-256 (1)
Contains the data necessary to perform the matching. Data	4758af6f02dfb5dc8795fa402e77a8a0486af5e85d2ca60c294476aadc40b220

Specifies which certificate in the chain is being pinned and how validation should be performed.Certificate Usage	Domain-issued certificate / DANE-EE (3)
Determines if the association is made with a certificate or with a public key (via its SPKI structure).Selector	SPKI structure (1)
Determines how matching is done; directly or via a hash. Matching Type	SHA2-256 (1)
Contains the data necessary to perform the matching. Data	996ad31d65e03f038b8ec950f6f26611529da03e3a283e4400cba2edd04b8a88 Leaf certificate: RSA 4096 bits Subject: CN=.mailbox.org Issuer: CN=Thawte TLS RSA CA G1, OU=www.digicert.com, O=DigiCert Inc, C=US .mailbox.org (RSA 4096 bits)

Analysis

Valid DANE configuration

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

DANE: mxext3.mailbox.org (80.241.60.216)

Specifies which certificate in the chain is being pinned and how validation should be performed.Certificate Usage	Domain-issued certificate / DANE-EE (3)
Determines if the association is made with a certificate or with a public key (via its SPKI structure).Selector	SPKI structure (1)
Determines how matching is done; directly or via a hash. Matching Type	SHA2-256 (1)
Contains the data necessary to perform the matching. Data	e41cc7633029afdba53744d7e5fc31ef507e592de9dfb33557bf3b9a79239446

Specifies which certificate in the chain is being pinned and how validation should be performed.Certificate Usage	Domain-issued certificate / DANE-EE (3)
Determines if the association is made with a certificate or with a public key (via its SPKI structure).Selector	SPKI structure (1)
Determines how matching is done; directly or via a hash. Matching Type	SHA2-256 (1)
Contains the data necessary to perform the matching. Data	996ad31d65e03f038b8ec950f6f26611529da03e3a283e4400cba2edd04b8a88 Leaf certificate: RSA 4096 bits Subject: CN=.mailbox.org Issuer: CN=Thawte TLS RSA CA G1, OU=www.digicert.com, O=DigiCert Inc, C=US .mailbox.org (RSA 4096 bits)

Specifies which certificate in the chain is being pinned and how validation should be performed.Certificate Usage	Domain-issued certificate / DANE-EE (3)
Determines if the association is made with a certificate or with a public key (via its SPKI structure).Selector	SPKI structure (1)
Determines how matching is done; directly or via a hash. Matching Type	SHA2-256 (1)
Contains the data necessary to perform the matching. Data	4758af6f02dfb5dc8795fa402e77a8a0486af5e85d2ca60c294476aadc40b220

Analysis

Valid DANE configuration

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

DANE: mxext4.mailbox.org (80.241.60.217)

Specifies which certificate in the chain is being pinned and how validation should be performed.Certificate Usage	Domain-issued certificate / DANE-EE (3)
Determines if the association is made with a certificate or with a public key (via its SPKI structure).Selector	SPKI structure (1)
Determines how matching is done; directly or via a hash. Matching Type	SHA2-256 (1)
Contains the data necessary to perform the matching. Data	e41cc7633029afdba53744d7e5fc31ef507e592de9dfb33557bf3b9a79239446

Specifies which certificate in the chain is being pinned and how validation should be performed.Certificate Usage	Domain-issued certificate / DANE-EE (3)
Determines if the association is made with a certificate or with a public key (via its SPKI structure).Selector	SPKI structure (1)
Determines how matching is done; directly or via a hash. Matching Type	SHA2-256 (1)
Contains the data necessary to perform the matching. Data	4758af6f02dfb5dc8795fa402e77a8a0486af5e85d2ca60c294476aadc40b220

Specifies which certificate in the chain is being pinned and how validation should be performed.Certificate Usage	Domain-issued certificate / DANE-EE (3)
Determines if the association is made with a certificate or with a public key (via its SPKI structure).Selector	SPKI structure (1)
Determines how matching is done; directly or via a hash. Matching Type	SHA2-256 (1)
Contains the data necessary to perform the matching. Data	996ad31d65e03f038b8ec950f6f26611529da03e3a283e4400cba2edd04b8a88 Leaf certificate: RSA 4096 bits Subject: CN=.mailbox.org Issuer: CN=Thawte TLS RSA CA G1, OU=www.digicert.com, O=DigiCert Inc, C=US .mailbox.org (RSA 4096 bits)

Analysis

Valid DANE configuration

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

SPF

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

Test passed

Everything seems to be well configured. Well done.

SPF Policy Information Main policy

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

Analysis

SPF policy found

Policy text: v=spf1 include:mailbox.org ~all

Location: turva.dev

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

SPF Policy Information Included policy

Host where this policy is located.Location	mailbox.org
SPF version used by this policy.v	spf1
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	213.203.238.0/25
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	195.10.208.0/24
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	91.198.250.0/24
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	80.241.56.0/21
This mechanism tests whether the IP address being tested is contained within a given IPv6 network. ip6	2001:67c:2050::/48
This mechanism matches if the sending IP address is one of the MX hosts for the domain name. mx
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.turva.dev
DMARC version used by this policy.v	DMARC1
Indicates the policy to be enacted by the receiver at the request of the domain owner. Possible values are: none, quarantine, and reject.p	quarantine
Percentage of messages from mail stream to which the DMARC policy is to be applied.pct	100
Indicates whether strict or relaxed DKIM alignment mode is required.adkim	s
Indicates whether strict or relaxed SPF alignment mode is required.aspf	s
Addresses to which aggregate feedback is to be sent.rua	mailto:re+gr4dh7urmxz@dmarc.postmarkapp.com

Analysis

DMARC policy found

Policy: v=DMARC1; p=quarantine; pct=100; adkim=s; aspf=s; rua=mailto:re+gr4dh7urmxz@dmarc.postmarkapp.com

Host: _dmarc.turva.dev

Valid external destination

Permission record location: turva.dev._report._dmarc.dmarc.postmarkapp.com

External destination: mailto:re+gr4dh7urmxz@dmarc.postmarkapp.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.

Test passed

Everything seems to be well configured. Well done.

MTA-STS Policy Indicator

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

Analysis

MTA-STS policy indicator valid

Good. Your MTA-STS policy indicator is valid.

MTA-STS Policy

The URL from which the policy was obtained.Location	https://mta-sts.turva.dev/.well-known/mta-sts.txt
Policy standard version.version	STSv1
Policy duration, which specifies how long the sending MTAs should remember and enforce the server policy for.max‑age	604,800 seconds (about 7 days)
Policy mode, which can be one of 'none', 'testing' and 'enforcing'. Guess which is best! :)mode	enforce
One 'mx' directive specifies one email server pattern that's allowed for this host.mx	mxext1.mailbox.org
One 'mx' directive specifies one email server pattern that's allowed for this host.mx	mxext2.mailbox.org
One 'mx' directive specifies one email server pattern that's allowed for this host.mx	mxext3.mailbox.org
One 'mx' directive specifies one email server pattern that's allowed for this host.mx	mxext4.mailbox.org

Analysis

MTA-STS policy is valid

Good. Your MTA-STS policy is valid.

Policy host certificate is valid

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

Policy HTTPS response information

Status code: 200

Length: 137 bytes

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

Certificate: mta-sts.turva.dev

Leaf certificate

turva.dev
Issuer: Let's Encrypt
Not Before: 13 Jul 2026 22:06:40 UTC
Not After: 11 Oct 2026 22:06:39 UTC (expires in 2 months 12 hours)
Key: EC 256 bits
Signature: SHA384withECDSA
View details

Names	*.turva.dev turva.dev
Subject DN	CN=turva.dev
Subject Key Identifier	78f89ba8032368fbd74cd96dc8840f57d1105751
Serial	05e73645ea5326c1be76934859818879f6bd
Not Before	13 Jul 2026 22:06:40 UTC
Not After	11 Oct 2026 22:06:39 UTC
Validity period	90 days
Key Usage	digitalSignature
Extended Key Usage	serverAuth
Must Staple	No
Issuer
Issuer DN	CN=YE2, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:b959f28ecf22f086d33748ff761418ba82d85587
Parent Certificate	http://ye2.i.lencr.org/
CRL	http://ye2.c.lencr.org/62.crl
Certificate Transparency
Signed Certificate Timestamps	13 Jul 2026 23:05:11 UTC \| Sectigo 'Tiger2026h2' \| Qualified 13 Jul 2026 23:05:11 UTC \| Geomys 'Tuscolo2026h2' \| Qualified
Fingerprints
SHA1	51f57c19987c00bbccf1bbdfa9589b477016189a
SHA256	cc32783df645ec308255cdb78f370c8b9c7bb1d6000e3ecad08d209bf7dcde83
SPKI SHA256	36a4a85c0b98054e56473acddd9cbfa5437f5c3c18d956e4044f55e4bd0ba9a9

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

turva.dev | cc32783
Not After: 11 Oct 2026 22:06:39 UTC (expires in 2 months 12 hours)
Authentication: EC 256 bits (SHA384withECDSA)
View details

Names	*.turva.dev turva.dev
Subject DN	CN=turva.dev
Subject Key Identifier	78f89ba8032368fbd74cd96dc8840f57d1105751
Serial	05e73645ea5326c1be76934859818879f6bd
Not Before	13 Jul 2026 22:06:40 UTC
Not After	11 Oct 2026 22:06:39 UTC
Validity period	90 days
Key Usage	digitalSignature
Extended Key Usage	serverAuth
Must Staple	No
Issuer
Issuer DN	CN=YE2, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:b959f28ecf22f086d33748ff761418ba82d85587
Parent Certificate	http://ye2.i.lencr.org/
CRL	http://ye2.c.lencr.org/62.crl
Certificate Transparency
Signed Certificate Timestamps	13 Jul 2026 23:05:11 UTC \| Sectigo 'Tiger2026h2' \| Qualified 13 Jul 2026 23:05:11 UTC \| Geomys 'Tuscolo2026h2' \| Qualified
Fingerprints
SHA1	51f57c19987c00bbccf1bbdfa9589b477016189a
SHA256	cc32783df645ec308255cdb78f370c8b9c7bb1d6000e3ecad08d209bf7dcde83
SPKI SHA256	36a4a85c0b98054e56473acddd9cbfa5437f5c3c18d956e4044f55e4bd0ba9a9

Intermediate certificate

YE2 | 97658de
Not After: 02 Sep 2028 23:59:59 UTC (expires in 2 years 22 days)
Authentication: EC 384 bits (SHA384withECDSA)
View details

Subject DN	CN=YE2, O=Let's Encrypt, C=US
Subject Key Identifier	b959f28ecf22f086d33748ff761418ba82d85587
Serial	4df3b15dd6c0784c507cd37b58e6f115
Not Before	03 Sep 2025 00:00:00 UTC
Not After	02 Sep 2028 23:59:59 UTC
Validity period	1096 days
Key Usage	digitalSignature, keyCertSign, cRLSign
Extended Key Usage	serverAuth
Issuer
Issuer DN	CN=Root YE, O=ISRG, C=US
Certification Authority	Let's Encrypt
Validation Type	Not Applicable
Authority Key Identifier	keyid:a3c8265a8ea14cd03563fc9b23c83aae56f34f56
Parent Certificate	http://ye.i.lencr.org/
CRL	http://ye.c.lencr.org/
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	f8158ca8a3a7c5dbd7842218f5d949cec83acdba
SHA256	97658de8c68dfa98ace1e5028a63d54a1aae911b3e21471076c6850cd08cbab4
SPKI SHA256	b3fb5d00e994cddf2cc9a4eea9f806bc5727e83cc0e4299bf956f2d524fe5376

Intermediate certificate

Root YE | 0fc0901
Not After: 02 Sep 2032 23:59:59 UTC (expires in 6 years 22 days)
Authentication: EC 384 bits (SHA384withECDSA)
View details

Subject DN	CN=Root YE, O=ISRG, C=US
Subject Key Identifier	a3c8265a8ea14cd03563fc9b23c83aae56f34f56
Serial	872165fc34b6e5fba8add5b3705fb53a
Not Before	13 May 2026 00:00:00 UTC
Not After	02 Sep 2032 23:59:59 UTC
Validity period	2305 days
Key Usage	keyCertSign, cRLSign
Extended Key Usage	serverAuth
Issuer
Issuer DN	CN=ISRG Root X2, O=Internet Security Research Group, C=US
Certification Authority	Let's Encrypt
Validation Type	Not Applicable
Authority Key Identifier	keyid:7c4296aede4b483bfa92f89e8ccf6d8ba9723795
Parent Certificate	http://x2.i.lencr.org/
CRL	http://x2.c.lencr.org/
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	f37620fc4b1cddd2a3d74b1d5e8db42e244ca006
SHA256	0fc0901cca2bae9e9fdbb02d50d02f1094f7b36672086991b9e897626dc485f0
SPKI SHA256	b0292ae545978e0fbb98abbd94c861605e5b18bb32ed523f50d5b7b5c71d47bc

Intermediate certificate

ISRG Root X2 | ee5f7ab
Not After: 02 Sep 2032 23:59:59 UTC (expires in 6 years 22 days)
Authentication: EC 384 bits (SHA256withRSA)
View details

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

Root certificate

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

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

Analysis

Certificate chain is correct

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

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.turva.dev
TLS-RPT standard version used by this policy indicator.Version	TLSRPTv1
Reporting endpoints specified in the policy.Reporting Endpoints	mailto:info@turva.dev

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://turva.dev/

1

http://turva.dev/

HTTP/1.1 301 Moved Permanently

Date	Tue, 11 Aug 2026 09:52:05 GMT
Content-Type	text/html; charset=UTF-8
Transfer-Encoding	chunked
Connection	keep-alive
Location	https://turva.dev/
X-Content-Type-Options	nosniff
Vary	accept-encoding
Server	cloudflare
CF-RAY	a2965873bc0505d2-IAD
alt-svc	h3=":443"; ma=86400

2

https://turva.dev/

HTTP/1.1 200 OK

Date	Tue, 11 Aug 2026 09:52:05 GMT
Content-Type	text/html; charset=utf-8
Transfer-Encoding	chunked
Connection	keep-alive
Cache-Control	public, max-age=3600
Content-Language	en
Link	</.well-known/api-catalog>; rel="api-catalog"; type="application/linkset+json", </.well-known/ai-catalog.json>; rel="ai-catalog"; type="application/json", </openapi.json>; rel="service-desc"; type="application/json", </llms.txt>; rel="service-doc"; type="text/plain", </llms-full.txt>; rel="service-doc"; type="text/plain"; title="Full content", </.well-known/signatures.json>; rel="signature"; type="application/json", </auth.md>; rel="agent-registration"; type="text/markdown"; title="Agent registration", </.well-known/mcp/server-card.json>; rel="service-meta"; type="application/json", </.well-known/agent-skills/index.json>; rel="agent-skills"; type="application/json", </.well-known/agent-card.json>; rel="service-meta"; type="application/json"; title="A2A Agent Card", </llms.txt>; rel="describedby"; type="text/plain", </sitemap.xml>; rel="sitemap"; type="application/xml", </.well-known/security.txt>; rel="security-txt"; type="text/plain", </.well-known/ai.txt>; rel="ai-policy"; type="text/plain", </robots.txt>; rel="robots"; type="text/plain", <https://www.linkedin.com/in/erikrekola/>; rel="author", </legal>; rel="license", </.well-known/oauth-authorization-server>; rel="oauth-authorization-server"; type="application/json", </.well-known/oauth-protected-resource>; rel="oauth-protected-resource"; type="application/json", </.well-known/ap2>; rel="ap2"; type="application/json", </.well-known/acp>; rel="acp"; type="application/json", </x402>; rel="x402-endpoint"; type="application/json", </.well-known/x402>; rel="x402"; type="application/json", </.well-known/mpp>; rel="mpp"; type="application/json", </.well-known/ucp>; rel="ucp"; type="application/json", </agent/auth/register>; rel="agent-auth-register"; type="application/json", <mailto:info@turva.dev?subject=Quote%20request>; rel="payment"; title="Request a quote", <https://social.turva.dev/@erik>; rel="me", <https://turva.dev/>; rel="alternate"; type="text/markdown"
Strict-Transport-Security	max-age=31536000; includeSubDomains; preload
Vary	Accept, accept-encoding
Content-Security-Policy	default-src 'self'; script-src 'self' 'sha256-MEp7ZMc/8fteHDIEWV9Siram2qVNEBJcTgqp6lEKsJ0='; style-src 'self' 'unsafe-inline' https: data:; img-src 'self' data: blob: https:; font-src 'self' data: https:; connect-src 'self' https: wss:; media-src 'self' https: data:; object-src 'none'; frame-ancestors 'none'; base-uri 'self'; form-action 'self' mailto:; upgrade-insecure-requests
Cross-Origin-Embedder-Policy	unsafe-none
Cross-Origin-Opener-Policy	same-origin
Cross-Origin-Resource-Policy	same-origin
Permissions-Policy	accelerometer=(), ambient-light-sensor=(), autoplay=(), battery=(), camera=(), display-capture=(), document-domain=(), encrypted-media=(), fullscreen=(self), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), midi=(), payment=(), picture-in-picture=(), publickey-credentials-get=(), screen-wake-lock=(), sync-xhr=(), usb=(), web-share=(), xr-spatial-tracking=()
RateLimit-Policy	"default";q=100;w=60
Referrer-Policy	no-referrer
X-Content-Type-Options	nosniff
X-Frame-Options	DENY
X-XSS-Protection	0
Server	cloudflare
CF-RAY	a2965874393b7afc-IAD
alt-svc	h3=":443"; ma=86400

Analysis

HTTP redirects to HTTPS

Good. This plaintext HTTP server redirects to HTTPS.

URL: http://www.turva.dev/

1

http://www.turva.dev/

HTTP/1.1 301 Moved Permanently

Date	Tue, 11 Aug 2026 09:52:05 GMT
Content-Type	text/html; charset=UTF-8
Transfer-Encoding	chunked
Connection	keep-alive
Location	https://www.turva.dev/
X-Content-Type-Options	nosniff
Vary	accept-encoding
Server	cloudflare
CF-RAY	a29658747fb4e5ec-IAD
alt-svc	h3=":443"; ma=86400

2

https://www.turva.dev/

HTTP/1.1 301 Moved Permanently

Date	Tue, 11 Aug 2026 09:52:05 GMT
Content-Type	text/html; charset=UTF-8
Transfer-Encoding	chunked
Connection	keep-alive
Location	https://turva.dev/
Strict-Transport-Security	max-age=31536000; includeSubDomains; preload
X-Content-Type-Options	nosniff
Server	cloudflare
CF-RAY	a2965874e90ad6c4-IAD
alt-svc	h3=":443"; ma=86400

3

https://turva.dev/

HTTP/1.1 200 OK

Date	Tue, 11 Aug 2026 09:52:06 GMT
Content-Type	text/html; charset=utf-8
Transfer-Encoding	chunked
Connection	keep-alive
Cache-Control	public, max-age=3600
Content-Language	en
Link	</.well-known/api-catalog>; rel="api-catalog"; type="application/linkset+json", </.well-known/ai-catalog.json>; rel="ai-catalog"; type="application/json", </openapi.json>; rel="service-desc"; type="application/json", </llms.txt>; rel="service-doc"; type="text/plain", </llms-full.txt>; rel="service-doc"; type="text/plain"; title="Full content", </.well-known/signatures.json>; rel="signature"; type="application/json", </auth.md>; rel="agent-registration"; type="text/markdown"; title="Agent registration", </.well-known/mcp/server-card.json>; rel="service-meta"; type="application/json", </.well-known/agent-skills/index.json>; rel="agent-skills"; type="application/json", </.well-known/agent-card.json>; rel="service-meta"; type="application/json"; title="A2A Agent Card", </llms.txt>; rel="describedby"; type="text/plain", </sitemap.xml>; rel="sitemap"; type="application/xml", </.well-known/security.txt>; rel="security-txt"; type="text/plain", </.well-known/ai.txt>; rel="ai-policy"; type="text/plain", </robots.txt>; rel="robots"; type="text/plain", <https://www.linkedin.com/in/erikrekola/>; rel="author", </legal>; rel="license", </.well-known/oauth-authorization-server>; rel="oauth-authorization-server"; type="application/json", </.well-known/oauth-protected-resource>; rel="oauth-protected-resource"; type="application/json", </.well-known/ap2>; rel="ap2"; type="application/json", </.well-known/acp>; rel="acp"; type="application/json", </x402>; rel="x402-endpoint"; type="application/json", </.well-known/x402>; rel="x402"; type="application/json", </.well-known/mpp>; rel="mpp"; type="application/json", </.well-known/ucp>; rel="ucp"; type="application/json", </agent/auth/register>; rel="agent-auth-register"; type="application/json", <mailto:info@turva.dev?subject=Quote%20request>; rel="payment"; title="Request a quote", <https://social.turva.dev/@erik>; rel="me", <https://turva.dev/>; rel="alternate"; type="text/markdown"
Strict-Transport-Security	max-age=31536000; includeSubDomains; preload
Vary	Accept, accept-encoding
Content-Security-Policy	default-src 'self'; script-src 'self' 'sha256-MEp7ZMc/8fteHDIEWV9Siram2qVNEBJcTgqp6lEKsJ0='; style-src 'self' 'unsafe-inline' https: data:; img-src 'self' data: blob: https:; font-src 'self' data: https:; connect-src 'self' https: wss:; media-src 'self' https: data:; object-src 'none'; frame-ancestors 'none'; base-uri 'self'; form-action 'self' mailto:; upgrade-insecure-requests
Cross-Origin-Embedder-Policy	unsafe-none
Cross-Origin-Opener-Policy	same-origin
Cross-Origin-Resource-Policy	same-origin
Permissions-Policy	accelerometer=(), ambient-light-sensor=(), autoplay=(), battery=(), camera=(), display-capture=(), document-domain=(), encrypted-media=(), fullscreen=(self), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), midi=(), payment=(), picture-in-picture=(), publickey-credentials-get=(), screen-wake-lock=(), sync-xhr=(), usb=(), web-share=(), xr-spatial-tracking=()
RateLimit-Policy	"default";q=100;w=60
Referrer-Policy	no-referrer
X-Content-Type-Options	nosniff
X-Frame-Options	DENY
X-XSS-Protection	0
Server	cloudflare
CF-RAY	a29658754d36202a-IAD
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://turva.dev/

1

https://turva.dev/

HTTP/1.1 200 OK

Date	Tue, 11 Aug 2026 09:52:06 GMT
Content-Type	text/html; charset=utf-8
Transfer-Encoding	chunked
Connection	keep-alive
Cache-Control	public, max-age=3600
Content-Language	en
Link	</.well-known/api-catalog>; rel="api-catalog"; type="application/linkset+json", </.well-known/ai-catalog.json>; rel="ai-catalog"; type="application/json", </openapi.json>; rel="service-desc"; type="application/json", </llms.txt>; rel="service-doc"; type="text/plain", </llms-full.txt>; rel="service-doc"; type="text/plain"; title="Full content", </.well-known/signatures.json>; rel="signature"; type="application/json", </auth.md>; rel="agent-registration"; type="text/markdown"; title="Agent registration", </.well-known/mcp/server-card.json>; rel="service-meta"; type="application/json", </.well-known/agent-skills/index.json>; rel="agent-skills"; type="application/json", </.well-known/agent-card.json>; rel="service-meta"; type="application/json"; title="A2A Agent Card", </llms.txt>; rel="describedby"; type="text/plain", </sitemap.xml>; rel="sitemap"; type="application/xml", </.well-known/security.txt>; rel="security-txt"; type="text/plain", </.well-known/ai.txt>; rel="ai-policy"; type="text/plain", </robots.txt>; rel="robots"; type="text/plain", <https://www.linkedin.com/in/erikrekola/>; rel="author", </legal>; rel="license", </.well-known/oauth-authorization-server>; rel="oauth-authorization-server"; type="application/json", </.well-known/oauth-protected-resource>; rel="oauth-protected-resource"; type="application/json", </.well-known/ap2>; rel="ap2"; type="application/json", </.well-known/acp>; rel="acp"; type="application/json", </x402>; rel="x402-endpoint"; type="application/json", </.well-known/x402>; rel="x402"; type="application/json", </.well-known/mpp>; rel="mpp"; type="application/json", </.well-known/ucp>; rel="ucp"; type="application/json", </agent/auth/register>; rel="agent-auth-register"; type="application/json", <mailto:info@turva.dev?subject=Quote%20request>; rel="payment"; title="Request a quote", <https://social.turva.dev/@erik>; rel="me", <https://turva.dev/>; rel="alternate"; type="text/markdown"
Strict-Transport-Security	max-age=31536000; includeSubDomains; preload
Vary	Accept, accept-encoding
Content-Security-Policy	default-src 'self'; script-src 'self' 'sha256-MEp7ZMc/8fteHDIEWV9Siram2qVNEBJcTgqp6lEKsJ0='; style-src 'self' 'unsafe-inline' https: data:; img-src 'self' data: blob: https:; font-src 'self' data: https:; connect-src 'self' https: wss:; media-src 'self' https: data:; object-src 'none'; frame-ancestors 'none'; base-uri 'self'; form-action 'self' mailto:; upgrade-insecure-requests
Cross-Origin-Embedder-Policy	unsafe-none
Cross-Origin-Opener-Policy	same-origin
Cross-Origin-Resource-Policy	same-origin
Permissions-Policy	accelerometer=(), ambient-light-sensor=(), autoplay=(), battery=(), camera=(), display-capture=(), document-domain=(), encrypted-media=(), fullscreen=(self), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), midi=(), payment=(), picture-in-picture=(), publickey-credentials-get=(), screen-wake-lock=(), sync-xhr=(), usb=(), web-share=(), xr-spatial-tracking=()
RateLimit-Policy	"default";q=100;w=60
Referrer-Policy	no-referrer
X-Content-Type-Options	nosniff
X-Frame-Options	DENY
X-XSS-Protection	0
Server	cloudflare
CF-RAY	a2965875fa957fae-IAD
alt-svc	h3=":443"; ma=86400

URL: https://www.turva.dev/

1

https://www.turva.dev/

HTTP/1.1 301 Moved Permanently

Date	Tue, 11 Aug 2026 09:52:06 GMT
Content-Type	text/html; charset=UTF-8
Transfer-Encoding	chunked
Connection	keep-alive
Location	https://turva.dev/
Strict-Transport-Security	max-age=31536000; includeSubDomains; preload
X-Content-Type-Options	nosniff
Server	cloudflare
CF-RAY	a2965876bda4cd1b-IAD
alt-svc	h3=":443"; ma=86400

2

https://turva.dev/

HTTP/1.1 200 OK

Date	Tue, 11 Aug 2026 09:52:06 GMT
Content-Type	text/html; charset=utf-8
Transfer-Encoding	chunked
Connection	keep-alive
Cache-Control	public, max-age=3600
Content-Language	en
Link	</.well-known/api-catalog>; rel="api-catalog"; type="application/linkset+json", </.well-known/ai-catalog.json>; rel="ai-catalog"; type="application/json", </openapi.json>; rel="service-desc"; type="application/json", </llms.txt>; rel="service-doc"; type="text/plain", </llms-full.txt>; rel="service-doc"; type="text/plain"; title="Full content", </.well-known/signatures.json>; rel="signature"; type="application/json", </auth.md>; rel="agent-registration"; type="text/markdown"; title="Agent registration", </.well-known/mcp/server-card.json>; rel="service-meta"; type="application/json", </.well-known/agent-skills/index.json>; rel="agent-skills"; type="application/json", </.well-known/agent-card.json>; rel="service-meta"; type="application/json"; title="A2A Agent Card", </llms.txt>; rel="describedby"; type="text/plain", </sitemap.xml>; rel="sitemap"; type="application/xml", </.well-known/security.txt>; rel="security-txt"; type="text/plain", </.well-known/ai.txt>; rel="ai-policy"; type="text/plain", </robots.txt>; rel="robots"; type="text/plain", <https://www.linkedin.com/in/erikrekola/>; rel="author", </legal>; rel="license", </.well-known/oauth-authorization-server>; rel="oauth-authorization-server"; type="application/json", </.well-known/oauth-protected-resource>; rel="oauth-protected-resource"; type="application/json", </.well-known/ap2>; rel="ap2"; type="application/json", </.well-known/acp>; rel="acp"; type="application/json", </x402>; rel="x402-endpoint"; type="application/json", </.well-known/x402>; rel="x402"; type="application/json", </.well-known/mpp>; rel="mpp"; type="application/json", </.well-known/ucp>; rel="ucp"; type="application/json", </agent/auth/register>; rel="agent-auth-register"; type="application/json", <mailto:info@turva.dev?subject=Quote%20request>; rel="payment"; title="Request a quote", <https://social.turva.dev/@erik>; rel="me", <https://turva.dev/>; rel="alternate"; type="text/markdown"
Strict-Transport-Security	max-age=31536000; includeSubDomains; preload
Vary	Accept, accept-encoding
Content-Security-Policy	default-src 'self'; script-src 'self' 'sha256-MEp7ZMc/8fteHDIEWV9Siram2qVNEBJcTgqp6lEKsJ0='; style-src 'self' 'unsafe-inline' https: data:; img-src 'self' data: blob: https:; font-src 'self' data: https:; connect-src 'self' https: wss:; media-src 'self' https: data:; object-src 'none'; frame-ancestors 'none'; base-uri 'self'; form-action 'self' mailto:; upgrade-insecure-requests
Cross-Origin-Embedder-Policy	unsafe-none
Cross-Origin-Opener-Policy	same-origin
Cross-Origin-Resource-Policy	same-origin
Permissions-Policy	accelerometer=(), ambient-light-sensor=(), autoplay=(), battery=(), camera=(), display-capture=(), document-domain=(), encrypted-media=(), fullscreen=(self), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), midi=(), payment=(), picture-in-picture=(), publickey-credentials-get=(), screen-wake-lock=(), sync-xhr=(), usb=(), web-share=(), xr-spatial-tracking=()
RateLimit-Policy	"default";q=100;w=60
Referrer-Policy	no-referrer
X-Content-Type-Options	nosniff
X-Frame-Options	DENY
X-XSS-Protection	0
Server	cloudflare
CF-RAY	a29658770ff6200a-IAD
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: turva.dev (2606:4700:20:0:0:0:681a:8c)

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_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_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_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_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits)

Analysis

TLS 1.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.

Only strong suites supported

Excellent. This server supports only strong cipher suites, which use strong authenticated encryption and provide forward secrecy.

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: turva.dev (2606:4700:20:0:0:0:ac43:48d4)

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_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_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_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_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits)

Analysis

TLS 1.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.

Only strong suites supported

Excellent. This server supports only strong cipher suites, which use strong authenticated encryption and provide forward secrecy.

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.turva.dev (2606:4700:20:0:0:0:681a:18c)

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_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_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_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_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits)
Signed Certificate Timestamps	TLS \| 13 Jul 2026 23:05:11 UTC \| Google 'Argon2026h2' log \| Qualified TLS \| 13 Jul 2026 23:05:11 UTC \| Google 'Xenon2026h2' log \| Qualified

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.

Only strong suites supported

Excellent. This server supports only strong cipher suites, which use strong authenticated encryption and provide forward secrecy.

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, TLS

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, TLS

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: turva.dev (2606:4700:20:0:0:0:681a:18c)

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_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_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_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_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits)

Analysis

TLS 1.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.

Only strong suites supported

Excellent. This server supports only strong cipher suites, which use strong authenticated encryption and provide forward secrecy.

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: turva.dev (104.26.1.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_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_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_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_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_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits)

Analysis

TLS 1.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.

Only strong suites supported

Excellent. This server supports only strong cipher suites, which use strong authenticated encryption and provide forward secrecy.

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.turva.dev (2606:4700:20:0:0:0:ac43:48d4)

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_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_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_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_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits)
Signed Certificate Timestamps	TLS \| 13 Jul 2026 23:05:11 UTC \| Google 'Argon2026h2' log \| Qualified TLS \| 13 Jul 2026 23:05:11 UTC \| Google 'Xenon2026h2' log \| Qualified

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.

Only strong suites supported

Excellent. This server supports only strong cipher suites, which use strong authenticated encryption and provide forward secrecy.

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, TLS

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, TLS

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: turva.dev (172.67.72.212)

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_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_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_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_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits)

Analysis

TLS 1.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.

Only strong suites supported

Excellent. This server supports only strong cipher suites, which use strong authenticated encryption and provide forward secrecy.

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.turva.dev (2606:4700:20:0:0:0:681a:8c)

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_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_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_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_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits)
Signed Certificate Timestamps	TLS \| 13 Jul 2026 23:05:11 UTC \| Google 'Argon2026h2' log \| Qualified TLS \| 13 Jul 2026 23:05:11 UTC \| Google 'Xenon2026h2' log \| Qualified

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.

Only strong suites supported

Excellent. This server supports only strong cipher suites, which use strong authenticated encryption and provide forward secrecy.

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, TLS

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, TLS

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.turva.dev (104.26.1.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_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_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_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_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_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits)
Signed Certificate Timestamps	TLS \| 13 Jul 2026 23:05:11 UTC \| Google 'Argon2026h2' log \| Qualified TLS \| 13 Jul 2026 23:05:11 UTC \| Google 'Xenon2026h2' log \| Qualified

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.

Only strong suites supported

Excellent. This server supports only strong cipher suites, which use strong authenticated encryption and provide forward secrecy.

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, TLS

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, TLS

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: turva.dev (104.26.0.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_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_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_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_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_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits)

Analysis

TLS 1.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.

Only strong suites supported

Excellent. This server supports only strong cipher suites, which use strong authenticated encryption and provide forward secrecy.

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.turva.dev (172.67.72.212)

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_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_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_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_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits)
Signed Certificate Timestamps	TLS \| 13 Jul 2026 23:05:11 UTC \| Google 'Argon2026h2' log \| Qualified TLS \| 13 Jul 2026 23:05:11 UTC \| Google 'Xenon2026h2' log \| Qualified

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.

Only strong suites supported

Excellent. This server supports only strong cipher suites, which use strong authenticated encryption and provide forward secrecy.

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, TLS

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, TLS

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.turva.dev (104.26.0.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_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_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_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_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_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits)
Signed Certificate Timestamps	TLS \| 13 Jul 2026 23:05:11 UTC \| Google 'Argon2026h2' log \| Qualified TLS \| 13 Jul 2026 23:05:11 UTC \| Google 'Xenon2026h2' log \| Qualified

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.

Only strong suites supported

Excellent. This server supports only strong cipher suites, which use strong authenticated encryption and provide forward secrecy.

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, TLS

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, TLS

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.turva.dev

Leaf certificate

turva.dev
Issuer: Let's Encrypt
Not Before: 13 Jul 2026 22:06:38 UTC
Not After: 11 Oct 2026 22:06:37 UTC (expires in 2 months 12 hours)
Key: RSA 2048 bits
Signature: SHA256withRSA
View details

Names	*.turva.dev turva.dev
Subject DN	CN=turva.dev
Subject Key Identifier	9f07acde6716393771a6378a051024f10c7278fc
Serial	05cf0c7be15f160b0fadc8f53e47cc625f2d
Not Before	13 Jul 2026 22:06:38 UTC
Not After	11 Oct 2026 22:06:37 UTC
Validity period	90 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth
Must Staple	No
Issuer
Issuer DN	CN=YR1, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:1f2f35be461482cd40b1ae792c5578faf7d468fb
Parent Certificate	http://yr1.i.lencr.org/
CRL	http://yr1.c.lencr.org/46.crl
Certificate Transparency
Signed Certificate Timestamps	13 Jul 2026 23:05:09 UTC \| Google 'Argon2026h2' log \| Qualified 13 Jul 2026 23:05:09 UTC \| Let's Encrypt 'Willow2026h2' \| Qualified
Fingerprints
SHA1	a2a005d9ca515b75bf955fc8f92ba52aa2239a0b
SHA256	c3a182b7d80d5ceefbce9bbfb6e7ab3def5fba934bc0641910f15e6ede44a4ef
SPKI SHA256	99fab762de162fa651db3bbc1a6200ee5b8da223223ee164e63e6f154c5baf39

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

turva.dev | c3a182b
Not After: 11 Oct 2026 22:06:37 UTC (expires in 2 months 12 hours)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Names	*.turva.dev turva.dev
Subject DN	CN=turva.dev
Subject Key Identifier	9f07acde6716393771a6378a051024f10c7278fc
Serial	05cf0c7be15f160b0fadc8f53e47cc625f2d
Not Before	13 Jul 2026 22:06:38 UTC
Not After	11 Oct 2026 22:06:37 UTC
Validity period	90 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth
Must Staple	No
Issuer
Issuer DN	CN=YR1, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:1f2f35be461482cd40b1ae792c5578faf7d468fb
Parent Certificate	http://yr1.i.lencr.org/
CRL	http://yr1.c.lencr.org/46.crl
Certificate Transparency
Signed Certificate Timestamps	13 Jul 2026 23:05:09 UTC \| Google 'Argon2026h2' log \| Qualified 13 Jul 2026 23:05:09 UTC \| Let's Encrypt 'Willow2026h2' \| Qualified
Fingerprints
SHA1	a2a005d9ca515b75bf955fc8f92ba52aa2239a0b
SHA256	c3a182b7d80d5ceefbce9bbfb6e7ab3def5fba934bc0641910f15e6ede44a4ef
SPKI SHA256	99fab762de162fa651db3bbc1a6200ee5b8da223223ee164e63e6f154c5baf39

Intermediate certificate

YR1 | 1394963
Not After: 02 Sep 2028 23:59:59 UTC (expires in 2 years 22 days)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

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

Intermediate certificate

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

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

Root certificate

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

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

Analysis

Certificate chain is correct

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

Certificate: turva.dev

Leaf certificate

turva.dev
Issuer: Google Trust Services LLC
Not Before: 21 Jul 2026 11:46:25 UTC
Not After: 19 Oct 2026 12:46:09 UTC (expires in 2 months 8 days)
Key: RSA 2048 bits
Signature: SHA256withRSA
View details

Names	turva.dev mcp.turva.dev *.mcp.turva.dev
Subject DN	CN=turva.dev
Subject Key Identifier	d7c89091206a4b30a4623ad1f8d6d1804a1bb5dc
Serial	60421b0e4f374d2813fe3ab47d66fbbb
Not Before	21 Jul 2026 11:46:25 UTC
Not After	19 Oct 2026 12:46:09 UTC
Validity period	91 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth
Must Staple	No
Issuer
Issuer DN	CN=WR1, O=Google Trust Services, C=US
Certification Authority	Google Trust Services LLC
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:666949d4de2a9c9103cf890e24b80e30036e882e
Parent Certificate	http://i.pki.goog/wr1.crt
CRL	http://c.pki.goog/wr1/B9cxXyw8AVc.crl
Certificate Transparency
Signed Certificate Timestamps	21 Jul 2026 12:46:27 UTC \| DigiCert 'Sphinx2026h2' \| Qualified 21 Jul 2026 12:46:27 UTC \| Google 'Xenon2026h2' log \| Qualified
Fingerprints
SHA1	aa7d24ce23c229cca3a5236ad71ee2f8d51396bf
SHA256	b3b15aadd2344365e71b07bee58aae999dbee82773bf142978b94f50f133862b
SPKI SHA256	be11e1581fd2fc3f66fccd790074697c3796ae1bf074394bc9e77bdb31dd8366

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

turva.dev | b3b15aa
Not After: 19 Oct 2026 12:46:09 UTC (expires in 2 months 8 days)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Names	turva.dev mcp.turva.dev *.mcp.turva.dev
Subject DN	CN=turva.dev
Subject Key Identifier	d7c89091206a4b30a4623ad1f8d6d1804a1bb5dc
Serial	60421b0e4f374d2813fe3ab47d66fbbb
Not Before	21 Jul 2026 11:46:25 UTC
Not After	19 Oct 2026 12:46:09 UTC
Validity period	91 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth
Must Staple	No
Issuer
Issuer DN	CN=WR1, O=Google Trust Services, C=US
Certification Authority	Google Trust Services LLC
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:666949d4de2a9c9103cf890e24b80e30036e882e
Parent Certificate	http://i.pki.goog/wr1.crt
CRL	http://c.pki.goog/wr1/B9cxXyw8AVc.crl
Certificate Transparency
Signed Certificate Timestamps	21 Jul 2026 12:46:27 UTC \| DigiCert 'Sphinx2026h2' \| Qualified 21 Jul 2026 12:46:27 UTC \| Google 'Xenon2026h2' log \| Qualified
Fingerprints
SHA1	aa7d24ce23c229cca3a5236ad71ee2f8d51396bf
SHA256	b3b15aadd2344365e71b07bee58aae999dbee82773bf142978b94f50f133862b
SPKI SHA256	be11e1581fd2fc3f66fccd790074697c3796ae1bf074394bc9e77bdb31dd8366

Intermediate certificate

WR1 | b10b6f0
Not After: 20 Feb 2029 14:00:00 UTC (expires in 2 years 6 months)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Subject DN	CN=WR1, O=Google Trust Services, C=US
Subject Key Identifier	666949d4de2a9c9103cf890e24b80e30036e882e
Serial	7fd9e2c2d2048a0474b627a26d0868a7
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 R1, O=Google Trust Services LLC, C=US
Certification Authority	Google Trust Services LLC
Validation Type	Not Applicable
Authority Key Identifier	keyid:e4af2b26711a2b4827852f52662ceff08913713e
Parent Certificate	http://i.pki.goog/r1.crt
CRL	http://c.pki.goog/r/r1.crl
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	41f091692f3b70803bd1fd77e92963d113718cd2
SHA256	b10b6f00e609509e8700f6d34687a2bfce38ea05a8fdf1cdc40c3a2a0d0d0e45
SPKI SHA256	c83bbda20db9e4d3791847fe0706bdad3aea150d04c9d674af514287d4dd016e

Intermediate certificate

GTS Root R1 | 3ee0278
Not After: 28 Jan 2028 00:00:42 UTC (expires in 1 year 5 months)
Authentication: RSA 4096 bits (SHA256withRSA)
View details

Subject DN	CN=GTS Root R1, O=Google Trust Services LLC, C=US
Subject Key Identifier	e4af2b26711a2b4827852f52662ceff08913713e
Serial	77bd0d6cdb36f91aea210fc4f058d30d
Not Before	19 Jun 2020 00:00:42 UTC
Not After	28 Jan 2028 00:00:42 UTC
Key Usage	digitalSignature, 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	Not Applicable
Authority Key Identifier	keyid:607b661a450d97ca89502f7d04cd34a8fffcfd4b
Parent Certificate	http://pki.goog/gsr1/gsr1.crt
CRL	http://crl.pki.goog/gsr1/gsr1.crl
OCSP	http://ocsp.pki.goog/gsr1
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	08745487e891c19e3078c1f2a07e452950ef36f6
SHA256	3ee0278df71fa3c125c4cd487f01d774694e6fc57e0cd94c24efd769133918e5
SPKI SHA256	871a9194f4eed5b312ff40c84c1d524aed2f778bbff25f138cf81f680a7adc67

Root certificate

GlobalSign Root CA | ebd4104
Not After: 28 Jan 2028 12:00:00 UTC (expires in 1 year 5 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: www.turva.dev

Leaf certificate

turva.dev
Issuer: Let's Encrypt
Not Before: 13 Jul 2026 22:06:40 UTC
Not After: 11 Oct 2026 22:06:39 UTC (expires in 2 months 12 hours)
Key: EC 256 bits
Signature: SHA384withECDSA
View details

Names	*.turva.dev turva.dev
Subject DN	CN=turva.dev
Subject Key Identifier	78f89ba8032368fbd74cd96dc8840f57d1105751
Serial	05e73645ea5326c1be76934859818879f6bd
Not Before	13 Jul 2026 22:06:40 UTC
Not After	11 Oct 2026 22:06:39 UTC
Validity period	90 days
Key Usage	digitalSignature
Extended Key Usage	serverAuth
Must Staple	No
Issuer
Issuer DN	CN=YE2, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:b959f28ecf22f086d33748ff761418ba82d85587
Parent Certificate	http://ye2.i.lencr.org/
CRL	http://ye2.c.lencr.org/62.crl
Certificate Transparency
Signed Certificate Timestamps	13 Jul 2026 23:05:11 UTC \| Sectigo 'Tiger2026h2' \| Qualified 13 Jul 2026 23:05:11 UTC \| Geomys 'Tuscolo2026h2' \| Qualified
Fingerprints
SHA1	51f57c19987c00bbccf1bbdfa9589b477016189a
SHA256	cc32783df645ec308255cdb78f370c8b9c7bb1d6000e3ecad08d209bf7dcde83
SPKI SHA256	36a4a85c0b98054e56473acddd9cbfa5437f5c3c18d956e4044f55e4bd0ba9a9

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

turva.dev | cc32783
Not After: 11 Oct 2026 22:06:39 UTC (expires in 2 months 12 hours)
Authentication: EC 256 bits (SHA384withECDSA)
View details

Names	*.turva.dev turva.dev
Subject DN	CN=turva.dev
Subject Key Identifier	78f89ba8032368fbd74cd96dc8840f57d1105751
Serial	05e73645ea5326c1be76934859818879f6bd
Not Before	13 Jul 2026 22:06:40 UTC
Not After	11 Oct 2026 22:06:39 UTC
Validity period	90 days
Key Usage	digitalSignature
Extended Key Usage	serverAuth
Must Staple	No
Issuer
Issuer DN	CN=YE2, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:b959f28ecf22f086d33748ff761418ba82d85587
Parent Certificate	http://ye2.i.lencr.org/
CRL	http://ye2.c.lencr.org/62.crl
Certificate Transparency
Signed Certificate Timestamps	13 Jul 2026 23:05:11 UTC \| Sectigo 'Tiger2026h2' \| Qualified 13 Jul 2026 23:05:11 UTC \| Geomys 'Tuscolo2026h2' \| Qualified
Fingerprints
SHA1	51f57c19987c00bbccf1bbdfa9589b477016189a
SHA256	cc32783df645ec308255cdb78f370c8b9c7bb1d6000e3ecad08d209bf7dcde83
SPKI SHA256	36a4a85c0b98054e56473acddd9cbfa5437f5c3c18d956e4044f55e4bd0ba9a9

Intermediate certificate

YE2 | 97658de
Not After: 02 Sep 2028 23:59:59 UTC (expires in 2 years 22 days)
Authentication: EC 384 bits (SHA384withECDSA)
View details

Subject DN	CN=YE2, O=Let's Encrypt, C=US
Subject Key Identifier	b959f28ecf22f086d33748ff761418ba82d85587
Serial	4df3b15dd6c0784c507cd37b58e6f115
Not Before	03 Sep 2025 00:00:00 UTC
Not After	02 Sep 2028 23:59:59 UTC
Validity period	1096 days
Key Usage	digitalSignature, keyCertSign, cRLSign
Extended Key Usage	serverAuth
Issuer
Issuer DN	CN=Root YE, O=ISRG, C=US
Certification Authority	Let's Encrypt
Validation Type	Not Applicable
Authority Key Identifier	keyid:a3c8265a8ea14cd03563fc9b23c83aae56f34f56
Parent Certificate	http://ye.i.lencr.org/
CRL	http://ye.c.lencr.org/
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	f8158ca8a3a7c5dbd7842218f5d949cec83acdba
SHA256	97658de8c68dfa98ace1e5028a63d54a1aae911b3e21471076c6850cd08cbab4
SPKI SHA256	b3fb5d00e994cddf2cc9a4eea9f806bc5727e83cc0e4299bf956f2d524fe5376

Intermediate certificate

Root YE | 0fc0901
Not After: 02 Sep 2032 23:59:59 UTC (expires in 6 years 22 days)
Authentication: EC 384 bits (SHA384withECDSA)
View details

Subject DN	CN=Root YE, O=ISRG, C=US
Subject Key Identifier	a3c8265a8ea14cd03563fc9b23c83aae56f34f56
Serial	872165fc34b6e5fba8add5b3705fb53a
Not Before	13 May 2026 00:00:00 UTC
Not After	02 Sep 2032 23:59:59 UTC
Validity period	2305 days
Key Usage	keyCertSign, cRLSign
Extended Key Usage	serverAuth
Issuer
Issuer DN	CN=ISRG Root X2, O=Internet Security Research Group, C=US
Certification Authority	Let's Encrypt
Validation Type	Not Applicable
Authority Key Identifier	keyid:7c4296aede4b483bfa92f89e8ccf6d8ba9723795
Parent Certificate	http://x2.i.lencr.org/
CRL	http://x2.c.lencr.org/
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	f37620fc4b1cddd2a3d74b1d5e8db42e244ca006
SHA256	0fc0901cca2bae9e9fdbb02d50d02f1094f7b36672086991b9e897626dc485f0
SPKI SHA256	b0292ae545978e0fbb98abbd94c861605e5b18bb32ed523f50d5b7b5c71d47bc

Intermediate certificate

ISRG Root X2 | ee5f7ab
Not After: 02 Sep 2032 23:59:59 UTC (expires in 6 years 22 days)
Authentication: EC 384 bits (SHA256withRSA)
View details

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

Root certificate

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

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

Analysis

Certificate chain is correct

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

Certificate: turva.dev

Leaf certificate

turva.dev
Issuer: Google Trust Services LLC
Not Before: 21 Jul 2026 11:46:47 UTC
Not After: 19 Oct 2026 12:46:33 UTC (expires in 2 months 8 days)
Key: EC 256 bits
Signature: SHA256withECDSA
View details

Names	turva.dev mcp.turva.dev *.mcp.turva.dev
Subject DN	CN=turva.dev
Subject Key Identifier	24c4493bcc08d2a736cccb8e22480df913b17e3f
Serial	90e71a6ccf40327013953d9d29d947b4
Not Before	21 Jul 2026 11:46:47 UTC
Not After	19 Oct 2026 12:46: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/6Xs4idXq35U.crl
Certificate Transparency
Signed Certificate Timestamps	21 Jul 2026 12:46:48 UTC \| Google 'Xenon2026h2' log \| Qualified 21 Jul 2026 12:46:48 UTC \| DigiCert 'Sphinx2026h2' \| Qualified
Fingerprints
SHA1	1133e23fde8012ce9fb59aed481cef8bca26062e
SHA256	b075e33fdfdfa4ec6ff4c8178d6e28ccf3840ba3dbe7a7785b93d45f7644bee9
SPKI SHA256	0afb4a543a7b18bb25eff4785045f43c904671c532cede028aa516a475bb09a6

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

turva.dev | b075e33
Not After: 19 Oct 2026 12:46:33 UTC (expires in 2 months 8 days)
Authentication: EC 256 bits (SHA256withECDSA)
View details

Names	turva.dev mcp.turva.dev *.mcp.turva.dev
Subject DN	CN=turva.dev
Subject Key Identifier	24c4493bcc08d2a736cccb8e22480df913b17e3f
Serial	90e71a6ccf40327013953d9d29d947b4
Not Before	21 Jul 2026 11:46:47 UTC
Not After	19 Oct 2026 12:46: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/6Xs4idXq35U.crl
Certificate Transparency
Signed Certificate Timestamps	21 Jul 2026 12:46:48 UTC \| Google 'Xenon2026h2' log \| Qualified 21 Jul 2026 12:46:48 UTC \| DigiCert 'Sphinx2026h2' \| Qualified
Fingerprints
SHA1	1133e23fde8012ce9fb59aed481cef8bca26062e
SHA256	b075e33fdfdfa4ec6ff4c8178d6e28ccf3840ba3dbe7a7785b93d45f7644bee9
SPKI SHA256	0afb4a543a7b18bb25eff4785045f43c904671c532cede028aa516a475bb09a6

Intermediate certificate

WE1 | 1dfc160
Not After: 20 Feb 2029 14:00:00 UTC (expires in 2 years 6 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 5 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 5 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.

0 script(s)
0 out of 0 are secure

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

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

Encryption of Outbound Links

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

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

Status	Link
Encrypted	https://github.com/...erekola/turva-worker
Encrypted	https://isitagentready.com/
Encrypted	https://isitagentready.com/
Encrypted	https://www.hardenize.com/report/turva.dev
Encrypted	https://internet.nl/site/turva.dev/
Encrypted	https://internet.nl/mail/turva.dev/
Encrypted	https://github.com/...erekola/turva-worker
Encrypted	https://tietopalvelu.ytj.fi/yritys/3600281-7
Encrypted	https://signal.me/
Encrypted	https://www.linkedin.com/in/erikrekola/
Encrypted	https://signal.me/
Encrypted	https://www.linkedin.com/in/erikrekola/
Encrypted	https://social.turva.dev/@erik
Encrypted	https://gravatar.com/erekola
Encrypted	https://github.com/erekola
Encrypted	https://tietopalvelu.ytj.fi/yritys/3600281-7

HTTP Strict Transport Security

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

Test passed

Everything seems to be well configured. Well done.

HSTS Policy Main host

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

Analysis

Policy is valid

OK. Your HSTS policy uses correct syntax.

Long policy age

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

Policy covers subdomains

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

Redirection from HTTP to HTTPS to the same host

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

Policy preloaded

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

Preloaded host: dev; includeSubDomains=true

HSTS Policy Apex host

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

Analysis

Policy is valid

OK. Your HSTS policy uses correct syntax.

Long policy age

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

Policy covers subdomains

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

Preload intent declared

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

Redirection from HTTP to HTTPS to the same host

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

Policy preloaded

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

Preloaded host: dev; includeSubDomains=true

HTTP Public Key Pinning

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

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

Content Security Policy

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

Test passed

Everything seems to be well configured. Well done.

Content-Security-Policy

default-src	'self'
script-src	'self' 'sha256-MEp7ZMc/8fteHDIEWV9Siram2qVNEBJcTgqp6lEKsJ0='
style-src	'self' This parameter shouldn't be used because it reenables insecure behavior that CSP disables by default.'unsafe-inline' https: data:
img-src	'self' data: blob: https:
font-src	'self' data: https:
connect-src	'self' https: wss:
media-src	'self' https: data:
object-src	'none'
frame-ancestors	'none'
base-uri	'self'
form-action	'self' mailto:
upgrade-insecure-requests

Analysis

Mixed content upgraded

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

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.

Analysis

CSP policy detected

Header: Content-Security-Policy

Value: default-src 'self'; script-src 'self' 'sha256-MEp7ZMc/8fteHDIEWV9Siram2qVNEBJcTgqp6lEKsJ0='; style-src 'self' 'unsafe-inline' https: data:; img-src 'self' data: blob: https:; font-src 'self' data: https:; connect-src 'self' https: wss:; media-src 'self' https: data:; object-src 'none'; frame-ancestors 'none'; base-uri 'self'; form-action 'self' mailto:; upgrade-insecure-requests

Location: https://turva.dev/

Subresource Integrity

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

Test passed

Everything seems to be well configured. Well done.

No external scripts
SRI not needed

No external stylesheets
SRI not needed

Analysis

No remote resources

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

Expect CT

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

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

Analysis

Deploy Expect-CT to enable reporting

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

Frame Options

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

Test passed

Everything seems to be well configured. Well done.

Analysis

Header information

Name: X-Frame-Options

Value: DENY

Framing blocked

Good. Your site doesn't allow page framing from any other page.

XSS Protection

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

Test passed

Everything seems to be well configured. Well done.

Analysis

Header information

Name: X-XSS-Protection

Value: 0

Browser XSS protection disabled

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

Content Type Options

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

Test passed

Everything seems to be well configured. Well done.

Analysis

Header information

Name: X-Content-Type-Options

Value: nosniff

Valid configuration

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

Public Report | turva.dev

turva.dev

Domain Name System

Email

WWW

DNS Zone

Nameserver Names

Nameserver Addresses

Start of Authority (SOA) Record

Analysis

Backing DNS Queries

DNS Records

DNS Records

Backing DNS Queries

DNSSEC

Analysis

Useful DNSSEC Tools

Certification Authority Authorization

CAA Policy Information

Analysis

Email (SMTP)

Analysis

Email TLS (SMTP)

TLS Configuration: mxext1.mailbox.org (80.241.60.212)

Analysis

TLS Configuration: mxext2.mailbox.org (80.241.60.215)

Analysis

TLS Configuration: mxext3.mailbox.org (80.241.60.216)

Analysis

TLS Configuration: mxext4.mailbox.org (80.241.60.217)

Analysis

Email Certificates (SMTP)

Certificate #1

Analysis

Certificate Chain

Analysis

Email DANE (SMTP)

DANE: mxext1.mailbox.org (80.241.60.212)

Analysis

DANE: mxext2.mailbox.org (80.241.60.215)

Analysis

DANE: mxext3.mailbox.org (80.241.60.216)

Analysis

DANE: mxext4.mailbox.org (80.241.60.217)

Analysis

SPF

SPF Policy Information Main policy

Analysis

SPF Policy Information Included policy

DMARC

DMARC Policy Information

Analysis

MTA Strict Transport Security

MTA-STS Policy Indicator

Analysis

MTA-STS Policy

Analysis

Certificate: mta-sts.turva.dev

Analysis

Certificate Chain

Analysis

SMTP TLS Reporting

TLS-RPT Policy

Analysis

HTTP (80)

URL: http://turva.dev/

Analysis

URL: http://www.turva.dev/

Analysis

HTTP (443)

URL: https://turva.dev/

URL: https://www.turva.dev/

WWW TLS

TLS Configuration: turva.dev (2606:4700:20:0:0:0:681a:8c)

Analysis

TLS Configuration: turva.dev (2606:4700:20:0:0:0:ac43:48d4)

Analysis

TLS Configuration: www.turva.dev (2606:4700:20:0:0:0:681a:18c)

Analysis

TLS Configuration: turva.dev (2606:4700:20:0:0:0:681a:18c)