Hardenize Report: mailbox.org

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

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 failed

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

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
dns3.cloudns.net. 185.136.96.88 2a06:fb00:1::1:88				NS REFERRAL
dns4.cloudns.net. 185.136.97.88 2a06:fb00:1::2:88				NS REFERRAL
ns.jpberlin.de. PRIMARY 91.198.250.3 2001:67c:2050:1::53:1				NS REFERRAL SOA
ns2.jpberlin.de. 194.150.191.56				NS REFERRAL
ns3.jpberlin.de. 88.198.52.15 2a01:4f8:221:4381::1				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
185.136.96.88 dns3.cloudns.net. PTR: dns3.cloudns.net.	NAME	4096
185.136.97.88 dns4.cloudns.net. PTR: dns4.cloudns.net.	NAME	4096
194.150.191.56 ns2.jpberlin.de. PTR: ns2.jpberlin.de.	NAME	1480
88.198.52.15 ns3.jpberlin.de. PTR: ns3.jpberlin.de.	NAME	1232
91.198.250.3 PRIMARY ns.jpberlin.de. PTR: ns.jpberlin.de.	NAME	1480
2001:67c:2050:1::53:1 PRIMARY ns.jpberlin.de. PTR: ns.jpberlin.de.	NAME	-
2a01:4f8:221:4381::1 ns3.jpberlin.de. PTR: ns3.jpberlin.de.	NAME	-
2a06:fb00:1::1:88 dns3.cloudns.net. PTR: dns3.cloudns.net.	NAME	-
2a06:fb00:1::2:88 dns4.cloudns.net. PTR: dns4.cloudns.net.	NAME	-

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	ns.jpberlin.de.
Email address of the persons responsible for this zone. Also known as RNAME.Admin email	root.jpberlin.de.
Zone serial or version number.Serial number	2014124154
The length of time secondary nameservers should wait before querying the primary for changes.Refresh interval	40,000 seconds (about 11 hours 6 minutes)
The length of time secondary nameservers should wait before querying an unresponsive primary again.Retry interval	7,200 seconds (about 2 hours)
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	86,400 seconds (about 1 day)
Time To Live (TTL) indicates for how long a record remains valid. SOA record TTL	900 seconds (about 15 minutes)

Analysis

Nameserver is not operational

We were not able to obtain any valid responses from this nameserver. This means that the server is either offline, or that the DNS configuration is wrong. In the latter case, someone taking over control of this server could lead to nameserver takeover. Check if the IP address of the server is provided only via glue. In that case, the nameservers in the parent zone are misconfigured.

Address: 2001:67c:2050:1::53:1

Reverse name: ns.jpberlin.de.

Name: ns.jpberlin.de.

Nameserver is not operational

We were not able to obtain any valid responses from this nameserver. This means that the server is either offline, or that the DNS configuration is wrong. In the latter case, someone taking over control of this server could lead to nameserver takeover. Check if the IP address of the server is provided only via glue. In that case, the nameservers in the parent zone are misconfigured.

Address: 2a01:4f8:221:4381::1

Reverse name: ns3.jpberlin.de.

Name: ns3.jpberlin.de.

Nameserver is not operational

We were not able to obtain any valid responses from this nameserver. This means that the server is either offline, or that the DNS configuration is wrong. In the latter case, someone taking over control of this server could lead to nameserver takeover. Check if the IP address of the server is provided only via glue. In that case, the nameservers in the parent zone are misconfigured.

Address: 2a06:fb00:1::1:88

Reverse name: dns3.cloudns.net.

Name: dns3.cloudns.net.

Nameserver is not operational

We were not able to obtain any valid responses from this nameserver. This means that the server is either offline, or that the DNS configuration is wrong. In the latter case, someone taking over control of this server could lead to nameserver takeover. Check if the IP address of the server is provided only via glue. In that case, the nameservers in the parent zone are misconfigured.

Address: 2a06:fb00:1::2:88

Reverse name: dns4.cloudns.net.

Name: dns4.cloudns.net.

Improve IPv6 support

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

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
mailbox.org.	900	A	185.97.174.194
www.mailbox.org.	900	A	185.97.174.194
mailbox.org.	900	AAAA	2001:67c:2050:b100:1:443:0:194
www.mailbox.org.	900	AAAA	2001:67c:2050:b100:1:443:0:194
mailbox.org.	300	CAA	0 iodef "mailto:security@heinlein-support.de"
mailbox.org.	300	CAA	0 issue "swisssign.com"
mailbox.org.	300	CAA	0 issue "letsencrypt.org"
mailbox.org.	300	CAA	0 iodef "mailto:mail@heinlein-support.de"
mailbox.org.	300	CAA	0 issue "digicert.com"
mailbox.org.	900	DNSKEY	256 3 10 BQEAAAAB1LEf+LUCBcflBj5sFAJiZnhv9WBP8lVkaau+VW9vVV4soJ/Q7UJz+pbhMPDFicgzArADejYML+zl8Lkn9vRRd+pu2iQ/vZnfpKQkuNCcd7eba4JSG24cO7TVLCdfsGJqvNgoN15mMUXKnTbhP+nFq9mfGIjKBTELekqkkYLl3zs=
mailbox.org.	900	DNSKEY	257 3 7 AwEAAdAx4Z+YqK6hogFjzM7TddRVDK9lE5WY9qTmWRwxAHDWYOOVV4b/N6FksRFWXV3rXfMIiyXRfdzt1Lnwt3rS2v9nYRCNlg1FDLHGwyDwV/I0D6CwgeZbTX7PSOL4oR0nFE1BYCbE2bHckgVE33tDF5fasDU0jXF00T9DPAhO0rxj
mailbox.org.	900	DNSKEY	256 3 7 BQEAAAABwcvTaaZokGcz2HFSgv+ixKiuypnYzA3z/pu9MlZ1XFD2qeN7KgVB/mmlvFKDUgKdraUV2m2KglZLzc4d8GoXTnpLDhcWVJx9et9tDYVUzzrXyW6SL/mEYUIoK9KvVP5gTUxU9eRr0qohT36SL7QdPR16Lig7jANGeCQKLsJNQ08=
mailbox.org.	3600	HTTPS	1 . alpn=http/1.1
www.mailbox.org.	3600	HTTPS	1 . alpn=http/1.1
mailbox.org.	7200	MX	50 mx-n.mailbox.org.
mailbox.org.	7200	MX	10 mx1.mailbox.org.
mailbox.org.	7200	MX	10 mx2.mailbox.org.
mailbox.org.	7200	MX	20 mx3.mailbox.org.
mailbox.org.	45	NS	ns.jpberlin.de.
mailbox.org.	45	NS	ns3.jpberlin.de.
mailbox.org.	45	NS	ns2.jpberlin.de.
mailbox.org.	45	NS	dns4.cloudns.net.
mailbox.org.	45	NS	dns3.cloudns.net.
mailbox.org.	900	SOA	ns.jpberlin.de. root.jpberlin.de. 2014124154 40000 7200 604800 86400
_xmpp-client._tcp.mailbox.org.	300	SRV	0 5 5222 xmpp.mailbox.org.
_xmpp-server._tcp.mailbox.org.	300	SRV	0 5 5269 xmpp.mailbox.org.
mailbox.org.	60	TXT	"google-site-verification=ojrG-cXIWNDWMmRomplDCsZknBUmg2PO32SffP1Xy2E"
mailbox.org.	60	TXT	"mailru-verification: 0c2c482975b1fc2f"
mailbox.org.	60	TXT	"swisssign-check=1tuXIQOBa4NZh2EIQI5nFD8fbJW2EvxB6W8rYhAoQ5"
mailbox.org.	60	TXT	"v=spf1 ip4:213.203.238.0/25 ip4:195.10.208.0/24 ip4:91.198.250.0/24 ip4:80.241.56.0/21 ip6:2001:67c:2050::/48 mx ~all"
mailbox.org.	60	TXT	"have-i-been-pwned-verification=aa98600469e4f52f5b4c8e6952a0927d"
mailbox.org.	60	TXT	"google-site-verification=bCdtsEmyfsVIfzBgWZpEvCf3TeJgpw0f6x5miXGwakY"
_dmarc.mailbox.org.	3600	TXT	"v=DMARC1; p=reject; adkim=r; aspf=r; pct=100; rua=mailto:abuse+arf@heinlein-support.de; rf=afrf; fo=1;"
_mta-sts.mailbox.org.	300	TXT	"v=STSv1;" "id=20181001090000"
_smtp._tls.mailbox.org.	3600	TXT	"v=TLSRPTv1;rua=mailto:abuse@heinlein-support.de"

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	mailbox.org
The issue property tag is used to request that certificate issuers perform CAA issue restriction processing for the domain and to grant authorization to specific certificate issuers.issue	letsencrypt.org flags: 0
The iodef property specifies a means of reporting certificate issue requests or cases of certificate issue for the corresponding domain that violate the security policy of the issuer or the domain name holder.iodef	mailto:security@heinlein-support.de flags: 0
The iodef property specifies a means of reporting certificate issue requests or cases of certificate issue for the corresponding domain that violate the security policy of the issuer or the domain name holder.iodef	mailto:mail@heinlein-support.de 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 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	swisssign.com flags: 0

