Hardenize Report: improvmx.com

Web Security Overview

HTTPS

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

For all sites VERY IMPORTANT medium EFFORT

HTTPS Redirection

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

For all sites VERY IMPORTANT low EFFORT

HTTP Strict Transport Security

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

For important sites VERY IMPORTANT medium EFFORT

HSTS Preloaded

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

For important sites VERY IMPORTANT medium EFFORT

Content Security Policy

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

For important sites IMPORTANT high EFFORT

Email Security Overview

STARTTLS

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

For all sites VERY IMPORTANT low EFFORT

SPF

Sender Policy Framework (SPF) enables organizations to designate servers that are allowed to send email messages on their behalf. With SPF in place, spam is easier to identify.
There are issues with this site's SPF configuration.

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
dns200.anycast.me. PRIMARY 46.105.206.200				SOA NS REFERRAL
ns200.anycast.me. 46.105.207.200				NS REFERRAL

Nameserver Addresses

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

Nameserver	Operational	Authoritative	Recursive	UDP	TCP	Sources	Payload Size
46.105.206.200 PRIMARY dns200.anycast.me. PTR: dns200.anycast.me.						NAME	1232
46.105.207.200 ns200.anycast.me. PTR: ns200.anycast.me.						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	dns200.anycast.me.
Email address of the persons responsible for this zone. Also known as RNAME.Admin email	tech.ovh.net.
Zone serial or version number.Serial number	2024042305
The length of time secondary nameservers should wait before querying the primary for changes.Refresh interval	86,400 seconds (about 1 day)
The length of time secondary nameservers should wait before querying an unresponsive primary again.Retry interval	3,600 seconds (about 1 hour)
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	3,600,000 seconds (about 1 month 10 days)
TTL for purposes of negative response caching. Negative cache TTL	300 seconds (about 5 minutes)
Time To Live (TTL) indicates for how long a record remains valid. SOA record TTL	3,600 seconds (about 1 hour)

Analysis

Improve IPv6 support

The Internet is in a slow transition to supporting IPv6 widely. Although at this time it is expected that most recursive DNS servers will use IPv4, adding support for IPv6 will enable transition to networks that use IPv6 exclusively.

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
improvmx.com.	3600	A	75.2.60.5
www.improvmx.com.	3600	CNAME	improvmx.com.
improvmx.com.	3600	CAA	128 issue "letsencrypt.org"
improvmx.com.	3600	CAA	128 iodef "mailto:support@improvmx.com"
improvmx.com.	3600	CAA	0 issue "amazonaws.com"
improvmx.com.	3600	DNSKEY	256 3 8 AwEAAbIkDvYrg5oJjNsNy5zcuz6nSCeFMhcp6vfo0xzaZTvp91Fn11Q9dgUvQy5TmgkLtx5fl2CzZ4zYTalFRaIDrYtlPkUkH79/omBnbvEEIailI5igjtgooDrYpr2QEji9GAD8PNha2AA464HTwiIgRCxW8t2HqFTkBKmWZ8IcFmr7
improvmx.com.	3600	DNSKEY	257 3 8 AwEAAaBSQW89qPoCLqlFPr1I7D/4WPgdJ19twhxZqW0OAq0lIgUzKhKht57EbijxfQgxnG2iBLiA3sPvEaf2g/6pvoqB0Rpi6nc8kPGsekFs/NDU/T8G4I/frHF0EV+v/FNuebtE2Qsf1uKd9r2tGwh0Dnkh1xIhlPPLDZuC6bdyE36/S3X01s9XOZxAkmxAygxKQ3ginH2KfQsdhqj5BsPM6Z6N5Ukzrg6gmEOtaVpuNKiAJdmcmoM0Kq8j/ja5wWwYazLcKShhey+2oV+1r3wEAqb+UJkSV/uEReEOK0QOi027JrLFgo1X0tFc4yLU8a6gGCHIPHFgTcprQLudDxs3Ro8=
improvmx.com.	3600	MX	10 mx1.improvmx.com.
improvmx.com.	3600	MX	20 mx2.improvmx.com.
improvmx.com.	3600	NS	ns200.anycast.me.
improvmx.com.	3600	NS	dns200.anycast.me.
improvmx.com.	3600	SOA	dns200.anycast.me. tech.ovh.net. 2024042305 86400 3600 3600000 300
improvmx.com.	3600	TXT	"stripe-verification=e8ac37e9e40cfa0f29104447026c2ef6437d9a2eb38e02eafad8377ffbf4b786"
improvmx.com.	3600	TXT	"protonmail-verification=8ebc3732f029015ec67ef74571c39f18e3fb4fc0"
improvmx.com.	3600	TXT	"google-site-verification=BMawvces9Rtu2O-iBWhmtbpFWeJlT0UZR0VECWreAwI"
improvmx.com.	3600	TXT	"v=spf1 include:spf.improvmx.com include:customeriomail.com include:mailgun.org include:_spf.protonmail.ch -all"
improvmx.com.	3600	TXT	"google-site-verification=1KSGTdo9WiB9LB5SLVWrriGG22syk-Jz2H808r665yk"
_dmarc.improvmx.com.	3600	TXT	"v=DMARC1; p=quarantine; pct=100; rua=mailto:re+t5suyseanrc@dmarc.postmarkapp.com; sp=none; aspf=r;"
_mta-sts.improvmx.com.	3600	TXT	"v=STSv1; id=20220128T104500;"
_smtp._tls.improvmx.com.	3600	TXT	"v=TLSRPTv1; rua=mailto:support@improvmx.com"

Backing DNS Queries

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

	ID	Server	Question Name	Type	Status

DNSSEC

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

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	improvmx.com
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 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: 128 ; critical
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:support@improvmx.com flags: 128 ; critical

Analysis

CAA policy found

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

Policy uses reporting

