Hardenize Report: hardenize.com

Web Security Overview

HTTPS

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

For all sites VERY IMPORTANT medium EFFORT

HTTPS Redirection

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

For all sites VERY IMPORTANT low EFFORT

HTTP Strict Transport Security

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

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
jobs.ns.cloudflare.com. PRIMARY 108.162.193.183 172.64.33.183 173.245.59.183 2606:4700:58::adf5:3bb7 2803:f800:50::6ca2:c1b7 2a06:98c1:50::ac40:21b7				SOA REFERRAL NS
leah.ns.cloudflare.com. 108.162.192.129 172.64.32.129 173.245.58.129 2606:4700:50::adf5:3a81 2803:f800:50::6ca2:c081 2a06:98c1:50::ac40:2081				REFERRAL NS

Nameserver Addresses

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

Nameserver	Sources	Payload Size
108.162.192.129 leah.ns.cloudflare.com. PTR: leah.ns.cloudflare.com.	NAME, GLUE	1232
108.162.193.183 PRIMARY jobs.ns.cloudflare.com. PTR: jobs.ns.cloudflare.com.	NAME, GLUE	1232
172.64.32.129 leah.ns.cloudflare.com. PTR: leah.ns.cloudflare.com.	NAME, GLUE	1232
172.64.33.183 PRIMARY jobs.ns.cloudflare.com. PTR: jobs.ns.cloudflare.com.	NAME, GLUE	1232
173.245.58.129 leah.ns.cloudflare.com. PTR: leah.ns.cloudflare.com.	NAME, GLUE	1232
173.245.59.183 PRIMARY jobs.ns.cloudflare.com. PTR: jobs.ns.cloudflare.com.	NAME, GLUE	1232
2606:4700:50::adf5:3a81 leah.ns.cloudflare.com. PTR: leah.ns.cloudflare.com.	NAME, GLUE	1232
2606:4700:58::adf5:3bb7 PRIMARY jobs.ns.cloudflare.com. PTR: jobs.ns.cloudflare.com.	NAME, GLUE	1232
2803:f800:50::6ca2:c081 leah.ns.cloudflare.com. PTR: leah.ns.cloudflare.com.	NAME, GLUE	1232
2803:f800:50::6ca2:c1b7 PRIMARY jobs.ns.cloudflare.com. PTR: jobs.ns.cloudflare.com.	NAME, GLUE	1232
2a06:98c1:50::ac40:2081 leah.ns.cloudflare.com. PTR: leah.ns.cloudflare.com.	NAME, GLUE	1232
2a06:98c1:50::ac40:21b7 PRIMARY jobs.ns.cloudflare.com. PTR: jobs.ns.cloudflare.com.	NAME, GLUE	1232

Start of Authority (SOA) Record

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

The domain name of the primary nameserver for the zone. Also known as MNAME.Primary nameserver	jobs.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	-1937377240
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
hardenize.com.	300	A	104.17.52.49
hardenize.com.	300	A	104.17.53.49
www.hardenize.com.	300	A	104.17.52.49
www.hardenize.com.	300	A	104.17.53.49
hardenize.com.	300	AAAA	2606:4700:0:0:0:0:6811:3431
hardenize.com.	300	AAAA	2606:4700:0:0:0:0:6811:3531
www.hardenize.com.	300	AAAA	2606:4700:0:0:0:0:6811:3431
www.hardenize.com.	300	AAAA	2606:4700:0:0:0:0:6811:3531
hardenize.com.	300	HTTPS	1 . alpn=h2 ipv4hint=104.17.52.49,104.17.53.49 ipv6hint=2606:4700:0:0:0:0:6811:3431,2606:4700:0:0:0:0:6811:3531
www.hardenize.com.	300	HTTPS	1 . alpn=h2 ipv4hint=104.17.52.49,104.17.53.49 ipv6hint=2606:4700:0:0:0:0:6811:3431,2606:4700:0:0:0:0:6811:3531
hardenize.com.	300	MX	5 alt2.aspmx.l.google.com.
hardenize.com.	300	MX	1 aspmx.l.google.com.
hardenize.com.	300	MX	10 aspmx2.googlemail.com.
hardenize.com.	300	MX	10 aspmx3.googlemail.com.
hardenize.com.	300	MX	5 alt1.aspmx.l.google.com.
hardenize.com.	86400	NS	leah.ns.cloudflare.com.
hardenize.com.	86400	NS	jobs.ns.cloudflare.com.
hardenize.com.	1800	SOA	jobs.ns.cloudflare.com. dns.cloudflare.com. 2357590056 10000 2400 604800 1800
hardenize.com.	300	TXT	"google-site-verification=Wro006IZ-OkEH1b7IpzTTsdDtrVWdUozqYGLAHJK3Ew"
hardenize.com.	300	TXT	"google-site-verification=sIGs5EKTWW6hKGbCmRAo7phRo-NPnqNkP_R2R6sZ27Q"
hardenize.com.	300	TXT	"v=spf1 include:_spf.google.com include:spf.mtasv.net include:mailgun.org ~all"
hardenize.com.	300	TXT	"abuseipdb-verification=35olZFzC"
_dmarc.hardenize.com.	300	TXT	"v=DMARC1; p=reject; pct=100; aspf=r; adkim=r; rua=mailto:6301a309@inbox.ondmarc.com,mailto:sysadmin+dmarc-aggregate@hardenize.com,mailto:re+vr7bygdurs5@dmarc.postmarkapp.com; ruf=mailto:6301a309@inbox.ondmarc.com,mailto:sysadmin+dmarc-forensic@hardenize.c" "om"
_mta-sts.hardenize.com.	300	TXT	"v=STSv1; id=aca9f86d663de32c6663c098f72f1bca;"
_smtp._tls.hardenize.com.	86400	TXT	"v=TLSRPTv1;rua=mailto:sysadmin+tlsrpt@hardenize.com"

Backing DNS Queries

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

	ID	Server	Question Name	Type	Status

DNSSEC

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

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

Useful DNSSEC Tools

Certification Authority Authorization

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

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

Analysis

There is no CAA policy on this domain

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

Email (SMTP)

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

Test passed

Everything seems to be well configured. Well done.

Some TLS and PKI information shown may have been retrieved from cache. The notes provide more information.

Server	Preference	Operational	STARTTLS	TLS	PKI	DNSSEC	DANE
aspmx.l.google.com 2607:f8b0:4004:c17:0:0:0:1a PTR: bl-in-f26.1e100.net	1
aspmx.l.google.com 64.233.180.26 PTR: on-in-f26.1e100.net	1
alt2.aspmx.l.google.com 2a00:1450:400c:c0b:0:0:0:1a PTR: wa-in-f26.1e100.net	5
alt2.aspmx.l.google.com 64.233.184.26 PTR: wa-in-f26.1e100.net	5
alt1.aspmx.l.google.com 2a00:1450:400b:c00:0:0:0:1a PTR: dg-in-x1a.1e100.net	5
alt1.aspmx.l.google.com 209.85.202.27 PTR: dg-in-f27.1e100.net	5
aspmx3.googlemail.com 2a00:1450:400c:c0b:0:0:0:1a PTR: wa-in-f26.1e100.net	10
aspmx3.googlemail.com 64.233.184.26 PTR: wa-in-f26.1e100.net	10
aspmx2.googlemail.com 2a00:1450:400b:c00:0:0:0:1a PTR: dg-in-x1a.1e100.net	10
aspmx2.googlemail.com 209.85.202.27 PTR: dg-in-f27.1e100.net	10

Analysis

Email servers match MTA-STS policy

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

Some SMTP server assessments have been retrieved from cache

Some SMTP server assessment results have been retrieved from our cache. Because many hosts point to the same SMTP servers, we use a short-term cache to avoid testing the same SMTP servers over and over again.

Latest cache timestamp: 25 Nov 2024 21:42 UTC

Earliest cache timestamp: 25 Nov 2024 08:53 UTC

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

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.

Some TLS and PKI information shown may have been retrieved from cache. The notes provide more information.

TLS Configuration: aspmx.l.google.com (2607:f8b0:4004:c17:0:0:0:1a) Cached

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.2
Shows cipher suite configuration for this protocol version.TLS v1.2	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)
These results have been retrieved from our cache. This row indicates when was that the original test ran.Retrieved from cache	25 Nov 2024 19:42 UTC

Analysis

TLS 1.2 supported

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

Strong key exchange detected

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

Partial results shown

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

Relaxed TLS assessment criteria applied to SMTP on port 25

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

TLS Configuration: aspmx.l.google.com (64.233.180.26) Cached

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.2
Shows cipher suite configuration for this protocol version.TLS v1.2	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)
These results have been retrieved from our cache. This row indicates when was that the original test ran.Retrieved from cache	25 Nov 2024 21:42 UTC

Analysis

TLS 1.2 supported

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

Strong key exchange detected

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

Partial results shown

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

Relaxed TLS assessment criteria applied to SMTP on port 25

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

TLS Configuration: alt2.aspmx.l.google.com (2a00:1450:400c:c0b:0:0:0:1a) Cached

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.2
Shows cipher suite configuration for this protocol version.TLS v1.2	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)
These results have been retrieved from our cache. This row indicates when was that the original test ran.Retrieved from cache	25 Nov 2024 09:09 UTC

Analysis

TLS 1.2 supported

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

Strong key exchange detected

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

Partial results shown

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

Relaxed TLS assessment criteria applied to SMTP on port 25

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

TLS Configuration: alt2.aspmx.l.google.com (64.233.184.26) Cached

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.2
Shows cipher suite configuration for this protocol version.TLS v1.2	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)
These results have been retrieved from our cache. This row indicates when was that the original test ran.Retrieved from cache	25 Nov 2024 09:06 UTC

Analysis

TLS 1.2 supported

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