Analysis

Issuance of S/MIME certificates not restricted

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

Issuance of BIMI not restricted

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

CAA policy restricts issuance

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

Policy uses reporting

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

Email (SMTP)

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

Test failed

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

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

Server	Preference	Operational	STARTTLS	TLS	PKI	DNSSEC	DANE
mx2.mailbox.org 2001:67c:2050:104:0:2:25:1 PTR: mx2.mailbox.org	10
mx2.mailbox.org 80.241.60.215 PTR: mx2.mailbox.org	10
mx1.mailbox.org 2001:67c:2050:104:0:1:25:1 PTR: mx1.mailbox.org	10
mx1.mailbox.org 80.241.60.212 PTR: mx1.mailbox.org	10
mx3.mailbox.org 2001:67c:2050:104:0:3:25:1 PTR: mx3.mailbox.org	20
mx3.mailbox.org 80.241.60.216 PTR: mx3.mailbox.org	20
mx-n.mailbox.org 2001:67c:2050:104:0:ffff:25:1 PTR: mx-n.mailbox.org	50
mx-n.mailbox.org 91.198.250.17 PTR: mx-n.mailbox.org	50

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.

Network Error

A network error occurred while we were trying to communicate with a server.

Address: 2001:67c:2050:104:0:ffff:25:1

Error message: Connect timed out

Host: mx-n.mailbox.org

Network Error

A network error occurred while we were trying to communicate with a server.

Address: 91.198.250.17

Error message: Connect timed out

Host: mx-n.mailbox.org

Some SMTP server assessments have been retrieved from cache

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

Latest cache timestamp: 31 Oct 2024 20:36 UTC

Earliest cache timestamp: 31 Oct 2024 20:36 UTC

Some SMTP server assessments contain partial information

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

Email TLS (SMTP)

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

Test failed

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

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

TLS Configuration: mx2.mailbox.org (2001:67c:2050:104:0:2:25:1) Cached

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

Analysis

TLS 1.2 supported

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

Strong key exchange detected

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

Partial results shown

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

Relaxed TLS assessment criteria applied to SMTP on port 25

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

TLS Configuration: mx2.mailbox.org (80.241.60.215) Cached

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

Analysis

TLS 1.2 supported

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

Strong key exchange detected

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

Partial results shown

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

Relaxed TLS assessment criteria applied to SMTP on port 25

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

TLS Configuration: mx1.mailbox.org (2001:67c:2050:104:0:1:25:1) Cached

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

Analysis

TLS 1.2 supported

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

Strong key exchange detected

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

Partial results shown

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

Relaxed TLS assessment criteria applied to SMTP on port 25

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

TLS Configuration: mx1.mailbox.org (80.241.60.212) Cached

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

Analysis

TLS 1.2 supported

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

Strong key exchange detected

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

Partial results shown

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

Relaxed TLS assessment criteria applied to SMTP on port 25

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

TLS Configuration: mx3.mailbox.org (2001:67c:2050:104:0:3:25:1) Cached

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

Analysis

TLS 1.2 supported

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

Strong key exchange detected

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

Partial results shown

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

Relaxed TLS assessment criteria applied to SMTP on port 25

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

TLS Configuration: mx3.mailbox.org (80.241.60.216) Cached

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

Analysis

TLS 1.2 supported

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

Strong key exchange detected

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

Partial results shown

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

Relaxed TLS assessment criteria applied to SMTP on port 25

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

Analysis

Network Error

A network error occurred while we were trying to communicate with a server.

Hostname: mx-n.mailbox.org

Error message: Connect timed out

IP address: 2001:67c:2050:104:0:ffff:25:1

Network Error

A network error occurred while we were trying to communicate with a server.

Hostname: mx-n.mailbox.org

Error message: Connect timed out

IP address: 91.198.250.17

Email Certificates (SMTP)

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

Test passed

Everything seems to be well configured. Well done.

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

Certificate #1 Cached

Leaf certificate

*.mailbox.org
Issuer: DigiCert
Not Before: 13 May 2024 00:00:00 UTC
Not After: 10 Jun 2025 23:59:59 UTC (expires in 7 months 4 days)
Key: RSA 4096 bits
Signature: SHA256withRSA
View details