Great. 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.improvmx.com 2a05:d012:412:e202:f36:2c1f:1a49:d38a PTR: -	10
mx1.improvmx.com 2a05:d012:412:e201:88aa:e7b9:7a43:12d7 PTR: -	10
mx1.improvmx.com 2a05:d012:412:e203:373a:f51a:4a85:1d25 PTR: -	10
mx1.improvmx.com 35.181.18.45 PTR: ec2-35-181-18-45.eu-west-3.compute.amazonaws.com	10
mx1.improvmx.com 13.37.195.136 PTR: ec2-13-37-195-136.eu-west-3.compute.amazonaws.com	10
mx1.improvmx.com 15.236.236.160 PTR: ec2-15-236-236-160.eu-west-3.compute.amazonaws.com	10
mx2.improvmx.com 2a05:d012:412:e201:1f6e:f6e4:8fd7:4678 PTR: -	20
mx2.improvmx.com 2a05:d012:412:e203:7e33:3d9c:28d7:ee20 PTR: -	20
mx2.improvmx.com 2a05:d012:412:e202:e81e:cc44:3b53:8a3d PTR: -	20
mx2.improvmx.com 13.36.107.63 PTR: ec2-13-36-107-63.eu-west-3.compute.amazonaws.com	20
mx2.improvmx.com 13.36.222.39 PTR: ec2-13-36-222-39.eu-west-3.compute.amazonaws.com	20
mx2.improvmx.com 15.236.61.92 PTR: ec2-15-236-61-92.eu-west-3.compute.amazonaws.com	20

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: 29 Apr 2024 18:28 UTC

Earliest cache timestamp: 29 Apr 2024 18:27 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.improvmx.com (2a05:d012:412:e202:f36:2c1f:1a49:d38a) 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_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 384 bits)
These results have been retrieved from our cache. This row indicates when was that the original test ran.Retrieved from cache	29 Apr 2024 18:27 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.improvmx.com (2a05:d012:412:e201:88aa:e7b9:7a43:12d7) 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_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 384 bits)
These results have been retrieved from our cache. This row indicates when was that the original test ran.Retrieved from cache	29 Apr 2024 18:27 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.improvmx.com (2a05:d012:412:e203:373a:f51a:4a85:1d25) 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_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 384 bits)
These results have been retrieved from our cache. This row indicates when was that the original test ran.Retrieved from cache	29 Apr 2024 18:27 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.improvmx.com (35.181.18.45) 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_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 384 bits)
These results have been retrieved from our cache. This row indicates when was that the original test ran.Retrieved from cache	29 Apr 2024 18:27 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.improvmx.com (13.37.195.136) 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_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 384 bits)
These results have been retrieved from our cache. This row indicates when was that the original test ran.Retrieved from cache	29 Apr 2024 18:27 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.improvmx.com (15.236.236.160) 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_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 384 bits)
These results have been retrieved from our cache. This row indicates when was that the original test ran.Retrieved from cache	29 Apr 2024 18:27 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.improvmx.com (2a05:d012:412:e201:1f6e:f6e4:8fd7:4678) 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_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 384 bits)
These results have been retrieved from our cache. This row indicates when was that the original test ran.Retrieved from cache	29 Apr 2024 18:28 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.improvmx.com (2a05:d012:412:e203:7e33:3d9c:28d7:ee20) 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_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 384 bits)
These results have been retrieved from our cache. This row indicates when was that the original test ran.Retrieved from cache	29 Apr 2024 18:27 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.improvmx.com (2a05:d012:412:e202:e81e:cc44:3b53:8a3d) 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_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 384 bits)
These results have been retrieved from our cache. This row indicates when was that the original test ran.Retrieved from cache	29 Apr 2024 18:27 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.improvmx.com (13.36.107.63) 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_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 384 bits)
These results have been retrieved from our cache. This row indicates when was that the original test ran.Retrieved from cache	29 Apr 2024 18:28 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.improvmx.com (13.36.222.39) 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_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 384 bits)
These results have been retrieved from our cache. This row indicates when was that the original test ran.Retrieved from cache	29 Apr 2024 18:28 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.improvmx.com (15.236.61.92) 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_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC secp384r1 (384 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 384 bits)
These results have been retrieved from our cache. This row indicates when was that the original test ran.Retrieved from cache	29 Apr 2024 18:28 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

mx1.improvmx.com
Issuer: Let's Encrypt
Not Before: 22 Apr 2024 23:03:43 UTC
Not After: 21 Jul 2024 23:03:42 UTC (expires in 2 months 18 days)
Key: RSA 2048 bits
Signature: SHA256withRSA
View details

Names	mx1.improvmx.com
Subject DN	CN=mx1.improvmx.com
Subject Key Identifier	74cedebb54bbc8acba6aa84431564cce6168e3fb
Serial	3cdb006b511f2d8c78463db9f5cff85b32a
Not Before	22 Apr 2024 23:03:43 UTC
Not After	21 Jul 2024 23:03:42 UTC
Validity period	90 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=R3, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:142eb317b75856cbae500940e61faf9d8b14c2c6
Parent Certificate	http://r3.i.lencr.org/
OCSP	http://r3.o.lencr.org
Certificate Transparency
Signed Certificate Timestamps	23 Apr 2024 00:03:43 UTC \| DigiCert Yeti2024 Log \| Qualified 23 Apr 2024 00:03:43 UTC \| Sectigo 'Mammoth2024h2' \| Qualified
Fingerprints
SHA1	545a9e03e40bb2ed902715b58d5f1f7083596422
SHA256	8fb87f4266c449f53fc28921cdb047d0b28dbc1ef33a07de3ee929d634c15895
SPKI SHA256	d77bd40e0772362a9b4cad139688a3306b7a89b825ddc771c4e545a08ddb46ec

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

mx1.improvmx.com | 8fb87f4
Not After: 21 Jul 2024 23:03:42 UTC (expires in 2 months 18 days)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Names	mx1.improvmx.com
Subject DN	CN=mx1.improvmx.com
Subject Key Identifier	74cedebb54bbc8acba6aa84431564cce6168e3fb
Serial	3cdb006b511f2d8c78463db9f5cff85b32a
Not Before	22 Apr 2024 23:03:43 UTC
Not After	21 Jul 2024 23:03:42 UTC
Validity period	90 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=R3, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:142eb317b75856cbae500940e61faf9d8b14c2c6
Parent Certificate	http://r3.i.lencr.org/
OCSP	http://r3.o.lencr.org
Certificate Transparency
Signed Certificate Timestamps	23 Apr 2024 00:03:43 UTC \| DigiCert Yeti2024 Log \| Qualified 23 Apr 2024 00:03:43 UTC \| Sectigo 'Mammoth2024h2' \| Qualified
Fingerprints
SHA1	545a9e03e40bb2ed902715b58d5f1f7083596422
SHA256	8fb87f4266c449f53fc28921cdb047d0b28dbc1ef33a07de3ee929d634c15895
SPKI SHA256	d77bd40e0772362a9b4cad139688a3306b7a89b825ddc771c4e545a08ddb46ec