Strong key exchange detected

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

Partial results shown

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

Relaxed TLS assessment criteria applied to SMTP on port 25

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

TLS Configuration: alt1.aspmx.l.google.com (2a00:1450:400b:c00:0:0:0:1a) Cached

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.2
Shows cipher suite configuration for this protocol version.TLS v1.2	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)
These results have been retrieved from our cache. This row indicates when was that the original test ran.Retrieved from cache	25 Nov 2024 10:05 UTC

Analysis

TLS 1.2 supported

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

Strong key exchange detected

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

Partial results shown

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

Relaxed TLS assessment criteria applied to SMTP on port 25

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

TLS Configuration: alt1.aspmx.l.google.com (209.85.202.27) Cached

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.2
Shows cipher suite configuration for this protocol version.TLS v1.2	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)
These results have been retrieved from our cache. This row indicates when was that the original test ran.Retrieved from cache	25 Nov 2024 09:40 UTC

Analysis

TLS 1.2 supported

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

Strong key exchange detected

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

Partial results shown

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

Relaxed TLS assessment criteria applied to SMTP on port 25

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

TLS Configuration: aspmx3.googlemail.com (2a00:1450:400c:c0b:0:0:0:1a) Cached

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.2
Shows cipher suite configuration for this protocol version.TLS v1.2	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)
These results have been retrieved from our cache. This row indicates when was that the original test ran.Retrieved from cache	25 Nov 2024 09:44 UTC

Analysis

TLS 1.2 supported

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

Strong key exchange detected

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

Partial results shown

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

Relaxed TLS assessment criteria applied to SMTP on port 25

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

TLS Configuration: aspmx3.googlemail.com (64.233.184.26) Cached

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.2
Shows cipher suite configuration for this protocol version.TLS v1.2	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)
These results have been retrieved from our cache. This row indicates when was that the original test ran.Retrieved from cache	25 Nov 2024 09:32 UTC

Analysis

TLS 1.2 supported

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

Strong key exchange detected

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

Partial results shown

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

Relaxed TLS assessment criteria applied to SMTP on port 25

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

TLS Configuration: aspmx2.googlemail.com (2a00:1450:400b:c00:0:0:0:1a) Cached

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.2
Shows cipher suite configuration for this protocol version.TLS v1.2	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)
These results have been retrieved from our cache. This row indicates when was that the original test ran.Retrieved from cache	25 Nov 2024 08:53 UTC

Analysis

TLS 1.2 supported

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

Strong key exchange detected

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

Partial results shown

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

Relaxed TLS assessment criteria applied to SMTP on port 25

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

TLS Configuration: aspmx2.googlemail.com (209.85.202.27) Cached

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.2
Shows cipher suite configuration for this protocol version.TLS v1.2	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)
These results have been retrieved from our cache. This row indicates when was that the original test ran.Retrieved from cache	25 Nov 2024 09:59 UTC

Analysis

TLS 1.2 supported

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

Strong key exchange detected

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

Partial results shown

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

Relaxed TLS assessment criteria applied to SMTP on port 25

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

Email Certificates (SMTP)

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

Test passed

Everything seems to be well configured. Well done.

Some TLS and PKI information shown may have been retrieved from cache. The notes provide more information.

Certificate #1 Cached

Leaf certificate

mx.google.com
Issuer: Google Trust Services LLC
Not Before: 21 Oct 2024 08:37:56 UTC
Not After: 13 Jan 2025 08:37:55 UTC (expires in 1 month 17 days)
Key: EC 256 bits
Signature: SHA256withRSA
View details

Names	mx.google.com smtp.google.com aspmx.l.google.com alt1.aspmx.l.google.com alt2.aspmx.l.google.com alt3.aspmx.l.google.com alt4.aspmx.l.google.com gmail-smtp-in.l.google.com alt1.gmail-smtp-in.l.google.com alt2.gmail-smtp-in.l.google.com alt3.gmail-smtp-in.l.google.com alt4.gmail-smtp-in.l.google.com gmr-smtp-in.l.google.com alt1.gmr-smtp-in.l.google.com alt2.gmr-smtp-in.l.google.com alt3.gmr-smtp-in.l.google.com alt4.gmr-smtp-in.l.google.com mx1.smtp.goog mx2.smtp.goog mx3.smtp.goog mx4.smtp.goog aspmx2.googlemail.com aspmx3.googlemail.com aspmx4.googlemail.com aspmx5.googlemail.com gmr-mx.google.com
Subject DN	CN=mx.google.com
Subject Key Identifier	b94918ecb780b657c0cd6f0a401f0941102d01b5
Serial	6c8d0a16e2917a800a93b1fed46bd726
Not Before	21 Oct 2024 08:37:56 UTC
Not After	13 Jan 2025 08:37:55 UTC
Validity period	84 days
Key Usage	digitalSignature
Extended Key Usage	serverAuth
Must Staple	No
Issuer
Issuer DN	CN=WR2, O=Google Trust Services, C=US
Certification Authority	Google Trust Services LLC
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:de1b1eed7915d43e3724c321bbec34396d42b230
Parent Certificate	http://i.pki.goog/wr2.crt
CRL	http://c.pki.goog/wr2/oQ6nyr8F0m0.crl
OCSP	http://o.pki.goog/wr2
Certificate Transparency
Signed Certificate Timestamps	21 Oct 2024 09:37:57 UTC \| Google 'Argon2025h1' log \| Qualified 21 Oct 2024 09:37:57 UTC \| DigiCert Nessie2025 Log \| Qualified
Fingerprints
SHA1	dd979a7e5f359a2daad4ea640021766659231c18
SHA256	53a560478048edf63abdaaa811c9d47c468b157cc72d429e6007b54f51b1cd39
SPKI SHA256	24813faa14d2b379fea412b6ad32a63f851a0e7062f723698b667ff9d4f271dc

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

mx.google.com | 53a5604
Not After: 13 Jan 2025 08:37:55 UTC (expires in 1 month 17 days)
Authentication: EC 256 bits (SHA256withRSA)
View details

Names	mx.google.com smtp.google.com aspmx.l.google.com alt1.aspmx.l.google.com alt2.aspmx.l.google.com alt3.aspmx.l.google.com alt4.aspmx.l.google.com gmail-smtp-in.l.google.com alt1.gmail-smtp-in.l.google.com alt2.gmail-smtp-in.l.google.com alt3.gmail-smtp-in.l.google.com alt4.gmail-smtp-in.l.google.com gmr-smtp-in.l.google.com alt1.gmr-smtp-in.l.google.com alt2.gmr-smtp-in.l.google.com alt3.gmr-smtp-in.l.google.com alt4.gmr-smtp-in.l.google.com mx1.smtp.goog mx2.smtp.goog mx3.smtp.goog mx4.smtp.goog aspmx2.googlemail.com aspmx3.googlemail.com aspmx4.googlemail.com aspmx5.googlemail.com gmr-mx.google.com
Subject DN	CN=mx.google.com
Subject Key Identifier	b94918ecb780b657c0cd6f0a401f0941102d01b5
Serial	6c8d0a16e2917a800a93b1fed46bd726
Not Before	21 Oct 2024 08:37:56 UTC
Not After	13 Jan 2025 08:37:55 UTC
Validity period	84 days
Key Usage	digitalSignature
Extended Key Usage	serverAuth
Must Staple	No
Issuer
Issuer DN	CN=WR2, O=Google Trust Services, C=US
Certification Authority	Google Trust Services LLC
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:de1b1eed7915d43e3724c321bbec34396d42b230
Parent Certificate	http://i.pki.goog/wr2.crt
CRL	http://c.pki.goog/wr2/oQ6nyr8F0m0.crl
OCSP	http://o.pki.goog/wr2
Certificate Transparency
Signed Certificate Timestamps	21 Oct 2024 09:37:57 UTC \| Google 'Argon2025h1' log \| Qualified 21 Oct 2024 09:37:57 UTC \| DigiCert Nessie2025 Log \| Qualified
Fingerprints
SHA1	dd979a7e5f359a2daad4ea640021766659231c18
SHA256	53a560478048edf63abdaaa811c9d47c468b157cc72d429e6007b54f51b1cd39
SPKI SHA256	24813faa14d2b379fea412b6ad32a63f851a0e7062f723698b667ff9d4f271dc

Intermediate certificate

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

Subject DN	CN=WR2, O=Google Trust Services, C=US
Subject Key Identifier	de1b1eed7915d43e3724c321bbec34396d42b230
Serial	7ff005a07c4cded100ad9d66a5107b98
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	66e4161260b100fee0de287a9a5293b4c2224ae6
SHA256	e6fe22bf45e4f0d3b85c59e02c0f495418e1eb8d3210f788d48cd5e1cb547cd4
SPKI SHA256	60fb4769fb4bc3aff4be773606734a185e78c62080dbc58571c723900e32a423

Intermediate certificate