Names	*.mailbox.org mailbox.org
Subject DN	CN=*.mailbox.org
Subject Key Identifier	67757539e587ffbbfa1396e908a1b555c861aa08
Serial	f3d7c6cfbe0096e2085bf06f162de32
Not Before	13 May 2024 00:00:00 UTC
Not After	10 Jun 2025 23:59:59 UTC
Validity period	394 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=Thawte TLS RSA CA G1, OU=www.digicert.com, O=DigiCert Inc, C=US
Certification Authority	DigiCert
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:a58cfe32cceb0f2cd419c608b80024885dc3c5b7
Parent Certificate	http://cacerts.thawte.com/ThawteTLSRSACAG1.crt
CRL	http://cdp.thawte.com/ThawteTLSRSACAG1.crl
OCSP	http://status.thawte.com
Certificate Transparency
Signed Certificate Timestamps	13 May 2024 11:37:45 UTC \| Google 'Argon2025h1' log \| Qualified 13 May 2024 11:37:45 UTC \| DigiCert Yeti2025 Log \| Qualified 13 May 2024 11:37:45 UTC \| DigiCert Nessie2025 Log \| Qualified
Fingerprints
SHA1	38d6cf2df22a5cdc2d920ea946d34092176ea8d8
SHA256	a8485043dbf16096aa1fc342dd297c23f5b0baae72c3be269c9815c522778dec
SPKI SHA256	996ad31d65e03f038b8ec950f6f26611529da03e3a283e4400cba2edd04b8a88

Analysis

Strong private key

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

Strong signature algorithm

Good. This certificate uses a strong signature algorithm.

Certificate matches hostname

Good. The provided certificate matches the expected hostnames.

Certificate dates match

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

Certificate has not been revoked

Good. This certificate has not been revoked.

Certificate satisfies Apple's CT compliance requirements

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

Symantec subordinate CA excluded from early expiration

Although the leaf certificate ultimately chains to a Symantec root, it has been issued from an independently-operated subordinate CA that has been excluded from early expiration.

Certificate Chain

Leaf certificate

*.mailbox.org | a848504
Not After: 10 Jun 2025 23:59:59 UTC (expires in 7 months 4 days)
Authentication: RSA 4096 bits (SHA256withRSA)
View details

Names	*.mailbox.org mailbox.org
Subject DN	CN=*.mailbox.org
Subject Key Identifier	67757539e587ffbbfa1396e908a1b555c861aa08
Serial	f3d7c6cfbe0096e2085bf06f162de32
Not Before	13 May 2024 00:00:00 UTC
Not After	10 Jun 2025 23:59:59 UTC
Validity period	394 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=Thawte TLS RSA CA G1, OU=www.digicert.com, O=DigiCert Inc, C=US
Certification Authority	DigiCert
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:a58cfe32cceb0f2cd419c608b80024885dc3c5b7
Parent Certificate	http://cacerts.thawte.com/ThawteTLSRSACAG1.crt
CRL	http://cdp.thawte.com/ThawteTLSRSACAG1.crl
OCSP	http://status.thawte.com
Certificate Transparency
Signed Certificate Timestamps	13 May 2024 11:37:45 UTC \| Google 'Argon2025h1' log \| Qualified 13 May 2024 11:37:45 UTC \| DigiCert Yeti2025 Log \| Qualified 13 May 2024 11:37:45 UTC \| DigiCert Nessie2025 Log \| Qualified
Fingerprints
SHA1	38d6cf2df22a5cdc2d920ea946d34092176ea8d8
SHA256	a8485043dbf16096aa1fc342dd297c23f5b0baae72c3be269c9815c522778dec
SPKI SHA256	996ad31d65e03f038b8ec950f6f26611529da03e3a283e4400cba2edd04b8a88

Intermediate certificate

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

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

Root certificate

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

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

Analysis

Certificate chain is correct

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

Email DANE (SMTP)

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

Test passed, but there are warnings

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

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

DANE: mx2.mailbox.org (2001:67c:2050:104:0:2:25:1)

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

Analysis

No service detected

We've detected DANE configuration which may or may not be valid, but there's no service (certificates) to match against. If you don't want to provide service you should remove the DANE records.

DANE: mx2.mailbox.org (80.241.60.215)

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

Analysis

Valid DANE configuration

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

DANE: mx1.mailbox.org (2001:67c:2050:104:0:1:25:1)

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

Analysis

No service detected

We've detected DANE configuration which may or may not be valid, but there's no service (certificates) to match against. If you don't want to provide service you should remove the DANE records.

DANE: mx1.mailbox.org (80.241.60.212)

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

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: mx3.mailbox.org (2001:67c:2050:104:0:3:25:1)

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

Analysis

No service detected

We've detected DANE configuration which may or may not be valid, but there's no service (certificates) to match against. If you don't want to provide service you should remove the DANE records.

DANE: mx3.mailbox.org (80.241.60.216)

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

Analysis

Valid DANE configuration

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

DANE: mx-n.mailbox.org (2001:67c:2050:104:0:ffff:25:1)

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

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

Analysis

No service detected

We've detected DANE configuration which may or may not be valid, but there's no service (certificates) to match against. If you don't want to provide service you should remove the DANE records.

DANE: mx-n.mailbox.org (91.198.250.17)

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

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

Analysis

No service detected

We've detected DANE configuration which may or may not be valid, but there's no service (certificates) to match against. If you don't want to provide service you should remove the DANE records.

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	mailbox.org
SPF version used by this policy.v	spf1
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	213.203.238.0/25
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	195.10.208.0/24
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	91.198.250.0/24
This mechanism tests whether the IP address being tested is contained within a given IPv4 network. ip4	80.241.56.0/21
This mechanism tests whether the IP address being tested is contained within a given IPv6 network. ip6	2001:67c:2050::/48
This mechanism matches if the sending IP address is one of the MX hosts for the domain name. mx
This policy element always matches. It's normally used at the end of a policy to specify the handling of hosts that don't match earlier mechanisms. ~all

Analysis

SPF policy found

Policy text: v=spf1 ip4:213.203.238.0/25 ip4:195.10.208.0/24 ip4:91.198.250.0/24 ip4:80.241.56.0/21 ip6:2001:67c:2050::/48 mx ~all

Location: mailbox.org

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

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.mailbox.org
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
Indicates whether strict or relaxed DKIM alignment mode is required.adkim	r
Indicates whether strict or relaxed SPF alignment mode is required.aspf	r
Percentage of messages from mail stream to which the DMARC policy is to be applied.pct	100
Addresses to which aggregate feedback is to be sent.rua	mailto:abuse+arf@heinlein-support.de
Specifies the format to be used when reporting failures.rf	afrf
Configures failure reporting.fo	1

Analysis

DMARC policy found

Policy: v=DMARC1; p=reject; adkim=r; aspf=r; pct=100; rua=mailto:abuse+arf@heinlein-support.de; rf=afrf; fo=1;

Host: _dmarc.mailbox.org

Valid external destination

Permission record location: mailbox.org._report._dmarc.heinlein-support.de

External destination: mailto:abuse+arf@heinlein-support.de

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.mailbox.org
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	20181001090000

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

Analysis

MTA-STS policy is valid

Good. Your MTA-STS policy is valid.

Policy host certificate is valid

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

Policy HTTPS response information

Status code: 200

Length: 170 bytes

Content-Type: text/plain

Certificate: mta-sts.mailbox.org

Leaf certificate

