Hardenize Report: simplelogin.io

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

For all sites VERY IMPORTANT medium EFFORT

HTTPS Redirection

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

For all sites VERY IMPORTANT low EFFORT

HTTP Strict Transport Security

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

For important sites VERY IMPORTANT medium EFFORT

HSTS Preloaded

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

For important sites VERY IMPORTANT medium EFFORT

Content Security Policy

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

For important sites IMPORTANT high EFFORT

Email Security Overview

STARTTLS

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

For all sites VERY IMPORTANT low EFFORT

SPF

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

For important sites IMPORTANT low EFFORT

DMARC

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

For important sites IMPORTANT low EFFORT

DNS Zone

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

Test passed

Everything seems to be well configured. Well done.

Nameserver Names

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

Nameserver	Operational	IPv4	IPv6	Sources
kay.ns.cloudflare.com. PRIMARY 108.162.192.125 172.64.32.125 173.245.58.125 2606:4700:50::adf5:3a7d 2803:f800:50::6ca2:c07d 2a06:98c1:50::ac40:207d				NS REFERRAL SOA
marek.ns.cloudflare.com. 108.162.193.202 172.64.33.202 173.245.59.202 2606:4700:58::adf5:3bca 2803:f800:50::6ca2:c1ca 2a06:98c1:50::ac40:21ca				NS REFERRAL

Nameserver Addresses

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

Nameserver	Sources	Payload Size
108.162.192.125 PRIMARY kay.ns.cloudflare.com. PTR: kay.ns.cloudflare.com.	NAME	1232
108.162.193.202 marek.ns.cloudflare.com. PTR: marek.ns.cloudflare.com.	NAME	1232
172.64.32.125 PRIMARY kay.ns.cloudflare.com. PTR: kay.ns.cloudflare.com.	NAME	1232
172.64.33.202 marek.ns.cloudflare.com. PTR: marek.ns.cloudflare.com.	NAME	1232
173.245.58.125 PRIMARY kay.ns.cloudflare.com. PTR: kay.ns.cloudflare.com.	NAME	1232
173.245.59.202 marek.ns.cloudflare.com. PTR: marek.ns.cloudflare.com.	NAME	1232
2606:4700:50::adf5:3a7d PRIMARY kay.ns.cloudflare.com. PTR: kay.ns.cloudflare.com.	NAME	1232
2606:4700:58::adf5:3bca marek.ns.cloudflare.com. PTR: marek.ns.cloudflare.com.	NAME	1232
2803:f800:50::6ca2:c07d PRIMARY kay.ns.cloudflare.com. PTR: kay.ns.cloudflare.com.	NAME	1232
2803:f800:50::6ca2:c1ca marek.ns.cloudflare.com. PTR: marek.ns.cloudflare.com.	NAME	1232
2a06:98c1:50::ac40:207d PRIMARY kay.ns.cloudflare.com. PTR: kay.ns.cloudflare.com.	NAME	1232
2a06:98c1:50::ac40:21ca marek.ns.cloudflare.com. PTR: marek.ns.cloudflare.com.	NAME	1232

Start of Authority (SOA) Record

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

The domain name of the primary nameserver for the zone. Also known as MNAME.Primary nameserver	kay.ns.cloudflare.com.
Email address of the persons responsible for this zone. Also known as RNAME.Admin email	dns.cloudflare.com.
Zone serial or version number.Serial number	-1918998517
The length of time secondary nameservers should wait before querying the primary for changes.Refresh interval	10,000 seconds (about 2 hours 46 minutes)
The length of time secondary nameservers should wait before querying an unresponsive primary again.Retry interval	2,400 seconds (about 40 minutes)
The length of time after which secondary nameservers should stop responding to queries for a zone, assuming no updates were obtained from the primary.Expire interval	604,800 seconds (about 7 days)
TTL for purposes of negative response caching. Negative cache TTL	1,800 seconds (about 30 minutes)
Time To Live (TTL) indicates for how long a record remains valid. SOA record TTL	1,800 seconds (about 30 minutes)

Analysis

No problems detected with the zone configuration

Excellent. This DNS zone is in a good working order. No problems detected.

Backing DNS Queries

Below are all DNS queries we submitted during the zone inspection.

	ID	Server	Transport	Question Name	Type	Status

DNS Records

Correctly functioning name servers are necessary to hold and distribute information that's necessary for your domain name to operate correctly. Examples include converting names to IP addresses, determining where email should go, and so on. More recently, the DNS is being used to communicate email and other security policies.

Test passed

Everything seems to be well configured. Well done.

DNS Records

These are the results of individual DNS queries against your nameserver for common resource record types.

Name	TTL	Type	Data
simplelogin.io.	300	A	176.119.200.11
www.simplelogin.io.	300	CNAME	web.simplelogin.co.
web.simplelogin.co.	300	A	176.119.200.11
simplelogin.io.	3600	CAA	0 issue "pki.goog; cansignhttpexchanges=yes"
simplelogin.io.	3600	CAA	0 issue "ssl.com"
simplelogin.io.	3600	CAA	0 issuewild "comodoca.com"
simplelogin.io.	3600	CAA	0 issuewild "digicert.com; cansignhttpexchanges=yes"
simplelogin.io.	3600	CAA	0 issuewild "letsencrypt.org"
simplelogin.io.	3600	CAA	0 issuewild "pki.goog; cansignhttpexchanges=yes"
simplelogin.io.	3600	CAA	0 issuewild "ssl.com"
simplelogin.io.	3600	CAA	0 issue "comodoca.com"
simplelogin.io.	3600	CAA	0 issue "digicert.com; cansignhttpexchanges=yes"
simplelogin.io.	3600	CAA	0 issue "letsencrypt.org"
simplelogin.io.	3600	DNSKEY	256 3 13 oJMRESz5E4gYzS/q6XDrvU1qMPYIjCWzJaOau8XNEZeqCYKD5ar0IRd8KqXXFJkqmVfRvMGPmM1x8fGAa2XhSA==
simplelogin.io.	3600	DNSKEY	257 3 13 mdsswUyr3DPW132mOi8V9xESWE8jTo0dxCjjnopKl+GqJxpVXckHAeF+KkxLbxILfDLUT0rAK9iUzy1L53eKGQ==
simplelogin.io.	300	MX	20 mx2.simplelogin.co.
simplelogin.io.	300	MX	10 mx1.simplelogin.co.
simplelogin.io.	86400	NS	marek.ns.cloudflare.com.
simplelogin.io.	86400	NS	kay.ns.cloudflare.com.
simplelogin.io.	1800	SOA	kay.ns.cloudflare.com. dns.cloudflare.com. 2375968779 10000 2400 604800 1800
simplelogin.io.	300	TXT	"v=spf1 include:simplelogin.co ~all"
simplelogin.io.	300	TXT	"google-site-verification=eGqgb3ZtWVnG4UDllggiJAF19xcfbdw1GCK3kaXNF6M"
simplelogin.io.	300	TXT	"google-site-verification=edUGaHD3wEFAoHRca08TXT2TaI9ebCRg1NA05JymoWI"
_dmarc.simplelogin.io.	300	TXT	"v=DMARC1; p=reject; sp=none; fo=1; rua=mailto:re+ubyevicmsxt@dmarc.postmarkapp.com; ruf=mailto:dmarc-ruf@simplelogin.co; adkim=r; aspf=r"
_mta-sts.simplelogin.io.	300	TXT	"v=STSv1; id=20200325;"
_smtp._tls.simplelogin.io.	300	TXT	"v=TLSRPTv1;rua=mailto:tlsrpt@simplelogin.io"

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

Analysis

Issuance of S/MIME certificates not restricted

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

Issuance of BIMI not restricted

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

CAA policy restricts issuance

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

Policy doesn't use reporting

This policy doesn't use reporting, which means that there is no way to contact you when a violation is detected. The CAA RFC defines the iodef property that can be used for this purpose. Do note that you're not guaranteed to be notified, given that CAs generally don't support notifications yet.

Email (SMTP)

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

Test passed

Everything seems to be well configured. Well done.

Server

Preference

Operational

STARTTLS

TLS

PKI

DNSSEC

DANE

mx1.simplelogin.co
176.119.200.136
PTR: mx1.simplelogin.co

10

mx2.simplelogin.co
176.119.200.136
PTR: mx1.simplelogin.co

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.

Limited testing of third-party SMTP servers

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

Email TLS (SMTP)

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

Test passed

Everything seems to be well configured. Well done.

