Hardenize Report: forwardemail.net

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
greg.ns.cloudflare.com. PRIMARY 108.162.193.115 172.64.33.115 173.245.59.115 2606:4700:58::adf5:3b73 2803:f800:50::6ca2:c173 2a06:98c1:50::ac40:2173				SOA REFERRAL NS
uma.ns.cloudflare.com. 108.162.192.146 172.64.32.146 173.245.58.146 2606:4700:50::adf5:3a92 2803:f800:50::6ca2:c092 2a06:98c1:50::ac40:2092				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.146 uma.ns.cloudflare.com. PTR: uma.ns.cloudflare.com.	NAME	1232
108.162.193.115 PRIMARY greg.ns.cloudflare.com. PTR: greg.ns.cloudflare.com.	NAME	1232
172.64.32.146 uma.ns.cloudflare.com. PTR: uma.ns.cloudflare.com.	NAME	1232
172.64.33.115 PRIMARY greg.ns.cloudflare.com. PTR: greg.ns.cloudflare.com.	NAME	1232
173.245.58.146 uma.ns.cloudflare.com. PTR: uma.ns.cloudflare.com.	NAME	1232
173.245.59.115 PRIMARY greg.ns.cloudflare.com. PTR: greg.ns.cloudflare.com.	NAME	1232
2606:4700:50::adf5:3a92 uma.ns.cloudflare.com. PTR: uma.ns.cloudflare.com.	NAME	1232
2606:4700:58::adf5:3b73 PRIMARY greg.ns.cloudflare.com. PTR: greg.ns.cloudflare.com.	NAME	1232
2803:f800:50::6ca2:c092 uma.ns.cloudflare.com. PTR: uma.ns.cloudflare.com.	NAME	1232
2803:f800:50::6ca2:c173 PRIMARY greg.ns.cloudflare.com. PTR: greg.ns.cloudflare.com.	NAME	1232
2a06:98c1:50::ac40:2092 uma.ns.cloudflare.com. PTR: uma.ns.cloudflare.com.	NAME	1232
2a06:98c1:50::ac40:2173 PRIMARY greg.ns.cloudflare.com. PTR: greg.ns.cloudflare.com.	NAME	1232

Start of Authority (SOA) Record

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

The domain name of the primary nameserver for the zone. Also known as MNAME.Primary nameserver	greg.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	-1939689526
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
forwardemail.net.	30	A	144.202.105.188
www.forwardemail.net.	300	A	104.26.3.178
www.forwardemail.net.	300	A	104.26.2.178
www.forwardemail.net.	300	A	172.67.72.142
forwardemail.net.	30	AAAA	2001:19f0:ac00:41b3:5400:4ff:febb:a905
www.forwardemail.net.	300	AAAA	2606:4700:20:0:0:0:681a:2b2
www.forwardemail.net.	300	AAAA	2606:4700:20:0:0:0:ac43:488e
www.forwardemail.net.	300	AAAA	2606:4700:20:0:0:0:681a:3b2
forwardemail.net.	300	CAA	0 issuewild "sectigo.com; cansignhttpexchanges=yes"
forwardemail.net.	300	CAA	0 issuewild "ssl.com"
forwardemail.net.	300	CAA	0 iodef "mailto:security@forwardemail.net"
forwardemail.net.	300	CAA	0 issue "amazon.com"
forwardemail.net.	300	CAA	0 issue "amazonaws.com"
forwardemail.net.	300	CAA	0 issue "amazontrust.com"
forwardemail.net.	300	CAA	0 issue "awstrust.com"
forwardemail.net.	300	CAA	0 issue "comodoca.com"
forwardemail.net.	300	CAA	0 issue "digicert.com; cansignhttpexchanges=yes"
forwardemail.net.	300	CAA	0 issue "letsencrypt.org"
forwardemail.net.	300	CAA	0 issue "pki.goog; cansignhttpexchanges=yes"
forwardemail.net.	300	CAA	0 issue "sectigo.com; cansignhttpexchanges=yes "
forwardemail.net.	300	CAA	0 issue "ssl.com"
forwardemail.net.	300	CAA	0 issuewild "comodoca.com"
forwardemail.net.	300	CAA	0 issuewild "digicert.com; cansignhttpexchanges=yes"
forwardemail.net.	300	CAA	0 issuewild "letsencrypt.org"
forwardemail.net.	300	CAA	0 issuewild "pki.goog; cansignhttpexchanges=yes"
forwardemail.net.	3600	DNSKEY	257 3 13 mdsswUyr3DPW132mOi8V9xESWE8jTo0dxCjjnopKl+GqJxpVXckHAeF+KkxLbxILfDLUT0rAK9iUzy1L53eKGQ==
forwardemail.net.	3600	DNSKEY	256 3 13 oJMRESz5E4gYzS/q6XDrvU1qMPYIjCWzJaOau8XNEZeqCYKD5ar0IRd8KqXXFJkqmVfRvMGPmM1x8fGAa2XhSA==
www.forwardemail.net.	300	HTTPS	1 . alpn=h2 ipv4hint=104.26.2.178,104.26.3.178,172.67.72.142 ipv6hint=2606:4700:20:0:0:0:681a:2b2,2606:4700:20:0:0:0:681a:3b2,2606:4700:20:0:0:0:ac43:488e
forwardemail.net.	3600	MX	0 mx1.forwardemail.net.
forwardemail.net.	3600	MX	0 mx2.forwardemail.net.
forwardemail.net.	86400	NS	greg.ns.cloudflare.com.
forwardemail.net.	86400	NS	uma.ns.cloudflare.com.
forwardemail.net.	1800	SOA	greg.ns.cloudflare.com. dns.cloudflare.com. 2355277770 10000 2400 604800 1800
forwardemail.net.	300	TXT	"v=spf1 a mx a:smtp.forwardemail.net -all"
forwardemail.net.	300	TXT	"yahoo-verification-key=si8Sk2QcPzmIrW2pUw29zPNEzRKzHr0ISgJTWimoxpM="
forwardemail.net.	300	TXT	"forward-email-site-verification=OgBtCf0Xkq"
forwardemail.net.	300	TXT	"google-site-verification=5nCKgW5qElZVdLWPF86WZyhUXDIEDRm8-C_E2niW3gE"
forwardemail.net.	300	TXT	"google-site-verification=DBUsD3_MzaXh2N1onlaZdCELRyT3dHKxkx9d8TpNZVQ"
forwardemail.net.	300	TXT	"google-site-verification=Dlc-ddlz_HZm-0Lpe6eKL6PJKa7xCPy_mIbf0O3hGWo"
forwardemail.net.	300	TXT	"google-site-verification=OjDxZN2DU7XqtvyPpDrvMcYjef2msFDLga3NuIXHJiE"
forwardemail.net.	300	TXT	"google-site-verification=TDhFtE5nIp6D7zTPt3CdsWbOoG87xWt_7um_P5iYwx8"
forwardemail.net.	300	TXT	"google-site-verification=fMQEHvvEIPRSxyjBBTu_R43f7l25UgcE3wxzwAYUoh4"
forwardemail.net.	300	TXT	"stripe-verification=3cf1eee253ef0954773402850376d9b3d97bfe3f2dee06bcbd76839c768a56c3"
_dmarc.forwardemail.net.	300	TXT	"v=DMARC1; p=reject; pct=100; rua=mailto:dmarc-646d8d480dd3cc2c671633e2@forwardemail.net;"
_mta-sts.forwardemail.net.	300	TXT	"v=STSv1; id=20231103T000000;"
_smtp._tls.forwardemail.net.	300	TXT	"v=TLSRPTv1; rua=mailto:tlsrpt@forwardemail.net"

Backing DNS Queries

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

	ID	Server	Question Name	Type	Status

DNSSEC

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

Test passed

Everything seems to be well configured. Well done.

Analysis

DNSSEC is well configured

Good. This domain name has well-configured DNSSEC.

Useful DNSSEC Tools

Certification Authority Authorization

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

Test passed

Everything seems to be well configured. Well done.

CAA Policy Information

The DNS hostname where this policy is located.Policy host	forwardemail.net
The issue property tag is used to request that certificate issuers perform CAA issue restriction processing for the domain and to grant authorization to specific certificate issuers.issue	amazontrust.com flags: 0
The issue property tag is used to request that certificate issuers perform CAA issue restriction processing for the domain and to grant authorization to specific certificate issuers.issue	ssl.com flags: 0
The issue property tag is used to request that certificate issuers perform CAA issue restriction processing for the domain and to grant authorization to specific certificate issuers.issue	comodoca.com flags: 0
The issue property tag is used to request that certificate issuers perform CAA issue restriction processing for the domain and to grant authorization to specific certificate issuers.issue	awstrust.com flags: 0
The issuewild property has the same syntax and semantics as the issue property except that issuewild properties only grant authorization to issue certificates that specify a wildcard domain and issuewild properties take precedence over issue properties when specified.issuewild	letsencrypt.org flags: 0
The issuewild property has the same syntax and semantics as the issue property except that issuewild properties only grant authorization to issue certificates that specify a wildcard domain and issuewild properties take precedence over issue properties when specified.issuewild	pki.goog; cansignhttpexchanges=yes flags: 0
The issue property tag is used to request that certificate issuers perform CAA issue restriction processing for the domain and to grant authorization to specific certificate issuers.issue	sectigo.com; cansignhttpexchanges=yes flags: 0
The issuewild property has the same syntax and semantics as the issue property except that issuewild properties only grant authorization to issue certificates that specify a wildcard domain and issuewild properties take precedence over issue properties when specified.issuewild	comodoca.com flags: 0
The issue property tag is used to request that certificate issuers perform CAA issue restriction processing for the domain and to grant authorization to specific certificate issuers.issue	pki.goog; cansignhttpexchanges=yes flags: 0
The issue property tag is used to request that certificate issuers perform CAA issue restriction processing for the domain and to grant authorization to specific certificate issuers.issue	digicert.com; cansignhttpexchanges=yes flags: 0
The issuewild property has the same syntax and semantics as the issue property except that issuewild properties only grant authorization to issue certificates that specify a wildcard domain and issuewild properties take precedence over issue properties when specified.issuewild	ssl.com flags: 0
The issue property tag is used to request that certificate issuers perform CAA issue restriction processing for the domain and to grant authorization to specific certificate issuers.issue	letsencrypt.org flags: 0
The issue property tag is used to request that certificate issuers perform CAA issue restriction processing for the domain and to grant authorization to specific certificate issuers.issue	amazon.com flags: 0
The issuewild property has the same syntax and semantics as the issue property except that issuewild properties only grant authorization to issue certificates that specify a wildcard domain and issuewild properties take precedence over issue properties when specified.issuewild	digicert.com; cansignhttpexchanges=yes flags: 0
The issue property tag is used to request that certificate issuers perform CAA issue restriction processing for the domain and to grant authorization to specific certificate issuers.issue	amazonaws.com flags: 0
The issuewild property has the same syntax and semantics as the issue property except that issuewild properties only grant authorization to issue certificates that specify a wildcard domain and issuewild properties take precedence over issue properties when specified.issuewild	sectigo.com; cansignhttpexchanges=yes flags: 0
The iodef property specifies a means of reporting certificate issue requests or cases of certificate issue for the corresponding domain that violate the security policy of the issuer or the domain name holder.iodef	mailto:security@forwardemail.net flags: 0

Analysis

Issuance of S/MIME certificates not restricted

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

Issuance of BIMI not restricted

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

CAA policy restricts issuance

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

Policy uses reporting

Good. This policy uses reporting, which means that your contact information is available should someone need to contact you about a CAA violation. Do note that you're not guaranteed to be notified, given that CAs generally don't support notifications yet.

Email (SMTP)

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

Test passed

Everything seems to be well configured. Well done.

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
mx1.forwardemail.net 2604:a880:2:d0:0:0:306:1 PTR: mx1.forwardemail.net	0
mx1.forwardemail.net 138.197.213.185 PTR: mx1.forwardemail.net	0
mx2.forwardemail.net 2604:a880:400:d1:0:0:cd:9001 PTR: mx2.forwardemail.net	0
mx2.forwardemail.net 104.248.224.170 PTR: mx2.forwardemail.net	0

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: 21 Oct 2024 12:53 UTC