Intermediate certificate

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

Subject DN	CN=R3, O=Let's Encrypt, C=US
Subject Key Identifier	142eb317b75856cbae500940e61faf9d8b14c2c6
Serial	912b084acf0c18a753f6d62e25a75f5a
Not Before	04 Sep 2020 00:00:00 UTC
Not After	15 Sep 2025 16:00:00 UTC
Validity period	1838 days
Key Usage	digitalSignature, keyCertSign, cRLSign
Extended Key Usage	clientAuth, serverAuth
Issuer
Issuer DN	CN=ISRG Root X1, O=Internet Security Research Group, C=US
Certification Authority	Let's Encrypt
Validation Type	Not Applicable
Authority Key Identifier	keyid:79b459e67bb6e5e40173800888c81a58f6e99b6e
Parent Certificate	http://x1.i.lencr.org/
CRL	http://x1.c.lencr.org/
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	a053375bfe84e8b748782c7cee15827a6af5a405
SHA256	67add1166b020ae61b8f5fc96813c04c2aa589960796865572a3c7e737613dfd
SPKI SHA256	8d02536c887482bc34ff54e41d2ba659bf85b341a0a20afadb5813dcfbcf286d

Root certificate

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

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

Analysis

Certificate chain is correct

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

Certificate #2 Cached

Leaf certificate

mx2.improvmx.com
Issuer: Let's Encrypt
Not Before: 22 Apr 2024 23:04:45 UTC
Not After: 21 Jul 2024 23:04:44 UTC (expires in 2 months 18 days)
Key: RSA 2048 bits
Signature: SHA256withRSA
View details

Names	mx2.improvmx.com
Subject DN	CN=mx2.improvmx.com
Subject Key Identifier	7abfeaf60fe283b344848b415269608e71753029
Serial	48d13a96640a4d0e1c5a1e3766effa05c23
Not Before	22 Apr 2024 23:04:45 UTC
Not After	21 Jul 2024 23:04:44 UTC
Validity period	90 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=R3, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:142eb317b75856cbae500940e61faf9d8b14c2c6
Parent Certificate	http://r3.i.lencr.org/
OCSP	http://r3.o.lencr.org
Certificate Transparency
Signed Certificate Timestamps	23 Apr 2024 00:04:45 UTC \| Let's Encrypt 'Oak2024H2' log \| Qualified 23 Apr 2024 00:04:46 UTC \| Sectigo 'Mammoth2024h2' \| Qualified
Fingerprints
SHA1	15998d85404cfd99e21f7487b57b390ffd97a482
SHA256	631719c65f1a27220b959891758a773b37037b3d4bfb6cefef3548e91a4433f4
SPKI SHA256	d112f7f7bf181aa2b398bbeffb297c7979c189a401201887be95198499f54937

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

mx2.improvmx.com | 631719c
Not After: 21 Jul 2024 23:04:44 UTC (expires in 2 months 18 days)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Names	mx2.improvmx.com
Subject DN	CN=mx2.improvmx.com
Subject Key Identifier	7abfeaf60fe283b344848b415269608e71753029
Serial	48d13a96640a4d0e1c5a1e3766effa05c23
Not Before	22 Apr 2024 23:04:45 UTC
Not After	21 Jul 2024 23:04:44 UTC
Validity period	90 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=R3, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:142eb317b75856cbae500940e61faf9d8b14c2c6
Parent Certificate	http://r3.i.lencr.org/
OCSP	http://r3.o.lencr.org
Certificate Transparency
Signed Certificate Timestamps	23 Apr 2024 00:04:45 UTC \| Let's Encrypt 'Oak2024H2' log \| Qualified 23 Apr 2024 00:04:46 UTC \| Sectigo 'Mammoth2024h2' \| Qualified
Fingerprints
SHA1	15998d85404cfd99e21f7487b57b390ffd97a482
SHA256	631719c65f1a27220b959891758a773b37037b3d4bfb6cefef3548e91a4433f4
SPKI SHA256	d112f7f7bf181aa2b398bbeffb297c7979c189a401201887be95198499f54937

Intermediate certificate

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

Subject DN	CN=R3, O=Let's Encrypt, C=US
Subject Key Identifier	142eb317b75856cbae500940e61faf9d8b14c2c6
Serial	912b084acf0c18a753f6d62e25a75f5a
Not Before	04 Sep 2020 00:00:00 UTC
Not After	15 Sep 2025 16:00:00 UTC
Validity period	1838 days
Key Usage	digitalSignature, keyCertSign, cRLSign
Extended Key Usage	clientAuth, serverAuth
Issuer
Issuer DN	CN=ISRG Root X1, O=Internet Security Research Group, C=US
Certification Authority	Let's Encrypt
Validation Type	Not Applicable
Authority Key Identifier	keyid:79b459e67bb6e5e40173800888c81a58f6e99b6e
Parent Certificate	http://x1.i.lencr.org/
CRL	http://x1.c.lencr.org/
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	a053375bfe84e8b748782c7cee15827a6af5a405
SHA256	67add1166b020ae61b8f5fc96813c04c2aa589960796865572a3c7e737613dfd
SPKI SHA256	8d02536c887482bc34ff54e41d2ba659bf85b341a0a20afadb5813dcfbcf286d

Root certificate

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

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

Analysis

Certificate chain is correct

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

Email DANE (SMTP)

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

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

SPF

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

Test failed

We've detected serious problems that require your immediate attention.

SPF Policy Information Main policy

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

Analysis

SPF policy found

Policy text: v=spf1 include:spf.improvmx.com include:customeriomail.com include:mailgun.org include:_spf.protonmail.ch -all

Location: improvmx.com

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 over limit

Your policy exceeds the allowed number of DNS queries. As a result, parts of it may not be processed by implementations that enforce this limit. Please refer to the SPF specification Section 4.6.4. for more information.

Lookups: 11

SPF Policy Information Included policy

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