*.mailbox.org
Issuer: DigiCert
Not Before: 13 May 2024 00:00:00 UTC
Not After: 10 Jun 2025 23:59:59 UTC (expires in 7 months 4 days)
Key: RSA 4096 bits
Signature: SHA256withRSA
View details

Names	*.mailbox.org mailbox.org
Subject DN	CN=*.mailbox.org
Subject Key Identifier	67757539e587ffbbfa1396e908a1b555c861aa08
Serial	f3d7c6cfbe0096e2085bf06f162de32
Not Before	13 May 2024 00:00:00 UTC
Not After	10 Jun 2025 23:59:59 UTC
Validity period	394 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=Thawte TLS RSA CA G1, OU=www.digicert.com, O=DigiCert Inc, C=US
Certification Authority	DigiCert
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:a58cfe32cceb0f2cd419c608b80024885dc3c5b7
Parent Certificate	http://cacerts.thawte.com/ThawteTLSRSACAG1.crt
CRL	http://cdp.thawte.com/ThawteTLSRSACAG1.crl
OCSP	http://status.thawte.com
Certificate Transparency
Signed Certificate Timestamps	13 May 2024 11:37:45 UTC \| Google 'Argon2025h1' log \| Qualified 13 May 2024 11:37:45 UTC \| DigiCert Yeti2025 Log \| Qualified 13 May 2024 11:37:45 UTC \| DigiCert Nessie2025 Log \| Qualified
Fingerprints
SHA1	38d6cf2df22a5cdc2d920ea946d34092176ea8d8
SHA256	a8485043dbf16096aa1fc342dd297c23f5b0baae72c3be269c9815c522778dec
SPKI SHA256	996ad31d65e03f038b8ec950f6f26611529da03e3a283e4400cba2edd04b8a88

Analysis

Strong private key

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

Strong signature algorithm

Good. This certificate uses a strong signature algorithm.

Certificate matches hostname

Good. The provided certificate matches the expected hostnames.

Certificate dates match

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

Certificate has not been revoked

Good. This certificate has not been revoked.

Certificate satisfies Apple's CT compliance requirements

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

Symantec subordinate CA excluded from early expiration

Although the leaf certificate ultimately chains to a Symantec root, it has been issued from an independently-operated subordinate CA that has been excluded from early expiration.

Certificate Chain

Leaf certificate

*.mailbox.org | a848504
Not After: 10 Jun 2025 23:59:59 UTC (expires in 7 months 4 days)
Authentication: RSA 4096 bits (SHA256withRSA)
View details

Names	*.mailbox.org mailbox.org
Subject DN	CN=*.mailbox.org
Subject Key Identifier	67757539e587ffbbfa1396e908a1b555c861aa08
Serial	f3d7c6cfbe0096e2085bf06f162de32
Not Before	13 May 2024 00:00:00 UTC
Not After	10 Jun 2025 23:59:59 UTC
Validity period	394 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=Thawte TLS RSA CA G1, OU=www.digicert.com, O=DigiCert Inc, C=US
Certification Authority	DigiCert
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:a58cfe32cceb0f2cd419c608b80024885dc3c5b7
Parent Certificate	http://cacerts.thawte.com/ThawteTLSRSACAG1.crt
CRL	http://cdp.thawte.com/ThawteTLSRSACAG1.crl
OCSP	http://status.thawte.com
Certificate Transparency
Signed Certificate Timestamps	13 May 2024 11:37:45 UTC \| Google 'Argon2025h1' log \| Qualified 13 May 2024 11:37:45 UTC \| DigiCert Yeti2025 Log \| Qualified 13 May 2024 11:37:45 UTC \| DigiCert Nessie2025 Log \| Qualified
Fingerprints
SHA1	38d6cf2df22a5cdc2d920ea946d34092176ea8d8
SHA256	a8485043dbf16096aa1fc342dd297c23f5b0baae72c3be269c9815c522778dec
SPKI SHA256	996ad31d65e03f038b8ec950f6f26611529da03e3a283e4400cba2edd04b8a88

Intermediate certificate

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

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

Root certificate

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

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

Analysis

Certificate chain is correct

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

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

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://mailbox.org/

1

http://mailbox.org/

HTTP/1.1 302 Found

Date	Wed, 06 Nov 2024 04:17:40 GMT
Server	Apache
Location	https://mailbox.org/
Content-Length	204
Keep-Alive	timeout=15, max=100
Connection	Keep-Alive
Content-Type	text/html; charset=iso-8859-1

2

https://mailbox.org/

HTTP/1.1 302 Found

Date	Wed, 06 Nov 2024 04:17:41 GMT
Server	Apache
Cache-Control	no-cache, private
Referrer-Policy	no-referrer-when-downgrade, strict-origin-when-cross-origin
Permissions-Policy	interest-cohort=()
Contao-Cache	miss
Strict-Transport-Security	max-age=15768000; includeSubDomains; preload
Location	https://mailbox.org/en/
Cache-Control	max-age=300
Expires	Wed, 06 Nov 2024 04:22:41 GMT
Vary	Origin
X-Permitted-Cross-Domain-Policies	none
Permissions-Policy	accelerometer=(), camera=(), gyroscope=(), magnetometer=(), microphone=(), usb=()
Content-Security-Policy	default-src 'self' ; img-src 'self' .mailbox.org; script-src 'self' .mailbox.org; style-src 'self' data: 'unsafe-inline' ; frame-src 'self' .mailbox.org; frame-ancestors 'self'; object-src 'none'; connect-src 'self' .mailbox.org;
Keep-Alive	timeout=15, max=100
Connection	Keep-Alive
Transfer-Encoding	chunked
Content-Type	text/html; charset=UTF-8

3

https://mailbox.org/en/

HTTP/1.1 200 OK

Date	Wed, 06 Nov 2024 04:17:41 GMT
Server	Apache
Cache-Control	must-revalidate, no-cache, no-store, private
X-Content-Type-Options	nosniff
Referrer-Policy	no-referrer-when-downgrade, strict-origin-when-cross-origin
Permissions-Policy	interest-cohort=()
X-Frame-Options	SAMEORIGIN
X-XSS-Protection	1; mode=block
Contao-Cache	miss
Age	0
Strict-Transport-Security	max-age=15768000; includeSubDomains; preload
Cache-Control	max-age=300
Expires	Wed, 06 Nov 2024 04:22:41 GMT
Vary	Accept-Encoding,Origin
X-Permitted-Cross-Domain-Policies	none
Permissions-Policy	accelerometer=(), camera=(), gyroscope=(), magnetometer=(), microphone=(), usb=()
Content-Security-Policy	default-src 'self' ; img-src 'self' .mailbox.org; script-src 'self' .mailbox.org; style-src 'self' data: 'unsafe-inline' ; frame-src 'self' .mailbox.org; frame-ancestors 'self'; object-src 'none'; connect-src 'self' .mailbox.org;
Keep-Alive	timeout=15, max=100
Connection	Keep-Alive
Content-Type	text/html; charset=utf-8

Analysis

HTTP redirects to HTTPS

Good. This plaintext HTTP server redirects to HTTPS.