Earliest cache timestamp: 21 Oct 2024 12: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: mx1.forwardemail.net (2604:a880:2:d0:0:0:306:1) 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_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)
These results have been retrieved from our cache. This row indicates when was that the original test ran.Retrieved from cache	21 Oct 2024 12: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: mx1.forwardemail.net (138.197.213.185) 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_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)
These results have been retrieved from our cache. This row indicates when was that the original test ran.Retrieved from cache	21 Oct 2024 12: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: mx2.forwardemail.net (2604:a880:400:d1:0:0:cd:9001) 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_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)
These results have been retrieved from our cache. This row indicates when was that the original test ran.Retrieved from cache	21 Oct 2024 12: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: mx2.forwardemail.net (104.248.224.170) 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_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)
These results have been retrieved from our cache. This row indicates when was that the original test ran.Retrieved from cache	21 Oct 2024 12: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.

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

*.forwardemail.net
Issuer: Sectigo
Not Before: 02 Nov 2023 00:00:00 UTC
Not After: 02 Dec 2024 23:59:59 UTC (expires in 1 month 7 days)
Key: RSA 2048 bits
Signature: SHA256withRSA
View details

Names	*.forwardemail.net forwardemail.net
Subject DN	CN=*.forwardemail.net
Subject Key Identifier	2dda91bc2a403f6a166c94bd74511519841eeb39
Serial	7da17d2650bdd12d6d0931598274cb6f
Not Before	02 Nov 2023 00:00:00 UTC
Not After	02 Dec 2024 23:59:59 UTC
Validity period	397 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=Sectigo RSA Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, ST=Greater Manchester, C=GB
Certification Authority	Sectigo
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:8d8c5ec454ad8ae177e99bf99b05e1b8018d61e1
Parent Certificate	http://crt.sectigo.com/SectigoRSADomainValidationSecureServerCA.crt
OCSP	http://ocsp.sectigo.com
Certificate Transparency
Signed Certificate Timestamps	02 Nov 2023 21:13:19 UTC \| Google 'Xenon2024' log \| Qualified 02 Nov 2023 21:13:19 UTC \| Let's Encrypt 'Oak2024H2' log \| Qualified 02 Nov 2023 21:13:19 UTC \| Google 'Argon2024' log \| Qualified
Fingerprints
SHA1	981960d9b3efe1ebc2e6eb18dea6dba10df12b22
SHA256	57baf3bfcc4cf7821c8361a242601ad3bf44214364e8a614923704fb2a07ebcb
SPKI SHA256	5e81da1af16df20b13e667ad6d9c2b65b95bfcd95150caffe7116c1707b4dd2c

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

*.forwardemail.net | 57baf3b
Not After: 02 Dec 2024 23:59:59 UTC (expires in 1 month 7 days)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Names	*.forwardemail.net forwardemail.net
Subject DN	CN=*.forwardemail.net
Subject Key Identifier	2dda91bc2a403f6a166c94bd74511519841eeb39
Serial	7da17d2650bdd12d6d0931598274cb6f
Not Before	02 Nov 2023 00:00:00 UTC
Not After	02 Dec 2024 23:59:59 UTC
Validity period	397 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=Sectigo RSA Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, ST=Greater Manchester, C=GB
Certification Authority	Sectigo
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:8d8c5ec454ad8ae177e99bf99b05e1b8018d61e1
Parent Certificate	http://crt.sectigo.com/SectigoRSADomainValidationSecureServerCA.crt
OCSP	http://ocsp.sectigo.com
Certificate Transparency
Signed Certificate Timestamps	02 Nov 2023 21:13:19 UTC \| Google 'Xenon2024' log \| Qualified 02 Nov 2023 21:13:19 UTC \| Let's Encrypt 'Oak2024H2' log \| Qualified 02 Nov 2023 21:13:19 UTC \| Google 'Argon2024' log \| Qualified
Fingerprints
SHA1	981960d9b3efe1ebc2e6eb18dea6dba10df12b22
SHA256	57baf3bfcc4cf7821c8361a242601ad3bf44214364e8a614923704fb2a07ebcb
SPKI SHA256	5e81da1af16df20b13e667ad6d9c2b65b95bfcd95150caffe7116c1707b4dd2c

Intermediate certificate

Sectigo RSA Domain Validation Secure Server CA | 7fa4ff6
Not After: 31 Dec 2030 23:59:59 UTC (expires in 6 years 2 months)
Authentication: RSA 2048 bits (SHA384withRSA)
View details

Subject DN	CN=Sectigo RSA Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, ST=Greater Manchester, C=GB
Subject Key Identifier	8d8c5ec454ad8ae177e99bf99b05e1b8018d61e1
Serial	7d5b5126b476ba11db74160bbc530da7
Not Before	02 Nov 2018 00:00:00 UTC
Not After	31 Dec 2030 23:59:59 UTC
Key Usage	digitalSignature, keyCertSign, cRLSign
Extended Key Usage	serverAuth, clientAuth
Issuer
Issuer DN	CN=USERTrust RSA Certification Authority, O=The USERTRUST Network, L=Jersey City, ST=New Jersey, C=US
Certification Authority	Sectigo
Validation Type	Not Applicable
Authority Key Identifier	keyid:5379bf5aaa2b4acf5480e1d89bc09df2b20366cb
Parent Certificate	http://crt.usertrust.com/USERTrustRSAAddTrustCA.crt
CRL	http://crl.usertrust.com/USERTrustRSACertificationAuthority.crl
OCSP	http://ocsp.usertrust.com
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	33e4e80807204c2b6182a3a14b591acd25b5f0db
SHA256	7fa4ff68ec04a99d7528d5085f94907f4d1dd1c5381bacdc832ed5c960214676
SPKI SHA256	e1ae9c3de848ece1ba72e0d991ae4d0d9ec547c6bad1dddab9d6beb0a7e0e0d8

Intermediate certificate

USERTrust RSA Certification Authority | 68b9c76
Not After: 31 Dec 2028 23:59:59 UTC (expires in 4 years 2 months)
Authentication: RSA 4096 bits (SHA384withRSA)
View details

Subject DN	CN=USERTrust RSA Certification Authority, O=The USERTRUST Network, L=Jersey City, ST=New Jersey, C=US
Subject Key Identifier	5379bf5aaa2b4acf5480e1d89bc09df2b20366cb
Serial	3972443af922b751d7d36c10dd313595
Not Before	12 Mar 2019 00:00:00 UTC
Not After	31 Dec 2028 23:59:59 UTC
Key Usage	digitalSignature, keyCertSign, cRLSign
Issuer
Issuer DN	CN=AAA Certificate Services, O=Comodo CA Limited, L=Salford, ST=Greater Manchester, C=GB
Certification Authority	Sectigo
Validation Type	Not Applicable
Authority Key Identifier	keyid:a0110a233e96f107ece2af29ef82a57fd030a4b4
CRL	http://crl.comodoca.com/AAACertificateServices.crl
OCSP	http://ocsp.comodoca.com
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	d89e3bd43d5d909b47a18977aa9d5ce36cee184c
SHA256	68b9c761219a5b1f0131784474665db61bbdb109e00f05ca9f74244ee5f5f52b
SPKI SHA256	c784333d20bcd742b9fdc3236f4e509b8937070e73067e254dd3bf9c45bf4dde

Root certificate

AAA Certificate Services | d7a7a0f
Not After: 31 Dec 2028 23:59:59 UTC (expires in 4 years 2 months)
Authentication: RSA 2048 bits (SHA1withRSA)
View details

Subject DN	CN=AAA Certificate Services, O=Comodo CA Limited, L=Salford, ST=Greater Manchester, C=GB
Subject Key Identifier	a0110a233e96f107ece2af29ef82a57fd030a4b4
Serial	1
Not Before	01 Jan 2004 00:00:00 UTC
Not After	31 Dec 2028 23:59:59 UTC
Key Usage	keyCertSign, cRLSign
Issuer
Issuer DN	CN=AAA Certificate Services, O=Comodo CA Limited, L=Salford, ST=Greater Manchester, C=GB
Certification Authority	Sectigo
Validation Type	Self-signed
CRL	http://crl.comodoca.com/AAACertificateServices.crl http://crl.comodo.net/AAACertificateServices.crl
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	d1eb23a46d17d68fd92564c2f1f1601764d8e349
SHA256	d7a7a0fb5d7e2731d771e9484ebcdef71d5f0c3e0a2948782bc83ee0ea699ef4
SPKI SHA256	bd153ed7b0434f6886b17bce8bbe84ed340c7132d702a8f4fa318f756ecbd6f3

Analysis

Certificate chain is correct

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

Email DANE (SMTP)

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

Test passed

Everything seems to be well configured. Well done.

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

DANE: mx1.forwardemail.net (2604:a880:2:d0:0:0:306:1)

Specifies which certificate in the chain is being pinned and how validation should be performed.Certificate Usage	Domain-issued certificate / DANE-EE (3)
Determines if the association is made with a certificate or with a public key (via its SPKI structure).Selector	SPKI structure (1)
Determines how matching is done; directly or via a hash. Matching Type	SHA2-256 (1)
Contains the data necessary to perform the matching. Data	5e81da1af16df20b13e667ad6d9c2b65b95bfcd95150caffe7116c1707b4dd2c Leaf certificate: RSA 2048 bits Subject: CN=.forwardemail.net Issuer: CN=Sectigo RSA Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, ST=Greater Manchester, C=GB .forwardemail.net (RSA 2048 bits)

Analysis

Valid DANE configuration

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

DANE: mx1.forwardemail.net (138.197.213.185)

Specifies which certificate in the chain is being pinned and how validation should be performed.Certificate Usage	Domain-issued certificate / DANE-EE (3)
Determines if the association is made with a certificate or with a public key (via its SPKI structure).Selector	SPKI structure (1)
Determines how matching is done; directly or via a hash. Matching Type	SHA2-256 (1)
Contains the data necessary to perform the matching. Data	5e81da1af16df20b13e667ad6d9c2b65b95bfcd95150caffe7116c1707b4dd2c Leaf certificate: RSA 2048 bits Subject: CN=.forwardemail.net Issuer: CN=Sectigo RSA Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, ST=Greater Manchester, C=GB .forwardemail.net (RSA 2048 bits)

Analysis

Valid DANE configuration

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

DANE: mx2.forwardemail.net (2604:a880:400:d1:0:0:cd:9001)

Specifies which certificate in the chain is being pinned and how validation should be performed.Certificate Usage	Domain-issued certificate / DANE-EE (3)
Determines if the association is made with a certificate or with a public key (via its SPKI structure).Selector	SPKI structure (1)
Determines how matching is done; directly or via a hash. Matching Type	SHA2-256 (1)
Contains the data necessary to perform the matching. Data	5e81da1af16df20b13e667ad6d9c2b65b95bfcd95150caffe7116c1707b4dd2c Leaf certificate: RSA 2048 bits Subject: CN=.forwardemail.net Issuer: CN=Sectigo RSA Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, ST=Greater Manchester, C=GB .forwardemail.net (RSA 2048 bits)

Analysis

Valid DANE configuration

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

DANE: mx2.forwardemail.net (104.248.224.170)

Specifies which certificate in the chain is being pinned and how validation should be performed.Certificate Usage	Domain-issued certificate / DANE-EE (3)
Determines if the association is made with a certificate or with a public key (via its SPKI structure).Selector	SPKI structure (1)
Determines how matching is done; directly or via a hash. Matching Type	SHA2-256 (1)
Contains the data necessary to perform the matching. Data	5e81da1af16df20b13e667ad6d9c2b65b95bfcd95150caffe7116c1707b4dd2c Leaf certificate: RSA 2048 bits Subject: CN=.forwardemail.net Issuer: CN=Sectigo RSA Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, ST=Greater Manchester, C=GB .forwardemail.net (RSA 2048 bits)

Analysis

Valid DANE configuration

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

SPF

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

Test passed

Everything seems to be well configured. Well done.

SPF Policy Information Main policy