SPF Policy Information Included policy

Host where this policy is located.Location	spf4.improvmx.com
SPF version used by this policy.v	spf1
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	51.91.128.110
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	51.91.128.125
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	51.91.67.147
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	51.91.72.73
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	51.255.220.160/27
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	91.134.148.0/27
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	5.39.55.160/27
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	51.77.22.128/27
This policy element always matches. It's normally used at the end of a policy to specify the handling of hosts that don't match earlier mechanisms. -all

SPF Policy Information Included policy

Host where this policy is located.Location	spf6.improvmx.com
SPF version used by this policy.v	spf1
This mechanism tests whether the IP address being tested is contained within a given IPv6 network. ip6	2001:41d0:303:be6e::/64
This mechanism tests whether the IP address being tested is contained within a given IPv6 network. ip6	2001:41d0:303:be7d::/64
This mechanism tests whether the IP address being tested is contained within a given IPv6 network. ip6	2001:41d0:303:c493::/64
This mechanism tests whether the IP address being tested is contained within a given IPv6 network. ip6	2001:41d0:303:c749::/64
This policy element always matches. It's normally used at the end of a policy to specify the handling of hosts that don't match earlier mechanisms. -all

SPF Policy Information Included policy

Host where this policy is located.Location	customeriomail.com
SPF version used by this policy.v	spf1
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	50.31.36.179
Evaluates SPF policy specified in another DNS location. This directive is typically used to allow hosts controlled by another organization. include	sendgrid.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

SPF Policy Information Included policy

Host where this policy is located.Location	sendgrid.net
SPF version used by this policy.v	spf1
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	167.89.0.0/17
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	208.117.48.0/20
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	50.31.32.0/19
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	198.37.144.0/20
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	198.21.0.0/21
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	192.254.112.0/20
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	168.245.0.0/17
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	149.72.0.0/16
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	159.183.0.0/16
Evaluates SPF policy specified in another DNS location. This directive is typically used to allow hosts controlled by another organization. include	ab.sendgrid.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

SPF Policy Information Included policy

Host where this policy is located.Location	ab.sendgrid.net
SPF version used by this policy.v	spf1
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	223.165.113.0/24
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	223.165.115.0/24
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	223.165.118.0/23
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	223.165.120.0/23
This policy element always matches. It's normally used at the end of a policy to specify the handling of hosts that don't match earlier mechanisms. ~all

SPF Policy Information Included policy

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

SPF Policy Information Included policy

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

SPF Policy Information Included policy

Host where this policy is located.Location	_spf.eu.mailgun.org
SPF version used by this policy.v	spf1
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	141.193.32.0/23
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	159.135.140.80/29
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	159.135.132.128/25
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	161.38.204.0/22
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	87.253.232.0/21
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	185.189.236.0/22
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	185.211.120.0/22
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	185.250.236.0/22
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	143.55.236.0/22
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	198.244.60.0/22
This policy element always matches. It's normally used at the end of a policy to specify the handling of hosts that don't match earlier mechanisms. ~all

SPF Policy Information Included policy

Host where this policy is located.Location	_spf.protonmail.ch
SPF version used by this policy.v	spf1
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	185.70.40.0/24
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	185.70.41.0/24
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	185.70.43.0/24
Evaluates SPF policy specified in another DNS location. This directive is typically used to allow hosts controlled by another organization. include	_spf2.protonmail.ch
This policy element always matches. It's normally used at the end of a policy to specify the handling of hosts that don't match earlier mechanisms. ~all

SPF Policy Information Included policy

Host where this policy is located.Location	_spf2.protonmail.ch
SPF version used by this policy.v	spf1
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	51.89.119.103
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	91.134.188.129
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	51.77.79.158
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	54.38.221.122
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	188.165.51.139
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	54.36.149.183
This policy element always matches. It's normally used at the end of a policy to specify the handling of hosts that don't match earlier mechanisms. ~all

DMARC

Domain-based Message Authentication, Reporting, and Conformance (DMARC) is a scalable mechanism by which a mail-originating organization can express domain-level policies and preferences for message validation, disposition, and reporting, that a mail-receiving organization can use to improve mail handling.

Test passed

Everything seems to be well configured. Well done.

DMARC Policy Information

The location from which we obtained this policy.Policy location	_dmarc.improvmx.com
DMARC version used by this policy.v	DMARC1
Indicates the policy to be enacted by the receiver at the request of the domain owner. Possible values are: none, quarantine, and reject.p	quarantine
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:re+t5suyseanrc@dmarc.postmarkapp.com
Requested mail receiver policy for all subdomains. Same format as for the p tag.sp	none
Indicates whether strict or relaxed SPF alignment mode is required.aspf	r

Analysis

DMARC policy found

Policy: v=DMARC1; p=quarantine; pct=100; rua=mailto:re+t5suyseanrc@dmarc.postmarkapp.com; sp=none; aspf=r;

Host: _dmarc.improvmx.com

Valid external destination

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

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

Permission record contents: v=DMARC1;

Policy is valid

Good. You have a valid DMARC policy.

MTA Strict Transport Security

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

Test passed

Everything seems to be well configured. Well done.

MTA-STS Policy Indicator

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

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

Analysis

MTA-STS policy is valid

Good. Your MTA-STS policy is valid.

Policy host certificate is valid

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

Policy HTTPS response information

Status code: 200

Length: 89 bytes

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

Certificate: mta-sts.improvmx.com

Leaf certificate

mta-sts.improvmx.com
Issuer: Let's Encrypt
Not Before: 18 Mar 2024 09:22:42 UTC
Not After: 16 Jun 2024 09:22:41 UTC (expires in 1 month 12 days)
Key: EC 256 bits
Signature: SHA256withRSA
View details