URL: http://www.mailbox.org/

1

http://www.mailbox.org/

HTTP/1.1 302 Found

Date	Wed, 06 Nov 2024 04:17:42 GMT
Server	Apache
Location	https://mailbox.org/
Content-Length	204
Keep-Alive	timeout=15, max=100
Connection	Keep-Alive
Content-Type	text/html; charset=iso-8859-1

2

https://mailbox.org/

HTTP/1.1 302 Found

Date	Wed, 06 Nov 2024 04:17:54 GMT
Server	Apache
Cache-Control	no-cache, private
Referrer-Policy	no-referrer-when-downgrade, strict-origin-when-cross-origin
Permissions-Policy	interest-cohort=()
Contao-Cache	miss
Strict-Transport-Security	max-age=15768000; includeSubDomains; preload
Location	https://mailbox.org/en/
Cache-Control	max-age=300
Expires	Wed, 06 Nov 2024 04:22:54 GMT
Vary	Origin
X-Permitted-Cross-Domain-Policies	none
Permissions-Policy	accelerometer=(), camera=(), gyroscope=(), magnetometer=(), microphone=(), usb=()
Content-Security-Policy	default-src 'self' ; img-src 'self' .mailbox.org; script-src 'self' .mailbox.org; style-src 'self' data: 'unsafe-inline' ; frame-src 'self' .mailbox.org; frame-ancestors 'self'; object-src 'none'; connect-src 'self' .mailbox.org;
Keep-Alive	timeout=15, max=100
Connection	Keep-Alive
Transfer-Encoding	chunked
Content-Type	text/html; charset=UTF-8

3

https://mailbox.org/en/

HTTP/1.1 200 OK

Date	Wed, 06 Nov 2024 04:18:05 GMT
Server	Apache
Cache-Control	must-revalidate, no-cache, no-store, private
X-Content-Type-Options	nosniff
Referrer-Policy	no-referrer-when-downgrade, strict-origin-when-cross-origin
Permissions-Policy	interest-cohort=()
X-Frame-Options	SAMEORIGIN
X-XSS-Protection	1; mode=block
Contao-Cache	miss
Age	0
Strict-Transport-Security	max-age=15768000; includeSubDomains; preload
Cache-Control	max-age=300
Expires	Wed, 06 Nov 2024 04:23:05 GMT
Vary	Accept-Encoding,Origin
X-Permitted-Cross-Domain-Policies	none
Permissions-Policy	accelerometer=(), camera=(), gyroscope=(), magnetometer=(), microphone=(), usb=()
Content-Security-Policy	default-src 'self' ; img-src 'self' .mailbox.org; script-src 'self' .mailbox.org; style-src 'self' data: 'unsafe-inline' ; frame-src 'self' .mailbox.org; frame-ancestors 'self'; object-src 'none'; connect-src 'self' .mailbox.org;
Keep-Alive	timeout=15, max=100
Connection	Keep-Alive
Content-Type	text/html; charset=utf-8

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://mailbox.org/

1

https://mailbox.org/

HTTP/1.1 302 Found

Date	Wed, 06 Nov 2024 04:18:05 GMT
Server	Apache
Cache-Control	no-cache, private
Referrer-Policy	no-referrer-when-downgrade, strict-origin-when-cross-origin
Permissions-Policy	interest-cohort=()
Contao-Cache	miss
Strict-Transport-Security	max-age=15768000; includeSubDomains; preload
Location	https://mailbox.org/en/
Cache-Control	max-age=300
Expires	Wed, 06 Nov 2024 04:23:05 GMT
Vary	Origin
X-Permitted-Cross-Domain-Policies	none
Permissions-Policy	accelerometer=(), camera=(), gyroscope=(), magnetometer=(), microphone=(), usb=()
Content-Security-Policy	default-src 'self' ; img-src 'self' .mailbox.org; script-src 'self' .mailbox.org; style-src 'self' data: 'unsafe-inline' ; frame-src 'self' .mailbox.org; frame-ancestors 'self'; object-src 'none'; connect-src 'self' .mailbox.org;
Keep-Alive	timeout=15, max=100
Connection	Keep-Alive
Transfer-Encoding	chunked
Content-Type	text/html; charset=UTF-8

2

https://mailbox.org/en/

HTTP/1.1 200 OK

Date	Wed, 06 Nov 2024 04:18:06 GMT
Server	Apache
Cache-Control	must-revalidate, no-cache, no-store, private
X-Content-Type-Options	nosniff
Referrer-Policy	no-referrer-when-downgrade, strict-origin-when-cross-origin
Permissions-Policy	interest-cohort=()
X-Frame-Options	SAMEORIGIN
X-XSS-Protection	1; mode=block
Contao-Cache	miss
Age	0
Strict-Transport-Security	max-age=15768000; includeSubDomains; preload
Cache-Control	max-age=300
Expires	Wed, 06 Nov 2024 04:23:06 GMT
Vary	Accept-Encoding,Origin
X-Permitted-Cross-Domain-Policies	none
Permissions-Policy	accelerometer=(), camera=(), gyroscope=(), magnetometer=(), microphone=(), usb=()
Content-Security-Policy	default-src 'self' ; img-src 'self' .mailbox.org; script-src 'self' .mailbox.org; style-src 'self' data: 'unsafe-inline' ; frame-src 'self' .mailbox.org; frame-ancestors 'self'; object-src 'none'; connect-src 'self' .mailbox.org;
Keep-Alive	timeout=15, max=100
Connection	Keep-Alive
Content-Type	text/html; charset=utf-8

URL: https://www.mailbox.org/

1

https://www.mailbox.org/

HTTP/1.1 302 Found

Date	Wed, 06 Nov 2024 04:18:07 GMT
Server	Apache
Location	https://mailbox.org/
Content-Length	204
Keep-Alive	timeout=15, max=100
Connection	Keep-Alive
Content-Type	text/html; charset=iso-8859-1

2

https://mailbox.org/

HTTP/1.1 302 Found

Date	Wed, 06 Nov 2024 04:18:17 GMT
Server	Apache
Cache-Control	no-cache, private
Referrer-Policy	no-referrer-when-downgrade, strict-origin-when-cross-origin
Permissions-Policy	interest-cohort=()
Contao-Cache	miss
Strict-Transport-Security	max-age=15768000; includeSubDomains; preload
Location	https://mailbox.org/en/
Cache-Control	max-age=300
Expires	Wed, 06 Nov 2024 04:23:17 GMT
Vary	Origin
X-Permitted-Cross-Domain-Policies	none
Permissions-Policy	accelerometer=(), camera=(), gyroscope=(), magnetometer=(), microphone=(), usb=()
Content-Security-Policy	default-src 'self' ; img-src 'self' .mailbox.org; script-src 'self' .mailbox.org; style-src 'self' data: 'unsafe-inline' ; frame-src 'self' .mailbox.org; frame-ancestors 'self'; object-src 'none'; connect-src 'self' .mailbox.org;
Keep-Alive	timeout=15, max=100
Connection	Keep-Alive
Transfer-Encoding	chunked
Content-Type	text/html; charset=UTF-8