Host where this policy is located.Location	forwardemail.net
SPF version used by this policy.v	spf1
This mechanism matches if the sending IP address is one of the IP addresses that belong to the target domain name. Matches both IPv4 and IPv6 addresses. a
This mechanism matches if the sending IP address is one of the MX hosts for the domain name. mx
This mechanism matches if the sending IP address is one of the IP addresses that belong to the target domain name. Matches both IPv4 and IPv6 addresses. a	smtp.forwardemail.net
This policy element always matches. It's normally used at the end of a policy to specify the handling of hosts that don't match earlier mechanisms. -all

Analysis

SPF policy found

Policy text: v=spf1 a mx a:smtp.forwardemail.net -all

Location: forwardemail.net

SPF policy is valid

Good. Your SPF policy is syntactically valid.

Policy uses default fail

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

Policy DNS lookups under limit

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

Lookups: 3

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.forwardemail.net
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
Addresses to which aggregate feedback is to be sent.rua	mailto:dmarc-646d8d480dd3cc2c671633e2@forwardemail.net

Analysis

DMARC policy found

Policy: v=DMARC1; p=reject; pct=100; rua=mailto:dmarc-646d8d480dd3cc2c671633e2@forwardemail.net;

Host: _dmarc.forwardemail.net

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.forwardemail.net
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	20231103T000000

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.forwardemail.net/.well-known/mta-sts.txt
Policy standard version.version	STSv1
Policy duration, which specifies how long the sending MTAs should remember and enforce the server policy for.max‑age	2,419,200 seconds (about 28 days)
Policy mode, which can be one of 'none', 'testing' and 'enforcing'. Guess which is best! :)mode	enforce
One 'mx' directive specifies one email server pattern that's allowed for this host.mx	mx1.forwardemail.net
One 'mx' directive specifies one email server pattern that's allowed for this host.mx	mx2.forwardemail.net

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

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

Certificate: mta-sts.forwardemail.net

Leaf certificate

mta-sts.forwardemail.net
Issuer: Let's Encrypt
Not Before: 06 Sep 2024 03:11:57 UTC
Not After: 05 Dec 2024 03:11:56 UTC (expires in 1 month 9 days)
Key: RSA 2048 bits
Signature: SHA256withRSA
View details

Names	mta-sts.forwardemail.net
Subject DN	CN=mta-sts.forwardemail.net
Subject Key Identifier	58c9b2aa68e6a548ccd82be842b2bf7fbe456668
Serial	48ff32600e3e5e5b8435fc96bd2fac2faed
Not Before	06 Sep 2024 03:11:57 UTC
Not After	05 Dec 2024 03:11:56 UTC
Validity period	90 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=R10, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:bbbcc347a5e4bca9c6c3a4720c108da235e1c8e8
Parent Certificate	http://r10.i.lencr.org/
OCSP	http://r10.o.lencr.org
Certificate Transparency
Signed Certificate Timestamps	06 Sep 2024 04:10:27 UTC \| Sectigo 'Mammoth2024h2' \| Qualified 06 Sep 2024 04:10:27 UTC \| DigiCert Yeti2024 Log \| Qualified
Fingerprints
SHA1	944800e5f1d1cb40007de38ca860d9eb38b8ceb8
SHA256	e5fd21c6f569f680ab32ae12310c52b137d09d9a4455675747eba51e1deb1cd2
SPKI SHA256	0d073b9b73b4b0ee16e3f580e521c7b6c7aa20a48a764a758e1b31dff5043d90

Analysis

Strong private key

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

Strong signature algorithm

Good. This certificate uses a strong signature algorithm.

Certificate matches hostname

Good. The provided certificate matches the expected hostnames.

Certificate dates match

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

Certificate has not been revoked

Good. This certificate has not been revoked.

Certificate satisfies Apple's CT compliance requirements

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

Certificate Chain

Leaf certificate

mta-sts.forwardemail.net | e5fd21c
Not After: 05 Dec 2024 03:11:56 UTC (expires in 1 month 9 days)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Names	mta-sts.forwardemail.net
Subject DN	CN=mta-sts.forwardemail.net
Subject Key Identifier	58c9b2aa68e6a548ccd82be842b2bf7fbe456668
Serial	48ff32600e3e5e5b8435fc96bd2fac2faed
Not Before	06 Sep 2024 03:11:57 UTC
Not After	05 Dec 2024 03:11:56 UTC
Validity period	90 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=R10, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:bbbcc347a5e4bca9c6c3a4720c108da235e1c8e8
Parent Certificate	http://r10.i.lencr.org/
OCSP	http://r10.o.lencr.org
Certificate Transparency
Signed Certificate Timestamps	06 Sep 2024 04:10:27 UTC \| Sectigo 'Mammoth2024h2' \| Qualified 06 Sep 2024 04:10:27 UTC \| DigiCert Yeti2024 Log \| Qualified
Fingerprints
SHA1	944800e5f1d1cb40007de38ca860d9eb38b8ceb8
SHA256	e5fd21c6f569f680ab32ae12310c52b137d09d9a4455675747eba51e1deb1cd2
SPKI SHA256	0d073b9b73b4b0ee16e3f580e521c7b6c7aa20a48a764a758e1b31dff5043d90

Intermediate certificate

R10 | 9d7c3f1
Not After: 12 Mar 2027 23:59:59 UTC (expires in 2 years 4 months)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Subject DN	CN=R10, O=Let's Encrypt, C=US
Subject Key Identifier	bbbcc347a5e4bca9c6c3a4720c108da235e1c8e8
Serial	4ba85293f79a2fa273064ba8048d75d0
Not Before	13 Mar 2024 00:00:00 UTC
Not After	12 Mar 2027 23:59:59 UTC
Validity period	1095 days
Key Usage	digitalSignature, keyCertSign, cRLSign
Extended Key Usage	clientAuth, serverAuth
Issuer
Issuer DN	CN=ISRG Root X1, O=Internet Security Research Group, C=US
Certification Authority	Let's Encrypt
Validation Type	Not Applicable
Authority Key Identifier	keyid:79b459e67bb6e5e40173800888c81a58f6e99b6e
Parent Certificate	http://x1.i.lencr.org/
CRL	http://x1.c.lencr.org/
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	00abefd055f9a9c784ffdeabd1dcdd8fed741436
SHA256	9d7c3f1aa6ad2b2ec0d5cf1e246f8d9ae6cbc9fd0755ad37bb974b1f2fb603f3
SPKI SHA256	2bbad93ab5c79279ec121507f272cbe0c6647a3aae52e22f388afab426b4adba

Root certificate

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

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

Analysis

Certificate chain is correct

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

SMTP TLS Reporting

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

Test passed

Everything seems to be well configured. Well done.

TLS-RPT Policy

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

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://forwardemail.net/

1

http://forwardemail.net/

HTTP/1.1 301 Moved Permanently

Location	https://forwardemail.net/
Date	Fri, 25 Oct 2024 22:06:20 GMT
Connection	keep-alive
Keep-Alive	timeout=5
Transfer-Encoding	chunked

2

https://forwardemail.net/

HTTP/1.1 301 Moved Permanently

X-Request-Id	404dc05c-ff93-4556-af49-7193d02dd0f6
X-XSS-Protection	0
X-CSP-Nonce	a59b3cb1dcb5784c77374c435d84e7e5
Content-Security-Policy	default-src 'self' https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-a59b3cb1dcb5784c77374c435d84e7e5'; connect-src 'self' data: https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-a59b3cb1dcb5784c77374c435d84e7e5' https://www.paypal.com https://noembed.com; font-src 'self' data: https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-a59b3cb1dcb5784c77374c435d84e7e5'; img-src 'self' data: https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-a59b3cb1dcb5784c77374c435d84e7e5' https://badge.hardenize.com https://tracking.qa.paypal.com https://www.paypalobjects.com https://github.com https://.github.com https://githubusercontent.com https://.githubusercontent.com https://shields.io https://.shields.io https://ytimg.com https://.ytimg.com; style-src 'self' data: https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-a59b3cb1dcb5784c77374c435d84e7e5' 'unsafe-inline' https://www.paypal.com https://challenges.cloudflare.com; script-src 'self' https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-a59b3cb1dcb5784c77374c435d84e7e5' 'unsafe-inline' https://challenges.cloudflare.com https://www.paypal.com; object-src 'none'; frame-ancestors 'self'; frame-src 'self' data: https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-a59b3cb1dcb5784c77374c435d84e7e5' https://www.youtube.com https://*.youtube-nocookie.com https://challenges.cloudflare.com https://www.paypal.com; report-uri https://forwardemail.net/report; base-uri 'self'; form-action 'self' https://www.namecheap.com https://login.ubuntu.com
X-DNS-Prefetch-Control	off
X-Frame-Options	SAMEORIGIN
Strict-Transport-Security	max-age=31557600; includeSubDomains; preload
X-Download-Options	noopen
X-Content-Type-Options	nosniff
Referrer-Policy	same-origin
Content-Language	en
Location	/en
Content-Type	text/html; charset=utf-8
Content-Length	37
X-Response-Time	148.755ms
Date	Fri, 25 Oct 2024 22:06:20 GMT
Connection	keep-alive

3

https://forwardemail.net/en

HTTP/1.1 200 OK

X-Request-Id	d022673a-e5d8-4677-a382-83af55a48991
X-XSS-Protection	0
Content-Security-Policy	default-src 'self' https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-991a227dea80a70056c1a3e44d2e5a16'; connect-src 'self' data: https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-991a227dea80a70056c1a3e44d2e5a16' https://www.paypal.com https://noembed.com; font-src 'self' data: https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-991a227dea80a70056c1a3e44d2e5a16'; img-src 'self' data: https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-991a227dea80a70056c1a3e44d2e5a16' https://badge.hardenize.com https://tracking.qa.paypal.com https://www.paypalobjects.com https://github.com https://.github.com https://githubusercontent.com https://.githubusercontent.com https://shields.io https://.shields.io https://ytimg.com https://.ytimg.com; style-src 'self' data: https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-991a227dea80a70056c1a3e44d2e5a16' 'unsafe-inline' https://www.paypal.com https://challenges.cloudflare.com; script-src 'self' https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-991a227dea80a70056c1a3e44d2e5a16' 'unsafe-inline' https://challenges.cloudflare.com https://www.paypal.com; object-src 'none'; frame-ancestors 'self'; frame-src 'self' data: https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-991a227dea80a70056c1a3e44d2e5a16' https://www.youtube.com https://*.youtube-nocookie.com https://challenges.cloudflare.com https://www.paypal.com; report-uri https://forwardemail.net/report; base-uri 'self'; form-action 'self' https://www.namecheap.com https://login.ubuntu.com
X-DNS-Prefetch-Control	off
X-Frame-Options	SAMEORIGIN
Strict-Transport-Security	max-age=31557600; includeSubDomains; preload
X-Download-Options	noopen
X-Content-Type-Options	nosniff
Referrer-Policy	same-origin
Content-Language	en
Set-Cookie	locale=en; path=/; expires=Sat, 26 Oct 2024 22:06:20 GMT; samesite=lax; secure; httponly
Set-Cookie	locale.sig=7KSTPLTadnyU856kb97usovZo5M; path=/; expires=Sat, 26 Oct 2024 22:06:20 GMT; samesite=lax; secure; httponly
Set-Cookie	lad.sid=0768d386772389f6852e236543faec1a; path=/; expires=Sat, 26 Oct 2024 22:06:20 GMT; samesite=lax; secure; httponly
Set-Cookie	lad.sid.sig=Uux39tNMgrVgy-7z8Oz8gWV8vGE; path=/; expires=Sat, 26 Oct 2024 22:06:20 GMT; samesite=lax; secure; httponly
Vary	Origin, Accept-Encoding, X-Requested-With
X-RateLimit-Remaining	999
X-RateLimit-Reset	1729894040
X-RateLimit-Limit	1000
Link	<https://forwardemail.net/en>; rel="canonical"
Content-Type	text/html; charset=utf-8
X-Response-Time	49.241ms
Date	Fri, 25 Oct 2024 22:06:20 GMT
Connection	keep-alive
Transfer-Encoding	chunked

Analysis

Same-host permanent redirection

This is a little-bit unusual. There's a permanent redirection from a root to a specific path on the same site. This may cause problems if the subpath ever changes. A temporary redirection is more appropriate in this case.