Names	mta-sts.improvmx.com
Subject DN	CN=mta-sts.improvmx.com
Subject Key Identifier	a6b5ff11ff4b91964d8f5f212c71bd0dfa909164
Serial	3a34e36b71116de17d3b0cd537e919a5fec
Not Before	18 Mar 2024 09:22:42 UTC
Not After	16 Jun 2024 09:22:41 UTC
Validity period	90 days
Key Usage	digitalSignature
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=R3, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:142eb317b75856cbae500940e61faf9d8b14c2c6
Parent Certificate	http://r3.i.lencr.org/
OCSP	http://r3.o.lencr.org
Certificate Transparency
Signed Certificate Timestamps	18 Mar 2024 10:22:42 UTC \| Google 'Argon2024' log \| Qualified 18 Mar 2024 10:22:42 UTC \| Sectigo 'Sabre2024h1' \| Qualified
Fingerprints
SHA1	7ed2e4f323a9b605fa60ec700af26e6ecfb683c9
SHA256	46534560c9f4a4832e9259ff95b45ed4e61e072e2b6041dcc708139c55ff3b15
SPKI SHA256	ca57cba74d35d9a519b1568449fc0d85a668db368c8bf658a7aa6471c21161da

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.improvmx.com | 4653456
Not After: 16 Jun 2024 09:22:41 UTC (expires in 1 month 12 days)
Authentication: EC 256 bits (SHA256withRSA)
View details

Names	mta-sts.improvmx.com
Subject DN	CN=mta-sts.improvmx.com
Subject Key Identifier	a6b5ff11ff4b91964d8f5f212c71bd0dfa909164
Serial	3a34e36b71116de17d3b0cd537e919a5fec
Not Before	18 Mar 2024 09:22:42 UTC
Not After	16 Jun 2024 09:22:41 UTC
Validity period	90 days
Key Usage	digitalSignature
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=R3, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:142eb317b75856cbae500940e61faf9d8b14c2c6
Parent Certificate	http://r3.i.lencr.org/
OCSP	http://r3.o.lencr.org
Certificate Transparency
Signed Certificate Timestamps	18 Mar 2024 10:22:42 UTC \| Google 'Argon2024' log \| Qualified 18 Mar 2024 10:22:42 UTC \| Sectigo 'Sabre2024h1' \| Qualified
Fingerprints
SHA1	7ed2e4f323a9b605fa60ec700af26e6ecfb683c9
SHA256	46534560c9f4a4832e9259ff95b45ed4e61e072e2b6041dcc708139c55ff3b15
SPKI SHA256	ca57cba74d35d9a519b1568449fc0d85a668db368c8bf658a7aa6471c21161da

Intermediate certificate

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

Subject DN	CN=R3, O=Let's Encrypt, C=US
Subject Key Identifier	142eb317b75856cbae500940e61faf9d8b14c2c6
Serial	912b084acf0c18a753f6d62e25a75f5a
Not Before	04 Sep 2020 00:00:00 UTC
Not After	15 Sep 2025 16:00:00 UTC
Validity period	1838 days
Key Usage	digitalSignature, keyCertSign, cRLSign
Extended Key Usage	clientAuth, serverAuth
Issuer
Issuer DN	CN=ISRG Root X1, O=Internet Security Research Group, C=US
Certification Authority	Let's Encrypt
Validation Type	Not Applicable
Authority Key Identifier	keyid:79b459e67bb6e5e40173800888c81a58f6e99b6e
Parent Certificate	http://x1.i.lencr.org/
CRL	http://x1.c.lencr.org/
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	a053375bfe84e8b748782c7cee15827a6af5a405
SHA256	67add1166b020ae61b8f5fc96813c04c2aa589960796865572a3c7e737613dfd
SPKI SHA256	8d02536c887482bc34ff54e41d2ba659bf85b341a0a20afadb5813dcfbcf286d

Root certificate

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

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

Analysis

Certificate chain is correct

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

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

Analysis

SMTP TLS-RPT policy valid

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

HTTP (80)

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

Test passed

Everything seems to be well configured. Well done.

URL: http://improvmx.com/

1

http://improvmx.com/

HTTP/1.1 301 Moved Permanently

Content-Type	text/plain; charset=utf-8
Date	Fri, 03 May 2024 21:08:33 GMT
Location	https://improvmx.com/
Server	Netlify
X-Nf-Request-Id	01HX04K412D4C954TSN4TDV246
Content-Length	36

2

https://improvmx.com/

HTTP/1.1 200 OK

Accept-Ranges	bytes
Age	64712
Cache-Control	public,max-age=0,must-revalidate
Cache-Status	"Netlify Edge"; hit
Content-Type	text/html; charset=UTF-8
Date	Fri, 03 May 2024 21:08:34 GMT
Etag	"ec9e8e5355410553b43b13ab445aab95-ssl-df"
Server	Netlify
Strict-Transport-Security	max-age=31536000
Vary	Accept-Encoding
X-Frame-Options	DENY
X-Nf-Request-Id	01HX04K431DR3VEK6CJHTVHR23
X-Xss-Protection	1; mode=block

Analysis

HTTP redirects to HTTPS

Good. This plaintext HTTP server redirects to HTTPS.

URL: http://www.improvmx.com/

1

http://www.improvmx.com/

HTTP/1.1 301 Moved Permanently

Content-Type	text/plain; charset=utf-8
Date	Fri, 03 May 2024 21:08:34 GMT
Location	https://www.improvmx.com/
Server	Netlify
X-Nf-Request-Id	01HX04K43JXWF5PHD1J908M7MR
Content-Length	40

2

https://www.improvmx.com/

HTTP/1.1 301 Moved Permanently

Content-Type	text/plain; charset=utf-8
Date	Fri, 03 May 2024 21:08:34 GMT
Location	https://improvmx.com/
Server	Netlify
Strict-Transport-Security	max-age=31536000
X-Nf-Request-Id	01HX04K45HRWWJZMJ29Q4SEYAR
Content-Length	36

3

https://improvmx.com/

HTTP/1.1 200 OK

Accept-Ranges	bytes
Age	64712
Cache-Control	public,max-age=0,must-revalidate
Cache-Status	"Netlify Edge"; hit
Content-Type	text/html; charset=UTF-8
Date	Fri, 03 May 2024 21:08:34 GMT
Etag	"ec9e8e5355410553b43b13ab445aab95-ssl-df"
Server	Netlify
Strict-Transport-Security	max-age=31536000
Vary	Accept-Encoding
X-Frame-Options	DENY
X-Nf-Request-Id	01HX04K481J4BK3KEJKE3MDWKV
X-Xss-Protection	1; mode=block

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

1

https://improvmx.com/

HTTP/1.1 200 OK