GTS Root R1 | 3ee0278
Not After: 28 Jan 2028 00:00:42 UTC (expires in 3 years 2 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 | b41b2fb
Not After: 28 Jan 2014 12:00:00 UTC (expired 10 years 9 months ago)
Authentication: RSA 2048 bits (MD5withRSA)
View details

Subject DN	CN=GlobalSign Root CA, OU=Root CA, O=GlobalSign nv-sa, C=BE
Subject Key Identifier	607b661a450d97ca89502f7d04cd34a8fffcfd4b
Serial	20000000000d678b79405
Not Before	01 Sep 1998 12:00:00 UTC
Not After	28 Jan 2014 12:00:00 UTC (expired 10 years 9 months ago)
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	2f173f7de99667afa57af80aa2d1b12fac830338
SHA256	b41b2fbfb93eeab3e0fa6b284adb932cdb3766ed4bc7d14837a8f2d9ae874a23
SPKI SHA256	2bcee858158cf5465fc9d76f0dfa312fef25a4dca8501da9b46b67d1fbfa1b64

Analysis

Certificate chain is correct

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

Email DANE (SMTP)

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

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

SPF

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

Test passed

Everything seems to be well configured. Well done.

SPF Policy Information Main policy

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

Analysis

SPF policy found

Policy text: v=spf1 include:_spf.google.com include:spf.mtasv.net include:mailgun.org ~all

Location: hardenize.com

SPF policy is valid

Good. Your SPF policy is syntactically valid.

Policy DNS lookups under limit

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

Lookups: 10

SPF Policy Information Included policy

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

SPF Policy Information Included policy

Host where this policy is located.Location	_netblocks.google.com
SPF version used by this policy.v	spf1
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	35.190.247.0/24
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	64.233.160.0/19
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	66.102.0.0/20
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	66.249.80.0/20
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	72.14.192.0/18
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	74.125.0.0/16
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	108.177.8.0/21
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	173.194.0.0/16
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	209.85.128.0/17
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	216.58.192.0/19
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	216.239.32.0/19
This policy element always matches. It's normally used at the end of a policy to specify the handling of hosts that don't match earlier mechanisms. ~all

SPF Policy Information Included policy

Host where this policy is located.Location	_netblocks2.google.com
SPF version used by this policy.v	spf1
This mechanism tests whether the IP address being tested is contained within a given IPv6 network. ip6	2001:4860:4000::/36
This mechanism tests whether the IP address being tested is contained within a given IPv6 network. ip6	2404:6800:4000::/36
This mechanism tests whether the IP address being tested is contained within a given IPv6 network. ip6	2607:f8b0:4000::/36
This mechanism tests whether the IP address being tested is contained within a given IPv6 network. ip6	2800:3f0:4000::/36
This mechanism tests whether the IP address being tested is contained within a given IPv6 network. ip6	2a00:1450:4000::/36
This mechanism tests whether the IP address being tested is contained within a given IPv6 network. ip6	2c0f:fb50:4000::/36
This policy element always matches. It's normally used at the end of a policy to specify the handling of hosts that don't match earlier mechanisms. ~all

SPF Policy Information Included policy

Host where this policy is located.Location	_netblocks3.google.com
SPF version used by this policy.v	spf1
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	172.217.0.0/19
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	172.217.32.0/20
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	172.217.128.0/19
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	172.217.160.0/20
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	172.217.192.0/19
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	172.253.56.0/21
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	172.253.112.0/20
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	108.177.96.0/19
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	35.191.0.0/16
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	130.211.0.0/22
This policy element always matches. It's normally used at the end of a policy to specify the handling of hosts that don't match earlier mechanisms. ~all

SPF Policy Information Included policy

Host where this policy is located.Location	spf.mtasv.net
SPF version used by this policy.v	spf1
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	50.31.156.96/27
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	104.245.209.192/26
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	50.31.205.0/24
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	147.160.158.0/24
This policy element always matches. It's normally used at the end of a policy to specify the handling of hosts that don't match earlier mechanisms. -all

SPF Policy Information Included policy

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

SPF Policy Information Included policy

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

SPF Policy Information Included policy

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

SPF Policy Information Included policy

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

SPF Policy Information Included policy

Host where this policy is located.Location	_spf.eu.mailgun.org
SPF version used by this policy.v	spf1
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	141.193.32.0/23
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	159.135.140.80/29
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	159.135.132.128/25
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	161.38.204.0/22
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	87.253.232.0/21
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	185.189.236.0/22
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	185.211.120.0/22
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	185.250.236.0/22
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	143.55.236.0/22
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	198.244.60.0/22
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	204.220.160.0/21
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.hardenize.com
DMARC version used by this policy.v	DMARC1
Indicates the policy to be enacted by the receiver at the request of the domain owner. Possible values are: none, quarantine, and reject.p	reject
Percentage of messages from mail stream to which the DMARC policy is to be applied.pct	100
Indicates whether strict or relaxed SPF alignment mode is required.aspf	r
Indicates whether strict or relaxed DKIM alignment mode is required.adkim	r
Addresses to which aggregate feedback is to be sent.rua	mailto:6301a309@inbox.ondmarc.com,mailto:sysadmin+dmarc-aggregate@hardenize.com,mailto:re+vr7bygdurs5@dmarc.postmarkapp.com
Addresses to which message-specific failure information is to be reported.ruf	mailto:6301a309@inbox.ondmarc.com,mailto:sysadmin+dmarc-forensic@hardenize.com

Analysis

DMARC policy found

Policy: v=DMARC1; p=reject; pct=100; aspf=r; adkim=r; rua=mailto:6301a309@inbox.ondmarc.com,mailto:sysadmin+dmarc-aggregate@hardenize.com,mailto:re+vr7bygdurs5@dmarc.postmarkapp.com; ruf=mailto:6301a309@inbox.ondmarc.com,mailto:sysadmin+dmarc-forensic@hardenize.com

Host: _dmarc.hardenize.com

Valid external destination

Permission record location: hardenize.com._report._dmarc.dmarc.postmarkapp.com

External destination: mailto:re+vr7bygdurs5@dmarc.postmarkapp.com

Permission record contents: v=DMARC1;

Valid external destination

Permission record location: hardenize.com._report._dmarc.inbox.ondmarc.com

External destination: mailto:6301a309@inbox.ondmarc.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.hardenize.com
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	aca9f86d663de32c6663c098f72f1bca

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.hardenize.com/.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	86,400 seconds (about 1 day)
Policy mode, which can be one of 'none', 'testing' and 'enforcing'. Guess which is best! :)mode	testing
One 'mx' directive specifies one email server pattern that's allowed for this host.mx	alt1.aspmx.l.google.com
One 'mx' directive specifies one email server pattern that's allowed for this host.mx	alt2.aspmx.l.google.com
One 'mx' directive specifies one email server pattern that's allowed for this host.mx	aspmx.l.google.com
One 'mx' directive specifies one email server pattern that's allowed for this host.mx	aspmx2.googlemail.com
One 'mx' directive specifies one email server pattern that's allowed for this host.mx	aspmx3.googlemail.com

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: 183 bytes

Content-Type: text/plain

Certificate: mta-sts.hardenize.com

Leaf certificate

hardenize.com
Issuer: Google Trust Services LLC
Not Before: 06 Oct 2024 04:32:51 UTC
Not After: 04 Jan 2025 04:32:50 UTC (expires in 1 month 8 days)
Key: EC 256 bits
Signature: SHA256withECDSA
View details

Names	hardenize.com *.hardenize.com
Subject DN	CN=hardenize.com
Subject Key Identifier	eb3dd990860bb4b34cce982a2f754f676cdd1df1
Serial	2908b6a150e07c913d70eb41a2e2b40
Not Before	06 Oct 2024 04:32:51 UTC
Not After	04 Jan 2025 04:32:50 UTC
Validity period	90 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/TgxXJzCQ3Ko.crl
OCSP	http://o.pki.goog/s/we1/ApA
Certificate Transparency
Signed Certificate Timestamps	06 Oct 2024 05:32:51 UTC \| Google 'Xenon2025h1' log \| Qualified 06 Oct 2024 05:32:51 UTC \| DigiCert Nessie2025 Log \| Qualified
Fingerprints
SHA1	19be52bd10a67ea2b07a73326b77dbd4dfc0bb39
SHA256	46ef67b522f7fceb71c27a341e79a6ae6982b6a3f57bd804e0137db6bdf0c4c3
SPKI SHA256	9399d89b35331008f146b74c5686869985c597600c38acf346044870112bf039

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

hardenize.com | 46ef67b
Not After: 04 Jan 2025 04:32:50 UTC (expires in 1 month 8 days)
Authentication: EC 256 bits (SHA256withECDSA)
View details

Names	hardenize.com *.hardenize.com
Subject DN	CN=hardenize.com
Subject Key Identifier	eb3dd990860bb4b34cce982a2f754f676cdd1df1
Serial	2908b6a150e07c913d70eb41a2e2b40
Not Before	06 Oct 2024 04:32:51 UTC
Not After	04 Jan 2025 04:32:50 UTC
Validity period	90 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/TgxXJzCQ3Ko.crl
OCSP	http://o.pki.goog/s/we1/ApA
Certificate Transparency
Signed Certificate Timestamps	06 Oct 2024 05:32:51 UTC \| Google 'Xenon2025h1' log \| Qualified 06 Oct 2024 05:32:51 UTC \| DigiCert Nessie2025 Log \| Qualified
Fingerprints
SHA1	19be52bd10a67ea2b07a73326b77dbd4dfc0bb39
SHA256	46ef67b522f7fceb71c27a341e79a6ae6982b6a3f57bd804e0137db6bdf0c4c3
SPKI SHA256	9399d89b35331008f146b74c5686869985c597600c38acf346044870112bf039

Intermediate certificate