From: https://forwardemail.net/

To: https://forwardemail.net/en

HTTP redirects to HTTPS

Good. This plaintext HTTP server redirects to HTTPS.

URL: http://www.forwardemail.net/

1

http://www.forwardemail.net/

HTTP/1.1 301 Moved Permanently

Date	Fri, 25 Oct 2024 22:06:21 GMT
Content-Type	text/html
Content-Length	167
Connection	keep-alive
Cache-Control	max-age=3600
Expires	Fri, 25 Oct 2024 23:06:21 GMT
Location	https://forwardemail.net
Vary	Accept-Encoding
Server	cloudflare
CF-RAY	8d8583667ce98017-IAD

2

https://forwardemail.net

HTTP/1.1 301 Moved Permanently

X-Request-Id	dec1cd02-f92c-48af-a0b2-53661cc0f5ae
X-XSS-Protection	0
X-CSP-Nonce	f5c757673c41d6821f78aa4d37bcf117
Content-Security-Policy	default-src 'self' https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-f5c757673c41d6821f78aa4d37bcf117'; connect-src 'self' data: https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-f5c757673c41d6821f78aa4d37bcf117' https://www.paypal.com https://noembed.com; font-src 'self' data: https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-f5c757673c41d6821f78aa4d37bcf117'; img-src 'self' data: https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-f5c757673c41d6821f78aa4d37bcf117' https://badge.hardenize.com https://tracking.qa.paypal.com https://www.paypalobjects.com https://github.com https://.github.com https://githubusercontent.com https://.githubusercontent.com https://shields.io https://.shields.io https://ytimg.com https://.ytimg.com; style-src 'self' data: https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-f5c757673c41d6821f78aa4d37bcf117' 'unsafe-inline' https://www.paypal.com https://challenges.cloudflare.com; script-src 'self' https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-f5c757673c41d6821f78aa4d37bcf117' 'unsafe-inline' https://challenges.cloudflare.com https://www.paypal.com; object-src 'none'; frame-ancestors 'self'; frame-src 'self' data: https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-f5c757673c41d6821f78aa4d37bcf117' https://www.youtube.com https://*.youtube-nocookie.com https://challenges.cloudflare.com https://www.paypal.com; report-uri https://forwardemail.net/report; base-uri 'self'; form-action 'self' https://www.namecheap.com https://login.ubuntu.com
X-DNS-Prefetch-Control	off
X-Frame-Options	SAMEORIGIN
Strict-Transport-Security	max-age=31557600; includeSubDomains; preload
X-Download-Options	noopen
X-Content-Type-Options	nosniff
Referrer-Policy	same-origin
Content-Language	en
Location	/en
Content-Type	text/html; charset=utf-8
Content-Length	37
X-Response-Time	3.715ms
Date	Fri, 25 Oct 2024 22:06:21 GMT
Connection	keep-alive

3

https://forwardemail.net/en

HTTP/1.1 200 OK

X-Request-Id	b4f9f4b2-b541-45b1-b3ad-e04e71aa3cb2
X-XSS-Protection	0
Content-Security-Policy	default-src 'self' https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-dfc963dce52a24776bc83c8e4fc0ec32'; connect-src 'self' data: https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-dfc963dce52a24776bc83c8e4fc0ec32' https://www.paypal.com https://noembed.com; font-src 'self' data: https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-dfc963dce52a24776bc83c8e4fc0ec32'; img-src 'self' data: https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-dfc963dce52a24776bc83c8e4fc0ec32' https://badge.hardenize.com https://tracking.qa.paypal.com https://www.paypalobjects.com https://github.com https://.github.com https://githubusercontent.com https://.githubusercontent.com https://shields.io https://.shields.io https://ytimg.com https://.ytimg.com; style-src 'self' data: https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-dfc963dce52a24776bc83c8e4fc0ec32' 'unsafe-inline' https://www.paypal.com https://challenges.cloudflare.com; script-src 'self' https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-dfc963dce52a24776bc83c8e4fc0ec32' 'unsafe-inline' https://challenges.cloudflare.com https://www.paypal.com; object-src 'none'; frame-ancestors 'self'; frame-src 'self' data: https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-dfc963dce52a24776bc83c8e4fc0ec32' https://www.youtube.com https://*.youtube-nocookie.com https://challenges.cloudflare.com https://www.paypal.com; report-uri https://forwardemail.net/report; base-uri 'self'; form-action 'self' https://www.namecheap.com https://login.ubuntu.com
X-DNS-Prefetch-Control	off
X-Frame-Options	SAMEORIGIN
Strict-Transport-Security	max-age=31557600; includeSubDomains; preload
X-Download-Options	noopen
X-Content-Type-Options	nosniff
Referrer-Policy	same-origin
Content-Language	en
Set-Cookie	locale=en; path=/; expires=Sat, 26 Oct 2024 22:06:21 GMT; samesite=lax; secure; httponly
Set-Cookie	locale.sig=7KSTPLTadnyU856kb97usovZo5M; path=/; expires=Sat, 26 Oct 2024 22:06:21 GMT; samesite=lax; secure; httponly
Set-Cookie	lad.sid=dc8f8265f52ddd788021b25c46428a4c; path=/; expires=Sat, 26 Oct 2024 22:06:21 GMT; samesite=lax; secure; httponly
Set-Cookie	lad.sid.sig=0gA3vZnfM06fcu_m3BgAKVnfXRk; path=/; expires=Sat, 26 Oct 2024 22:06:21 GMT; samesite=lax; secure; httponly
Vary	Origin, Accept-Encoding, X-Requested-With
X-RateLimit-Remaining	999
X-RateLimit-Reset	1729894041
X-RateLimit-Limit	1000
Link	<https://forwardemail.net/en>; rel="canonical"
Content-Type	text/html; charset=utf-8
X-Response-Time	50.090ms
Date	Fri, 25 Oct 2024 22:06:21 GMT
Connection	keep-alive
Transfer-Encoding	chunked

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://forwardemail.net/

1

https://forwardemail.net/

HTTP/1.1 301 Moved Permanently

X-Request-Id	52e88909-7a95-4726-b61f-bca5532021b5
X-XSS-Protection	0
X-CSP-Nonce	78c1fee47aa8641384f36412c5d183ab
Content-Security-Policy	default-src 'self' https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-78c1fee47aa8641384f36412c5d183ab'; connect-src 'self' data: https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-78c1fee47aa8641384f36412c5d183ab' https://www.paypal.com https://noembed.com; font-src 'self' data: https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-78c1fee47aa8641384f36412c5d183ab'; img-src 'self' data: https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-78c1fee47aa8641384f36412c5d183ab' https://badge.hardenize.com https://tracking.qa.paypal.com https://www.paypalobjects.com https://github.com https://.github.com https://githubusercontent.com https://.githubusercontent.com https://shields.io https://.shields.io https://ytimg.com https://.ytimg.com; style-src 'self' data: https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-78c1fee47aa8641384f36412c5d183ab' 'unsafe-inline' https://www.paypal.com https://challenges.cloudflare.com; script-src 'self' https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-78c1fee47aa8641384f36412c5d183ab' 'unsafe-inline' https://challenges.cloudflare.com https://www.paypal.com; object-src 'none'; frame-ancestors 'self'; frame-src 'self' data: https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-78c1fee47aa8641384f36412c5d183ab' https://www.youtube.com https://*.youtube-nocookie.com https://challenges.cloudflare.com https://www.paypal.com; report-uri https://forwardemail.net/report; base-uri 'self'; form-action 'self' https://www.namecheap.com https://login.ubuntu.com
X-DNS-Prefetch-Control	off
X-Frame-Options	SAMEORIGIN
Strict-Transport-Security	max-age=31557600; includeSubDomains; preload
X-Download-Options	noopen
X-Content-Type-Options	nosniff
Referrer-Policy	same-origin
Content-Language	en
Location	/en
Content-Type	text/html; charset=utf-8
Content-Length	37
X-Response-Time	5.229ms
Date	Fri, 25 Oct 2024 22:06:22 GMT
Connection	keep-alive

2

https://forwardemail.net/en

HTTP/1.1 200 OK

X-Request-Id	05e01e4e-838e-4b45-9d0f-e4e408e36b7d
X-XSS-Protection	0
Content-Security-Policy	default-src 'self' https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-a2ee73793986ab4576ff5b1f96a62db5'; connect-src 'self' data: https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-a2ee73793986ab4576ff5b1f96a62db5' https://www.paypal.com https://noembed.com; font-src 'self' data: https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-a2ee73793986ab4576ff5b1f96a62db5'; img-src 'self' data: https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-a2ee73793986ab4576ff5b1f96a62db5' https://badge.hardenize.com https://tracking.qa.paypal.com https://www.paypalobjects.com https://github.com https://.github.com https://githubusercontent.com https://.githubusercontent.com https://shields.io https://.shields.io https://ytimg.com https://.ytimg.com; style-src 'self' data: https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-a2ee73793986ab4576ff5b1f96a62db5' 'unsafe-inline' https://www.paypal.com https://challenges.cloudflare.com; script-src 'self' https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-a2ee73793986ab4576ff5b1f96a62db5' 'unsafe-inline' https://challenges.cloudflare.com https://www.paypal.com; object-src 'none'; frame-ancestors 'self'; frame-src 'self' data: https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-a2ee73793986ab4576ff5b1f96a62db5' https://www.youtube.com https://*.youtube-nocookie.com https://challenges.cloudflare.com https://www.paypal.com; report-uri https://forwardemail.net/report; base-uri 'self'; form-action 'self' https://www.namecheap.com https://login.ubuntu.com
X-DNS-Prefetch-Control	off
X-Frame-Options	SAMEORIGIN
Strict-Transport-Security	max-age=31557600; includeSubDomains; preload
X-Download-Options	noopen
X-Content-Type-Options	nosniff
Referrer-Policy	same-origin
Content-Language	en
Set-Cookie	locale=en; path=/; expires=Sat, 26 Oct 2024 22:06:22 GMT; samesite=lax; secure; httponly
Set-Cookie	locale.sig=7KSTPLTadnyU856kb97usovZo5M; path=/; expires=Sat, 26 Oct 2024 22:06:22 GMT; samesite=lax; secure; httponly
Set-Cookie	lad.sid=7ca4170d222f391781d2ee98e37a81d3; path=/; expires=Sat, 26 Oct 2024 22:06:22 GMT; samesite=lax; secure; httponly
Set-Cookie	lad.sid.sig=P3U1doOWndW-or-rHx5jhgziCjg; path=/; expires=Sat, 26 Oct 2024 22:06:22 GMT; samesite=lax; secure; httponly
Vary	Origin, Accept-Encoding, X-Requested-With
X-RateLimit-Remaining	998
X-RateLimit-Reset	1729894042
X-RateLimit-Limit	1000
Link	<https://forwardemail.net/en>; rel="canonical"
Content-Type	text/html; charset=utf-8
X-Response-Time	38.080ms
Date	Fri, 25 Oct 2024 22:06:22 GMT
Connection	keep-alive
Transfer-Encoding	chunked

Analysis

Same-host permanent redirection

This is a little-bit unusual. There's a permanent redirection from a root to a specific path on the same site. This may cause problems if the subpath ever changes. A temporary redirection is more appropriate in this case.

From: https://forwardemail.net/

To: https://forwardemail.net/en

URL: https://www.forwardemail.net/

1

https://www.forwardemail.net/

HTTP/1.1 301 Moved Permanently

Date	Fri, 25 Oct 2024 22:06:23 GMT
Content-Type	text/html
Content-Length	167
Connection	keep-alive
Cache-Control	max-age=3600
Expires	Fri, 25 Oct 2024 23:06:23 GMT
Location	https://forwardemail.net
Vary	Accept-Encoding
Server	cloudflare
CF-RAY	8d858373d84f5812-IAD

2

https://forwardemail.net

HTTP/1.1 301 Moved Permanently