3

https://mailbox.org/en/

HTTP/1.1 200 OK

Date	Wed, 06 Nov 2024 04:18:28 GMT
Server	Apache
Cache-Control	must-revalidate, no-cache, no-store, private
X-Content-Type-Options	nosniff
Referrer-Policy	no-referrer-when-downgrade, strict-origin-when-cross-origin
Permissions-Policy	interest-cohort=()
X-Frame-Options	SAMEORIGIN
X-XSS-Protection	1; mode=block
Contao-Cache	miss
Age	0
Strict-Transport-Security	max-age=15768000; includeSubDomains; preload
Cache-Control	max-age=300
Expires	Wed, 06 Nov 2024 04:23:28 GMT
Vary	Accept-Encoding,Origin
X-Permitted-Cross-Domain-Policies	none
Permissions-Policy	accelerometer=(), camera=(), gyroscope=(), magnetometer=(), microphone=(), usb=()
Content-Security-Policy	default-src 'self' ; img-src 'self' .mailbox.org; script-src 'self' .mailbox.org; style-src 'self' data: 'unsafe-inline' ; frame-src 'self' .mailbox.org; frame-ancestors 'self'; object-src 'none'; connect-src 'self' .mailbox.org;
Keep-Alive	timeout=15, max=100
Connection	Keep-Alive
Content-Type	text/html; charset=utf-8

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 failed

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

TLS Configuration: www.mailbox.org (185.97.174.194)

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

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 not supported

This server doesn't support TLS 1.2, which may be necessary to support a wide range of clients, including the ones that don't yet support TLS 1.3. If you're receiving reports of connection problems to your web site, this could be the root cause.

Deprecated protocols not supported

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

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.

Server is not compliant with Chrome's CT requirements

Not all TLS connections with this server satisfy Chrome's CT requirements even. This is not necessarily a problem, as CT compliance is only required for certificates issued from May 2018.

DHE suites not supported

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

TLS Configuration: www.mailbox.org (2001:67c:2050:b100:1:443:0:194)

Analysis

TLS connection failed

We failed to connect to the server using TLS.

Error message: Connect timed out

TLS Configuration: mailbox.org (2001:67c:2050:b100:1:443:0:194)

Analysis

TLS connection failed

We failed to connect to the server using TLS.

Error message: Connect timed out

TLS Configuration: mailbox.org (185.97.174.194)

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

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: mailbox.org

Leaf certificate

*.mailbox.org
Issuer: DigiCert
Not Before: 13 May 2024 00:00:00 UTC
Not After: 10 Jun 2025 23:59:59 UTC (expires in 7 months 4 days)
Key: RSA 4096 bits
Signature: SHA256withRSA
View details

Names	*.mailbox.org mailbox.org
Subject DN	CN=*.mailbox.org
Subject Key Identifier	67757539e587ffbbfa1396e908a1b555c861aa08
Serial	f3d7c6cfbe0096e2085bf06f162de32
Not Before	13 May 2024 00:00:00 UTC
Not After	10 Jun 2025 23:59:59 UTC
Validity period	394 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=Thawte TLS RSA CA G1, OU=www.digicert.com, O=DigiCert Inc, C=US
Certification Authority	DigiCert
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:a58cfe32cceb0f2cd419c608b80024885dc3c5b7
Parent Certificate	http://cacerts.thawte.com/ThawteTLSRSACAG1.crt
CRL	http://cdp.thawte.com/ThawteTLSRSACAG1.crl
OCSP	http://status.thawte.com
Certificate Transparency
Signed Certificate Timestamps	13 May 2024 11:37:45 UTC \| Google 'Argon2025h1' log \| Qualified 13 May 2024 11:37:45 UTC \| DigiCert Yeti2025 Log \| Qualified 13 May 2024 11:37:45 UTC \| DigiCert Nessie2025 Log \| Qualified
Fingerprints
SHA1	38d6cf2df22a5cdc2d920ea946d34092176ea8d8
SHA256	a8485043dbf16096aa1fc342dd297c23f5b0baae72c3be269c9815c522778dec
SPKI SHA256	996ad31d65e03f038b8ec950f6f26611529da03e3a283e4400cba2edd04b8a88

Analysis

Strong private key

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

Strong signature algorithm

Good. This certificate uses a strong signature algorithm.

Certificate matches hostname

Good. The provided certificate matches the expected hostnames.

Certificate dates match

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

Certificate has not been revoked

Good. This certificate has not been revoked.

Certificate satisfies Apple's CT compliance requirements

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

Symantec subordinate CA excluded from early expiration

Although the leaf certificate ultimately chains to a Symantec root, it has been issued from an independently-operated subordinate CA that has been excluded from early expiration.

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

*.mailbox.org | a848504
Not After: 10 Jun 2025 23:59:59 UTC (expires in 7 months 4 days)
Authentication: RSA 4096 bits (SHA256withRSA)
View details

Names	*.mailbox.org mailbox.org
Subject DN	CN=*.mailbox.org
Subject Key Identifier	67757539e587ffbbfa1396e908a1b555c861aa08
Serial	f3d7c6cfbe0096e2085bf06f162de32
Not Before	13 May 2024 00:00:00 UTC
Not After	10 Jun 2025 23:59:59 UTC
Validity period	394 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=Thawte TLS RSA CA G1, OU=www.digicert.com, O=DigiCert Inc, C=US
Certification Authority	DigiCert
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:a58cfe32cceb0f2cd419c608b80024885dc3c5b7
Parent Certificate	http://cacerts.thawte.com/ThawteTLSRSACAG1.crt
CRL	http://cdp.thawte.com/ThawteTLSRSACAG1.crl
OCSP	http://status.thawte.com
Certificate Transparency
Signed Certificate Timestamps	13 May 2024 11:37:45 UTC \| Google 'Argon2025h1' log \| Qualified 13 May 2024 11:37:45 UTC \| DigiCert Yeti2025 Log \| Qualified 13 May 2024 11:37:45 UTC \| DigiCert Nessie2025 Log \| Qualified
Fingerprints
SHA1	38d6cf2df22a5cdc2d920ea946d34092176ea8d8
SHA256	a8485043dbf16096aa1fc342dd297c23f5b0baae72c3be269c9815c522778dec
SPKI SHA256	996ad31d65e03f038b8ec950f6f26611529da03e3a283e4400cba2edd04b8a88

Intermediate certificate

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

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

Root certificate

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

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

Analysis

Certificate chain is correct

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

Certificate: www.mailbox.org

Leaf certificate

*.mailbox.org
Issuer: DigiCert
Not Before: 13 May 2024 00:00:00 UTC
Not After: 10 Jun 2025 23:59:59 UTC (expires in 7 months 4 days)
Key: RSA 4096 bits
Signature: SHA256withRSA
View details