WE1 | 1dfc160
Not After: 20 Feb 2029 14:00:00 UTC (expires in 4 years 2 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 3 years 2 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 | b41b2fb
Not After: 28 Jan 2014 12:00:00 UTC (expired 10 years 9 months ago)
Authentication: RSA 2048 bits (MD5withRSA)
View details

Subject DN	CN=GlobalSign Root CA, OU=Root CA, O=GlobalSign nv-sa, C=BE
Subject Key Identifier	607b661a450d97ca89502f7d04cd34a8fffcfd4b
Serial	20000000000d678b79405
Not Before	01 Sep 1998 12:00:00 UTC
Not After	28 Jan 2014 12:00:00 UTC (expired 10 years 9 months ago)
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	2f173f7de99667afa57af80aa2d1b12fac830338
SHA256	b41b2fbfb93eeab3e0fa6b284adb932cdb3766ed4bc7d14837a8f2d9ae874a23
SPKI SHA256	2bcee858158cf5465fc9d76f0dfa312fef25a4dca8501da9b46b67d1fbfa1b64

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.hardenize.com
TLS-RPT standard version used by this policy indicator.Version	TLSRPTv1
Reporting endpoints specified in the policy.Reporting Endpoints	mailto:sysadmin+tlsrpt@hardenize.com

Analysis

SMTP TLS-RPT policy valid

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

HTTP (80)

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

Test passed

Everything seems to be well configured. Well done.

URL: http://hardenize.com/

1

http://hardenize.com/

HTTP/1.1 301 Moved Permanently

Date	Tue, 26 Nov 2024 12:40:23 GMT
Content-Type	text/html
Content-Length	185
Connection	keep-alive
Location	https://hardenize.com/
CF-Cache-Status	DYNAMIC
Server	cloudflare
CF-RAY	8e89f2585b513b71-IAD

2

https://hardenize.com/

HTTP/1.1 302 Found

Date	Tue, 26 Nov 2024 12:40:23 GMT
Content-Type	text/html
Content-Length	161
Connection	keep-alive
location	https://www.hardenize.com/
strict-transport-security	max-age=31536000; includeSubDomains; preload
expect-ct	max-age=31536000, report-uri="https://h.reporting.hardenize.com"
report-to	{"group": "default", "max_age": 31536000, "endpoints": [{"url": "https://h.reporting.hardenize.com"}], "include_subdomains": true}
nel	{"report_to": "default", "max_age": 31536000, "include_subdomains": true, "success_fraction": 0.05}
CF-Cache-Status	DYNAMIC
Server	cloudflare
CF-RAY	8e89f2590bedd6e3-IAD

3

https://www.hardenize.com/

HTTP/1.1 200 OK

Date	Tue, 26 Nov 2024 12:40:23 GMT
Content-Type	text/html;charset=UTF-8
Transfer-Encoding	chunked
Connection	keep-alive
vary	Accept-Encoding
Cache-Control	private, no-cache, no-store, must-revalidate, max-age=0
x-content-type-options	nosniff
content-security-policy	default-src 'self'; media-src 'self'; img-src 'self' data: blob:; form-action 'self' https://app.redsift.io https://app.redsift.cloud; connect-src 'self' sentry.io https://plausible.io; frame-ancestors https://app.redsift.io https://app.redsift.cloud; frame-src https://www.google.com; object-src 'self'; font-src 'self' data:; script-src 'report-sample' 'self' 'nonce-b4f79e45007ce7f5cee8cd9dfa861002' https://plausible.io; style-src 'self' 'unsafe-inline'; report-uri https://sentry.io/api/1544333/csp-report/?sentry_key=49d512bfcf954f33a5b9c68f30d60783
x-xss-protection	0
Set-Cookie	__Secure-SESSIONID=BB4AE68BCF2C0E281E9306B8109E4520; Path=/; SameSite=Lax; Secure; HttpOnly
strict-transport-security	max-age=31536000; includeSubDomains; preload
expect-ct	max-age=31536000, report-uri="https://h.reporting.hardenize.com"
report-to	{"group": "default", "max_age": 31536000, "endpoints": [{"url": "https://h.reporting.hardenize.com"}], "include_subdomains": true}
nel	{"report_to": "default", "max_age": 31536000, "include_subdomains": true, "success_fraction": 0.05}
CF-Cache-Status	DYNAMIC
Server	cloudflare
CF-RAY	8e89f259af8d8302-IAD

Analysis

HTTP redirects to HTTPS

Good. This plaintext HTTP server redirects to HTTPS.

URL: http://www.hardenize.com/

1

http://www.hardenize.com/

HTTP/1.1 301 Moved Permanently

Date	Tue, 26 Nov 2024 12:40:23 GMT
Content-Type	text/html
Content-Length	185
Connection	keep-alive
Location	https://www.hardenize.com/
CF-Cache-Status	DYNAMIC
Server	cloudflare
CF-RAY	8e89f25a3c2c0800-IAD

2

https://www.hardenize.com/

HTTP/1.1 200 OK

Date	Tue, 26 Nov 2024 12:40:23 GMT
Content-Type	text/html;charset=UTF-8
Transfer-Encoding	chunked
Connection	keep-alive
vary	Accept-Encoding
Cache-Control	private, no-cache, no-store, must-revalidate, max-age=0
x-content-type-options	nosniff
content-security-policy	default-src 'self'; media-src 'self'; img-src 'self' data: blob:; form-action 'self' https://app.redsift.io https://app.redsift.cloud; connect-src 'self' sentry.io https://plausible.io; frame-ancestors https://app.redsift.io https://app.redsift.cloud; frame-src https://www.google.com; object-src 'self'; font-src 'self' data:; script-src 'report-sample' 'self' 'nonce-a392ff6bcc3cc8fde736657d8ad0fc33' https://plausible.io; style-src 'self' 'unsafe-inline'; report-uri https://sentry.io/api/1544333/csp-report/?sentry_key=49d512bfcf954f33a5b9c68f30d60783
x-xss-protection	0
Set-Cookie	__Secure-SESSIONID=526BC7492BD079DBD215BFE8FBE3ED44; Path=/; SameSite=Lax; Secure; HttpOnly
strict-transport-security	max-age=31536000; includeSubDomains; preload
expect-ct	max-age=31536000, report-uri="https://h.reporting.hardenize.com"
report-to	{"group": "default", "max_age": 31536000, "endpoints": [{"url": "https://h.reporting.hardenize.com"}], "include_subdomains": true}
nel	{"report_to": "default", "max_age": 31536000, "include_subdomains": true, "success_fraction": 0.05}
CF-Cache-Status	DYNAMIC
Server	cloudflare
CF-RAY	8e89f25aee263944-IAD

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

1

https://hardenize.com/

HTTP/1.1 302 Found

Date	Tue, 26 Nov 2024 12:40:23 GMT
Content-Type	text/html
Content-Length	161
Connection	keep-alive
location	https://www.hardenize.com/
strict-transport-security	max-age=31536000; includeSubDomains; preload
expect-ct	max-age=31536000, report-uri="https://h.reporting.hardenize.com"
report-to	{"group": "default", "max_age": 31536000, "endpoints": [{"url": "https://h.reporting.hardenize.com"}], "include_subdomains": true}
nel	{"report_to": "default", "max_age": 31536000, "include_subdomains": true, "success_fraction": 0.05}
CF-Cache-Status	DYNAMIC
Server	cloudflare
CF-RAY	8e89f25bdc885986-IAD

2

https://www.hardenize.com/

HTTP/1.1 200 OK

Date	Tue, 26 Nov 2024 12:40:23 GMT
Content-Type	text/html;charset=UTF-8
Transfer-Encoding	chunked
Connection	keep-alive
vary	Accept-Encoding
Cache-Control	private, no-cache, no-store, must-revalidate, max-age=0
x-content-type-options	nosniff
content-security-policy	default-src 'self'; media-src 'self'; img-src 'self' data: blob:; form-action 'self' https://app.redsift.io https://app.redsift.cloud; connect-src 'self' sentry.io https://plausible.io; frame-ancestors https://app.redsift.io https://app.redsift.cloud; frame-src https://www.google.com; object-src 'self'; font-src 'self' data:; script-src 'report-sample' 'self' 'nonce-18c3f521520965e8459f5bc1c1d801de' https://plausible.io; style-src 'self' 'unsafe-inline'; report-uri https://sentry.io/api/1544333/csp-report/?sentry_key=49d512bfcf954f33a5b9c68f30d60783
x-xss-protection	0
Set-Cookie	__Secure-SESSIONID=EE2706D431CAC725F442A057B9F588A1; Path=/; SameSite=Lax; Secure; HttpOnly
strict-transport-security	max-age=31536000; includeSubDomains; preload
expect-ct	max-age=31536000, report-uri="https://h.reporting.hardenize.com"
report-to	{"group": "default", "max_age": 31536000, "endpoints": [{"url": "https://h.reporting.hardenize.com"}], "include_subdomains": true}
nel	{"report_to": "default", "max_age": 31536000, "include_subdomains": true, "success_fraction": 0.05}
CF-Cache-Status	DYNAMIC
Server	cloudflare
CF-RAY	8e89f25c6f47c9ad-IAD

URL: https://www.hardenize.com/

1

https://www.hardenize.com/

HTTP/1.1 200 OK

Date	Tue, 26 Nov 2024 12:40:24 GMT
Content-Type	text/html;charset=UTF-8
Transfer-Encoding	chunked
Connection	keep-alive
vary	Accept-Encoding
Cache-Control	private, no-cache, no-store, must-revalidate, max-age=0
x-content-type-options	nosniff
content-security-policy	default-src 'self'; media-src 'self'; img-src 'self' data: blob:; form-action 'self' https://app.redsift.io https://app.redsift.cloud; connect-src 'self' sentry.io https://plausible.io; frame-ancestors https://app.redsift.io https://app.redsift.cloud; frame-src https://www.google.com; object-src 'self'; font-src 'self' data:; script-src 'report-sample' 'self' 'nonce-d413783584b373a656e01107dbcf76f4' https://plausible.io; style-src 'self' 'unsafe-inline'; report-uri https://sentry.io/api/1544333/csp-report/?sentry_key=49d512bfcf954f33a5b9c68f30d60783
x-xss-protection	0
Set-Cookie	__Secure-SESSIONID=9DE4D669E35CB5136E5CE6C52DF196E4; Path=/; SameSite=Lax; Secure; HttpOnly
strict-transport-security	max-age=31536000; includeSubDomains; preload
expect-ct	max-age=31536000, report-uri="https://h.reporting.hardenize.com"
report-to	{"group": "default", "max_age": 31536000, "endpoints": [{"url": "https://h.reporting.hardenize.com"}], "include_subdomains": true}
nel	{"report_to": "default", "max_age": 31536000, "include_subdomains": true, "success_fraction": 0.05}
CF-Cache-Status	DYNAMIC
Server	cloudflare
CF-RAY	8e89f25dbe3e2d10-IAD

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: hardenize.com (2606:4700:0:0:0:0:6811:3531)

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: DH Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (DHE 768 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: DH Forward secrecy: Yes PRF: SHA256 TLS_AES_128_GCM_SHA256 128 bits (DHE 768 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: DH Forward secrecy: Yes PRF: SHA384 TLS_AES_256_GCM_SHA384 256 bits (DHE 768 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2 Server preference	Suite: TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca9 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02b Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA Suite ID: 0xc009 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc02c Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA Suite ID: 0xc00a Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 Suite ID: 0xc023 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 Suite ID: 0xc024 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA Suite ID: 0xc013 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0x9c Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_128_GCM_SHA256 128 bits Suite: TLS_RSA_WITH_AES_128_CBC_SHA Suite ID: 0x2f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_128_CBC_SHA 128 bits Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA Suite ID: 0xc014 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA 256 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0x9d Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA384 TLS_RSA_WITH_AES_256_GCM_SHA384 256 bits Suite: TLS_RSA_WITH_AES_256_CBC_SHA Suite ID: 0x35 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_256_CBC_SHA 256 bits Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 Suite ID: 0xc027 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_128_CBC_SHA256 Suite ID: 0x3c Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_128_CBC_SHA256 128 bits Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 Suite ID: 0xc028 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_256_CBC_SHA256 Suite ID: 0x3d Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_256_CBC_SHA256 256 bits

Analysis

TLS 1.3 supported

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

TLS 1.2 supported

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

Deprecated protocols not supported

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

Strong key exchange detected

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

Server prefers forward secrecy and authenticated encryption suites

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

Server enforces cipher suite preferences

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

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

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

SCT transports: CERT

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

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

SCT transports: CERT

Post-quantum key exchange supported

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

Algorithm: X25519MLKEM768

DHE suites not supported

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

TLS Configuration: hardenize.com (104.17.52.49)

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: DH Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (DHE 768 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: DH Forward secrecy: Yes PRF: SHA256 TLS_AES_128_GCM_SHA256 128 bits (DHE 768 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: DH Forward secrecy: Yes PRF: SHA384 TLS_AES_256_GCM_SHA384 256 bits (DHE 768 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2 Server preference	Suite: TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca9 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02b Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA Suite ID: 0xc009 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc02c Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA Suite ID: 0xc00a Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 Suite ID: 0xc023 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 Suite ID: 0xc024 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA Suite ID: 0xc013 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0x9c Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_128_GCM_SHA256 128 bits Suite: TLS_RSA_WITH_AES_128_CBC_SHA Suite ID: 0x2f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_128_CBC_SHA 128 bits Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA Suite ID: 0xc014 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA 256 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0x9d Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA384 TLS_RSA_WITH_AES_256_GCM_SHA384 256 bits Suite: TLS_RSA_WITH_AES_256_CBC_SHA Suite ID: 0x35 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_256_CBC_SHA 256 bits Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 Suite ID: 0xc027 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_128_CBC_SHA256 Suite ID: 0x3c Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_128_CBC_SHA256 128 bits Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 Suite ID: 0xc028 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_256_CBC_SHA256 Suite ID: 0x3d Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_256_CBC_SHA256 256 bits

Analysis

TLS 1.3 supported

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

TLS 1.2 supported

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

Deprecated protocols not supported

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

Strong key exchange detected

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

Server prefers forward secrecy and authenticated encryption suites

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

Server enforces cipher suite preferences

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

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

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

SCT transports: CERT

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

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

SCT transports: CERT

Post-quantum key exchange supported

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

Algorithm: X25519MLKEM768

DHE suites not supported

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

TLS Configuration: www.hardenize.com (2606:4700:0:0:0:0:6811:3531)

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: DH Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (DHE 768 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: DH Forward secrecy: Yes PRF: SHA256 TLS_AES_128_GCM_SHA256 128 bits (DHE 768 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: DH Forward secrecy: Yes PRF: SHA384 TLS_AES_256_GCM_SHA384 256 bits (DHE 768 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2 Server preference	Suite: TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca9 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02b Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA Suite ID: 0xc009 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc02c Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA Suite ID: 0xc00a Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 Suite ID: 0xc023 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 Suite ID: 0xc024 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA Suite ID: 0xc013 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0x9c Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_128_GCM_SHA256 128 bits Suite: TLS_RSA_WITH_AES_128_CBC_SHA Suite ID: 0x2f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_128_CBC_SHA 128 bits Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA Suite ID: 0xc014 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA 256 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0x9d Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA384 TLS_RSA_WITH_AES_256_GCM_SHA384 256 bits Suite: TLS_RSA_WITH_AES_256_CBC_SHA Suite ID: 0x35 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_256_CBC_SHA 256 bits Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 Suite ID: 0xc027 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_128_CBC_SHA256 Suite ID: 0x3c Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_128_CBC_SHA256 128 bits Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 Suite ID: 0xc028 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_256_CBC_SHA256 Suite ID: 0x3d Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_256_CBC_SHA256 256 bits

Analysis

TLS 1.3 supported

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

TLS 1.2 supported

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

Deprecated protocols not supported

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

Strong key exchange detected

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

Server prefers forward secrecy and authenticated encryption suites

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

Server enforces cipher suite preferences

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

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

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

SCT transports: CERT

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

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

SCT transports: CERT

Post-quantum key exchange supported

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

Algorithm: X25519MLKEM768

DHE suites not supported

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

TLS Configuration: hardenize.com (104.17.53.49)

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: DH Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (DHE 768 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: DH Forward secrecy: Yes PRF: SHA256 TLS_AES_128_GCM_SHA256 128 bits (DHE 768 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: DH Forward secrecy: Yes PRF: SHA384 TLS_AES_256_GCM_SHA384 256 bits (DHE 768 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2 Server preference	Suite: TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca9 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02b Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA Suite ID: 0xc009 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc02c Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA Suite ID: 0xc00a Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 Suite ID: 0xc023 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 Suite ID: 0xc024 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA Suite ID: 0xc013 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0x9c Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_128_GCM_SHA256 128 bits Suite: TLS_RSA_WITH_AES_128_CBC_SHA Suite ID: 0x2f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_128_CBC_SHA 128 bits Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA Suite ID: 0xc014 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA 256 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0x9d Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA384 TLS_RSA_WITH_AES_256_GCM_SHA384 256 bits Suite: TLS_RSA_WITH_AES_256_CBC_SHA Suite ID: 0x35 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_256_CBC_SHA 256 bits Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 Suite ID: 0xc027 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_128_CBC_SHA256 Suite ID: 0x3c Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_128_CBC_SHA256 128 bits Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 Suite ID: 0xc028 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_256_CBC_SHA256 Suite ID: 0x3d Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_256_CBC_SHA256 256 bits

Analysis

TLS 1.3 supported

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

TLS 1.2 supported

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

Deprecated protocols not supported

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

Strong key exchange detected

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

Server prefers forward secrecy and authenticated encryption suites

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

Server enforces cipher suite preferences

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

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

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

SCT transports: CERT

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

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

SCT transports: CERT

Post-quantum key exchange supported

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

Algorithm: X25519MLKEM768

DHE suites not supported

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

TLS Configuration: www.hardenize.com (2606:4700:0:0:0:0:6811:3431)

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: DH Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (DHE 768 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: DH Forward secrecy: Yes PRF: SHA256 TLS_AES_128_GCM_SHA256 128 bits (DHE 768 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: DH Forward secrecy: Yes PRF: SHA384 TLS_AES_256_GCM_SHA384 256 bits (DHE 768 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2 Server preference	Suite: TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca9 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02b Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA Suite ID: 0xc009 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc02c Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA Suite ID: 0xc00a Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 Suite ID: 0xc023 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 Suite ID: 0xc024 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA Suite ID: 0xc013 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0x9c Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_128_GCM_SHA256 128 bits Suite: TLS_RSA_WITH_AES_128_CBC_SHA Suite ID: 0x2f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_128_CBC_SHA 128 bits Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA Suite ID: 0xc014 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA 256 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0x9d Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA384 TLS_RSA_WITH_AES_256_GCM_SHA384 256 bits Suite: TLS_RSA_WITH_AES_256_CBC_SHA Suite ID: 0x35 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_256_CBC_SHA 256 bits Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 Suite ID: 0xc027 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_128_CBC_SHA256 Suite ID: 0x3c Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_128_CBC_SHA256 128 bits Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 Suite ID: 0xc028 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_256_CBC_SHA256 Suite ID: 0x3d Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_256_CBC_SHA256 256 bits

Analysis

TLS 1.3 supported

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

TLS 1.2 supported

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

Deprecated protocols not supported

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

Strong key exchange detected

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

Server prefers forward secrecy and authenticated encryption suites

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

Server enforces cipher suite preferences

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

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

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

SCT transports: CERT

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

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

SCT transports: CERT

Post-quantum key exchange supported

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

Algorithm: X25519MLKEM768

DHE suites not supported

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

TLS Configuration: www.hardenize.com (104.17.52.49)

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: DH Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (DHE 768 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: DH Forward secrecy: Yes PRF: SHA256 TLS_AES_128_GCM_SHA256 128 bits (DHE 768 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: DH Forward secrecy: Yes PRF: SHA384 TLS_AES_256_GCM_SHA384 256 bits (DHE 768 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2 Server preference	Suite: TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca9 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02b Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA Suite ID: 0xc009 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc02c Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA Suite ID: 0xc00a Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 Suite ID: 0xc023 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 Suite ID: 0xc024 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA Suite ID: 0xc013 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0x9c Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_128_GCM_SHA256 128 bits Suite: TLS_RSA_WITH_AES_128_CBC_SHA Suite ID: 0x2f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_128_CBC_SHA 128 bits Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA Suite ID: 0xc014 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA 256 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0x9d Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA384 TLS_RSA_WITH_AES_256_GCM_SHA384 256 bits Suite: TLS_RSA_WITH_AES_256_CBC_SHA Suite ID: 0x35 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_256_CBC_SHA 256 bits Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 Suite ID: 0xc027 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_128_CBC_SHA256 Suite ID: 0x3c Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_128_CBC_SHA256 128 bits Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 Suite ID: 0xc028 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_256_CBC_SHA256 Suite ID: 0x3d Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_256_CBC_SHA256 256 bits

Analysis

TLS 1.3 supported

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

TLS 1.2 supported

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

Deprecated protocols not supported

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

Strong key exchange detected

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

Server prefers forward secrecy and authenticated encryption suites

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

Server enforces cipher suite preferences

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

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

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

SCT transports: CERT

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

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

SCT transports: CERT

Post-quantum key exchange supported

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

Algorithm: X25519MLKEM768

DHE suites not supported

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

TLS Configuration: hardenize.com (2606:4700:0:0:0:0:6811:3431)

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: DH Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (DHE 768 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: DH Forward secrecy: Yes PRF: SHA256 TLS_AES_128_GCM_SHA256 128 bits (DHE 768 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: DH Forward secrecy: Yes PRF: SHA384 TLS_AES_256_GCM_SHA384 256 bits (DHE 768 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2 Server preference	Suite: TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca9 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02b Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA Suite ID: 0xc009 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc02c Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA Suite ID: 0xc00a Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 Suite ID: 0xc023 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 Suite ID: 0xc024 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA Suite ID: 0xc013 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0x9c Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_128_GCM_SHA256 128 bits Suite: TLS_RSA_WITH_AES_128_CBC_SHA Suite ID: 0x2f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_128_CBC_SHA 128 bits Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA Suite ID: 0xc014 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA 256 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0x9d Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA384 TLS_RSA_WITH_AES_256_GCM_SHA384 256 bits Suite: TLS_RSA_WITH_AES_256_CBC_SHA Suite ID: 0x35 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_256_CBC_SHA 256 bits Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 Suite ID: 0xc027 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_128_CBC_SHA256 Suite ID: 0x3c Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_128_CBC_SHA256 128 bits Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 Suite ID: 0xc028 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_256_CBC_SHA256 Suite ID: 0x3d Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_256_CBC_SHA256 256 bits

Analysis

TLS 1.3 supported

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

TLS 1.2 supported

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

Deprecated protocols not supported

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

Strong key exchange detected

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

Server prefers forward secrecy and authenticated encryption suites

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

Server enforces cipher suite preferences

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

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

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

SCT transports: CERT

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

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

SCT transports: CERT

Post-quantum key exchange supported

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

Algorithm: X25519MLKEM768

DHE suites not supported

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

TLS Configuration: www.hardenize.com (104.17.53.49)

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: DH Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (DHE 768 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: DH Forward secrecy: Yes PRF: SHA256 TLS_AES_128_GCM_SHA256 128 bits (DHE 768 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: DH Forward secrecy: Yes PRF: SHA384 TLS_AES_256_GCM_SHA384 256 bits (DHE 768 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2 Server preference	Suite: TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca9 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02b Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA Suite ID: 0xc009 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc02c Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA Suite ID: 0xc00a Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 Suite ID: 0xc023 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 Suite ID: 0xc024 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_ECDSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA Suite ID: 0xc013 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0x9c Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_128_GCM_SHA256 128 bits Suite: TLS_RSA_WITH_AES_128_CBC_SHA Suite ID: 0x2f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_128_CBC_SHA 128 bits Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA Suite ID: 0xc014 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA 256 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0x9d Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA384 TLS_RSA_WITH_AES_256_GCM_SHA384 256 bits Suite: TLS_RSA_WITH_AES_256_CBC_SHA Suite ID: 0x35 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_AES_256_CBC_SHA 256 bits Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 Suite ID: 0xc027 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_128_CBC_SHA256 Suite ID: 0x3c Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_128_CBC_SHA256 128 bits Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 Suite ID: 0xc028 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_256_CBC_SHA256 Suite ID: 0x3d Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_256_CBC_SHA256 256 bits

Analysis

TLS 1.3 supported

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

TLS 1.2 supported

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

Deprecated protocols not supported

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

Strong key exchange detected

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

Server prefers forward secrecy and authenticated encryption suites

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

Server enforces cipher suite preferences

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

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

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

SCT transports: CERT

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

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

SCT transports: CERT

Post-quantum key exchange supported

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

Algorithm: X25519MLKEM768

DHE suites not supported

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

WWW Certificates

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

Test passed

Everything seems to be well configured. Well done.

Certificate: hardenize.com

Leaf certificate

hardenize.com
Issuer: Google Trust Services LLC
Not Before: 06 Oct 2024 04:32:51 UTC
Not After: 04 Jan 2025 04:32:50 UTC (expires in 1 month 8 days)
Key: EC 256 bits
Signature: SHA256withECDSA
View details

Names	hardenize.com *.hardenize.com
Subject DN	CN=hardenize.com
Subject Key Identifier	eb3dd990860bb4b34cce982a2f754f676cdd1df1
Serial	2908b6a150e07c913d70eb41a2e2b40
Not Before	06 Oct 2024 04:32:51 UTC
Not After	04 Jan 2025 04:32:50 UTC
Validity period	90 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/TgxXJzCQ3Ko.crl
OCSP	http://o.pki.goog/s/we1/ApA
Certificate Transparency
Signed Certificate Timestamps	06 Oct 2024 05:32:51 UTC \| Google 'Xenon2025h1' log \| Qualified 06 Oct 2024 05:32:51 UTC \| DigiCert Nessie2025 Log \| Qualified
Fingerprints
SHA1	19be52bd10a67ea2b07a73326b77dbd4dfc0bb39
SHA256	46ef67b522f7fceb71c27a341e79a6ae6982b6a3f57bd804e0137db6bdf0c4c3
SPKI SHA256	9399d89b35331008f146b74c5686869985c597600c38acf346044870112bf039

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

hardenize.com | 46ef67b
Not After: 04 Jan 2025 04:32:50 UTC (expires in 1 month 8 days)
Authentication: EC 256 bits (SHA256withECDSA)
View details

Names	hardenize.com *.hardenize.com
Subject DN	CN=hardenize.com
Subject Key Identifier	eb3dd990860bb4b34cce982a2f754f676cdd1df1
Serial	2908b6a150e07c913d70eb41a2e2b40
Not Before	06 Oct 2024 04:32:51 UTC
Not After	04 Jan 2025 04:32:50 UTC
Validity period	90 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/TgxXJzCQ3Ko.crl
OCSP	http://o.pki.goog/s/we1/ApA
Certificate Transparency
Signed Certificate Timestamps	06 Oct 2024 05:32:51 UTC \| Google 'Xenon2025h1' log \| Qualified 06 Oct 2024 05:32:51 UTC \| DigiCert Nessie2025 Log \| Qualified
Fingerprints
SHA1	19be52bd10a67ea2b07a73326b77dbd4dfc0bb39
SHA256	46ef67b522f7fceb71c27a341e79a6ae6982b6a3f57bd804e0137db6bdf0c4c3
SPKI SHA256	9399d89b35331008f146b74c5686869985c597600c38acf346044870112bf039

Intermediate certificate

WE1 | 1dfc160
Not After: 20 Feb 2029 14:00:00 UTC (expires in 4 years 2 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 3 years 2 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 | b41b2fb
Not After: 28 Jan 2014 12:00:00 UTC (expired 10 years 9 months ago)
Authentication: RSA 2048 bits (MD5withRSA)
View details

Subject DN	CN=GlobalSign Root CA, OU=Root CA, O=GlobalSign nv-sa, C=BE
Subject Key Identifier	607b661a450d97ca89502f7d04cd34a8fffcfd4b
Serial	20000000000d678b79405
Not Before	01 Sep 1998 12:00:00 UTC
Not After	28 Jan 2014 12:00:00 UTC (expired 10 years 9 months ago)
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	2f173f7de99667afa57af80aa2d1b12fac830338
SHA256	b41b2fbfb93eeab3e0fa6b284adb932cdb3766ed4bc7d14837a8f2d9ae874a23
SPKI SHA256	2bcee858158cf5465fc9d76f0dfa312fef25a4dca8501da9b46b67d1fbfa1b64

Analysis

Certificate chain is correct

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

Certificate: hardenize.com

Leaf certificate

hardenize.com
Issuer: Google Trust Services LLC
Not Before: 06 Oct 2024 04:32:43 UTC
Not After: 04 Jan 2025 04:32:42 UTC (expires in 1 month 8 days)
Key: RSA 2048 bits
Signature: SHA256withRSA
View details

Names	hardenize.com *.hardenize.com
Subject DN	CN=hardenize.com
Subject Key Identifier	df32b5314023a0fcbff010ea0352eadc44a28093
Serial	a172756b5672cba3132c79d8be13f9ea
Not Before	06 Oct 2024 04:32:43 UTC
Not After	04 Jan 2025 04:32:42 UTC
Validity period	90 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/brD8Lo8p_3U.crl
OCSP	http://o.pki.goog/s/wr1/oXI
Certificate Transparency
Signed Certificate Timestamps	06 Oct 2024 05:32:44 UTC \| Google 'Xenon2025h1' log \| Qualified 06 Oct 2024 05:32:45 UTC \| Cloudflare 'Nimbus2025' \| Qualified
Fingerprints
SHA1	e1d5ab7da40d0a031eda3ae14e43fb764bbbcaa1
SHA256	df3d573c94ce046e601cf8425150c382a6f267e489201c6f891637692bb8923f
SPKI SHA256	b074f6d7138f34cd48af9ca4b7fba4c4bd0be36b2ed72d9773280dd9a317a55a

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

hardenize.com | df3d573
Not After: 04 Jan 2025 04:32:42 UTC (expires in 1 month 8 days)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Names	hardenize.com *.hardenize.com
Subject DN	CN=hardenize.com
Subject Key Identifier	df32b5314023a0fcbff010ea0352eadc44a28093
Serial	a172756b5672cba3132c79d8be13f9ea
Not Before	06 Oct 2024 04:32:43 UTC
Not After	04 Jan 2025 04:32:42 UTC
Validity period	90 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/brD8Lo8p_3U.crl
OCSP	http://o.pki.goog/s/wr1/oXI
Certificate Transparency
Signed Certificate Timestamps	06 Oct 2024 05:32:44 UTC \| Google 'Xenon2025h1' log \| Qualified 06 Oct 2024 05:32:45 UTC \| Cloudflare 'Nimbus2025' \| Qualified
Fingerprints
SHA1	e1d5ab7da40d0a031eda3ae14e43fb764bbbcaa1
SHA256	df3d573c94ce046e601cf8425150c382a6f267e489201c6f891637692bb8923f
SPKI SHA256	b074f6d7138f34cd48af9ca4b7fba4c4bd0be36b2ed72d9773280dd9a317a55a

Intermediate certificate

WR1 | b10b6f0
Not After: 20 Feb 2029 14:00:00 UTC (expires in 4 years 2 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 3 years 2 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 | b41b2fb
Not After: 28 Jan 2014 12:00:00 UTC (expired 10 years 9 months ago)
Authentication: RSA 2048 bits (MD5withRSA)
View details

Subject DN	CN=GlobalSign Root CA, OU=Root CA, O=GlobalSign nv-sa, C=BE
Subject Key Identifier	607b661a450d97ca89502f7d04cd34a8fffcfd4b
Serial	20000000000d678b79405
Not Before	01 Sep 1998 12:00:00 UTC
Not After	28 Jan 2014 12:00:00 UTC (expired 10 years 9 months ago)
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	2f173f7de99667afa57af80aa2d1b12fac830338
SHA256	b41b2fbfb93eeab3e0fa6b284adb932cdb3766ed4bc7d14837a8f2d9ae874a23
SPKI SHA256	2bcee858158cf5465fc9d76f0dfa312fef25a4dca8501da9b46b67d1fbfa1b64

Analysis

Certificate chain is correct

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

Certificate: www.hardenize.com

Leaf certificate

hardenize.com
Issuer: Google Trust Services LLC
Not Before: 06 Oct 2024 04:32:43 UTC
Not After: 04 Jan 2025 04:32:42 UTC (expires in 1 month 8 days)
Key: RSA 2048 bits
Signature: SHA256withRSA
View details

Names	hardenize.com *.hardenize.com
Subject DN	CN=hardenize.com
Subject Key Identifier	df32b5314023a0fcbff010ea0352eadc44a28093
Serial	a172756b5672cba3132c79d8be13f9ea
Not Before	06 Oct 2024 04:32:43 UTC
Not After	04 Jan 2025 04:32:42 UTC
Validity period	90 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/brD8Lo8p_3U.crl
OCSP	http://o.pki.goog/s/wr1/oXI
Certificate Transparency
Signed Certificate Timestamps	06 Oct 2024 05:32:44 UTC \| Google 'Xenon2025h1' log \| Qualified 06 Oct 2024 05:32:45 UTC \| Cloudflare 'Nimbus2025' \| Qualified
Fingerprints
SHA1	e1d5ab7da40d0a031eda3ae14e43fb764bbbcaa1
SHA256	df3d573c94ce046e601cf8425150c382a6f267e489201c6f891637692bb8923f
SPKI SHA256	b074f6d7138f34cd48af9ca4b7fba4c4bd0be36b2ed72d9773280dd9a317a55a

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

hardenize.com | df3d573
Not After: 04 Jan 2025 04:32:42 UTC (expires in 1 month 8 days)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Names	hardenize.com *.hardenize.com
Subject DN	CN=hardenize.com
Subject Key Identifier	df32b5314023a0fcbff010ea0352eadc44a28093
Serial	a172756b5672cba3132c79d8be13f9ea
Not Before	06 Oct 2024 04:32:43 UTC
Not After	04 Jan 2025 04:32:42 UTC
Validity period	90 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/brD8Lo8p_3U.crl
OCSP	http://o.pki.goog/s/wr1/oXI
Certificate Transparency
Signed Certificate Timestamps	06 Oct 2024 05:32:44 UTC \| Google 'Xenon2025h1' log \| Qualified 06 Oct 2024 05:32:45 UTC \| Cloudflare 'Nimbus2025' \| Qualified
Fingerprints
SHA1	e1d5ab7da40d0a031eda3ae14e43fb764bbbcaa1
SHA256	df3d573c94ce046e601cf8425150c382a6f267e489201c6f891637692bb8923f
SPKI SHA256	b074f6d7138f34cd48af9ca4b7fba4c4bd0be36b2ed72d9773280dd9a317a55a

Intermediate certificate

WR1 | b10b6f0
Not After: 20 Feb 2029 14:00:00 UTC (expires in 4 years 2 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 3 years 2 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 | b41b2fb
Not After: 28 Jan 2014 12:00:00 UTC (expired 10 years 9 months ago)
Authentication: RSA 2048 bits (MD5withRSA)
View details

Subject DN	CN=GlobalSign Root CA, OU=Root CA, O=GlobalSign nv-sa, C=BE
Subject Key Identifier	607b661a450d97ca89502f7d04cd34a8fffcfd4b
Serial	20000000000d678b79405
Not Before	01 Sep 1998 12:00:00 UTC
Not After	28 Jan 2014 12:00:00 UTC (expired 10 years 9 months ago)
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	2f173f7de99667afa57af80aa2d1b12fac830338
SHA256	b41b2fbfb93eeab3e0fa6b284adb932cdb3766ed4bc7d14837a8f2d9ae874a23
SPKI SHA256	2bcee858158cf5465fc9d76f0dfa312fef25a4dca8501da9b46b67d1fbfa1b64

Analysis

Certificate chain is correct

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

Certificate: www.hardenize.com

Leaf certificate

hardenize.com
Issuer: Google Trust Services LLC
Not Before: 06 Oct 2024 04:32:51 UTC
Not After: 04 Jan 2025 04:32:50 UTC (expires in 1 month 8 days)
Key: EC 256 bits
Signature: SHA256withECDSA
View details

Names	hardenize.com *.hardenize.com
Subject DN	CN=hardenize.com
Subject Key Identifier	eb3dd990860bb4b34cce982a2f754f676cdd1df1
Serial	2908b6a150e07c913d70eb41a2e2b40
Not Before	06 Oct 2024 04:32:51 UTC
Not After	04 Jan 2025 04:32:50 UTC
Validity period	90 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/TgxXJzCQ3Ko.crl
OCSP	http://o.pki.goog/s/we1/ApA
Certificate Transparency
Signed Certificate Timestamps	06 Oct 2024 05:32:51 UTC \| Google 'Xenon2025h1' log \| Qualified 06 Oct 2024 05:32:51 UTC \| DigiCert Nessie2025 Log \| Qualified
Fingerprints
SHA1	19be52bd10a67ea2b07a73326b77dbd4dfc0bb39
SHA256	46ef67b522f7fceb71c27a341e79a6ae6982b6a3f57bd804e0137db6bdf0c4c3
SPKI SHA256	9399d89b35331008f146b74c5686869985c597600c38acf346044870112bf039

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

hardenize.com | 46ef67b
Not After: 04 Jan 2025 04:32:50 UTC (expires in 1 month 8 days)
Authentication: EC 256 bits (SHA256withECDSA)
View details

Names	hardenize.com *.hardenize.com
Subject DN	CN=hardenize.com
Subject Key Identifier	eb3dd990860bb4b34cce982a2f754f676cdd1df1
Serial	2908b6a150e07c913d70eb41a2e2b40
Not Before	06 Oct 2024 04:32:51 UTC
Not After	04 Jan 2025 04:32:50 UTC
Validity period	90 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/TgxXJzCQ3Ko.crl
OCSP	http://o.pki.goog/s/we1/ApA
Certificate Transparency
Signed Certificate Timestamps	06 Oct 2024 05:32:51 UTC \| Google 'Xenon2025h1' log \| Qualified 06 Oct 2024 05:32:51 UTC \| DigiCert Nessie2025 Log \| Qualified
Fingerprints
SHA1	19be52bd10a67ea2b07a73326b77dbd4dfc0bb39
SHA256	46ef67b522f7fceb71c27a341e79a6ae6982b6a3f57bd804e0137db6bdf0c4c3
SPKI SHA256	9399d89b35331008f146b74c5686869985c597600c38acf346044870112bf039

Intermediate certificate

WE1 | 1dfc160
Not After: 20 Feb 2029 14:00:00 UTC (expires in 4 years 2 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 3 years 2 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 | b41b2fb
Not After: 28 Jan 2014 12:00:00 UTC (expired 10 years 9 months ago)
Authentication: RSA 2048 bits (MD5withRSA)
View details

Subject DN	CN=GlobalSign Root CA, OU=Root CA, O=GlobalSign nv-sa, C=BE
Subject Key Identifier	607b661a450d97ca89502f7d04cd34a8fffcfd4b
Serial	20000000000d678b79405
Not Before	01 Sep 1998 12:00:00 UTC
Not After	28 Jan 2014 12:00:00 UTC (expired 10 years 9 months ago)
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	2f173f7de99667afa57af80aa2d1b12fac830338
SHA256	b41b2fbfb93eeab3e0fa6b284adb932cdb3766ed4bc7d14837a8f2d9ae874a23
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.

HTTP Cookie: __Secure-SESSIONID Session cookie

Cookie value. As far as the cookie RFC is concerned, the value is an opaque string which only the application should interpret.Value	9DE4D669E35CB5136E5CE6C52DF196E4
Cookie domain. When domain is implied (not explicitly set in a cookie), most browsers (but not IE) treat the cookie as host-only, meaning that no other server can overwrite it.Domain	Implied (www.hardenize.com)
Cookie path. This field can't be used as security measure, but it could be of use to avoid cookie name collision in non-adversarial contexts.Path	/
The HttpOnly flag prevents the cookie from being accessed from JavaScript, thus making them more difficult to obtain after a successful XSS attack.HttpOnly
The Secure flag signals to browsers that the cookie should be transmitted only over an encrypted channel.Secure
Normally, when a browser makes a request to a web site, it sends all associated cookies. This is not always desirable, because it might allow third-party sites to perform site actions under the identity of the user. This attack is known as Cross-Site Request Forgery. With SameSite cookies (still in development, but already supported in some browsers), you can choose to be more strict. The possible values are 'lax' and 'strict'.SameSite	lax

Analysis

Session cookie is secure

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

Session cookie is HttpOnly

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

SameSite attribute deployed

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

Cookie uses host name prefix

Excellent. This cookie uses a special name prefix that makes it more secure. Unlike normal cookies, cookies whose names begin with '__Host-' can't be overwritten by cookies sent from any other hostname variant.

Analysis

All cookies are secure

Great. All observed cookies are marked secure.

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.

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

Status	Link
Encrypted	https://www.hardenize.com/.../jquery-3.5.1.min.js
Encrypted	https://www.hardenize.com/...ry.basictable.min.js
Encrypted	https://www.hardenize.com/...46/js/parsley.min.js
Encrypted	https://www.hardenize.com/...546/js/sentry.min.js
Encrypted	https://www.hardenize.com/.../common-functions.js
Encrypted	https://www.hardenize.com/...2541546/js/detect.js
Encrypted	https://www.hardenize.com/...js/datatables.min.js
Encrypted	https://www.hardenize.com/...Tables.pageResize.js
Encrypted	https://www.hardenize.com/...hardenize-plugins.js
Encrypted	https://www.hardenize.com/...541546/js/redsift.js

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

Status	Link
Encrypted	https://www.hardenize.com/...1732541546/fonts.css
Encrypted	https://www.hardenize.com/...font-awesome.min.css
Encrypted	https://www.hardenize.com/...46/css/normalize.css
Encrypted	https://www.hardenize.com/...41546/css/common.css
Encrypted	https://www.hardenize.com/...1546/css/website.css
Encrypted	https://www.hardenize.com/...6/css/basictable.css
Encrypted	https://www.hardenize.com/...6/css/responsive.css
Encrypted	https://www.hardenize.com/...s/system-message.css

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

Status	Link
Encrypted	https://www.hardenize.com/...s/hardenize-logo.png
Encrypted	https://www.hardenize.com/...5/customer-logos.png
Encrypted	https://www.hardenize.com/...eport-full-white.png

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.

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

Status	Link
Encrypted	https://twitter.com/hardenize

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

Analysis

Policy is valid

OK. Your HSTS policy uses correct syntax.

Long policy age

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

Policy covers subdomains

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

Redirection from HTTP to HTTPS to the same host

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

Policy preloaded

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

Preloaded host: hardenize.com; includeSubDomains=true

HSTS Policy Apex host

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

Analysis

Policy is valid

OK. Your HSTS policy uses correct syntax.

Long policy age

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

Policy covers subdomains

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

Preload intent declared

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

Redirection from HTTP to HTTPS to the same host

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

Policy preloaded

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

Preloaded host: hardenize.com; 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'
img-src	'self' data: blob:
form-action	'self' https://app.redsift.io https://app.redsift.cloud
connect-src	'self' sentry.io https://plausible.io
frame-ancestors	https://app.redsift.io https://app.redsift.cloud
frame-src	https://www.google.com
font-src	'self' data:
script-src	'report-sample' 'self' 'nonce-d413783584b373a656e01107dbcf76f4' https://plausible.io
style-src	'self' This parameter shouldn't be used because it reenables insecure behavior that CSP disables by default.'unsafe-inline'
report-uri	https://sentry.io/api/1544333/csp-report/

Analysis

Inline styles are allowed

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

Mixed content not blocked

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

Analysis

CSP policy detected

Header: content-security-policy

Value: default-src 'self'; media-src 'self'; img-src 'self' data: blob:; form-action 'self' https://app.redsift.io https://app.redsift.cloud; connect-src 'self' sentry.io https://plausible.io; frame-ancestors https://app.redsift.io https://app.redsift.cloud; frame-src https://www.google.com; object-src 'self'; font-src 'self' data:; script-src 'report-sample' 'self' 'nonce-d413783584b373a656e01107dbcf76f4' https://plausible.io; style-src 'self' 'unsafe-inline'; report-uri https://sentry.io/api/1544333/csp-report/?sentry_key=49d512bfcf954f33a5b9c68f30d60783

Location: https://www.hardenize.com/

Subresource Integrity

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

Test passed

Everything seems to be well configured. Well done.

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

Status	Link
Local	/include-web-1732541546/js/jquery-3.5.1.min.js
Local	/include-web-1732541546/js/jquery.basictable.min.js
Local	/include-web-1732541546/js/parsley.min.js
Local	/include-web-1732541546/js/sentry.min.js
Local	/include-web-1732541546/js/common-functions.js
Local	/include-web-1732541546/js/detect.js
Local	/include-report-1732541546/js/datatables.min.js
Local	/include-report-1732541546/js/dataTables.pageResize.js
Local	/include-report-1732541546/js/dataTables.hardenize-plugins.js
Local	/include-web-1732541546/js/redsift.js

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

Status	Link
Local	/include-fonts-1732541546/fonts.css
Local	/include-fonts-1732541546/font-awesome.min.css
Local	/include-web-1732541546/css/normalize.css
Local	/include-web-1732541546/css/common.css
Local	/include-web-1732541546/css/website.css
Local	/include-web-1732541546/css/basictable.css
Local	/include-web-1732541546/css/responsive.css
Local	/application/include-1732541546/css/system-message.css

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.

Test passed

Everything seems to be well configured. Well done.

Expect-CT Policy

URL from which this policy was obtained.Location	https://www.hardenize.com/
Specifies policy duration. Once activated, Expect-CT stays in force until this time lapses. Browsers update policy cache duration every time they receive a new Expect-CT header from a site.max‑age	31,536,000 seconds (about 1 year)
This optional directive controls whether CT compliance will be enforced by your policy. It's useful if you're confident in your configuration and wish to deploy CT before browsers start enforcing it.enforce
This optional directive enables reporting and specifies the endpoint clients should use to submit reports.report-uri	https://h.reporting.hardenize.com

Analysis

Header information

Policy text: max-age=31536000, report-uri="https://h.reporting.hardenize.com"

Reporting endpoint operational

Good. The reporting endpoint accepted our test submission.

Report URI: https://h.reporting.hardenize.com

Expect-CT enabled

Excellent. This web site has a valid Expect-CT policy.

Frame Options

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

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

XSS Protection

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

Test passed

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

hardenize.com

Domain Name System

Email

WWW

DNS Zone

Nameserver Names

Nameserver Addresses

Start of Authority (SOA) Record

Analysis

Backing DNS Queries

DNS Records

DNS Records

Backing DNS Queries

DNSSEC

Useful DNSSEC Tools

Certification Authority Authorization

Analysis

Email (SMTP)

Analysis

Email TLS (SMTP)

TLS Configuration: aspmx.l.google.com (2607:f8b0:4004:c17:0:0:0:1a) Cached

Analysis

TLS Configuration: aspmx.l.google.com (64.233.180.26) Cached

Analysis

TLS Configuration: alt2.aspmx.l.google.com (2a00:1450:400c:c0b:0:0:0:1a) Cached

Analysis

TLS Configuration: alt2.aspmx.l.google.com (64.233.184.26) Cached

Analysis

TLS Configuration: alt1.aspmx.l.google.com (2a00:1450:400b:c00:0:0:0:1a) Cached

Analysis

TLS Configuration: alt1.aspmx.l.google.com (209.85.202.27) Cached

Analysis

TLS Configuration: aspmx3.googlemail.com (2a00:1450:400c:c0b:0:0:0:1a) Cached

Analysis

TLS Configuration: aspmx3.googlemail.com (64.233.184.26) Cached

Analysis

TLS Configuration: aspmx2.googlemail.com (2a00:1450:400b:c00:0:0:0:1a) Cached

Analysis

TLS Configuration: aspmx2.googlemail.com (209.85.202.27) Cached

Analysis

Email Certificates (SMTP)

Certificate #1 Cached

Analysis

Certificate Chain

Analysis

Email DANE (SMTP)

SPF

SPF Policy Information Main policy

Analysis

SPF Policy Information Included policy

SPF Policy Information Included policy

SPF Policy Information Included policy

SPF Policy Information Included policy

SPF Policy Information Included policy

SPF Policy Information Included policy

SPF Policy Information Included policy

SPF Policy Information Included policy

SPF Policy Information Included policy

SPF Policy Information Included policy

DMARC

DMARC Policy Information

Analysis

MTA Strict Transport Security

MTA-STS Policy Indicator

Analysis

MTA-STS Policy

Analysis

Certificate: mta-sts.hardenize.com

Analysis

Certificate Chain

Analysis

SMTP TLS Reporting

TLS-RPT Policy

Analysis

HTTP (80)

URL: http://hardenize.com/

Analysis

URL: http://www.hardenize.com/

Analysis