X-Request-Id	c1fe1b4b-5322-4694-b1a4-200c579e346f
X-XSS-Protection	0
X-CSP-Nonce	3678ae7da2a8f603b67f4e1b4ef57f8f
Content-Security-Policy	default-src 'self' https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-3678ae7da2a8f603b67f4e1b4ef57f8f'; connect-src 'self' data: https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-3678ae7da2a8f603b67f4e1b4ef57f8f' https://www.paypal.com https://noembed.com; font-src 'self' data: https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-3678ae7da2a8f603b67f4e1b4ef57f8f'; img-src 'self' data: https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-3678ae7da2a8f603b67f4e1b4ef57f8f' https://badge.hardenize.com https://tracking.qa.paypal.com https://www.paypalobjects.com https://github.com https://.github.com https://githubusercontent.com https://.githubusercontent.com https://shields.io https://.shields.io https://ytimg.com https://.ytimg.com; style-src 'self' data: https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-3678ae7da2a8f603b67f4e1b4ef57f8f' 'unsafe-inline' https://www.paypal.com https://challenges.cloudflare.com; script-src 'self' https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-3678ae7da2a8f603b67f4e1b4ef57f8f' 'unsafe-inline' https://challenges.cloudflare.com https://www.paypal.com; object-src 'none'; frame-ancestors 'self'; frame-src 'self' data: https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-3678ae7da2a8f603b67f4e1b4ef57f8f' https://www.youtube.com https://*.youtube-nocookie.com https://challenges.cloudflare.com https://www.paypal.com; report-uri https://forwardemail.net/report; base-uri 'self'; form-action 'self' https://www.namecheap.com https://login.ubuntu.com
X-DNS-Prefetch-Control	off
X-Frame-Options	SAMEORIGIN
Strict-Transport-Security	max-age=31557600; includeSubDomains; preload
X-Download-Options	noopen
X-Content-Type-Options	nosniff
Referrer-Policy	same-origin
Content-Language	en
Location	/en
Content-Type	text/html; charset=utf-8
Content-Length	37
X-Response-Time	3.902ms
Date	Fri, 25 Oct 2024 22:06:23 GMT
Connection	keep-alive

3

https://forwardemail.net/en

HTTP/1.1 200 OK

X-Request-Id	d78cb677-c53d-4adf-9b14-ce31cae02a0d
X-XSS-Protection	0
Content-Security-Policy	default-src 'self' https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-c562c55f0e16fa1656c77ddf84b843f8'; connect-src 'self' data: https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-c562c55f0e16fa1656c77ddf84b843f8' https://www.paypal.com https://noembed.com; font-src 'self' data: https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-c562c55f0e16fa1656c77ddf84b843f8'; img-src 'self' data: https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-c562c55f0e16fa1656c77ddf84b843f8' https://badge.hardenize.com https://tracking.qa.paypal.com https://www.paypalobjects.com https://github.com https://.github.com https://githubusercontent.com https://.githubusercontent.com https://shields.io https://.shields.io https://ytimg.com https://.ytimg.com; style-src 'self' data: https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-c562c55f0e16fa1656c77ddf84b843f8' 'unsafe-inline' https://www.paypal.com https://challenges.cloudflare.com; script-src 'self' https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-c562c55f0e16fa1656c77ddf84b843f8' 'unsafe-inline' https://challenges.cloudflare.com https://www.paypal.com; object-src 'none'; frame-ancestors 'self'; frame-src 'self' data: https://.forwardemail.net: https://forwardemail.net https://forwardemail.net:* 'nonce-c562c55f0e16fa1656c77ddf84b843f8' https://www.youtube.com https://*.youtube-nocookie.com https://challenges.cloudflare.com https://www.paypal.com; report-uri https://forwardemail.net/report; base-uri 'self'; form-action 'self' https://www.namecheap.com https://login.ubuntu.com
X-DNS-Prefetch-Control	off
X-Frame-Options	SAMEORIGIN
Strict-Transport-Security	max-age=31557600; includeSubDomains; preload
X-Download-Options	noopen
X-Content-Type-Options	nosniff
Referrer-Policy	same-origin
Content-Language	en
Set-Cookie	locale=en; path=/; expires=Sat, 26 Oct 2024 22:06:24 GMT; samesite=lax; secure; httponly
Set-Cookie	locale.sig=7KSTPLTadnyU856kb97usovZo5M; path=/; expires=Sat, 26 Oct 2024 22:06:24 GMT; samesite=lax; secure; httponly
Set-Cookie	lad.sid=28fe0a85f69abc6161f4dfd2fa9966e7; path=/; expires=Sat, 26 Oct 2024 22:06:24 GMT; samesite=lax; secure; httponly
Set-Cookie	lad.sid.sig=PNeQyJZolx2hAZkZDIFV00WZ8zw; path=/; expires=Sat, 26 Oct 2024 22:06:24 GMT; samesite=lax; secure; httponly
Vary	Origin, Accept-Encoding, X-Requested-With
X-RateLimit-Remaining	998
X-RateLimit-Reset	1729894044
X-RateLimit-Limit	1000
Link	<https://forwardemail.net/en>; rel="canonical"
Content-Type	text/html; charset=utf-8
X-Response-Time	54.071ms
Date	Fri, 25 Oct 2024 22:06:24 GMT
Connection	keep-alive
Transfer-Encoding	chunked

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: forwardemail.net (2001:19f0:ac00:41b3:5400:4ff:febb:a905)

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.3 TLS v1.2
Servers should always enforce their own cipher suite preference, as that is the only approach that guarantees that the best possible suite is selected.Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3 Server preference	Suite: TLS_AES_256_GCM_SHA384 Suite ID: 0x1302 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_CHACHA20_POLY1305_SHA256 Suite ID: 0x1303 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_AES_128_GCM_SHA256 Suite ID: 0x1301 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2 Server preference	Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_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_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_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_ARIA_256_GCM_SHA384 Suite ID: 0xc061 Cipher name: ARIA Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_ARIA_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_ARIA_128_GCM_SHA256 Suite ID: 0xc060 Cipher name: ARIA Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_ARIA_128_GCM_SHA256 128 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_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_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_CCM_8 Suite ID: 0xc0a1 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_256_CCM_8 256 bits Suite: TLS_RSA_WITH_AES_256_CCM Suite ID: 0xc09d Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_256_CCM 256 bits Suite: TLS_RSA_WITH_ARIA_256_GCM_SHA384 Suite ID: 0xc051 Cipher name: ARIA Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA384 TLS_RSA_WITH_ARIA_256_GCM_SHA384 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_CCM_8 Suite ID: 0xc0a0 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_128_CCM_8 128 bits Suite: TLS_RSA_WITH_AES_128_CCM Suite ID: 0xc09c Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_128_CCM 128 bits Suite: TLS_RSA_WITH_ARIA_128_GCM_SHA256 Suite ID: 0xc050 Cipher name: ARIA Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_ARIA_128_GCM_SHA256 128 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 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_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_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

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

DHE suites not supported

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

TLS Configuration: www.forwardemail.net (2606:4700:20:0:0:0:ac43:488e)

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.2 TLS v1.1 TLS v1.0
Servers should always enforce their own cipher suite preference, as that is the only approach that guarantees that the best possible suite is selected.Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.2 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
Shows cipher suite configuration for this protocol version.TLS v1.1 Server preference	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_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_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_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_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_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
Shows cipher suite configuration for this protocol version.TLS v1.0 Server preference	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_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_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_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_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_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_RSA_WITH_3DES_EDE_CBC_SHA Suite ID: 0xa Cipher name: 3DES (WEAK) Cipher strength: 112 bits Cipher block size: 64 bits (WEAK) Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_3DES_EDE_CBC_SHA 112 bits
Signed Certificate Timestamps	TLS \| 23 Oct 2024 00:14:09 UTC \| Google 'Argon2025h1' log \| Qualified TLS \| 23 Oct 2024 00:14:04 UTC \| Google 'Xenon2025h1' log \| Qualified

Analysis

Deprecated protocols supported

TLS 1.0 and TLS 1.1 are deprecated protocols that should be disabled if possible. TLS 1.0, in particular, is a weak older protocol that has many weaknesses. Sites that aim at a wide audience might still need to support TLS 1.0 for the time being, because many older clients don't support newer protocol versions. Sites with a modern user base might be able to disable TLS 1.0 even now. We recommend that you enable logging of encryption parameters, after which you can examine your protocol usage and make a decision with confidence. As of July 2018, PCI DSS doesn't allow use of TLS 1.0. Exceptions apply in some cases.

TLS 1.3 not supported

TLS 1.3 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. This version of TLS should be the main protocol used with modern clients.

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.

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

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

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

SCT transports: CERT, TLS

DHE suites not supported

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

TLS Configuration: www.forwardemail.net (2606:4700:20:0:0:0:681a:2b2)

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.2 TLS v1.1 TLS v1.0
Servers should always enforce their own cipher suite preference, as that is the only approach that guarantees that the best possible suite is selected.Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.2 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
Shows cipher suite configuration for this protocol version.TLS v1.1 Server preference	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_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_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_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_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_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
Shows cipher suite configuration for this protocol version.TLS v1.0 Server preference	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_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_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_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_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_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_RSA_WITH_3DES_EDE_CBC_SHA Suite ID: 0xa Cipher name: 3DES (WEAK) Cipher strength: 112 bits Cipher block size: 64 bits (WEAK) Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_3DES_EDE_CBC_SHA 112 bits
Signed Certificate Timestamps	TLS \| 23 Oct 2024 00:14:09 UTC \| Google 'Argon2025h1' log \| Qualified TLS \| 23 Oct 2024 00:14:04 UTC \| Google 'Xenon2025h1' log \| Qualified

Analysis

Deprecated protocols supported

TLS 1.0 and TLS 1.1 are deprecated protocols that should be disabled if possible. TLS 1.0, in particular, is a weak older protocol that has many weaknesses. Sites that aim at a wide audience might still need to support TLS 1.0 for the time being, because many older clients don't support newer protocol versions. Sites with a modern user base might be able to disable TLS 1.0 even now. We recommend that you enable logging of encryption parameters, after which you can examine your protocol usage and make a decision with confidence. As of July 2018, PCI DSS doesn't allow use of TLS 1.0. Exceptions apply in some cases.

TLS 1.3 not supported

TLS 1.3 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. This version of TLS should be the main protocol used with modern clients.

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.

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

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

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

SCT transports: CERT, TLS

DHE suites not supported

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

TLS Configuration: forwardemail.net (144.202.105.188)

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.3 TLS v1.2
Servers should always enforce their own cipher suite preference, as that is the only approach that guarantees that the best possible suite is selected.Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3 Server preference	Suite: TLS_AES_256_GCM_SHA384 Suite ID: 0x1302 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_CHACHA20_POLY1305_SHA256 Suite ID: 0x1303 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_AES_128_GCM_SHA256 Suite ID: 0x1301 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2 Server preference	Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_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_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_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_ARIA_256_GCM_SHA384 Suite ID: 0xc061 Cipher name: ARIA Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_ARIA_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_ARIA_128_GCM_SHA256 Suite ID: 0xc060 Cipher name: ARIA Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_ARIA_128_GCM_SHA256 128 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_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_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_CCM_8 Suite ID: 0xc0a1 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_256_CCM_8 256 bits Suite: TLS_RSA_WITH_AES_256_CCM Suite ID: 0xc09d Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_256_CCM 256 bits Suite: TLS_RSA_WITH_ARIA_256_GCM_SHA384 Suite ID: 0xc051 Cipher name: ARIA Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA384 TLS_RSA_WITH_ARIA_256_GCM_SHA384 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_CCM_8 Suite ID: 0xc0a0 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_128_CCM_8 128 bits Suite: TLS_RSA_WITH_AES_128_CCM Suite ID: 0xc09c Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_128_CCM 128 bits Suite: TLS_RSA_WITH_ARIA_128_GCM_SHA256 Suite ID: 0xc050 Cipher name: ARIA Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_ARIA_128_GCM_SHA256 128 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 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_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_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

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

DHE suites not supported

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