TLS Configuration: mx1.simplelogin.co (176.119.200.136)

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 Unknown preference	Suite: TLS_CHACHA20_POLY1305_SHA256 Suite ID: 0x1303 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_AES_128_GCM_SHA256 Suite ID: 0x1301 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_AES_256_GCM_SHA384 Suite ID: 0x1302 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_AES_128_CCM_SHA256 Suite ID: 0x1304 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_AES_128_CCM_SHA256 128 bits (ECDHE 256 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2 Unknown preference	Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA Suite ID: 0xc013 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA Suite ID: 0xc014 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 Suite ID: 0xc027 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 Suite ID: 0xc028 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_ARIA_128_GCM_SHA256 Suite ID: 0xc050 Cipher name: ARIA Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 4096 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_ARIA_128_GCM_SHA256 128 bits Suite: TLS_RSA_WITH_ARIA_256_GCM_SHA384 Suite ID: 0xc051 Cipher name: ARIA Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 4096 bits Forward secrecy: No (WEAK) PRF: SHA384 TLS_RSA_WITH_ARIA_256_GCM_SHA384 256 bits Suite: TLS_ECDHE_RSA_WITH_ARIA_128_GCM_SHA256 Suite ID: 0xc060 Cipher name: ARIA Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_ARIA_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_ARIA_256_GCM_SHA384 Suite ID: 0xc061 Cipher name: ARIA Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_ARIA_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_128_CCM Suite ID: 0xc09c Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 4096 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_128_CCM 128 bits Suite: TLS_RSA_WITH_AES_256_CCM Suite ID: 0xc09d Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 4096 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_256_CCM 256 bits Suite: TLS_RSA_WITH_AES_128_CCM_8 Suite ID: 0xc0a0 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 4096 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_128_CCM_8 128 bits Suite: TLS_RSA_WITH_AES_256_CCM_8 Suite ID: 0xc0a1 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 4096 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_256_CCM_8 256 bits

Analysis

TLS 1.2 supported

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

Server doesn't enforce cipher suite preferences

Servers that don't enforce cipher suite preferences select the first cipher suite they support from the list provided by clients. This approach doesn't guarantee that best-possible cipher suite is negotiated.

Strong key exchange detected

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

Server prefers forward secrecy and authenticated encryption suites

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

Relaxed TLS assessment criteria applied to SMTP on port 25

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

DHE suites not supported

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

TLS Configuration: mx2.simplelogin.co (176.119.200.136)

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 Unknown preference	Suite: TLS_CHACHA20_POLY1305_SHA256 Suite ID: 0x1303 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_AES_128_GCM_SHA256 Suite ID: 0x1301 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_AES_256_GCM_SHA384 Suite ID: 0x1302 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_AES_128_CCM_SHA256 Suite ID: 0x1304 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_AES_128_CCM_SHA256 128 bits (ECDHE 256 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2 Unknown preference	Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA Suite ID: 0xc013 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA Suite ID: 0xc014 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 Suite ID: 0xc027 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 Suite ID: 0xc028 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: CBC Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_ARIA_128_GCM_SHA256 Suite ID: 0xc050 Cipher name: ARIA Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 4096 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_ARIA_128_GCM_SHA256 128 bits Suite: TLS_RSA_WITH_ARIA_256_GCM_SHA384 Suite ID: 0xc051 Cipher name: ARIA Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 4096 bits Forward secrecy: No (WEAK) PRF: SHA384 TLS_RSA_WITH_ARIA_256_GCM_SHA384 256 bits Suite: TLS_ECDHE_RSA_WITH_ARIA_128_GCM_SHA256 Suite ID: 0xc060 Cipher name: ARIA Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_ARIA_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_ARIA_256_GCM_SHA384 Suite ID: 0xc061 Cipher name: ARIA Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_ARIA_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_RSA_WITH_AES_128_CCM Suite ID: 0xc09c Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 4096 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_128_CCM 128 bits Suite: TLS_RSA_WITH_AES_256_CCM Suite ID: 0xc09d Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 4096 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_256_CCM 256 bits Suite: TLS_RSA_WITH_AES_128_CCM_8 Suite ID: 0xc0a0 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 4096 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_128_CCM_8 128 bits Suite: TLS_RSA_WITH_AES_256_CCM_8 Suite ID: 0xc0a1 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: RSA Key exchange strength: 4096 bits Forward secrecy: No (WEAK) PRF: SHA256 TLS_RSA_WITH_AES_256_CCM_8 256 bits

Analysis

TLS 1.2 supported

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

Server doesn't enforce cipher suite preferences

Servers that don't enforce cipher suite preferences select the first cipher suite they support from the list provided by clients. This approach doesn't guarantee that best-possible cipher suite is negotiated.

Strong key exchange detected

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

Server prefers forward secrecy and authenticated encryption suites

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

Relaxed TLS assessment criteria applied to SMTP on port 25

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

DHE suites not supported

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

Email Certificates (SMTP)

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

Test passed

Everything seems to be well configured. Well done.

Certificate #1

Leaf certificate

mx1.simplelogin.co
Issuer: Let's Encrypt
Not Before: 12 Jun 2025 13:12:28 UTC
Not After: 10 Sep 2025 13:12:27 UTC (expires in 2 months 11 days)
Key: RSA 4096 bits
Signature: SHA256withRSA
View details

Names	mx1.simplelogin.co mx2.simplelogin.co
Subject DN	CN=mx1.simplelogin.co
Subject Key Identifier	a1d22b45a3b16e8bd9b3e210456996c1d7426b18
Serial	058f9a68cf42190f913ce5bb3e0abcfe7386
Not Before	12 Jun 2025 13:12:28 UTC
Not After	10 Sep 2025 13:12:27 UTC
Validity period	90 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=R10, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:bbbcc347a5e4bca9c6c3a4720c108da235e1c8e8
Parent Certificate	http://r10.i.lencr.org/
CRL	http://r10.c.lencr.org/7.crl
Certificate Transparency
Signed Certificate Timestamps	12 Jun 2025 14:10:58 UTC \| Google 'Argon2025h2' log \| Qualified 12 Jun 2025 14:11:01 UTC \| Sectigo 'Sabre2025h2' \| Qualified
Fingerprints
SHA1	1d49f688ed6004ff223747606e23a1538e72cbe0
SHA256	ca29d06ee535cd730c76b07709e6a595d61fe28255ff5ad6f016030313436ba9
SPKI SHA256	6b56dc55058100c47bef4bb8020d2a24f907743e0a788911637bfc979a3fcf8d

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.simplelogin.co | ca29d06
Not After: 10 Sep 2025 13:12:27 UTC (expires in 2 months 11 days)
Authentication: RSA 4096 bits (SHA256withRSA)
View details

Names	mx1.simplelogin.co mx2.simplelogin.co
Subject DN	CN=mx1.simplelogin.co
Subject Key Identifier	a1d22b45a3b16e8bd9b3e210456996c1d7426b18
Serial	058f9a68cf42190f913ce5bb3e0abcfe7386
Not Before	12 Jun 2025 13:12:28 UTC
Not After	10 Sep 2025 13:12:27 UTC
Validity period	90 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=R10, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:bbbcc347a5e4bca9c6c3a4720c108da235e1c8e8
Parent Certificate	http://r10.i.lencr.org/
CRL	http://r10.c.lencr.org/7.crl
Certificate Transparency
Signed Certificate Timestamps	12 Jun 2025 14:10:58 UTC \| Google 'Argon2025h2' log \| Qualified 12 Jun 2025 14:11:01 UTC \| Sectigo 'Sabre2025h2' \| Qualified
Fingerprints
SHA1	1d49f688ed6004ff223747606e23a1538e72cbe0
SHA256	ca29d06ee535cd730c76b07709e6a595d61fe28255ff5ad6f016030313436ba9
SPKI SHA256	6b56dc55058100c47bef4bb8020d2a24f907743e0a788911637bfc979a3fcf8d

Intermediate certificate

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

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

Root certificate

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

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

Analysis

Certificate chain is correct

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

Email DANE (SMTP)

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

Test passed

Everything seems to be well configured. Well done.

DANE: mx1.simplelogin.co (176.119.200.136)

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

Specifies which certificate in the chain is being pinned and how validation should be performed.Certificate Usage	Domain-issued certificate / DANE-EE (3)
Determines if the association is made with a certificate or with a public key (via its SPKI structure).Selector	SPKI structure (1)
Determines how matching is done; directly or via a hash. Matching Type	SHA2-256 (1)
Contains the data necessary to perform the matching. Data	6b56dc55058100c47bef4bb8020d2a24f907743e0a788911637bfc979a3fcf8d Leaf certificate: RSA 4096 bits Subject: CN=mx1.simplelogin.co Issuer: CN=R10, O=Let's Encrypt, C=US mx1.simplelogin.co (RSA 4096 bits)

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

Analysis

Valid DANE configuration

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

DANE: mx2.simplelogin.co (176.119.200.136)

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

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

Specifies which certificate in the chain is being pinned and how validation should be performed.Certificate Usage	Domain-issued certificate / DANE-EE (3)
Determines if the association is made with a certificate or with a public key (via its SPKI structure).Selector	SPKI structure (1)
Determines how matching is done; directly or via a hash. Matching Type	SHA2-256 (1)
Contains the data necessary to perform the matching. Data	6b56dc55058100c47bef4bb8020d2a24f907743e0a788911637bfc979a3fcf8d Leaf certificate: RSA 4096 bits Subject: CN=mx1.simplelogin.co Issuer: CN=R10, O=Let's Encrypt, C=US mx1.simplelogin.co (RSA 4096 bits)

Analysis

Valid DANE configuration

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

SPF

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

Test passed

Everything seems to be well configured. Well done.

SPF Policy Information Main policy

Host where this policy is located.Location	simplelogin.io
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	simplelogin.co
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:simplelogin.co ~all

Location: simplelogin.io

SPF policy is valid

Good. Your SPF policy is syntactically valid.

Policy DNS lookups under limit

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

Lookups: 1

SPF Policy Information Included policy

Host where this policy is located.Location	simplelogin.co
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	176.119.200.160/29
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	79.135.107.160/29
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	94.237.111.15
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.simplelogin.io
DMARC version used by this policy.v	DMARC1
Indicates the policy to be enacted by the receiver at the request of the domain owner. Possible values are: none, quarantine, and reject.p	reject
Requested mail receiver policy for all subdomains. Same format as for the p tag.sp	none
Configures failure reporting.fo	1
Addresses to which aggregate feedback is to be sent.rua	mailto:re+ubyevicmsxt@dmarc.postmarkapp.com
Addresses to which message-specific failure information is to be reported.ruf	mailto:dmarc-ruf@simplelogin.co
Indicates whether strict or relaxed DKIM alignment mode is required.adkim	r
Indicates whether strict or relaxed SPF alignment mode is required.aspf	r

Analysis

DMARC policy found

Policy: v=DMARC1; p=reject; sp=none; fo=1; rua=mailto:re+ubyevicmsxt@dmarc.postmarkapp.com; ruf=mailto:dmarc-ruf@simplelogin.co; adkim=r; aspf=r

Host: _dmarc.simplelogin.io

Valid external destination

Permission record location: simplelogin.io._report._dmarc.dmarc.postmarkapp.com

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

Permission record contents: v=DMARC1;

Valid external destination

Permission record location: simplelogin.io._report._dmarc.simplelogin.co

External destination: mailto:dmarc-ruf@simplelogin.co

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.simplelogin.io
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	20200325

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

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

Content-Type: text/plain

Certificate: mta-sts.simplelogin.io

Leaf certificate

*.8alias.com
Issuer: Let's Encrypt
Not Before: 19 May 2025 12:16:16 UTC
Not After: 17 Aug 2025 12:16:15 UTC (expires in 1 month 18 days)
Key: RSA 2048 bits
Signature: SHA256withRSA
View details

Names	.8alias.com .8shield.net .aleeas.com .dralias.com .pass2mail.com .passfwd.com .passinbox.com .passmail.com .passmail.net .silomails.com .simplelogin.co .simplelogin.com .simplelogin.fr .simplelogin.io .slmail.me .slmails.com 8alias.com 8shield.net aleeas.com dralias.com pass2mail.com passfwd.com passinbox.com passmail.com passmail.net silomails.com simplelogin.co simplelogin.com simplelogin.fr simplelogin.io slmail.me slmails.com
Subject DN	CN=*.8alias.com
Subject Key Identifier	e9cb9bbacd62689f812452b57a65e7f5c15f5a37
Serial	06220a8bfd69aca8cd0a4c04d5db69a299f8
Not Before	19 May 2025 12:16:16 UTC
Not After	17 Aug 2025 12:16:15 UTC
Validity period	90 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=R10, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:bbbcc347a5e4bca9c6c3a4720c108da235e1c8e8
Parent Certificate	http://r10.i.lencr.org/
CRL	http://r10.c.lencr.org/121.crl
Certificate Transparency
Signed Certificate Timestamps	19 May 2025 13:14:46 UTC \| Let's Encrypt 'Oak2025h2' \| Qualified 19 May 2025 13:14:48 UTC \| DigiCert 'Sphinx2025h2' Log \| Qualified
Fingerprints
SHA1	1253f0438ba7cd6daf354728341b08a4a81ff328
SHA256	7802866cc30da7a3bf3af317b0e22ac495da016af77805059b82cdce3f7fa642
SPKI SHA256	7b57280de92710a0dc81f82f888f00a930a90add3e627a86a7c574970bae172b

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

*.8alias.com | 7802866
Not After: 17 Aug 2025 12:16:15 UTC (expires in 1 month 18 days)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Names	.8alias.com .8shield.net .aleeas.com .dralias.com .pass2mail.com .passfwd.com .passinbox.com .passmail.com .passmail.net .silomails.com .simplelogin.co .simplelogin.com .simplelogin.fr .simplelogin.io .slmail.me .slmails.com 8alias.com 8shield.net aleeas.com dralias.com pass2mail.com passfwd.com passinbox.com passmail.com passmail.net silomails.com simplelogin.co simplelogin.com simplelogin.fr simplelogin.io slmail.me slmails.com
Subject DN	CN=*.8alias.com
Subject Key Identifier	e9cb9bbacd62689f812452b57a65e7f5c15f5a37
Serial	06220a8bfd69aca8cd0a4c04d5db69a299f8
Not Before	19 May 2025 12:16:16 UTC
Not After	17 Aug 2025 12:16:15 UTC
Validity period	90 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=R10, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:bbbcc347a5e4bca9c6c3a4720c108da235e1c8e8
Parent Certificate	http://r10.i.lencr.org/
CRL	http://r10.c.lencr.org/121.crl
Certificate Transparency
Signed Certificate Timestamps	19 May 2025 13:14:46 UTC \| Let's Encrypt 'Oak2025h2' \| Qualified 19 May 2025 13:14:48 UTC \| DigiCert 'Sphinx2025h2' Log \| Qualified
Fingerprints
SHA1	1253f0438ba7cd6daf354728341b08a4a81ff328
SHA256	7802866cc30da7a3bf3af317b0e22ac495da016af77805059b82cdce3f7fa642
SPKI SHA256	7b57280de92710a0dc81f82f888f00a930a90add3e627a86a7c574970bae172b

Intermediate certificate

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

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

Root certificate

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

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

Analysis

Certificate chain is correct

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

SMTP TLS Reporting

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

Test passed

Everything seems to be well configured. Well done.

TLS-RPT Policy

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

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://simplelogin.io/

1

http://simplelogin.io/

HTTP/1.1 301 Moved Permanently

Server	nginx
Date	Mon, 30 Jun 2025 03:08:44 GMT
Content-Type	text/html
Content-Length	162
Connection	keep-alive
Location	https://simplelogin.io/
X-SL-Protocol	http

2

https://simplelogin.io/

HTTP/1.1 200 OK

Server	nginx
Date	Mon, 30 Jun 2025 03:08:45 GMT
Content-Type	text/html
Last-Modified	Thu, 19 Jun 2025 08:53:11 GMT
Transfer-Encoding	chunked
Connection	keep-alive
Vary	Accept-Encoding
ETag	W/"6853cff7-140af"
Expires	Thu, 01 Jan 1970 00:00:01 GMT
Cache-Control	no-cache
Strict-Transport-Security	max-age=63072000; includeSubDomains; preload
Expect-CT	enforce, max-age=604800, report-uri="https://simplelogin.report-uri.com/r/d/ct/enforce"
X-Frame-Options	SAMEORIGIN
X-Content-Type-Options	nosniff
X-XSS-Protection	1; mode=block
Content-Security-Policy	script-src 'self' 'unsafe-inline' 'unsafe-eval' https://cdn.paddle.com/paddle/paddle.js https://gc.zgo.at/count.js https://hcaptcha.com https://.hcaptcha.com https://plausible.simplelogin.io/js/index.js; child-src 'self' https://hcaptcha.com https://.hcaptcha.com https://.paddle.com https://www.youtube.com https://app.tryhoist.com; style-src 'self' 'unsafe-inline' https://hcaptcha.com https://.hcaptcha.com https://cdn.paddle.com

Analysis

HTTP redirects to HTTPS

Good. This plaintext HTTP server redirects to HTTPS.

URL: http://www.simplelogin.io/

1

http://www.simplelogin.io/

HTTP/1.1 301 Moved Permanently

Server	nginx
Date	Mon, 30 Jun 2025 03:08:45 GMT
Content-Type	text/html
Content-Length	162
Connection	keep-alive
Location	https://www.simplelogin.io/
X-SL-Protocol	http

2

https://www.simplelogin.io/

HTTP/1.1 301 Moved Permanently

Server	nginx
Date	Mon, 30 Jun 2025 03:08:45 GMT
Content-Type	text/html
Content-Length	162
Connection	keep-alive
Location	https://simplelogin.io/
Strict-Transport-Security	max-age=63072000; includeSubDomains; preload
Expect-CT	enforce, max-age=604800, report-uri="https://simplelogin.report-uri.com/r/d/ct/enforce"
Cache-Control	no-store, no-cache, must-revalidate
X-Frame-Options	SAMEORIGIN
X-Content-Type-Options	nosniff
X-XSS-Protection	1; mode=block
Content-Security-Policy	script-src 'self' 'unsafe-inline' 'unsafe-eval' https://cdn.paddle.com/paddle/paddle.js https://gc.zgo.at/count.js https://hcaptcha.com https://.hcaptcha.com https://plausible.simplelogin.io/js/index.js; child-src 'self' https://hcaptcha.com https://.hcaptcha.com https://.paddle.com https://www.youtube.com https://app.tryhoist.com; style-src 'self' 'unsafe-inline' https://hcaptcha.com https://.hcaptcha.com https://cdn.paddle.com

3

https://simplelogin.io/

HTTP/1.1 200 OK

Server	nginx
Date	Mon, 30 Jun 2025 03:08:46 GMT
Content-Type	text/html
Last-Modified	Thu, 19 Jun 2025 08:42:07 GMT
Transfer-Encoding	chunked
Connection	keep-alive
Vary	Accept-Encoding
ETag	W/"6853cd5f-140af"
Expires	Thu, 01 Jan 1970 00:00:01 GMT
Cache-Control	no-cache
Strict-Transport-Security	max-age=63072000; includeSubDomains; preload
Expect-CT	enforce, max-age=604800, report-uri="https://simplelogin.report-uri.com/r/d/ct/enforce"
X-Frame-Options	SAMEORIGIN
X-Content-Type-Options	nosniff
X-XSS-Protection	1; mode=block
Content-Security-Policy	script-src 'self' 'unsafe-inline' 'unsafe-eval' https://cdn.paddle.com/paddle/paddle.js https://gc.zgo.at/count.js https://hcaptcha.com https://.hcaptcha.com https://plausible.simplelogin.io/js/index.js; child-src 'self' https://hcaptcha.com https://.hcaptcha.com https://.paddle.com https://www.youtube.com https://app.tryhoist.com; style-src 'self' 'unsafe-inline' https://hcaptcha.com https://.hcaptcha.com https://cdn.paddle.com

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://simplelogin.io/

1

https://simplelogin.io/

HTTP/1.1 200 OK

Server	nginx
Date	Mon, 30 Jun 2025 03:08:47 GMT
Content-Type	text/html
Last-Modified	Thu, 19 Jun 2025 08:49:45 GMT
Transfer-Encoding	chunked
Connection	keep-alive
Vary	Accept-Encoding
ETag	W/"6853cf29-140af"
Expires	Thu, 01 Jan 1970 00:00:01 GMT
Cache-Control	no-cache
Strict-Transport-Security	max-age=63072000; includeSubDomains; preload
Expect-CT	enforce, max-age=604800, report-uri="https://simplelogin.report-uri.com/r/d/ct/enforce"
X-Frame-Options	SAMEORIGIN
X-Content-Type-Options	nosniff
X-XSS-Protection	1; mode=block
Content-Security-Policy	script-src 'self' 'unsafe-inline' 'unsafe-eval' https://cdn.paddle.com/paddle/paddle.js https://gc.zgo.at/count.js https://hcaptcha.com https://.hcaptcha.com https://plausible.simplelogin.io/js/index.js; child-src 'self' https://hcaptcha.com https://.hcaptcha.com https://.paddle.com https://www.youtube.com https://app.tryhoist.com; style-src 'self' 'unsafe-inline' https://hcaptcha.com https://.hcaptcha.com https://cdn.paddle.com

URL: https://www.simplelogin.io/

1

https://www.simplelogin.io/

HTTP/1.1 301 Moved Permanently

Server	nginx
Date	Mon, 30 Jun 2025 03:08:47 GMT
Content-Type	text/html
Content-Length	162
Connection	keep-alive
Location	https://simplelogin.io/
Strict-Transport-Security	max-age=63072000; includeSubDomains; preload
Expect-CT	enforce, max-age=604800, report-uri="https://simplelogin.report-uri.com/r/d/ct/enforce"
Cache-Control	no-store, no-cache, must-revalidate
X-Frame-Options	SAMEORIGIN
X-Content-Type-Options	nosniff
X-XSS-Protection	1; mode=block
Content-Security-Policy	script-src 'self' 'unsafe-inline' 'unsafe-eval' https://cdn.paddle.com/paddle/paddle.js https://gc.zgo.at/count.js https://hcaptcha.com https://.hcaptcha.com https://plausible.simplelogin.io/js/index.js; child-src 'self' https://hcaptcha.com https://.hcaptcha.com https://.paddle.com https://www.youtube.com https://app.tryhoist.com; style-src 'self' 'unsafe-inline' https://hcaptcha.com https://.hcaptcha.com https://cdn.paddle.com

2

https://simplelogin.io/

HTTP/1.1 200 OK

Server	nginx
Date	Mon, 30 Jun 2025 03:08:48 GMT
Content-Type	text/html
Last-Modified	Thu, 19 Jun 2025 08:38:05 GMT
Transfer-Encoding	chunked
Connection	keep-alive
Vary	Accept-Encoding
ETag	W/"6853cc6d-140af"
Expires	Thu, 01 Jan 1970 00:00:01 GMT
Cache-Control	no-cache
Strict-Transport-Security	max-age=63072000; includeSubDomains; preload
Expect-CT	enforce, max-age=604800, report-uri="https://simplelogin.report-uri.com/r/d/ct/enforce"
X-Frame-Options	SAMEORIGIN
X-Content-Type-Options	nosniff
X-XSS-Protection	1; mode=block
Content-Security-Policy	script-src 'self' 'unsafe-inline' 'unsafe-eval' https://cdn.paddle.com/paddle/paddle.js https://gc.zgo.at/count.js https://hcaptcha.com https://.hcaptcha.com https://plausible.simplelogin.io/js/index.js; child-src 'self' https://hcaptcha.com https://.hcaptcha.com https://.paddle.com https://www.youtube.com https://app.tryhoist.com; style-src 'self' 'unsafe-inline' https://hcaptcha.com https://.hcaptcha.com https://cdn.paddle.com

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: simplelogin.io (176.119.200.11)

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 Unknown preference	Suite: TLS_CHACHA20_POLY1305_SHA256 Suite ID: 0x1303 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_AES_128_GCM_SHA256 Suite ID: 0x1301 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_AES_256_GCM_SHA384 Suite ID: 0x1302 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2 Unknown preference	Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0x9e Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: DHE_RSA Key exchange strength: 2048 bits Forward secrecy: Yes PRF: SHA256 TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (DHE 2048 bits) Suite: TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0x9f Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: DHE_RSA Key exchange strength: 2048 bits Forward secrecy: Yes PRF: SHA384 TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (DHE 2048 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 server parameter not reused

This server does not reuse the private value used for the Diffie-Hellman key exchange.

TLS Configuration: www.simplelogin.io (176.119.200.11)

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 Unknown preference	Suite: TLS_CHACHA20_POLY1305_SHA256 Suite ID: 0x1303 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_AES_128_GCM_SHA256 Suite ID: 0x1301 Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_AES_256_GCM_SHA384 Suite ID: 0x1302 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ecdh_x25519 Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2 Unknown preference	Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 Suite ID: 0xcca8 Cipher name: CHACHA20 Cipher strength: 256 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 256 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0xc02f Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (ECDHE 256 bits) Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0xc030 Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: ECDHE_RSA Key exchange strength: EC ecdh_x25519 (256 bits) Forward secrecy: Yes PRF: SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (ECDHE 256 bits) Suite: TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 Suite ID: 0x9e Cipher name: AES Cipher strength: 128 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: DHE_RSA Key exchange strength: 2048 bits Forward secrecy: Yes PRF: SHA256 TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 128 bits (DHE 2048 bits) Suite: TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 Suite ID: 0x9f Cipher name: AES Cipher strength: 256 bits Cipher block size: 128 bits Cipher mode: AEAD Key exchange: DHE_RSA Key exchange strength: 2048 bits Forward secrecy: Yes PRF: SHA384 TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 256 bits (DHE 2048 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 server parameter not reused

This server does not reuse the private value used for the Diffie-Hellman 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.simplelogin.io

Leaf certificate

*.8alias.com
Issuer: Let's Encrypt
Not Before: 17 May 2025 17:32:25 UTC
Not After: 15 Aug 2025 17:32:24 UTC (expires in 1 month 16 days)
Key: RSA 2048 bits
Signature: SHA256withRSA
View details

Names	.8alias.com .8shield.net .aleeas.com .dralias.com .pass2mail.com .passfwd.com .passinbox.com .passmail.com .passmail.net .silomails.com .simplelogin.co .simplelogin.com .simplelogin.fr .simplelogin.io .slmail.me .slmails.com 8alias.com 8shield.net aleeas.com dralias.com pass2mail.com passfwd.com passinbox.com passmail.com passmail.net silomails.com simplelogin.co simplelogin.com simplelogin.fr simplelogin.io slmail.me slmails.com
Subject DN	CN=*.8alias.com
Subject Key Identifier	eacf4bf6089a23499a9751198d90b3afca7ca525
Serial	0656b1408ff62e5bda83b8b95d929f15ee9d
Not Before	17 May 2025 17:32:25 UTC
Not After	15 Aug 2025 17:32:24 UTC
Validity period	90 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=R11, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:c5cf46a4eaf4c3c07a6c95c42db05e922f26e3b9
Parent Certificate	http://r11.i.lencr.org/
CRL	http://r11.c.lencr.org/30.crl
Certificate Transparency
Signed Certificate Timestamps	17 May 2025 18:30:55 UTC \| Google 'Argon2025h2' log \| Qualified 17 May 2025 18:30:57 UTC \| DigiCert 'Wyvern2025h2' Log \| Qualified
Fingerprints
SHA1	9f91259823cd0c8c05982e884575114fb31b00dc
SHA256	2ff9e82f32c17b08998c8507627d76c7c55c2f25affda37307173520e9776ac2
SPKI SHA256	bb21cfb2cac4d40902f8541d3a13c45f538f5163537cae2d4c3be2e5ebbc7ef6

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

*.8alias.com | 2ff9e82
Not After: 15 Aug 2025 17:32:24 UTC (expires in 1 month 16 days)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Names	.8alias.com .8shield.net .aleeas.com .dralias.com .pass2mail.com .passfwd.com .passinbox.com .passmail.com .passmail.net .silomails.com .simplelogin.co .simplelogin.com .simplelogin.fr .simplelogin.io .slmail.me .slmails.com 8alias.com 8shield.net aleeas.com dralias.com pass2mail.com passfwd.com passinbox.com passmail.com passmail.net silomails.com simplelogin.co simplelogin.com simplelogin.fr simplelogin.io slmail.me slmails.com
Subject DN	CN=*.8alias.com
Subject Key Identifier	eacf4bf6089a23499a9751198d90b3afca7ca525
Serial	0656b1408ff62e5bda83b8b95d929f15ee9d
Not Before	17 May 2025 17:32:25 UTC
Not After	15 Aug 2025 17:32:24 UTC
Validity period	90 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=R11, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:c5cf46a4eaf4c3c07a6c95c42db05e922f26e3b9
Parent Certificate	http://r11.i.lencr.org/
CRL	http://r11.c.lencr.org/30.crl
Certificate Transparency
Signed Certificate Timestamps	17 May 2025 18:30:55 UTC \| Google 'Argon2025h2' log \| Qualified 17 May 2025 18:30:57 UTC \| DigiCert 'Wyvern2025h2' Log \| Qualified
Fingerprints
SHA1	9f91259823cd0c8c05982e884575114fb31b00dc
SHA256	2ff9e82f32c17b08998c8507627d76c7c55c2f25affda37307173520e9776ac2
SPKI SHA256	bb21cfb2cac4d40902f8541d3a13c45f538f5163537cae2d4c3be2e5ebbc7ef6

Intermediate certificate

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

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

Root certificate

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

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

Analysis

Certificate chain is correct

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

Certificate: www.simplelogin.io

Leaf certificate

*.8alias.com
Issuer: Let's Encrypt
Not Before: 17 May 2025 16:52:20 UTC
Not After: 15 Aug 2025 16:52:19 UTC (expires in 1 month 16 days)
Key: RSA 2048 bits
Signature: SHA256withRSA
View details

Names	.8alias.com .8shield.net .aleeas.com .dralias.com .pass2mail.com .passfwd.com .passinbox.com .passmail.com .passmail.net .silomails.com .simplelogin.co .simplelogin.com .simplelogin.fr .simplelogin.io .slmail.me .slmails.com 8alias.com 8shield.net aleeas.com dralias.com pass2mail.com passfwd.com passinbox.com passmail.com passmail.net silomails.com simplelogin.co simplelogin.com simplelogin.fr simplelogin.io slmail.me slmails.com
Subject DN	CN=*.8alias.com
Subject Key Identifier	5cb4d5668cf4b71bc7dfe5923184b38bcc8e29f6
Serial	0552f839fc900e1f251c2a3457c6d96367b1
Not Before	17 May 2025 16:52:20 UTC
Not After	15 Aug 2025 16:52:19 UTC
Validity period	90 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=R11, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:c5cf46a4eaf4c3c07a6c95c42db05e922f26e3b9
Parent Certificate	http://r11.i.lencr.org/
CRL	http://r11.c.lencr.org/50.crl
Certificate Transparency
Signed Certificate Timestamps	17 May 2025 17:50:50 UTC \| Cloudflare 'Nimbus2025' \| Qualified 17 May 2025 17:50:50 UTC \| Let's Encrypt 'Oak2025h2' \| Qualified
Fingerprints
SHA1	099219bea105af4d0bc07b0e78b5a765febb395a
SHA256	4a1cfbbe708dc20136ad7326b7ddfe679cd7b63998e6c380d77b7c5fbd6056b5
SPKI SHA256	23ec3ee3ead38704c493fb29a10331eee14db1856ad948c64eed25ec9e40716d

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

*.8alias.com | 4a1cfbb
Not After: 15 Aug 2025 16:52:19 UTC (expires in 1 month 16 days)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Names	.8alias.com .8shield.net .aleeas.com .dralias.com .pass2mail.com .passfwd.com .passinbox.com .passmail.com .passmail.net .silomails.com .simplelogin.co .simplelogin.com .simplelogin.fr .simplelogin.io .slmail.me .slmails.com 8alias.com 8shield.net aleeas.com dralias.com pass2mail.com passfwd.com passinbox.com passmail.com passmail.net silomails.com simplelogin.co simplelogin.com simplelogin.fr simplelogin.io slmail.me slmails.com
Subject DN	CN=*.8alias.com
Subject Key Identifier	5cb4d5668cf4b71bc7dfe5923184b38bcc8e29f6
Serial	0552f839fc900e1f251c2a3457c6d96367b1
Not Before	17 May 2025 16:52:20 UTC
Not After	15 Aug 2025 16:52:19 UTC
Validity period	90 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=R11, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:c5cf46a4eaf4c3c07a6c95c42db05e922f26e3b9
Parent Certificate	http://r11.i.lencr.org/
CRL	http://r11.c.lencr.org/50.crl
Certificate Transparency
Signed Certificate Timestamps	17 May 2025 17:50:50 UTC \| Cloudflare 'Nimbus2025' \| Qualified 17 May 2025 17:50:50 UTC \| Let's Encrypt 'Oak2025h2' \| Qualified
Fingerprints
SHA1	099219bea105af4d0bc07b0e78b5a765febb395a
SHA256	4a1cfbbe708dc20136ad7326b7ddfe679cd7b63998e6c380d77b7c5fbd6056b5
SPKI SHA256	23ec3ee3ead38704c493fb29a10331eee14db1856ad948c64eed25ec9e40716d

Intermediate certificate

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

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

Root certificate

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

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

Analysis

Certificate chain is correct

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

Certificate: www.simplelogin.io

Leaf certificate

*.8alias.com
Issuer: Let's Encrypt
Not Before: 17 May 2025 23:05:54 UTC
Not After: 15 Aug 2025 23:05:53 UTC (expires in 1 month 16 days)
Key: RSA 2048 bits
Signature: SHA256withRSA
View details

Names	.8alias.com .8shield.net .aleeas.com .dralias.com .pass2mail.com .passfwd.com .passinbox.com .passmail.com .passmail.net .silomails.com .simplelogin.co .simplelogin.com .simplelogin.fr .simplelogin.io .slmail.me .slmails.com 8alias.com 8shield.net aleeas.com dralias.com pass2mail.com passfwd.com passinbox.com passmail.com passmail.net silomails.com simplelogin.co simplelogin.com simplelogin.fr simplelogin.io slmail.me slmails.com
Subject DN	CN=*.8alias.com
Subject Key Identifier	3b408bc32946eefd52553b6c569b67183eb3dd87
Serial	069750427cd13b33303d01b491319f2766d9
Not Before	17 May 2025 23:05:54 UTC
Not After	15 Aug 2025 23:05:53 UTC
Validity period	90 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=R11, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:c5cf46a4eaf4c3c07a6c95c42db05e922f26e3b9
Parent Certificate	http://r11.i.lencr.org/
CRL	http://r11.c.lencr.org/90.crl
Certificate Transparency
Signed Certificate Timestamps	18 May 2025 00:04:24 UTC \| Google 'Argon2025h2' log \| Qualified 18 May 2025 00:04:26 UTC \| DigiCert 'Wyvern2025h2' Log \| Qualified
Fingerprints
SHA1	7049ee3bc14257dbb5b1246089f11c35ff49faf6
SHA256	d88e5111efaa6b56a40058aab1a638af4b854bc5e33f930bbc5feb74eaecfaf1
SPKI SHA256	abfaf9490e8d69bfb3eab807628856405a771bc50e60b3b7be6043145542f618

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

*.8alias.com | d88e511
Not After: 15 Aug 2025 23:05:53 UTC (expires in 1 month 16 days)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Names	.8alias.com .8shield.net .aleeas.com .dralias.com .pass2mail.com .passfwd.com .passinbox.com .passmail.com .passmail.net .silomails.com .simplelogin.co .simplelogin.com .simplelogin.fr .simplelogin.io .slmail.me .slmails.com 8alias.com 8shield.net aleeas.com dralias.com pass2mail.com passfwd.com passinbox.com passmail.com passmail.net silomails.com simplelogin.co simplelogin.com simplelogin.fr simplelogin.io slmail.me slmails.com
Subject DN	CN=*.8alias.com
Subject Key Identifier	3b408bc32946eefd52553b6c569b67183eb3dd87
Serial	069750427cd13b33303d01b491319f2766d9
Not Before	17 May 2025 23:05:54 UTC
Not After	15 Aug 2025 23:05:53 UTC
Validity period	90 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=R11, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:c5cf46a4eaf4c3c07a6c95c42db05e922f26e3b9
Parent Certificate	http://r11.i.lencr.org/
CRL	http://r11.c.lencr.org/90.crl
Certificate Transparency
Signed Certificate Timestamps	18 May 2025 00:04:24 UTC \| Google 'Argon2025h2' log \| Qualified 18 May 2025 00:04:26 UTC \| DigiCert 'Wyvern2025h2' Log \| Qualified
Fingerprints
SHA1	7049ee3bc14257dbb5b1246089f11c35ff49faf6
SHA256	d88e5111efaa6b56a40058aab1a638af4b854bc5e33f930bbc5feb74eaecfaf1
SPKI SHA256	abfaf9490e8d69bfb3eab807628856405a771bc50e60b3b7be6043145542f618

Intermediate certificate

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

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

Root certificate

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

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

Analysis

Certificate chain is correct

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

Certificate: simplelogin.io

Leaf certificate

*.8alias.com
Issuer: Let's Encrypt
Not Before: 17 May 2025 16:52:20 UTC
Not After: 15 Aug 2025 16:52:19 UTC (expires in 1 month 16 days)
Key: RSA 2048 bits
Signature: SHA256withRSA
View details

Names	.8alias.com .8shield.net .aleeas.com .dralias.com .pass2mail.com .passfwd.com .passinbox.com .passmail.com .passmail.net .silomails.com .simplelogin.co .simplelogin.com .simplelogin.fr .simplelogin.io .slmail.me .slmails.com 8alias.com 8shield.net aleeas.com dralias.com pass2mail.com passfwd.com passinbox.com passmail.com passmail.net silomails.com simplelogin.co simplelogin.com simplelogin.fr simplelogin.io slmail.me slmails.com
Subject DN	CN=*.8alias.com
Subject Key Identifier	5cb4d5668cf4b71bc7dfe5923184b38bcc8e29f6
Serial	0552f839fc900e1f251c2a3457c6d96367b1
Not Before	17 May 2025 16:52:20 UTC
Not After	15 Aug 2025 16:52:19 UTC
Validity period	90 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=R11, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:c5cf46a4eaf4c3c07a6c95c42db05e922f26e3b9
Parent Certificate	http://r11.i.lencr.org/
CRL	http://r11.c.lencr.org/50.crl
Certificate Transparency
Signed Certificate Timestamps	17 May 2025 17:50:50 UTC \| Cloudflare 'Nimbus2025' \| Qualified 17 May 2025 17:50:50 UTC \| Let's Encrypt 'Oak2025h2' \| Qualified
Fingerprints
SHA1	099219bea105af4d0bc07b0e78b5a765febb395a
SHA256	4a1cfbbe708dc20136ad7326b7ddfe679cd7b63998e6c380d77b7c5fbd6056b5
SPKI SHA256	23ec3ee3ead38704c493fb29a10331eee14db1856ad948c64eed25ec9e40716d

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

*.8alias.com | 4a1cfbb
Not After: 15 Aug 2025 16:52:19 UTC (expires in 1 month 16 days)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Names	.8alias.com .8shield.net .aleeas.com .dralias.com .pass2mail.com .passfwd.com .passinbox.com .passmail.com .passmail.net .silomails.com .simplelogin.co .simplelogin.com .simplelogin.fr .simplelogin.io .slmail.me .slmails.com 8alias.com 8shield.net aleeas.com dralias.com pass2mail.com passfwd.com passinbox.com passmail.com passmail.net silomails.com simplelogin.co simplelogin.com simplelogin.fr simplelogin.io slmail.me slmails.com
Subject DN	CN=*.8alias.com
Subject Key Identifier	5cb4d5668cf4b71bc7dfe5923184b38bcc8e29f6
Serial	0552f839fc900e1f251c2a3457c6d96367b1
Not Before	17 May 2025 16:52:20 UTC
Not After	15 Aug 2025 16:52:19 UTC
Validity period	90 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=R11, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:c5cf46a4eaf4c3c07a6c95c42db05e922f26e3b9
Parent Certificate	http://r11.i.lencr.org/
CRL	http://r11.c.lencr.org/50.crl
Certificate Transparency
Signed Certificate Timestamps	17 May 2025 17:50:50 UTC \| Cloudflare 'Nimbus2025' \| Qualified 17 May 2025 17:50:50 UTC \| Let's Encrypt 'Oak2025h2' \| Qualified
Fingerprints
SHA1	099219bea105af4d0bc07b0e78b5a765febb395a
SHA256	4a1cfbbe708dc20136ad7326b7ddfe679cd7b63998e6c380d77b7c5fbd6056b5
SPKI SHA256	23ec3ee3ead38704c493fb29a10331eee14db1856ad948c64eed25ec9e40716d

Intermediate certificate

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

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

Root certificate

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

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

Analysis

Certificate chain is correct

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

Certificate: www.simplelogin.io

Leaf certificate

*.8alias.com
Issuer: Let's Encrypt
Not Before: 19 May 2025 12:16:16 UTC
Not After: 17 Aug 2025 12:16:15 UTC (expires in 1 month 18 days)
Key: RSA 2048 bits
Signature: SHA256withRSA
View details

Names	.8alias.com .8shield.net .aleeas.com .dralias.com .pass2mail.com .passfwd.com .passinbox.com .passmail.com .passmail.net .silomails.com .simplelogin.co .simplelogin.com .simplelogin.fr .simplelogin.io .slmail.me .slmails.com 8alias.com 8shield.net aleeas.com dralias.com pass2mail.com passfwd.com passinbox.com passmail.com passmail.net silomails.com simplelogin.co simplelogin.com simplelogin.fr simplelogin.io slmail.me slmails.com
Subject DN	CN=*.8alias.com
Subject Key Identifier	e9cb9bbacd62689f812452b57a65e7f5c15f5a37
Serial	06220a8bfd69aca8cd0a4c04d5db69a299f8
Not Before	19 May 2025 12:16:16 UTC
Not After	17 Aug 2025 12:16:15 UTC
Validity period	90 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=R10, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:bbbcc347a5e4bca9c6c3a4720c108da235e1c8e8
Parent Certificate	http://r10.i.lencr.org/
CRL	http://r10.c.lencr.org/121.crl
Certificate Transparency
Signed Certificate Timestamps	19 May 2025 13:14:46 UTC \| Let's Encrypt 'Oak2025h2' \| Qualified 19 May 2025 13:14:48 UTC \| DigiCert 'Sphinx2025h2' Log \| Qualified
Fingerprints
SHA1	1253f0438ba7cd6daf354728341b08a4a81ff328
SHA256	7802866cc30da7a3bf3af317b0e22ac495da016af77805059b82cdce3f7fa642
SPKI SHA256	7b57280de92710a0dc81f82f888f00a930a90add3e627a86a7c574970bae172b

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

*.8alias.com | 7802866
Not After: 17 Aug 2025 12:16:15 UTC (expires in 1 month 18 days)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Names	.8alias.com .8shield.net .aleeas.com .dralias.com .pass2mail.com .passfwd.com .passinbox.com .passmail.com .passmail.net .silomails.com .simplelogin.co .simplelogin.com .simplelogin.fr .simplelogin.io .slmail.me .slmails.com 8alias.com 8shield.net aleeas.com dralias.com pass2mail.com passfwd.com passinbox.com passmail.com passmail.net silomails.com simplelogin.co simplelogin.com simplelogin.fr simplelogin.io slmail.me slmails.com
Subject DN	CN=*.8alias.com
Subject Key Identifier	e9cb9bbacd62689f812452b57a65e7f5c15f5a37
Serial	06220a8bfd69aca8cd0a4c04d5db69a299f8
Not Before	19 May 2025 12:16:16 UTC
Not After	17 Aug 2025 12:16:15 UTC
Validity period	90 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=R10, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:bbbcc347a5e4bca9c6c3a4720c108da235e1c8e8
Parent Certificate	http://r10.i.lencr.org/
CRL	http://r10.c.lencr.org/121.crl
Certificate Transparency
Signed Certificate Timestamps	19 May 2025 13:14:46 UTC \| Let's Encrypt 'Oak2025h2' \| Qualified 19 May 2025 13:14:48 UTC \| DigiCert 'Sphinx2025h2' Log \| Qualified
Fingerprints
SHA1	1253f0438ba7cd6daf354728341b08a4a81ff328
SHA256	7802866cc30da7a3bf3af317b0e22ac495da016af77805059b82cdce3f7fa642
SPKI SHA256	7b57280de92710a0dc81f82f888f00a930a90add3e627a86a7c574970bae172b

Intermediate certificate

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

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

Root certificate

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

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

Analysis

Certificate chain is correct

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

Certificate: simplelogin.io

Leaf certificate

*.8alias.com
Issuer: Let's Encrypt
Not Before: 17 May 2025 15:14:31 UTC
Not After: 15 Aug 2025 15:14:30 UTC (expires in 1 month 16 days)
Key: RSA 2048 bits
Signature: SHA256withRSA
View details

Names	.8alias.com .8shield.net .aleeas.com .dralias.com .pass2mail.com .passfwd.com .passinbox.com .passmail.com .passmail.net .silomails.com .simplelogin.co .simplelogin.com .simplelogin.fr .simplelogin.io .slmail.me .slmails.com 8alias.com 8shield.net aleeas.com dralias.com pass2mail.com passfwd.com passinbox.com passmail.com passmail.net silomails.com simplelogin.co simplelogin.com simplelogin.fr simplelogin.io slmail.me slmails.com
Subject DN	CN=*.8alias.com
Subject Key Identifier	b5ab900a0399285727249f928ce7599e17e61e19
Serial	058a2ead40220b55b6df6fe0892e4ff1697b
Not Before	17 May 2025 15:14:31 UTC
Not After	15 Aug 2025 15:14:30 UTC
Validity period	90 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=R11, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:c5cf46a4eaf4c3c07a6c95c42db05e922f26e3b9
Parent Certificate	http://r11.i.lencr.org/
CRL	http://r11.c.lencr.org/124.crl
Certificate Transparency
Signed Certificate Timestamps	17 May 2025 16:13:01 UTC \| DigiCert 'Wyvern2025h2' Log \| Qualified 17 May 2025 16:13:02 UTC \| Google 'Xenon2025h2' log \| Qualified
Fingerprints
SHA1	a2f1ff764e4c1fb7273ed9135d87994d7ef63088
SHA256	38059c8a8638d971df6949f713a384f081b5b8469bace83ecaca08389f8620f9
SPKI SHA256	119d6b9065086738d61bf6059b3cd173aa4816a71c6c1bb37e53aa19be7e7b6b

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

*.8alias.com | 38059c8
Not After: 15 Aug 2025 15:14:30 UTC (expires in 1 month 16 days)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Names	.8alias.com .8shield.net .aleeas.com .dralias.com .pass2mail.com .passfwd.com .passinbox.com .passmail.com .passmail.net .silomails.com .simplelogin.co .simplelogin.com .simplelogin.fr .simplelogin.io .slmail.me .slmails.com 8alias.com 8shield.net aleeas.com dralias.com pass2mail.com passfwd.com passinbox.com passmail.com passmail.net silomails.com simplelogin.co simplelogin.com simplelogin.fr simplelogin.io slmail.me slmails.com
Subject DN	CN=*.8alias.com
Subject Key Identifier	b5ab900a0399285727249f928ce7599e17e61e19
Serial	058a2ead40220b55b6df6fe0892e4ff1697b
Not Before	17 May 2025 15:14:31 UTC
Not After	15 Aug 2025 15:14:30 UTC
Validity period	90 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=R11, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:c5cf46a4eaf4c3c07a6c95c42db05e922f26e3b9
Parent Certificate	http://r11.i.lencr.org/
CRL	http://r11.c.lencr.org/124.crl
Certificate Transparency
Signed Certificate Timestamps	17 May 2025 16:13:01 UTC \| DigiCert 'Wyvern2025h2' Log \| Qualified 17 May 2025 16:13:02 UTC \| Google 'Xenon2025h2' log \| Qualified
Fingerprints
SHA1	a2f1ff764e4c1fb7273ed9135d87994d7ef63088
SHA256	38059c8a8638d971df6949f713a384f081b5b8469bace83ecaca08389f8620f9
SPKI SHA256	119d6b9065086738d61bf6059b3cd173aa4816a71c6c1bb37e53aa19be7e7b6b

Intermediate certificate

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

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

Root certificate

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

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

Analysis

Certificate chain is correct

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

Certificate: simplelogin.io

Leaf certificate

*.8alias.com
Issuer: Let's Encrypt
Not Before: 17 May 2025 17:32:25 UTC
Not After: 15 Aug 2025 17:32:24 UTC (expires in 1 month 16 days)
Key: RSA 2048 bits
Signature: SHA256withRSA
View details

Names	.8alias.com .8shield.net .aleeas.com .dralias.com .pass2mail.com .passfwd.com .passinbox.com .passmail.com .passmail.net .silomails.com .simplelogin.co .simplelogin.com .simplelogin.fr .simplelogin.io .slmail.me .slmails.com 8alias.com 8shield.net aleeas.com dralias.com pass2mail.com passfwd.com passinbox.com passmail.com passmail.net silomails.com simplelogin.co simplelogin.com simplelogin.fr simplelogin.io slmail.me slmails.com
Subject DN	CN=*.8alias.com
Subject Key Identifier	eacf4bf6089a23499a9751198d90b3afca7ca525
Serial	0656b1408ff62e5bda83b8b95d929f15ee9d
Not Before	17 May 2025 17:32:25 UTC
Not After	15 Aug 2025 17:32:24 UTC
Validity period	90 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=R11, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:c5cf46a4eaf4c3c07a6c95c42db05e922f26e3b9
Parent Certificate	http://r11.i.lencr.org/
CRL	http://r11.c.lencr.org/30.crl
Certificate Transparency
Signed Certificate Timestamps	17 May 2025 18:30:55 UTC \| Google 'Argon2025h2' log \| Qualified 17 May 2025 18:30:57 UTC \| DigiCert 'Wyvern2025h2' Log \| Qualified
Fingerprints
SHA1	9f91259823cd0c8c05982e884575114fb31b00dc
SHA256	2ff9e82f32c17b08998c8507627d76c7c55c2f25affda37307173520e9776ac2
SPKI SHA256	bb21cfb2cac4d40902f8541d3a13c45f538f5163537cae2d4c3be2e5ebbc7ef6

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

*.8alias.com | 2ff9e82
Not After: 15 Aug 2025 17:32:24 UTC (expires in 1 month 16 days)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Names	.8alias.com .8shield.net .aleeas.com .dralias.com .pass2mail.com .passfwd.com .passinbox.com .passmail.com .passmail.net .silomails.com .simplelogin.co .simplelogin.com .simplelogin.fr .simplelogin.io .slmail.me .slmails.com 8alias.com 8shield.net aleeas.com dralias.com pass2mail.com passfwd.com passinbox.com passmail.com passmail.net silomails.com simplelogin.co simplelogin.com simplelogin.fr simplelogin.io slmail.me slmails.com
Subject DN	CN=*.8alias.com
Subject Key Identifier	eacf4bf6089a23499a9751198d90b3afca7ca525
Serial	0656b1408ff62e5bda83b8b95d929f15ee9d
Not Before	17 May 2025 17:32:25 UTC
Not After	15 Aug 2025 17:32:24 UTC
Validity period	90 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=R11, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:c5cf46a4eaf4c3c07a6c95c42db05e922f26e3b9
Parent Certificate	http://r11.i.lencr.org/
CRL	http://r11.c.lencr.org/30.crl
Certificate Transparency
Signed Certificate Timestamps	17 May 2025 18:30:55 UTC \| Google 'Argon2025h2' log \| Qualified 17 May 2025 18:30:57 UTC \| DigiCert 'Wyvern2025h2' Log \| Qualified
Fingerprints
SHA1	9f91259823cd0c8c05982e884575114fb31b00dc
SHA256	2ff9e82f32c17b08998c8507627d76c7c55c2f25affda37307173520e9776ac2
SPKI SHA256	bb21cfb2cac4d40902f8541d3a13c45f538f5163537cae2d4c3be2e5ebbc7ef6

Intermediate certificate

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

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

Root certificate

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

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

Analysis

Certificate chain is correct

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

Certificate: simplelogin.io

Leaf certificate

*.8alias.com
Issuer: Let's Encrypt
Not Before: 19 May 2025 12:16:16 UTC
Not After: 17 Aug 2025 12:16:15 UTC (expires in 1 month 18 days)
Key: RSA 2048 bits
Signature: SHA256withRSA
View details

Names	.8alias.com .8shield.net .aleeas.com .dralias.com .pass2mail.com .passfwd.com .passinbox.com .passmail.com .passmail.net .silomails.com .simplelogin.co .simplelogin.com .simplelogin.fr .simplelogin.io .slmail.me .slmails.com 8alias.com 8shield.net aleeas.com dralias.com pass2mail.com passfwd.com passinbox.com passmail.com passmail.net silomails.com simplelogin.co simplelogin.com simplelogin.fr simplelogin.io slmail.me slmails.com
Subject DN	CN=*.8alias.com
Subject Key Identifier	e9cb9bbacd62689f812452b57a65e7f5c15f5a37
Serial	06220a8bfd69aca8cd0a4c04d5db69a299f8
Not Before	19 May 2025 12:16:16 UTC
Not After	17 Aug 2025 12:16:15 UTC
Validity period	90 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=R10, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:bbbcc347a5e4bca9c6c3a4720c108da235e1c8e8
Parent Certificate	http://r10.i.lencr.org/
CRL	http://r10.c.lencr.org/121.crl
Certificate Transparency
Signed Certificate Timestamps	19 May 2025 13:14:46 UTC \| Let's Encrypt 'Oak2025h2' \| Qualified 19 May 2025 13:14:48 UTC \| DigiCert 'Sphinx2025h2' Log \| Qualified
Fingerprints
SHA1	1253f0438ba7cd6daf354728341b08a4a81ff328
SHA256	7802866cc30da7a3bf3af317b0e22ac495da016af77805059b82cdce3f7fa642
SPKI SHA256	7b57280de92710a0dc81f82f888f00a930a90add3e627a86a7c574970bae172b

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

*.8alias.com | 7802866
Not After: 17 Aug 2025 12:16:15 UTC (expires in 1 month 18 days)
Authentication: RSA 2048 bits (SHA256withRSA)
View details

Names	.8alias.com .8shield.net .aleeas.com .dralias.com .pass2mail.com .passfwd.com .passinbox.com .passmail.com .passmail.net .silomails.com .simplelogin.co .simplelogin.com .simplelogin.fr .simplelogin.io .slmail.me .slmails.com 8alias.com 8shield.net aleeas.com dralias.com pass2mail.com passfwd.com passinbox.com passmail.com passmail.net silomails.com simplelogin.co simplelogin.com simplelogin.fr simplelogin.io slmail.me slmails.com
Subject DN	CN=*.8alias.com
Subject Key Identifier	e9cb9bbacd62689f812452b57a65e7f5c15f5a37
Serial	06220a8bfd69aca8cd0a4c04d5db69a299f8
Not Before	19 May 2025 12:16:16 UTC
Not After	17 Aug 2025 12:16:15 UTC
Validity period	90 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=R10, O=Let's Encrypt, C=US
Certification Authority	Let's Encrypt
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:bbbcc347a5e4bca9c6c3a4720c108da235e1c8e8
Parent Certificate	http://r10.i.lencr.org/
CRL	http://r10.c.lencr.org/121.crl
Certificate Transparency
Signed Certificate Timestamps	19 May 2025 13:14:46 UTC \| Let's Encrypt 'Oak2025h2' \| Qualified 19 May 2025 13:14:48 UTC \| DigiCert 'Sphinx2025h2' Log \| Qualified
Fingerprints
SHA1	1253f0438ba7cd6daf354728341b08a4a81ff328
SHA256	7802866cc30da7a3bf3af317b0e22ac495da016af77805059b82cdce3f7fa642
SPKI SHA256	7b57280de92710a0dc81f82f888f00a930a90add3e627a86a7c574970bae172b

Intermediate certificate

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

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

Root certificate

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

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

Analysis

Certificate chain is correct

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

DANE (443)

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

Test failed

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

TLSA Record #1: _443._tcp.simplelogin.io.

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

TLSA Record #2: _443._tcp.simplelogin.io.

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

Analysis

No DANE match

DANE configuration is present for this service, but a valid match couldn't be found. Clients that support DANE will likely fail to connect.

Certificate Key Algorithm: RSA

Certificate SHA-256: 38059c8a8638d971df6949f713a384f081b5b8469bace83ecaca08389f8620f9

Certificate SPKI SHA-256: 119d6b9065086738d61bf6059b3cd173aa4816a71c6c1bb37e53aa19be7e7b6b

Certificate Subject: CN=*.8alias.com

DANE configuration mismatch

Your DANE configuration doesn't match the one or more certificate chains provided by the service. Clients who support and validate DANE might refuse to connect.

Cookies

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

Test passed

Everything seems to be well configured. Well done.

HTML Content

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

Test passed

Everything seems to be well configured. Well done.

Encryption of Embedded Resources

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

0 script(s)
0 out of 0 are secure

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

Status	Link
Encrypted	https://simplelogin.io/...tawesome-all.min.css
Encrypted	https://simplelogin.io/....css/animate.min.css
Encrypted	https://simplelogin.io/.../src/hs.megamenu.css
Encrypted	https://simplelogin.io/...usel/slick/slick.css
Encrypted	https://simplelogin.io/...ts/css/theme.min.css
Encrypted	https://simplelogin.io/prism.css
Encrypted	https://simplelogin.io/custom.css

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

Status	Link
Encrypted	https://simplelogin.io/logo.svg
Encrypted	https://simplelogin.io/images/5-stars.svg
Encrypted	https://simplelogin.io/images/hero.svg
Encrypted	https://simplelogin.io/images/nytimes.svg
Encrypted	https://simplelogin.io/images/pcmag.png
Encrypted	https://simplelogin.io/...imonial/techlore.svg
Encrypted	https://simplelogin.io/...imonial/theverge.svg
Encrypted	https://simplelogin.io/...teltechniques100.png
Encrypted	https://simplelogin.io/...estimonial/nbtv.jpeg
Encrypted	https://simplelogin.io/...-things-secured.jpeg
Encrypted	https://simplelogin.io/.../one-click-alias.gif
Encrypted	https://simplelogin.io/...es/how-it-work-2.svg
Encrypted	https://simplelogin.io/...es/how-it-work-3.svg
Encrypted	https://simplelogin.io/...mages/everywhere.png
Encrypted	https://simplelogin.io/...app-logos/chrome.svg
Encrypted	https://simplelogin.io/...pp-logos/firefox.svg
Encrypted	https://simplelogin.io/...app-logos/safari.svg
Encrypted	https://simplelogin.io/...p-logos/appstore.svg
Encrypted	https://simplelogin.io/...-logos/playstore.svg
Encrypted	https://simplelogin.io/...pp-logos/f-droid.svg
Encrypted	https://simplelogin.io/...imonial/techlore.svg
Encrypted	https://simplelogin.io/...teltechniques100.png
Encrypted	https://simplelogin.io/...estimonial/nbtv.jpeg
Encrypted	https://simplelogin.io/...-things-secured.jpeg
Encrypted	https://simplelogin.io/...imonial/cuong100.jpg
Encrypted	https://simplelogin.io/...timonial/max100.jpeg

Encryption of Outbound Links

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

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

Status	Link
Encrypted	https://github.com/simple-login/app
Encrypted	https://github.com/...ogin/app/discussions
Encrypted	https://app.simplelogin.io/auth/login
Encrypted	https://app.simplelogin.io/auth/register
Encrypted	https://fosstodon.org/@simplelogin
Encrypted	https://github.com/simple-login/
Encrypted	https://app.simplelogin.io/auth/register
Encrypted	https://www.nytimes.com/...umbers-credit-cards/
Encrypted	https://www.pcmag.com/reviews/simplelogin
Encrypted	https://www.youtube.com/watch
Encrypted	https://www.theverge.com/...apple-firefox-how-to
Encrypted	https://inteltechniques.com/...nt-show-episode-173/
Encrypted	https://youtu.be/5HHdk_GP-Ew
Encrypted	https://youtu.be/J7uGUD9kprs
Encrypted	https://chrome.google.com/...kdjbpfohgikllaljmgbn
Encrypted	https://addons.mozilla.org/...x/addon/simplelogin/
Encrypted	https://apps.apple.com/app/id6475835429
Encrypted	https://apps.apple.com/app/id1494359858
Encrypted	https://play.google.com/store/apps/details
Encrypted	https://f-droid.org/...ogin.android.fdroid/
Encrypted	https://www.youtube.com/watch
Encrypted	https://inteltechniques.com/...nt-show-episode-173/
Encrypted	https://youtu.be/5HHdk_GP-Ew
Encrypted	https://youtu.be/J7uGUD9kprs
Encrypted	https://www.linkedin.com/in/nncuong/
Encrypted	https://twitter.com/mxschumacher
Encrypted	https://en.wikipedia.org/...iki/Email_forwarding
Encrypted	https://haveibeenpwned.com
Encrypted	https://github.com/simple-login/app
Encrypted	https://github.com/...login/app/projects/1
Encrypted	https://temp-mail.org/en/
Encrypted	https://github.com/...ogin/app/discussions

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.simplelogin.io/
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	63,072,000 seconds (about 2 years)
When present, this directive forces HSTS activation on allsubdomains. For best security, HSTS should be deployed on the bare domain name (e.g., example.com) and all its subdomains.includeSubDomains
Presence of this directive indicates that a web site wishes to permanently use HSTS and that its policy information should be preloaded (embedded in browsers).preload

Analysis

Policy is valid

OK. Your HSTS policy uses correct syntax.

Long policy age

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

Policy covers subdomains

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

Redirection from HTTP to HTTPS to the same host

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

Policy preloaded

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

Preloaded host: simplelogin.io; includeSubDomains=true

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://simplelogin.io/assets/vendor/font-awesome/css/fontawesome-all.min.css

HSTS Policy Apex host

URL from which this policy was obtained.Location	https://simplelogin.io/
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	63,072,000 seconds (about 2 years)
When present, this directive forces HSTS activation on allsubdomains. For best security, HSTS should be deployed on the bare domain name (e.g., example.com) and all its subdomains.includeSubDomains
Presence of this directive indicates that a web site wishes to permanently use HSTS and that its policy information should be preloaded (embedded in browsers).preload

Analysis

Policy is valid

OK. Your HSTS policy uses correct syntax.

Long policy age

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

Policy covers subdomains

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

Preload intent declared

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

Redirection from HTTP to HTTPS to the same host

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

Policy preloaded

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

Preloaded host: simplelogin.io; includeSubDomains=true

HTTP Public Key Pinning

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

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

Content Security Policy

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

Test passed

Everything seems to be well configured. Well done.

Content-Security-Policy

script-src	'self' This parameter shouldn't be used because it reenables insecure behavior that CSP disables by default.'unsafe-inline' This parameter shouldn't be used because it reenables insecure behavior that CSP disables by default.'unsafe-eval' https://cdn.paddle.com/paddle/paddle.js https://gc.zgo.at/count.js https://hcaptcha.com https://*.hcaptcha.com https://plausible.simplelogin.io/js/index.js
child-src	'self' https://hcaptcha.com https://.hcaptcha.com https://.paddle.com https://www.youtube.com https://app.tryhoist.com
style-src	'self' This parameter shouldn't be used because it reenables insecure behavior that CSP disables by default.'unsafe-inline' https://hcaptcha.com https://*.hcaptcha.com https://cdn.paddle.com

Analysis

Inline scripts are allowed

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

Inline styles are allowed

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

Dynamic code execution is allowed

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

Mixed content not blocked

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

Form targets not restricted

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

Analysis

CSP policy detected

Header: Content-Security-Policy

Value: script-src 'self' 'unsafe-inline' 'unsafe-eval' https://cdn.paddle.com/paddle/paddle.js https://gc.zgo.at/count.js https://hcaptcha.com https://*.hcaptcha.com https://plausible.simplelogin.io/js/index.js; child-src 'self' https://hcaptcha.com https://*.hcaptcha.com https://*.paddle.com https://www.youtube.com https://app.tryhoist.com; style-src 'self' 'unsafe-inline' https://hcaptcha.com https://*.hcaptcha.com https://cdn.paddle.com

Location: https://simplelogin.io/

Subresource Integrity

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

Test passed

Everything seems to be well configured. Well done.

No external scripts
SRI not needed

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

Status	Link
Local	https://simplelogin.io/assets/css/theme.min.css
Local	https://simplelogin.io/assets/vendor/animate.css/animate.min.css
Local	https://simplelogin.io/assets/vendor/font-awesome/css/fontawesome-all.min.css
Local	https://simplelogin.io/assets/vendor/hs-megamenu/src/hs.megamenu.css
Local	https://simplelogin.io/assets/vendor/slick-carousel/slick/slick.css
Local	https://simplelogin.io/custom.css?v=4
Local	https://simplelogin.io/prism.css

Analysis

No remote resources

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

Expect CT

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

Test passed

Everything seems to be well configured. Well done.

Expect-CT Policy

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

Analysis

Header information

Policy text: enforce, max-age=604800, report-uri="https://simplelogin.report-uri.com/r/d/ct/enforce"

Reporting endpoint operational

Good. The reporting endpoint accepted our test submission.

Report URI: https://simplelogin.report-uri.com/r/d/ct/enforce

Expect-CT enabled

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

Frame Options

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

Test passed

Everything seems to be well configured. Well done.

Analysis

Header information

Name: X-Frame-Options

Value: SAMEORIGIN

Framing allowed from the same origin only

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

XSS Protection

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

Test passed, but there are warnings

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

Analysis

Header information

Name: X-XSS-Protection

Value: 1; mode=block

XSS auditor blocking is dangerous

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

Content Type Options

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

Test passed

Everything seems to be well configured. Well done.

Analysis

Header information

Name: X-Content-Type-Options

Value: nosniff

Valid configuration

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

Public Report | simplelogin.io

simplelogin.io

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.simplelogin.co (176.119.200.136)

Analysis

TLS Configuration: mx2.simplelogin.co (176.119.200.136)

Analysis

Email Certificates (SMTP)

Certificate #1

Analysis

Certificate Chain

Analysis

Email DANE (SMTP)

DANE: mx1.simplelogin.co (176.119.200.136)

Analysis

DANE: mx2.simplelogin.co (176.119.200.136)

Analysis

SPF

SPF Policy Information Main policy

Analysis

SPF Policy Information Included policy

DMARC

DMARC Policy Information

Analysis

MTA Strict Transport Security

MTA-STS Policy Indicator

Analysis

MTA-STS Policy

Analysis

Certificate: mta-sts.simplelogin.io

Analysis

Certificate Chain

Analysis

SMTP TLS Reporting

TLS-RPT Policy

Analysis

HTTP (80)

URL: http://simplelogin.io/

Analysis

URL: http://www.simplelogin.io/

Analysis

HTTP (443)

URL: https://simplelogin.io/

URL: https://www.simplelogin.io/

WWW TLS

TLS Configuration: simplelogin.io (176.119.200.11)

Analysis

TLS Configuration: www.simplelogin.io (176.119.200.11)

Analysis

WWW Certificates

Certificate: www.simplelogin.io

Analysis

Certificate Trust

Certificate Chain

Analysis

Certificate: www.simplelogin.io

Analysis

Certificate Trust

Certificate Chain

Analysis