Accept-Ranges	bytes
Age	64712
Cache-Control	public,max-age=0,must-revalidate
Cache-Status	"Netlify Edge"; hit
Content-Type	text/html; charset=UTF-8
Date	Fri, 03 May 2024 21:08:34 GMT
Etag	"ec9e8e5355410553b43b13ab445aab95-ssl-df"
Server	Netlify
Strict-Transport-Security	max-age=31536000
Vary	Accept-Encoding
X-Frame-Options	DENY
X-Nf-Request-Id	01HX04K4A9JZMHBXPNGH6VH16S
X-Xss-Protection	1; mode=block

URL: https://www.improvmx.com/

1

https://www.improvmx.com/

HTTP/1.1 301 Moved Permanently

Content-Type	text/plain; charset=utf-8
Date	Fri, 03 May 2024 21:08:34 GMT
Location	https://improvmx.com/
Server	Netlify
Strict-Transport-Security	max-age=31536000
X-Nf-Request-Id	01HX04K4CJRVGT873SP5GE6FJM
Content-Length	36

2

https://improvmx.com/

HTTP/1.1 200 OK

Accept-Ranges	bytes
Age	64712
Cache-Control	public,max-age=0,must-revalidate
Cache-Status	"Netlify Edge"; hit
Content-Type	text/html; charset=UTF-8
Date	Fri, 03 May 2024 21:08:34 GMT
Etag	"ec9e8e5355410553b43b13ab445aab95-ssl-df"
Server	Netlify
Strict-Transport-Security	max-age=31536000
Vary	Accept-Encoding
X-Frame-Options	DENY
X-Nf-Request-Id	01HX04K4EC7FSWMPJWDG9AGMVB
X-Xss-Protection	1; mode=block

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: improvmx.com (75.2.60.5)

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

Analysis

TLS 1.3 supported

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

TLS 1.2 supported

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

Deprecated protocols not supported

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

Strong key exchange detected

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

Only strong suites supported

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

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

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

SCT transports: CERT

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

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

SCT transports: CERT

DHE suites not supported

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

TLS Configuration: www.improvmx.com (75.2.60.5)

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

Analysis

TLS 1.3 supported

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

TLS 1.2 supported

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

Deprecated protocols not supported

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

Strong key exchange detected

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

Only strong suites supported

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

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

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

SCT transports: CERT

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

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

SCT transports: CERT

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

Leaf certificate

improv.mx
Issuer: Let's Encrypt
Not Before: 02 May 2024 01:13:15 UTC
Not After: 31 Jul 2024 01:13:14 UTC (expires in 2 months 27 days)
Key: EC 256 bits
Signature: SHA256withRSA
View details

Names	improv.mx improvedmx.com improvemx.co improvemx.com improvemx.net improvmx-mails.com improvmx.com improvmx.net improvmx.org www.improv.mx www.improvedmx.com www.improvemx.co www.improvemx.com www.improvemx.net www.improvmx-mails.com www.improvmx.com www.improvmx.net www.improvmx.org
Subject DN	CN=improv.mx
Subject Key Identifier	8cfce895606fc0f5e56e628c0b6683947a69d65c
Serial	35e6a8c1a7ab49daf03ad42c61351172cca
Not Before	02 May 2024 01:13:15 UTC
Not After	31 Jul 2024 01:13:14 UTC
Validity period	90 days
Key Usage	digitalSignature
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=R3, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:142eb317b75856cbae500940e61faf9d8b14c2c6
Parent Certificate	http://r3.i.lencr.org/
OCSP	http://r3.o.lencr.org
Certificate Transparency
Signed Certificate Timestamps	02 May 2024 02:13:15 UTC \| Sectigo 'Sabre2024h2' \| Qualified 02 May 2024 02:13:15 UTC \| Google 'Xenon2024' log \| Qualified
Fingerprints
SHA1	67a20569f2fcf9a3f981d7c506274773c4ee1221
SHA256	70ec2eeee274bcc55eaea6f51118b1a08f2cac418bd40dc33b690e89374b2907
SPKI SHA256	928d90271df81b9db7f531f9110a4999d1157b397f72394f2193ee506ba2fba6

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

improv.mx | 70ec2ee
Not After: 31 Jul 2024 01:13:14 UTC (expires in 2 months 27 days)
Authentication: EC 256 bits (SHA256withRSA)
View details

Names	improv.mx improvedmx.com improvemx.co improvemx.com improvemx.net improvmx-mails.com improvmx.com improvmx.net improvmx.org www.improv.mx www.improvedmx.com www.improvemx.co www.improvemx.com www.improvemx.net www.improvmx-mails.com www.improvmx.com www.improvmx.net www.improvmx.org
Subject DN	CN=improv.mx
Subject Key Identifier	8cfce895606fc0f5e56e628c0b6683947a69d65c
Serial	35e6a8c1a7ab49daf03ad42c61351172cca
Not Before	02 May 2024 01:13:15 UTC
Not After	31 Jul 2024 01:13:14 UTC
Validity period	90 days
Key Usage	digitalSignature
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=R3, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:142eb317b75856cbae500940e61faf9d8b14c2c6
Parent Certificate	http://r3.i.lencr.org/
OCSP	http://r3.o.lencr.org
Certificate Transparency
Signed Certificate Timestamps	02 May 2024 02:13:15 UTC \| Sectigo 'Sabre2024h2' \| Qualified 02 May 2024 02:13:15 UTC \| Google 'Xenon2024' log \| Qualified
Fingerprints
SHA1	67a20569f2fcf9a3f981d7c506274773c4ee1221
SHA256	70ec2eeee274bcc55eaea6f51118b1a08f2cac418bd40dc33b690e89374b2907
SPKI SHA256	928d90271df81b9db7f531f9110a4999d1157b397f72394f2193ee506ba2fba6

Intermediate certificate

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