TLS Configuration: www.forwardemail.net (2606:4700:20:0:0:0:681a:3b2)

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.2 TLS v1.1 TLS v1.0
Servers should always enforce their own cipher suite preference, as that is the only approach that guarantees that the best possible suite is selected.Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.2 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
Shows cipher suite configuration for this protocol version.TLS v1.1 Server preference	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_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_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_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_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_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
Shows cipher suite configuration for this protocol version.TLS v1.0 Server preference	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_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_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_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_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_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_RSA_WITH_3DES_EDE_CBC_SHA Suite ID: 0xa Cipher name: 3DES (WEAK) Cipher strength: 112 bits Cipher block size: 64 bits (WEAK) Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_3DES_EDE_CBC_SHA 112 bits
Signed Certificate Timestamps	TLS \| 23 Oct 2024 00:14:09 UTC \| Google 'Argon2025h1' log \| Qualified TLS \| 23 Oct 2024 00:14:04 UTC \| Google 'Xenon2025h1' log \| Qualified

Analysis

Deprecated protocols supported

TLS 1.0 and TLS 1.1 are deprecated protocols that should be disabled if possible. TLS 1.0, in particular, is a weak older protocol that has many weaknesses. Sites that aim at a wide audience might still need to support TLS 1.0 for the time being, because many older clients don't support newer protocol versions. Sites with a modern user base might be able to disable TLS 1.0 even now. We recommend that you enable logging of encryption parameters, after which you can examine your protocol usage and make a decision with confidence. As of July 2018, PCI DSS doesn't allow use of TLS 1.0. Exceptions apply in some cases.

TLS 1.3 not supported

TLS 1.3 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. This version of TLS should be the main protocol used with modern clients.

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.

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

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

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

SCT transports: CERT, TLS

DHE suites not supported

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

TLS Configuration: www.forwardemail.net (104.26.3.178)

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.2 TLS v1.1 TLS v1.0
Servers should always enforce their own cipher suite preference, as that is the only approach that guarantees that the best possible suite is selected.Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.2 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
Shows cipher suite configuration for this protocol version.TLS v1.1 Server preference	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_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_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_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_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_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
Shows cipher suite configuration for this protocol version.TLS v1.0 Server preference	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_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_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_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_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_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_RSA_WITH_3DES_EDE_CBC_SHA Suite ID: 0xa Cipher name: 3DES (WEAK) Cipher strength: 112 bits Cipher block size: 64 bits (WEAK) Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_3DES_EDE_CBC_SHA 112 bits
Signed Certificate Timestamps	TLS \| 23 Oct 2024 00:14:09 UTC \| Google 'Argon2025h1' log \| Qualified TLS \| 23 Oct 2024 00:14:04 UTC \| Google 'Xenon2025h1' log \| Qualified

Analysis

Deprecated protocols supported

TLS 1.0 and TLS 1.1 are deprecated protocols that should be disabled if possible. TLS 1.0, in particular, is a weak older protocol that has many weaknesses. Sites that aim at a wide audience might still need to support TLS 1.0 for the time being, because many older clients don't support newer protocol versions. Sites with a modern user base might be able to disable TLS 1.0 even now. We recommend that you enable logging of encryption parameters, after which you can examine your protocol usage and make a decision with confidence. As of July 2018, PCI DSS doesn't allow use of TLS 1.0. Exceptions apply in some cases.

TLS 1.3 not supported

TLS 1.3 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. This version of TLS should be the main protocol used with modern clients.

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.

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

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

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

SCT transports: CERT, TLS

DHE suites not supported

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

TLS Configuration: www.forwardemail.net (104.26.2.178)

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.2 TLS v1.1 TLS v1.0
Servers should always enforce their own cipher suite preference, as that is the only approach that guarantees that the best possible suite is selected.Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.2 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
Shows cipher suite configuration for this protocol version.TLS v1.1 Server preference	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_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_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_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_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_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
Shows cipher suite configuration for this protocol version.TLS v1.0 Server preference	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_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_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_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_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_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_RSA_WITH_3DES_EDE_CBC_SHA Suite ID: 0xa Cipher name: 3DES (WEAK) Cipher strength: 112 bits Cipher block size: 64 bits (WEAK) Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_3DES_EDE_CBC_SHA 112 bits
Signed Certificate Timestamps	TLS \| 23 Oct 2024 00:14:09 UTC \| Google 'Argon2025h1' log \| Qualified TLS \| 23 Oct 2024 00:14:04 UTC \| Google 'Xenon2025h1' log \| Qualified

Analysis

Deprecated protocols supported

TLS 1.0 and TLS 1.1 are deprecated protocols that should be disabled if possible. TLS 1.0, in particular, is a weak older protocol that has many weaknesses. Sites that aim at a wide audience might still need to support TLS 1.0 for the time being, because many older clients don't support newer protocol versions. Sites with a modern user base might be able to disable TLS 1.0 even now. We recommend that you enable logging of encryption parameters, after which you can examine your protocol usage and make a decision with confidence. As of July 2018, PCI DSS doesn't allow use of TLS 1.0. Exceptions apply in some cases.

TLS 1.3 not supported

TLS 1.3 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. This version of TLS should be the main protocol used with modern clients.

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.

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

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

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

SCT transports: CERT, TLS

DHE suites not supported

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

TLS Configuration: www.forwardemail.net (172.67.72.142)

Encryption protocol version determines what features are available for negotiation between client and server.Supported protocols	TLS v1.2 TLS v1.1 TLS v1.0
Servers should always enforce their own cipher suite preference, as that is the only approach that guarantees that the best possible suite is selected.Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.2 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
Shows cipher suite configuration for this protocol version.TLS v1.1 Server preference	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_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_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_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_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_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
Shows cipher suite configuration for this protocol version.TLS v1.0 Server preference	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_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_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_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_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_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_RSA_WITH_3DES_EDE_CBC_SHA Suite ID: 0xa Cipher name: 3DES (WEAK) Cipher strength: 112 bits Cipher block size: 64 bits (WEAK) Cipher mode: CBC Key exchange: RSA Key exchange strength: 2048 bits Forward secrecy: No (WEAK) PRF: SHA TLS_RSA_WITH_3DES_EDE_CBC_SHA 112 bits
Signed Certificate Timestamps	TLS \| 23 Oct 2024 00:14:09 UTC \| Google 'Argon2025h1' log \| Qualified TLS \| 23 Oct 2024 00:14:04 UTC \| Google 'Xenon2025h1' log \| Qualified

Analysis

Deprecated protocols supported

TLS 1.0 and TLS 1.1 are deprecated protocols that should be disabled if possible. TLS 1.0, in particular, is a weak older protocol that has many weaknesses. Sites that aim at a wide audience might still need to support TLS 1.0 for the time being, because many older clients don't support newer protocol versions. Sites with a modern user base might be able to disable TLS 1.0 even now. We recommend that you enable logging of encryption parameters, after which you can examine your protocol usage and make a decision with confidence. As of July 2018, PCI DSS doesn't allow use of TLS 1.0. Exceptions apply in some cases.

TLS 1.3 not supported

TLS 1.3 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. This version of TLS should be the main protocol used with modern clients.

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.

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

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

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

SCT transports: CERT, TLS

DHE suites not supported

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

WWW Certificates

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

Test passed

Everything seems to be well configured. Well done.

Certificate: www.forwardemail.net

Leaf certificate

forwardemail.net
Issuer: Let's Encrypt
Not Before: 22 Oct 2024 23:15:12 UTC
Not After: 20 Jan 2025 23:15:11 UTC (expires in 2 months 26 days)
Key: RSA 2048 bits
Signature: SHA256withRSA
View details

Names	*.forwardemail.net forwardemail.net
Subject DN	CN=forwardemail.net
Subject Key Identifier	57dadfb90ac005c9b93e4a3c3adb8773e73003fe
Serial	3fd53e01aa3f0d26dd60bb268ed6cadcc84
Not Before	22 Oct 2024 23:15:12 UTC
Not After	20 Jan 2025 23:15:11 UTC
Validity period	90 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=R11, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:c5cf46a4eaf4c3c07a6c95c42db05e922f26e3b9
Parent Certificate	http://r11.i.lencr.org/
OCSP	http://r11.o.lencr.org
Certificate Transparency
Signed Certificate Timestamps	23 Oct 2024 00:13:42 UTC \| Let's Encrypt 'Oak2025h1' \| Qualified 23 Oct 2024 00:13:42 UTC \| Google 'Xenon2025h1' log \| Qualified
Fingerprints
SHA1	8fbed7ea400f855e27b508c1dee8bd8cb0ce7ccc
SHA256	c3192f8b9df2859db4ba871db9fab53435f13b7419afa0a335fde4372cb3025f
SPKI SHA256	ff243e1e4cb0b36bb660266d26495929a0afec34d438cdc62760644847b75fbe

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

forwardemail.net | c3192f8
Not After: 20 Jan 2025 23:15:11 UTC (expires in 2 months 26 days)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Names	*.forwardemail.net forwardemail.net
Subject DN	CN=forwardemail.net
Subject Key Identifier	57dadfb90ac005c9b93e4a3c3adb8773e73003fe
Serial	3fd53e01aa3f0d26dd60bb268ed6cadcc84
Not Before	22 Oct 2024 23:15:12 UTC
Not After	20 Jan 2025 23:15:11 UTC
Validity period	90 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=R11, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:c5cf46a4eaf4c3c07a6c95c42db05e922f26e3b9
Parent Certificate	http://r11.i.lencr.org/
OCSP	http://r11.o.lencr.org
Certificate Transparency
Signed Certificate Timestamps	23 Oct 2024 00:13:42 UTC \| Let's Encrypt 'Oak2025h1' \| Qualified 23 Oct 2024 00:13:42 UTC \| Google 'Xenon2025h1' log \| Qualified
Fingerprints
SHA1	8fbed7ea400f855e27b508c1dee8bd8cb0ce7ccc
SHA256	c3192f8b9df2859db4ba871db9fab53435f13b7419afa0a335fde4372cb3025f
SPKI SHA256	ff243e1e4cb0b36bb660266d26495929a0afec34d438cdc62760644847b75fbe

Intermediate certificate

R11 | 591e9ce
Not After: 12 Mar 2027 23:59:59 UTC (expires in 2 years 4 months)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Subject DN	CN=R11, O=Let's Encrypt, C=US
Subject Key Identifier	c5cf46a4eaf4c3c07a6c95c42db05e922f26e3b9
Serial	8a7d3e13d62f30ef2386bd29076b34f8
Not Before	13 Mar 2024 00:00:00 UTC
Not After	12 Mar 2027 23:59:59 UTC
Validity period	1095 days
Key Usage	digitalSignature, keyCertSign, cRLSign
Extended Key Usage	clientAuth, serverAuth
Issuer
Issuer DN	CN=ISRG Root X1, O=Internet Security Research Group, C=US
Certification Authority	Let's Encrypt
Validation Type	Not Applicable
Authority Key Identifier	keyid:79b459e67bb6e5e40173800888c81a58f6e99b6e
Parent Certificate	http://x1.i.lencr.org/
CRL	http://x1.c.lencr.org/
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	696db3af0dffc17e65c6a20d925c5a7bd24dec7e
SHA256	591e9ce6c863d3a079e9fabe1478c7339a26b21269dde795211361024ae31a44
SPKI SHA256	6ddac18698f7f1f7e1c69b9bce420d974ac6f94ca8b2c761701623f99c767dc7

Root certificate

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

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

Analysis

Certificate chain is correct

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

Certificate: www.forwardemail.net

Leaf certificate

forwardemail.net
Issuer: Let's Encrypt
Not Before: 22 Oct 2024 23:15:33 UTC
Not After: 20 Jan 2025 23:15:32 UTC (expires in 2 months 26 days)
Key: EC 256 bits
Signature: SHA384withECDSA
View details

Names	*.forwardemail.net forwardemail.net
Subject DN	CN=forwardemail.net
Subject Key Identifier	54e82115583ab526a175f1734faa3dfc299a0edc
Serial	35683af5eea3688aff405978342d943ccc6
Not Before	22 Oct 2024 23:15:33 UTC
Not After	20 Jan 2025 23:15:32 UTC
Validity period	90 days
Key Usage	digitalSignature
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=E5, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:9f2b5fcf3c214f9d04b7ed2b2cc4c6708bd2d70d
Parent Certificate	http://e5.i.lencr.org/
OCSP	http://e5.o.lencr.org
Certificate Transparency
Signed Certificate Timestamps	23 Oct 2024 00:14:03 UTC \| DigiCert Nessie2025 Log \| Qualified 23 Oct 2024 00:14:03 UTC \| Sectigo 'Mammoth2025h1' \| Qualified
Fingerprints
SHA1	919f4b7b1c27b881798d3184ab59540938d70be4
SHA256	5bc27f7a11da29ec3fe413a93af3181b5acf51a5a6d2f1c7d20dd858ccbf557a
SPKI SHA256	e78f909d858856e0b891acf0a35acaef59ef0e9d1fb8790313fd02e5325e8a6a

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