Names	*.mailbox.org mailbox.org
Subject DN	CN=*.mailbox.org
Subject Key Identifier	67757539e587ffbbfa1396e908a1b555c861aa08
Serial	f3d7c6cfbe0096e2085bf06f162de32
Not Before	13 May 2024 00:00:00 UTC
Not After	10 Jun 2025 23:59:59 UTC
Validity period	394 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=Thawte TLS RSA CA G1, OU=www.digicert.com, O=DigiCert Inc, C=US
Certification Authority	DigiCert
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:a58cfe32cceb0f2cd419c608b80024885dc3c5b7
Parent Certificate	http://cacerts.thawte.com/ThawteTLSRSACAG1.crt
CRL	http://cdp.thawte.com/ThawteTLSRSACAG1.crl
OCSP	http://status.thawte.com
Certificate Transparency
Signed Certificate Timestamps	13 May 2024 11:37:45 UTC \| Google 'Argon2025h1' log \| Qualified 13 May 2024 11:37:45 UTC \| DigiCert Yeti2025 Log \| Qualified 13 May 2024 11:37:45 UTC \| DigiCert Nessie2025 Log \| Qualified
Fingerprints
SHA1	38d6cf2df22a5cdc2d920ea946d34092176ea8d8
SHA256	a8485043dbf16096aa1fc342dd297c23f5b0baae72c3be269c9815c522778dec
SPKI SHA256	996ad31d65e03f038b8ec950f6f26611529da03e3a283e4400cba2edd04b8a88

Analysis

Strong private key

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

Strong signature algorithm

Good. This certificate uses a strong signature algorithm.

Certificate matches hostname

Good. The provided certificate matches the expected hostnames.

Certificate dates match

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

Certificate has not been revoked

Good. This certificate has not been revoked.

Certificate satisfies Apple's CT compliance requirements

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

Symantec subordinate CA excluded from early expiration

Although the leaf certificate ultimately chains to a Symantec root, it has been issued from an independently-operated subordinate CA that has been excluded from early expiration.

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

*.mailbox.org | a848504
Not After: 10 Jun 2025 23:59:59 UTC (expires in 7 months 4 days)
Authentication: RSA 4096 bits (SHA256withRSA)
View details

Names	*.mailbox.org mailbox.org
Subject DN	CN=*.mailbox.org
Subject Key Identifier	67757539e587ffbbfa1396e908a1b555c861aa08
Serial	f3d7c6cfbe0096e2085bf06f162de32
Not Before	13 May 2024 00:00:00 UTC
Not After	10 Jun 2025 23:59:59 UTC
Validity period	394 days
Key Usage	digitalSignature, keyEncipherment
Extended Key Usage	serverAuth, clientAuth
Must Staple	No
Issuer
Issuer DN	CN=Thawte TLS RSA CA G1, OU=www.digicert.com, O=DigiCert Inc, C=US
Certification Authority	DigiCert
Validation Type	Domain Validation (DV)
Authority Key Identifier	keyid:a58cfe32cceb0f2cd419c608b80024885dc3c5b7
Parent Certificate	http://cacerts.thawte.com/ThawteTLSRSACAG1.crt
CRL	http://cdp.thawte.com/ThawteTLSRSACAG1.crl
OCSP	http://status.thawte.com
Certificate Transparency
Signed Certificate Timestamps	13 May 2024 11:37:45 UTC \| Google 'Argon2025h1' log \| Qualified 13 May 2024 11:37:45 UTC \| DigiCert Yeti2025 Log \| Qualified 13 May 2024 11:37:45 UTC \| DigiCert Nessie2025 Log \| Qualified
Fingerprints
SHA1	38d6cf2df22a5cdc2d920ea946d34092176ea8d8
SHA256	a8485043dbf16096aa1fc342dd297c23f5b0baae72c3be269c9815c522778dec
SPKI SHA256	996ad31d65e03f038b8ec950f6f26611529da03e3a283e4400cba2edd04b8a88

Intermediate certificate

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

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

Root certificate

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

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

Analysis

Certificate chain is correct

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

DANE (443)

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

Test passed

Everything seems to be well configured. Well done.

TLSA Record #1: _443._tcp.mailbox.org.

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	51e89750f7d9d0867c2840dc66d9f635e2844541a38ef7586db59088b846fe59

TLSA Record #2: _443._tcp.mailbox.org.

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	e09e6e1d92c23ff23edbdce189da4a9133c94864db71f0f4c683542e5b6e2f2c

TLSA Record #3: _443._tcp.mailbox.org.

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	29681d7841e22492cc6bac79698b59192d474cc36e413627d5f06060766ed702

TLSA Record #4: _443._tcp.mailbox.org.

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

TLSA Record #5: _443._tcp.mailbox.org.

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	ece6745a10d73a2a5b0dcce5c319f0cfb281f48941ca548a9648f58ed1ab2a56

Analysis

DANE configuration matches

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

Valid DANE configuration

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

TLSA Record #6: _443._tcp.www.mailbox.org.

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

TLSA Record #7: _443._tcp.www.mailbox.org.

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	e09e6e1d92c23ff23edbdce189da4a9133c94864db71f0f4c683542e5b6e2f2c

TLSA Record #8: _443._tcp.www.mailbox.org.

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

TLSA Record #9: _443._tcp.www.mailbox.org.

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

Analysis

DANE configuration matches

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

Valid DANE configuration

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

Cookies

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

Test passed

Everything seems to be well configured. Well done.

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.

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

Status	Link
Encrypted	https://mailbox.org/...n.js,...-4dcf90c3.js
Encrypted	https://mailbox.org/files/js/numbers.js
Encrypted	https://mailbox.org/.../js/jquery-ui.min.js
Encrypted	https://mailbox.org/...x/js/colorbox.min.js
Encrypted	https://mailbox.org/...nt-and-player.min.js
Encrypted	https://mailbox.org/...js/highlight.pack.js
Encrypted	https://mailbox.org/...nt-and-player.min.js
Encrypted	https://mailbox.org/...query.marquee.min.js
Encrypted	https://mailbox.org/...uery.validate.min.js
Encrypted	https://mailbox.org/...s/rangeslider.min.js
Encrypted	https://mailbox.org/...iles/js/footer-en.js

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

Status	Link
Encrypted	https://mailbox.org/...tsKi...-2579b0e2.css

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