Subject DN	CN=R3, O=Let's Encrypt, C=US
Subject Key Identifier	142eb317b75856cbae500940e61faf9d8b14c2c6
Serial	912b084acf0c18a753f6d62e25a75f5a
Not Before	04 Sep 2020 00:00:00 UTC
Not After	15 Sep 2025 16:00:00 UTC
Validity period	1838 days
Key Usage	digitalSignature, keyCertSign, cRLSign
Extended Key Usage	clientAuth, serverAuth
Issuer
Issuer DN	CN=ISRG Root X1, O=Internet Security Research Group, C=US
Certification Authority	Let's Encrypt
Validation Type	Not Applicable
Authority Key Identifier	keyid:79b459e67bb6e5e40173800888c81a58f6e99b6e
Parent Certificate	http://x1.i.lencr.org/
CRL	http://x1.c.lencr.org/
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	a053375bfe84e8b748782c7cee15827a6af5a405
SHA256	67add1166b020ae61b8f5fc96813c04c2aa589960796865572a3c7e737613dfd
SPKI SHA256	8d02536c887482bc34ff54e41d2ba659bf85b341a0a20afadb5813dcfbcf286d

Root certificate

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

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

Analysis

Certificate chain is correct

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

Certificate: improvmx.com

Leaf certificate

improv.mx
Issuer: Let's Encrypt
Not Before: 02 May 2024 01:13:15 UTC
Not After: 31 Jul 2024 01:13:14 UTC (expires in 2 months 27 days)
Key: EC 256 bits
Signature: SHA256withRSA
View details

Names	improv.mx improvedmx.com improvemx.co improvemx.com improvemx.net improvmx-mails.com improvmx.com improvmx.net improvmx.org www.improv.mx www.improvedmx.com www.improvemx.co www.improvemx.com www.improvemx.net www.improvmx-mails.com www.improvmx.com www.improvmx.net www.improvmx.org
Subject DN	CN=improv.mx
Subject Key Identifier	8cfce895606fc0f5e56e628c0b6683947a69d65c
Serial	35e6a8c1a7ab49daf03ad42c61351172cca
Not Before	02 May 2024 01:13:15 UTC
Not After	31 Jul 2024 01:13:14 UTC
Validity period	90 days
Key Usage	digitalSignature
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=R3, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:142eb317b75856cbae500940e61faf9d8b14c2c6
Parent Certificate	http://r3.i.lencr.org/
OCSP	http://r3.o.lencr.org
Certificate Transparency
Signed Certificate Timestamps	02 May 2024 02:13:15 UTC \| Sectigo 'Sabre2024h2' \| Qualified 02 May 2024 02:13:15 UTC \| Google 'Xenon2024' log \| Qualified
Fingerprints
SHA1	67a20569f2fcf9a3f981d7c506274773c4ee1221
SHA256	70ec2eeee274bcc55eaea6f51118b1a08f2cac418bd40dc33b690e89374b2907
SPKI SHA256	928d90271df81b9db7f531f9110a4999d1157b397f72394f2193ee506ba2fba6

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

improv.mx | 70ec2ee
Not After: 31 Jul 2024 01:13:14 UTC (expires in 2 months 27 days)
Authentication: EC 256 bits (SHA256withRSA)
View details

Names	improv.mx improvedmx.com improvemx.co improvemx.com improvemx.net improvmx-mails.com improvmx.com improvmx.net improvmx.org www.improv.mx www.improvedmx.com www.improvemx.co www.improvemx.com www.improvemx.net www.improvmx-mails.com www.improvmx.com www.improvmx.net www.improvmx.org
Subject DN	CN=improv.mx
Subject Key Identifier	8cfce895606fc0f5e56e628c0b6683947a69d65c
Serial	35e6a8c1a7ab49daf03ad42c61351172cca
Not Before	02 May 2024 01:13:15 UTC
Not After	31 Jul 2024 01:13:14 UTC
Validity period	90 days
Key Usage	digitalSignature
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=R3, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:142eb317b75856cbae500940e61faf9d8b14c2c6
Parent Certificate	http://r3.i.lencr.org/
OCSP	http://r3.o.lencr.org
Certificate Transparency
Signed Certificate Timestamps	02 May 2024 02:13:15 UTC \| Sectigo 'Sabre2024h2' \| Qualified 02 May 2024 02:13:15 UTC \| Google 'Xenon2024' log \| Qualified
Fingerprints
SHA1	67a20569f2fcf9a3f981d7c506274773c4ee1221
SHA256	70ec2eeee274bcc55eaea6f51118b1a08f2cac418bd40dc33b690e89374b2907
SPKI SHA256	928d90271df81b9db7f531f9110a4999d1157b397f72394f2193ee506ba2fba6

Intermediate certificate

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

Subject DN	CN=R3, O=Let's Encrypt, C=US
Subject Key Identifier	142eb317b75856cbae500940e61faf9d8b14c2c6
Serial	912b084acf0c18a753f6d62e25a75f5a
Not Before	04 Sep 2020 00:00:00 UTC
Not After	15 Sep 2025 16:00:00 UTC
Validity period	1838 days
Key Usage	digitalSignature, keyCertSign, cRLSign
Extended Key Usage	clientAuth, serverAuth
Issuer
Issuer DN	CN=ISRG Root X1, O=Internet Security Research Group, C=US
Certification Authority	Let's Encrypt
Validation Type	Not Applicable
Authority Key Identifier	keyid:79b459e67bb6e5e40173800888c81a58f6e99b6e
Parent Certificate	http://x1.i.lencr.org/
CRL	http://x1.c.lencr.org/
CA certificate	Yes (pathlen 0)
Fingerprints
SHA1	a053375bfe84e8b748782c7cee15827a6af5a405
SHA256	67add1166b020ae61b8f5fc96813c04c2aa589960796865572a3c7e737613dfd
SPKI SHA256	8d02536c887482bc34ff54e41d2ba659bf85b341a0a20afadb5813dcfbcf286d

Root certificate

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

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

Analysis

Certificate chain is correct

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

DANE (443)

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

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

Cookies

Cookies are small chunks of text that are sent between your browser and a website. They are often essential to the operation of the site and sometimes contain sensitive information. Session cookies sent from secure sites must be explicitly marked as secure to prevent being obtained by active network attackers.

Test passed

Everything seems to be well configured. Well done.

Mixed Content

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

Test passed

Everything seems to be well configured. Well done.

Embedded Resources

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

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

Status	Link
Encrypted	https://improvmx.com/...jquery/jquery.min.js
Encrypted	https://improvmx.com/...query-migrate.min.js
Encrypted	https://improvmx.com/...provmx/js/scripts.js
Encrypted	https://improvmx.com/...ausible/js/script.js
Encrypted	https://improvmx.com/.../improvmx/js/home.js

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