forwardemail.net | 5bc27f7
Not After: 20 Jan 2025 23:15:32 UTC (expires in 2 months 26 days)
Authentication: EC 256 bits (SHA384withECDSA)
View details

Names	*.forwardemail.net forwardemail.net
Subject DN	CN=forwardemail.net
Subject Key Identifier	54e82115583ab526a175f1734faa3dfc299a0edc
Serial	35683af5eea3688aff405978342d943ccc6
Not Before	22 Oct 2024 23:15:33 UTC
Not After	20 Jan 2025 23:15:32 UTC
Validity period	90 days
Key Usage	digitalSignature
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=E5, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:9f2b5fcf3c214f9d04b7ed2b2cc4c6708bd2d70d
Parent Certificate	http://e5.i.lencr.org/
OCSP	http://e5.o.lencr.org
Certificate Transparency
Signed Certificate Timestamps	23 Oct 2024 00:14:03 UTC \| DigiCert Nessie2025 Log \| Qualified 23 Oct 2024 00:14:03 UTC \| Sectigo 'Mammoth2025h1' \| Qualified
Fingerprints
SHA1	919f4b7b1c27b881798d3184ab59540938d70be4
SHA256	5bc27f7a11da29ec3fe413a93af3181b5acf51a5a6d2f1c7d20dd858ccbf557a
SPKI SHA256	e78f909d858856e0b891acf0a35acaef59ef0e9d1fb8790313fd02e5325e8a6a

Intermediate certificate

E5 | 5dfdb3c
Not After: 12 Mar 2027 23:59:59 UTC (expires in 2 years 4 months)
Authentication: EC 384 bits (SHA256withRSA)
View details

Subject DN	CN=E5, O=Let's Encrypt, C=US
Subject Key Identifier	9f2b5fcf3c214f9d04b7ed2b2cc4c6708bd2d70d
Serial	838f6c63ceb1398c6206628315c9fdde
Not Before	13 Mar 2024 00:00:00 UTC
Not After	12 Mar 2027 23:59:59 UTC
Validity period	1095 days
Key Usage	digitalSignature, keyCertSign, cRLSign
Extended Key Usage	clientAuth, serverAuth
Issuer
Issuer DN	CN=ISRG Root X1, O=Internet Security Research Group, C=US
Certification Authority	Let's Encrypt
Validation Type	Not Applicable
Authority Key Identifier	keyid:79b459e67bb6e5e40173800888c81a58f6e99b6e
Parent Certificate	http://x1.i.lencr.org/
CRL	http://x1.c.lencr.org/
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	5f28d9c589ee4bf31a11b78c72b8d13f079ddc45
SHA256	5dfdb3cf31b26f23d87c09f3a0cef642f64069a9fb7cfe29270bb5dc0f1e16bb
SPKI SHA256	3586d4ecf070578cbd27aedce20b964e48bc149faeb9dad72f46b857869172b8

Root certificate

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

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

Analysis

Certificate chain is correct

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

Certificate: forwardemail.net

Leaf certificate

*.forwardemail.net
Issuer: Sectigo
Not Before: 02 Nov 2023 00:00:00 UTC
Not After: 02 Dec 2024 23:59:59 UTC (expires in 1 month 7 days)
Key: RSA 2048 bits
Signature: SHA256withRSA
View details

Names	*.forwardemail.net forwardemail.net
Subject DN	CN=*.forwardemail.net
Subject Key Identifier	2dda91bc2a403f6a166c94bd74511519841eeb39
Serial	7da17d2650bdd12d6d0931598274cb6f
Not Before	02 Nov 2023 00:00:00 UTC
Not After	02 Dec 2024 23:59:59 UTC
Validity period	397 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=Sectigo RSA Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, ST=Greater Manchester, C=GB
Certification Authority	Sectigo
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:8d8c5ec454ad8ae177e99bf99b05e1b8018d61e1
Parent Certificate	http://crt.sectigo.com/SectigoRSADomainValidationSecureServerCA.crt
OCSP	http://ocsp.sectigo.com
Certificate Transparency
Signed Certificate Timestamps	02 Nov 2023 21:13:19 UTC \| Google 'Xenon2024' log \| Qualified 02 Nov 2023 21:13:19 UTC \| Let's Encrypt 'Oak2024H2' log \| Qualified 02 Nov 2023 21:13:19 UTC \| Google 'Argon2024' log \| Qualified
Fingerprints
SHA1	981960d9b3efe1ebc2e6eb18dea6dba10df12b22
SHA256	57baf3bfcc4cf7821c8361a242601ad3bf44214364e8a614923704fb2a07ebcb
SPKI SHA256	5e81da1af16df20b13e667ad6d9c2b65b95bfcd95150caffe7116c1707b4dd2c

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

*.forwardemail.net | 57baf3b
Not After: 02 Dec 2024 23:59:59 UTC (expires in 1 month 7 days)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Names	*.forwardemail.net forwardemail.net
Subject DN	CN=*.forwardemail.net
Subject Key Identifier	2dda91bc2a403f6a166c94bd74511519841eeb39
Serial	7da17d2650bdd12d6d0931598274cb6f
Not Before	02 Nov 2023 00:00:00 UTC
Not After	02 Dec 2024 23:59:59 UTC
Validity period	397 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=Sectigo RSA Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, ST=Greater Manchester, C=GB
Certification Authority	Sectigo
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:8d8c5ec454ad8ae177e99bf99b05e1b8018d61e1
Parent Certificate	http://crt.sectigo.com/SectigoRSADomainValidationSecureServerCA.crt
OCSP	http://ocsp.sectigo.com
Certificate Transparency
Signed Certificate Timestamps	02 Nov 2023 21:13:19 UTC \| Google 'Xenon2024' log \| Qualified 02 Nov 2023 21:13:19 UTC \| Let's Encrypt 'Oak2024H2' log \| Qualified 02 Nov 2023 21:13:19 UTC \| Google 'Argon2024' log \| Qualified
Fingerprints
SHA1	981960d9b3efe1ebc2e6eb18dea6dba10df12b22
SHA256	57baf3bfcc4cf7821c8361a242601ad3bf44214364e8a614923704fb2a07ebcb
SPKI SHA256	5e81da1af16df20b13e667ad6d9c2b65b95bfcd95150caffe7116c1707b4dd2c

Intermediate certificate

Sectigo RSA Domain Validation Secure Server CA | 7fa4ff6
Not After: 31 Dec 2030 23:59:59 UTC (expires in 6 years 2 months)
Authentication: RSA 2048 bits (SHA384withRSA)
View details

Subject DN	CN=Sectigo RSA Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, ST=Greater Manchester, C=GB
Subject Key Identifier	8d8c5ec454ad8ae177e99bf99b05e1b8018d61e1
Serial	7d5b5126b476ba11db74160bbc530da7
Not Before	02 Nov 2018 00:00:00 UTC
Not After	31 Dec 2030 23:59:59 UTC
Key Usage	digitalSignature, keyCertSign, cRLSign
Extended Key Usage	serverAuth, clientAuth
Issuer
Issuer DN	CN=USERTrust RSA Certification Authority, O=The USERTRUST Network, L=Jersey City, ST=New Jersey, C=US
Certification Authority	Sectigo
Validation Type	Not Applicable
Authority Key Identifier	keyid:5379bf5aaa2b4acf5480e1d89bc09df2b20366cb
Parent Certificate	http://crt.usertrust.com/USERTrustRSAAddTrustCA.crt
CRL	http://crl.usertrust.com/USERTrustRSACertificationAuthority.crl
OCSP	http://ocsp.usertrust.com
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	33e4e80807204c2b6182a3a14b591acd25b5f0db
SHA256	7fa4ff68ec04a99d7528d5085f94907f4d1dd1c5381bacdc832ed5c960214676
SPKI SHA256	e1ae9c3de848ece1ba72e0d991ae4d0d9ec547c6bad1dddab9d6beb0a7e0e0d8

Intermediate certificate

USERTrust RSA Certification Authority | 68b9c76
Not After: 31 Dec 2028 23:59:59 UTC (expires in 4 years 2 months)
Authentication: RSA 4096 bits (SHA384withRSA)
View details

Subject DN	CN=USERTrust RSA Certification Authority, O=The USERTRUST Network, L=Jersey City, ST=New Jersey, C=US
Subject Key Identifier	5379bf5aaa2b4acf5480e1d89bc09df2b20366cb
Serial	3972443af922b751d7d36c10dd313595
Not Before	12 Mar 2019 00:00:00 UTC
Not After	31 Dec 2028 23:59:59 UTC
Key Usage	digitalSignature, keyCertSign, cRLSign
Issuer
Issuer DN	CN=AAA Certificate Services, O=Comodo CA Limited, L=Salford, ST=Greater Manchester, C=GB
Certification Authority	Sectigo
Validation Type	Not Applicable
Authority Key Identifier	keyid:a0110a233e96f107ece2af29ef82a57fd030a4b4
CRL	http://crl.comodoca.com/AAACertificateServices.crl
OCSP	http://ocsp.comodoca.com
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	d89e3bd43d5d909b47a18977aa9d5ce36cee184c
SHA256	68b9c761219a5b1f0131784474665db61bbdb109e00f05ca9f74244ee5f5f52b
SPKI SHA256	c784333d20bcd742b9fdc3236f4e509b8937070e73067e254dd3bf9c45bf4dde

Root certificate

AAA Certificate Services | d7a7a0f
Not After: 31 Dec 2028 23:59:59 UTC (expires in 4 years 2 months)
Authentication: RSA 2048 bits (SHA1withRSA)
View details

Subject DN	CN=AAA Certificate Services, O=Comodo CA Limited, L=Salford, ST=Greater Manchester, C=GB
Subject Key Identifier	a0110a233e96f107ece2af29ef82a57fd030a4b4
Serial	1
Not Before	01 Jan 2004 00:00:00 UTC
Not After	31 Dec 2028 23:59:59 UTC
Key Usage	keyCertSign, cRLSign
Issuer
Issuer DN	CN=AAA Certificate Services, O=Comodo CA Limited, L=Salford, ST=Greater Manchester, C=GB
Certification Authority	Sectigo
Validation Type	Self-signed
CRL	http://crl.comodoca.com/AAACertificateServices.crl http://crl.comodo.net/AAACertificateServices.crl
CA certificate	Yes (pathlen unlimited)
Fingerprints
SHA1	d1eb23a46d17d68fd92564c2f1f1601764d8e349
SHA256	d7a7a0fb5d7e2731d771e9484ebcdef71d5f0c3e0a2948782bc83ee0ea699ef4
SPKI SHA256	bd153ed7b0434f6886b17bce8bbe84ed340c7132d702a8f4fa318f756ecbd6f3

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.

Test passed

Everything seems to be well configured. Well done.

TLSA Record #1: _443._tcp.forwardemail.net.

Specifies which certificate in the chain is being pinned and how validation should be performed.Certificate Usage	Domain-issued certificate / DANE-EE (3)
Determines if the association is made with a certificate or with a public key (via its SPKI structure).Selector	SPKI structure (1)
Determines how matching is done; directly or via a hash. Matching Type	SHA2-256 (1)
Contains the data necessary to perform the matching. Data	5e81da1af16df20b13e667ad6d9c2b65b95bfcd95150caffe7116c1707b4dd2c Leaf certificate: RSA 2048 bits Subject: CN=.forwardemail.net Issuer: CN=Sectigo RSA Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, ST=Greater Manchester, C=GB .forwardemail.net (RSA 2048 bits)

Analysis

DANE configuration matches

DANE configuration is present for this service and matches the certificate chain.

Valid DANE configuration

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

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