Status	Link
Encrypted	https://mailbox.org/...il-Anbieter-2021.jpg
Encrypted	https://mailbox.org/...role_1_data_EN_p.svg
Encrypted	https://mailbox.org/...le_2_Energy_EN_p.svg
Encrypted	https://mailbox.org/...role_3_GDPR_EN_p.svg
Encrypted	https://mailbox.org/..._Encryption_EN_p.svg
Encrypted	https://mailbox.org/...5_Security_EN_p2.svg
Encrypted	https://mailbox.org/...out/Privatkunden.jpg
Encrypted	https://mailbox.org/...o_start_business.jpg
Encrypted	https://mailbox.org/...ng-Beh%C3%B6rden.jpg
Encrypted	https://mailbox.org/...Kostenlos-Testen.jpg
Encrypted	https://mailbox.org/...er/Umzugsservice.jpg
Encrypted	https://mailbox.org/...er_eigene_domain.jpg
Encrypted	https://mailbox.org/...ugung-Motivation.jpg
Encrypted	https://mailbox.org/...go/opt-bg-slider.jpg
Encrypted	https://mailbox.org/...-opentalk-update.jpg
Encrypted	https://mailbox.org/...EO-peer-heinlein.jpg
Encrypted	https://mailbox.org/...email-continuity.jpg
Encrypted	https://mailbox.org/...bsi/sik_en-01012.png
Encrypted	https://mailbox.org/...bsi/sik_en-01011.png
Encrypted	https://mailbox.org/...bsi/sik_en-01010.png
Encrypted	https://mailbox.org/...ment/paypal_logo.svg
Encrypted	https://mailbox.org/...right-Retina%401.svg
Encrypted	https://mailbox.org/...t_RGB_black_60px.svg
Encrypted	https://mailbox.org/.../Payment/ec_logo.svg
Encrypted	https://mailbox.org/.../mastercard_logo.svg
Encrypted	https://mailbox.org/...ayment/visa_logo.svg
Encrypted	https://mailbox.org/...can_express_logo.svg
Encrypted	https://mailbox.org/.../Payment/SEPA_DE.svg

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.

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

Status	Link
Encrypted	https://login.mailbox.org/en
Encrypted	https://kb.mailbox.org/en/private
Encrypted	https://register.mailbox.org/en
Encrypted	https://register.mailbox.org/en
Encrypted	https://register.mailbox.org/en
Encrypted	https://register.mailbox.org/en/tariff
Encrypted	https://register.mailbox.org/en/tariff
Encrypted	https://register.mailbox.org/en/tariff
Encrypted	https://www.bsi.bund.de/dok/sik-01012
Encrypted	https://www.bsi.bund.de/dok/sik-01011
Encrypted	https://www.bsi.bund.de/dok/sik-01010
Encrypted	https://kb.mailbox.org/en/private
Encrypted	https://userforum-en.mailbox.org/
Encrypted	https://register.mailbox.org/en/cancellation
Encrypted	https://twitter.com/mailbox_org
Encrypted	https://social.mailbox.org/@mailbox_org
Encrypted	https://social.mailbox.org/@mailbox_org

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://mailbox.org/
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	15,768,000 seconds (about 6 months 1 day)
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: mailbox.org; includeSubDomains=true

HSTS Policy Apex host

URL from which this policy was obtained.Location	https://mailbox.org/en/
Specifies policy duration. Once activated, HSTS stays in force until this time lapses. Browsers update policy cache duration every time they receive a new HSTS header from a site.max‑age	15,768,000 seconds (about 6 months 1 day)
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: mailbox.org; includeSubDomains=true

HTTP Public Key Pinning

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

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

Content Security Policy

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

Test passed

Everything seems to be well configured. Well done.

Content-Security-Policy

default-src	'self'
img-src	'self' *.mailbox.org
script-src	'self' *.mailbox.org
style-src	'self' data: This parameter shouldn't be used because it reenables insecure behavior that CSP disables by default.'unsafe-inline'
frame-src	'self' *.mailbox.org
frame-ancestors	'self'
object-src	'none'
connect-src	'self' *.mailbox.org

Analysis

Inline styles are allowed

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

Mixed content not blocked

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

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: default-src 'self' ; img-src 'self' *.mailbox.org; script-src 'self' *.mailbox.org; style-src 'self' data: 'unsafe-inline' ; frame-src 'self' *.mailbox.org; frame-ancestors 'self'; object-src 'none'; connect-src 'self' *.mailbox.org;

Location: https://mailbox.org/en/

Subresource Integrity

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

Test passed

Everything seems to be well configured. Well done.

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

Status	Link
Local	assets/js/jquery.min.js,haste_plus.min.js,environment.min.js,files.min.js,...-4dcf90c3.js
Local	/files/js/numbers.js
Local	assets/jquery-ui/js/jquery-ui.min.js?v=1.12.1.1
Local	assets/colorbox/js/colorbox.min.js?v=1.6.4.1
Local	assets/mediaelement/js/mediaelement-and-player.min.js?v=4.2.9
Local	assets/highlight/js/highlight.pack.js?v=9.12.0
Local	assets/mediaelement/js/mediaelement-and-player.min.js?v=4.2.9
Local	files/js/jquery.marquee.min.js?v=4ea59168
Local	files/js/jquery.validate.min.js?v=e906b452
Local	files/js/rangeslider.min.js?v=1b95a959
Local	/files/js/footer-en.js

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

Status	Link
Local	assets/css/layout.min.css,colorbox.min.css,foundation.css,MyFontsWebfontsKi...-2579b0e2.css

Analysis

No remote resources

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

Expect CT

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

Feature not applicable, not implemented, or disabled

Your server doesn't support this feature.

Analysis

Deploy Expect-CT to enable reporting

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

Frame Options

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

Test passed

Everything seems to be well configured. Well done.

Analysis

Header information

Name: X-Frame-Options

Value: 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 | mailbox.org

mailbox.org

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: mx2.mailbox.org (2001:67c:2050:104:0:2:25:1) Cached

Analysis

TLS Configuration: mx2.mailbox.org (80.241.60.215) Cached

Analysis

TLS Configuration: mx1.mailbox.org (2001:67c:2050:104:0:1:25:1) Cached

Analysis

TLS Configuration: mx1.mailbox.org (80.241.60.212) Cached

Analysis

TLS Configuration: mx3.mailbox.org (2001:67c:2050:104:0:3:25:1) Cached

Analysis

TLS Configuration: mx3.mailbox.org (80.241.60.216) Cached

Analysis

Analysis

Email Certificates (SMTP)

Certificate #1 Cached

Analysis

Certificate Chain

Analysis

Email DANE (SMTP)

DANE: mx2.mailbox.org (2001:67c:2050:104:0:2:25:1)

Analysis

DANE: mx2.mailbox.org (80.241.60.215)

Analysis

DANE: mx1.mailbox.org (2001:67c:2050:104:0:1:25:1)

Analysis

DANE: mx1.mailbox.org (80.241.60.212)

Analysis

DANE: mx3.mailbox.org (2001:67c:2050:104:0:3:25:1)

Analysis

DANE: mx3.mailbox.org (80.241.60.216)

Analysis

DANE: mx-n.mailbox.org (2001:67c:2050:104:0:ffff:25:1)

Analysis

DANE: mx-n.mailbox.org (91.198.250.17)

Analysis

SPF

SPF Policy Information Main policy

Analysis

DMARC

DMARC Policy Information

Analysis

MTA Strict Transport Security

MTA-STS Policy Indicator

Analysis

MTA-STS Policy

Analysis

Certificate: mta-sts.mailbox.org

Analysis

Certificate Chain

Analysis

SMTP TLS Reporting

TLS-RPT Policy

Analysis

HTTP (80)

URL: http://mailbox.org/

Analysis

URL: http://www.mailbox.org/