Status	Link
Encrypted	https://improvmx.com/...ibrary/style.min.css
Encrypted	https://improvmx.com/...s/improvmx/style.css

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

Status	Link
Encrypted	https://improvmx.com/...il-forwarding@2x.jpg
Encrypted	https://improvmx.com/...-using-improvemx.svg
Encrypted	https://improvmx.com/...img/danny-postma.jpg
Encrypted	https://improvmx.com/...ovmx/img/help@2x.png
Encrypted	https://www.youtube-nocookie.com/embed/ak8Y4mnuvvc

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.

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

Status	Link
Encrypted	https://app.improvmx.com/
Encrypted	https://getfernand.com/
Encrypted	https://status.improvmx.com/
Encrypted	https://twitter.com/dannypostmaa
Encrypted	https://headshotpro.com/
Encrypted	https://ecologi.com/improvmx

HTTP Strict Transport Security

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

Test passed

Everything seems to be well configured. Well done.

HSTS Policy Main host

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

Analysis

Policy is valid

OK. Your HSTS policy uses correct syntax.

Long policy age

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

No subdomains

This HSTS policy doesn't cover subdomains. Without full coverage, HSTS can't protect from certain cookie attacks that typically allow active network attackers to inject cookies into an application. Additionally, subdomain coverage is one of the requirements to allow preloading.

Preload directive has no effect here

This policy doesn't enable preloading, but that's all right. The preload directive doesn't have any effect unless it's used on an apex hostname.

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.

No parent protection

This host could benefit from further protection if the apex hostname would be configured with a HSTS policy that uses 'includeSubDomains'. Enabling HSTS on an entire domain name is the only approach that provides robust security.

Apex policy activated on every page visit

The homepage of this web site contains a link to a resource on the apex hostname. This approach will ensure that, whenever HSTS is activated on the main site, it's activated on the apex hostname too.

Resource URL: https://improvmx.com/wp-includes/js/jquery/jquery.min.js

HSTS Policy Apex host

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

Analysis

Policy is valid

OK. Your HSTS policy uses correct syntax.

Long policy age

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

No subdomains

This HSTS policy doesn't cover subdomains. Without full coverage, HSTS can't protect from certain cookie attacks that typically allow active network attackers to inject cookies into an application. Additionally, subdomain coverage is one of the requirements to allow preloading.

Preloading not enabled

This policy doesn't give browsers permission to embed it and provide protection even to the first request to the web site. Sites that wish to use preloading can apply at hstspreload.org.

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.

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.

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

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.

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

Status	Link
Local	https://improvmx.com/wp-includes/js/jquery/jquery.min.js
Local	https://improvmx.com/wp-includes/js/jquery/jquery-migrate.min.js
Local	https://improvmx.com/wp-content/themes/improvmx/js/scripts.js
Local	/plausible/js/script.js
Local	/wp-content/themes/improvmx/js/home.js

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

Status	Link
Local	https://improvmx.com/wp-includes/css/dist/block-library/style.min.css
Local	https://improvmx.com/wp-content/themes/improvmx/style.css

Analysis

No remote resources

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

Expect CT

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

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

Analysis

Deploy Expect-CT to enable reporting

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

Frame Options

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

Test passed

Everything seems to be well configured. Well done.

Analysis

Header information

Name: X-Frame-Options

Value: DENY

Framing blocked

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

XSS Protection

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

Test passed, but there are warnings

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

Analysis

Header information

Name: X-Xss-Protection

Value: 1; mode=block

XSS auditor blocking is dangerous

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

Content Type Options

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

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

Public Report | improvmx.com

improvmx.com

Domain Name System

Email

WWW

DNS Zone

Nameserver Names

Nameserver Addresses

Start of Authority (SOA) Record

Analysis

Backing DNS Queries

DNS Records

DNS Records

Backing DNS Queries

DNSSEC

Analysis

Useful DNSSEC Tools

Certification Authority Authorization

CAA Policy Information

Analysis

Email (SMTP)

Analysis

Email TLS (SMTP)

TLS Configuration: mx1.improvmx.com (2a05:d012:412:e202:f36:2c1f:1a49:d38a) Cached

Analysis

TLS Configuration: mx1.improvmx.com (2a05:d012:412:e201:88aa:e7b9:7a43:12d7) Cached

Analysis

TLS Configuration: mx1.improvmx.com (2a05:d012:412:e203:373a:f51a:4a85:1d25) Cached

Analysis

TLS Configuration: mx1.improvmx.com (35.181.18.45) Cached

Analysis

TLS Configuration: mx1.improvmx.com (13.37.195.136) Cached

Analysis

TLS Configuration: mx1.improvmx.com (15.236.236.160) Cached

Analysis

TLS Configuration: mx2.improvmx.com (2a05:d012:412:e201:1f6e:f6e4:8fd7:4678) Cached

Analysis

TLS Configuration: mx2.improvmx.com (2a05:d012:412:e203:7e33:3d9c:28d7:ee20) Cached

Analysis

TLS Configuration: mx2.improvmx.com (2a05:d012:412:e202:e81e:cc44:3b53:8a3d) Cached

Analysis

TLS Configuration: mx2.improvmx.com (13.36.107.63) Cached

Analysis

TLS Configuration: mx2.improvmx.com (13.36.222.39) Cached

Analysis

TLS Configuration: mx2.improvmx.com (15.236.61.92) Cached

Analysis

Email Certificates (SMTP)

Certificate #1 Cached

Analysis

Certificate Chain

Analysis

Certificate #2 Cached

Analysis

Certificate Chain

Analysis

Email DANE (SMTP)

SPF

SPF Policy Information Main policy

Analysis

SPF Policy Information Included policy

SPF Policy Information Included policy

SPF Policy Information Included policy

SPF Policy Information Included policy

SPF Policy Information Included policy

SPF Policy Information Included policy

SPF Policy Information Included policy

SPF Policy Information Included policy

SPF Policy Information Included policy

SPF Policy Information Included policy

SPF Policy Information Included policy

DMARC

DMARC Policy Information

Analysis

MTA Strict Transport Security

MTA-STS Policy Indicator

Analysis

MTA-STS Policy

Analysis

Certificate: mta-sts.improvmx.com