Cookie value. As far as the cookie RFC is concerned, the value is an opaque string which only the application should interpret.Value	en
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 (forwardemail.net)
Cookie path. This field can't be used as security measure, but it could be of use to avoid cookie name collision in non-adversarial contexts.Path	/
Cookies are designed to always expire. Session cookies are truly ephemeral and remain cached until the browser is closed. The Expires and Max-Age cookie attributes can be used to specify that a cookie should stay alive for longer.Expires	Sat Oct 26 22:06:24 UTC 2024 (23 hours 59 minutes)
The HttpOnly flag prevents the cookie from being accessed from JavaScript, thus making them more difficult to obtain after a successful XSS attack.HttpOnly
The Secure flag signals to browsers that the cookie should be transmitted only over an encrypted channel.Secure
Normally, when a browser makes a request to a web site, it sends all associated cookies. This is not always desirable, because it might allow third-party sites to perform site actions under the identity of the user. This attack is known as Cross-Site Request Forgery. With SameSite cookies (still in development, but already supported in some browsers), you can choose to be more strict. The possible values are 'lax' and 'strict'.SameSite	lax

Analysis

Cookie is secure

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

HTTP Cookie: locale.sig

Cookie value. As far as the cookie RFC is concerned, the value is an opaque string which only the application should interpret.Value	7KSTPLTadnyU856kb97usovZo5M
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 (forwardemail.net)
Cookie path. This field can't be used as security measure, but it could be of use to avoid cookie name collision in non-adversarial contexts.Path	/
Cookies are designed to always expire. Session cookies are truly ephemeral and remain cached until the browser is closed. The Expires and Max-Age cookie attributes can be used to specify that a cookie should stay alive for longer.Expires	Sat Oct 26 22:06:24 UTC 2024 (23 hours 59 minutes)
The HttpOnly flag prevents the cookie from being accessed from JavaScript, thus making them more difficult to obtain after a successful XSS attack.HttpOnly
The Secure flag signals to browsers that the cookie should be transmitted only over an encrypted channel.Secure
Normally, when a browser makes a request to a web site, it sends all associated cookies. This is not always desirable, because it might allow third-party sites to perform site actions under the identity of the user. This attack is known as Cross-Site Request Forgery. With SameSite cookies (still in development, but already supported in some browsers), you can choose to be more strict. The possible values are 'lax' and 'strict'.SameSite	lax

Analysis

Cookie is secure

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

HTTP Cookie: lad.sid

Cookie value. As far as the cookie RFC is concerned, the value is an opaque string which only the application should interpret.Value	28fe0a85f69abc6161f4dfd2fa9966e7
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 (forwardemail.net)
Cookie path. This field can't be used as security measure, but it could be of use to avoid cookie name collision in non-adversarial contexts.Path	/
Cookies are designed to always expire. Session cookies are truly ephemeral and remain cached until the browser is closed. The Expires and Max-Age cookie attributes can be used to specify that a cookie should stay alive for longer.Expires	Sat Oct 26 22:06:24 UTC 2024 (23 hours 59 minutes)
The HttpOnly flag prevents the cookie from being accessed from JavaScript, thus making them more difficult to obtain after a successful XSS attack.HttpOnly
The Secure flag signals to browsers that the cookie should be transmitted only over an encrypted channel.Secure
Normally, when a browser makes a request to a web site, it sends all associated cookies. This is not always desirable, because it might allow third-party sites to perform site actions under the identity of the user. This attack is known as Cross-Site Request Forgery. With SameSite cookies (still in development, but already supported in some browsers), you can choose to be more strict. The possible values are 'lax' and 'strict'.SameSite	lax

Analysis

Cookie is secure

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

HTTP Cookie: lad.sid.sig

Cookie value. As far as the cookie RFC is concerned, the value is an opaque string which only the application should interpret.Value	PNeQyJZolx2hAZkZDIFV00WZ8zw
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 (forwardemail.net)
Cookie path. This field can't be used as security measure, but it could be of use to avoid cookie name collision in non-adversarial contexts.Path	/
Cookies are designed to always expire. Session cookies are truly ephemeral and remain cached until the browser is closed. The Expires and Max-Age cookie attributes can be used to specify that a cookie should stay alive for longer.Expires	Sat Oct 26 22:06:24 UTC 2024 (23 hours 59 minutes)
The HttpOnly flag prevents the cookie from being accessed from JavaScript, thus making them more difficult to obtain after a successful XSS attack.HttpOnly
The Secure flag signals to browsers that the cookie should be transmitted only over an encrypted channel.Secure
Normally, when a browser makes a request to a web site, it sends all associated cookies. This is not always desirable, because it might allow third-party sites to perform site actions under the identity of the user. This attack is known as Cross-Site Request Forgery. With SameSite cookies (still in development, but already supported in some browsers), you can choose to be more strict. The possible values are 'lax' and 'strict'.SameSite	lax

Analysis

Cookie is secure

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

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.

0 script(s)
0 out of 0 are secure

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

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

Encryption of Outbound Links

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

0 link(s)
0 out of 0 are encrypted

HTTP Strict Transport Security

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

Test passed

Everything seems to be well configured. Well done.

HSTS Policy Main host

URL from which this policy was obtained.Location	https://forwardemail.net
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,557,600 seconds (about 1 year 6 hours)
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: forwardemail.net; includeSubDomains=true

HSTS Policy Apex host

URL from which this policy was obtained.Location	https://forwardemail.net/en
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,557,600 seconds (about 1 year 6 hours)
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: forwardemail.net; 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' https://.forwardemail.net: https://forwardemail.net:*
connect-src	'self' data: https://.forwardemail.net: https://forwardemail.net:* 'nonce-c562c55f0e16fa1656c77ddf84b843f8' https://www.paypal.com https://noembed.com
font-src	'self' data: https://.forwardemail.net: https://forwardemail.net:* 'nonce-c562c55f0e16fa1656c77ddf84b843f8'
img-src	'self' data: https://.forwardemail.net: https://forwardemail.net:* 'nonce-c562c55f0e16fa1656c77ddf84b843f8' https://badge.hardenize.com https://tracking.qa.paypal.com https://www.paypalobjects.com https://github.com https://.github.com https://githubusercontent.com https://.githubusercontent.com https://shields.io https://.shields.io https://ytimg.com https://.ytimg.com
style-src	'self' data: https://.forwardemail.net: https://forwardemail.net:* 'nonce-c562c55f0e16fa1656c77ddf84b843f8' This parameter shouldn't be used because it reenables insecure behavior that CSP disables by default.'unsafe-inline' https://www.paypal.com https://challenges.cloudflare.com
script-src	'self' https://.forwardemail.net: https://forwardemail.net:* 'nonce-c562c55f0e16fa1656c77ddf84b843f8' This parameter shouldn't be used because it reenables insecure behavior that CSP disables by default.'unsafe-inline' https://challenges.cloudflare.com https://www.paypal.com
object-src	'none'
frame-ancestors	'self'
frame-src	'self' data: https://.forwardemail.net: https://forwardemail.net:* 'nonce-c562c55f0e16fa1656c77ddf84b843f8' https://www.youtube.com https://*.youtube-nocookie.com https://challenges.cloudflare.com https://www.paypal.com
report-uri	https://forwardemail.net/report
base-uri	'self'
form-action	'self' https://www.namecheap.com https://login.ubuntu.com

Analysis

Inline scripts are allowed

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

Inline styles are allowed

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

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' https://*.forwardemail.net:* https://forwardemail.net https://forwardemail.net:* 'nonce-c562c55f0e16fa1656c77ddf84b843f8'; connect-src 'self' data: https://*.forwardemail.net:* https://forwardemail.net https://forwardemail.net:* 'nonce-c562c55f0e16fa1656c77ddf84b843f8' https://www.paypal.com https://noembed.com; font-src 'self' data: https://*.forwardemail.net:* https://forwardemail.net https://forwardemail.net:* 'nonce-c562c55f0e16fa1656c77ddf84b843f8'; img-src 'self' data: https://*.forwardemail.net:* https://forwardemail.net https://forwardemail.net:* 'nonce-c562c55f0e16fa1656c77ddf84b843f8' https://badge.hardenize.com https://tracking.qa.paypal.com https://www.paypalobjects.com https://github.com https://*.github.com https://githubusercontent.com https://*.githubusercontent.com https://shields.io https://*.shields.io https://ytimg.com https://*.ytimg.com; style-src 'self' data: https://*.forwardemail.net:* https://forwardemail.net https://forwardemail.net:* 'nonce-c562c55f0e16fa1656c77ddf84b843f8' 'unsafe-inline' https://www.paypal.com https://challenges.cloudflare.com; script-src 'self' https://*.forwardemail.net:* https://forwardemail.net https://forwardemail.net:* 'nonce-c562c55f0e16fa1656c77ddf84b843f8' 'unsafe-inline' https://challenges.cloudflare.com https://www.paypal.com; object-src 'none'; frame-ancestors 'self'; frame-src 'self' data: https://*.forwardemail.net:* https://forwardemail.net https://forwardemail.net:* 'nonce-c562c55f0e16fa1656c77ddf84b843f8' https://www.youtube.com https://*.youtube-nocookie.com https://challenges.cloudflare.com https://www.paypal.com; report-uri https://forwardemail.net/report; base-uri 'self'; form-action 'self' https://www.namecheap.com https://login.ubuntu.com

Location: https://forwardemail.net/en

Subresource Integrity

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

Test passed

Everything seems to be well configured. Well done.

No external scripts
SRI not needed

No external stylesheets
SRI not needed

Analysis

No remote resources

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

Expect CT

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

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

Analysis

Deploy Expect-CT to enable reporting

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

Frame Options

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

Test passed

Everything seems to be well configured. Well done.

Analysis

Header information

Name: X-Frame-Options

Value: SAMEORIGIN

Framing allowed from the same origin only

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

XSS Protection

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

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 | forwardemail.net

forwardemail.net

Domain Name System

Email

WWW

DNS Zone

Nameserver Names

Nameserver Addresses

Start of Authority (SOA) Record

Analysis

Backing DNS Queries

DNS Records

DNS Records

Backing DNS Queries

DNSSEC

Analysis

Useful DNSSEC Tools

Certification Authority Authorization

CAA Policy Information

Analysis

Email (SMTP)

Analysis

Email TLS (SMTP)

TLS Configuration: mx1.forwardemail.net (2604:a880:2:d0:0:0:306:1) Cached

Analysis

TLS Configuration: mx1.forwardemail.net (138.197.213.185) Cached

Analysis

TLS Configuration: mx2.forwardemail.net (2604:a880:400:d1:0:0:cd:9001) Cached

Analysis

TLS Configuration: mx2.forwardemail.net (104.248.224.170) Cached

Analysis

Email Certificates (SMTP)

Certificate #1 Cached

Analysis

Certificate Chain

Analysis

Email DANE (SMTP)

DANE: mx1.forwardemail.net (2604:a880:2:d0:0:0:306:1)

Analysis

DANE: mx1.forwardemail.net (138.197.213.185)

Analysis

DANE: mx2.forwardemail.net (2604:a880:400:d1:0:0:cd:9001)

Analysis

DANE: mx2.forwardemail.net (104.248.224.170)

Analysis

SPF

SPF Policy Information Main policy

Analysis

DMARC

DMARC Policy Information

Analysis

MTA Strict Transport Security

MTA-STS Policy Indicator

Analysis

MTA-STS Policy

Analysis

Certificate: mta-sts.forwardemail.net

Analysis

Certificate Chain

Analysis

SMTP TLS Reporting

TLS-RPT Policy

Analysis

HTTP (80)

URL: http://forwardemail.net/

Analysis

URL: http://www.forwardemail.net/

Analysis

HTTP (443)

URL: https://forwardemail.net/

Analysis

URL: https://www.forwardemail.net/

WWW TLS

TLS Configuration: forwardemail.net (2001:19f0:ac00:41b3:5400:4ff:febb:a905)

Analysis

TLS Configuration: www.forwardemail.net (2606:4700:20:0:0:0:ac43:488e)

Analysis

TLS Configuration: www.forwardemail.net (2606:4700:20:0:0:0:681a:2b2)

Analysis

TLS Configuration: forwardemail.net (144.202.105.188)