Web Security Overview
Error
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
Not supported
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
Not supported
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
Not supported
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
Not supported
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
Warning
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
Supported and well configured
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
Not supported
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

Name Server Configuration

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 Configuration

These are the results of individual DNS queries against your nameserver for each resource record type.

Name TTL Type Data
onionmail.info.     3600 A 188.165.137.181            
www.onionmail.info.     1799 A 188.165.137.181            
onionmail.info.     300 MX 10 onionmail.info.            
onionmail.info.     1799 TXT v=spf1 mx a ip4:188.165.137.181 ~all            
onionmail.info.     1800 NS dns1.registrar-servers.com.            
onionmail.info.     1800 NS dns2.registrar-servers.com.            
onionmail.info.     3601 SOA dns1.registrar-servers.com. hostmaster.registrar-servers.com. 1582640238 43200 3600 604800 3601            

DNSSEC

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

Feature not implemented or disabled
Your server doesn't support this feature.

Useful DNSSEC Tools

Certification Authority Authorization

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

Feature not implemented or disabled
Your server doesn't support this feature.

Analysis

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

Email (SMTP)

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

Test passed, but there are warnings
Some aspect of your site's configuration require your attention.
Server Preference Operational STARTTLS TLS PKI DNSSEC DANE
onionmail.info
188.165.137.181
PTR: onionmail.info
10
220 onionmail.info (onionmail) TESMTP OnionMail 1.0.0 10010000 Sat, 19 Jun 2021 16:59:53 GMT
EHLO outbound.hardenize.com
250-<onionmail.info> Hello outbound.hardenize.com [0.0.0.0]
250-STARTTLS
250-SIZE 2000000
250-AUTH PLAIN LOGIN
250-TKIM
250 TORM V=1.5, VMAT, MX, MF2
QUIT
221 onionmail.info closing connection
Supports STARTTLS. Not supported. Not applicable,
requires TLS.

Email TLS (SMTP)

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

Test passed, but there are warnings
Some aspect of your site's configuration require your attention.

TLS Configuration: onionmail.info (188.165.137.181)

Encryption protocol version determines what features are
available for negotiation between client and server.
Supported protocols
TLS v1.2
TLS v1.1
TLS v1.0
SSL v3
Servers should always enforce their own cipher
suite preference, as that is the only approach
that guarantees that the best possible suite is
selected.
Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.2
Unknown preference
Suite: TLS_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x2f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_128_CBC_SHA
 128 bits
Suite: TLS_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x35
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits
Suite: TLS_RSA_WITH_AES_128_CBC_SHA256
Suite ID: 0x3c
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_128_CBC_SHA256
 128 bits
Suite: TLS_RSA_WITH_AES_256_CBC_SHA256
Suite ID: 0x3d
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_256_CBC_SHA256
 256 bits
Shows cipher suite configuration for this protocol version.TLS v1.1
Unknown preference
Suite: TLS_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x2f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_128_CBC_SHA
 128 bits
Suite: TLS_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x35
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits
Shows cipher suite configuration for this protocol version.TLS v1.0
Unknown preference
Suite: TLS_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x2f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_128_CBC_SHA
 128 bits
Suite: TLS_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x35
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits
Shows cipher suite configuration for this protocol version.SSL v3
Unknown preference
Suite: TLS_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x2f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_128_CBC_SHA
 128 bits
Suite: TLS_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x35
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits

Analysis

Notice
Deprecated TLS 1.0 protocol supported
TLS 1.0 is a weak older protocol that should be phased out. Sites that aim at a wide audience might still need to support TLS 1.0 for the time being, because many older clients don't support newer protocol versions. Sites with a modern user base might be able to disable TLS 1.0 even now. We recommend that you enable logging of encryption parameters, after which you can examine your protocol usage and make decisions with confidence.
Warning
Weak SSL 3.0 protocol supported
This server uses SSL 3.0, which is affected by the POODLE attack and should not be used. Modern browsers no longer support this older protocol version.
Good
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.
Powerup!
Server doesn't enforce cipher suite preferences
Servers that don't enforce cipher suite preferences select the first cipher suite they support from the list provided by clients. This approach doesn't guarantee that best-possible cipher suite is negotiated.
Good
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.
Warning
Reconfigure server to use forward secrecy and authenticated encryption
Even though this server supports TLS 1.2, the cipher suite configuration is suboptimal. We recommend that you reconfigure the server so that the cipher suites providing forward secrecy (ECDHE or DHE in the name, in this order of preference) and authenticated encryption (GCM or CHACHA20 in the name) are at the top. The server must also be configured to select the best-available suite.
Notice
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.
Notice
DHE suites not supported
This server doesn't support the Diffie-Hellman (DH) key exchange.

Email Certificates (SMTP)

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

Test passed, but there are warnings
Some aspect of your site's configuration require your attention.

Certificate #1

Self-signed certificate louhlbgyupgktsw7.onion
Issuer: Unknown
Not Before: 29 Mar 2013 23:42:11 UTC
Not After: 20 May 2024 23:42:11 UTC (expires in 2 years 11 months)
Key: RSA 2048 bits
Signature: SHA256withRSA
 View details

Analysis

Good
Strong private key
Good. The private key associated with this certificate is secure.
Good
Strong signature algorithm
Good. This certificate uses a strong signature algorithm.
Warning
Certificate doesn't match hostname
The provided certificate doesn't match the expected hostname. Default relaxed criteria for SMTP applies.

Expected hostname: onionmail.info

Good
Certificate dates match
Good. The certificate is valid for use at this point of time.
Notice
Certificate doesn't embed any CT log signatures
This certificate doesn't include any information related to Certificate Transparency.
Warning
Certificate not publicly trusted
This certificate is not trusted. Default relaxed criteria for SMTP applies.

Certificate Chain

Self-signed certificate
louhlbgyupgktsw7.onion | 63def81
Not After: 20 May 2024 23:42:11 UTC (expires in 2 years 11 months)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details

Analysis

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

Email DANE (SMTP)

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

Feature not implemented or disabled
Your server doesn't support this feature.

SPF

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

Test passed
Everything seems to be well configured. Well done.

SPF Policy Information Main policy

Host where this policy is located.Location onionmail.info
SPF version used by this policy.v spf1
This mechanism matches if the sending IP address
is one of the MX hosts for the domain name.
mx
This mechanism matches if the sending IP address
is one of the IP addresses that belong to the target
domain name. Matches both IPv4 and IPv6 addresses.
a
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
188.165.137.181
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

Info
SPF policy found

Policy text: v=spf1 mx a ip4:188.165.137.181 ~all

Location: onionmail.info

Good
SPF policy is valid
Good. Your SPF policy is valid.
Good
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: 2

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.

Feature not implemented or disabled
Your server doesn't support this feature.

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.

Feature not implemented or disabled
Your server doesn't support this feature.

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.

Feature not implemented or disabled
Your server doesn't support this feature.

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 failed
We've detected serious problems that require your immediate attention.

URL: http://onionmail.info/

1
http://onionmail.info/
HTTP/1.0 200 Ok

Analysis

Powerup!
Information leakage in HTTP response header
A HTTP response provided by this server includes a server that reveals potentially sensitive information about the software running on it. There is no reason why this information should be provided to the public and we recommend that it is removed.

Header value: PHP/4.1.2

Header name: X-Powered-By

Error
Plaintext HTTP server doesn't redirect to HTTPS
This plaintext HTTP server doesn't redirect to HTTPS, leaving its user vulnerable to content sniffing and active network attacks. From late July 2018, Chrome marks plaintext web sites as 'not secure'. We recommend that a redirection is added as soon as possible.

URL: http://www.onionmail.info/

1
http://www.onionmail.info/
HTTP/1.0 200 Ok

Analysis

Powerup!
Information leakage in HTTP response header
A HTTP response provided by this server includes a server that reveals potentially sensitive information about the software running on it. There is no reason why this information should be provided to the public and we recommend that it is removed.

Header value: PHP/4.1.2

Header name: X-Powered-By

Error
Plaintext HTTP server doesn't redirect to HTTPS
This plaintext HTTP server doesn't redirect to HTTPS, leaving its user vulnerable to content sniffing and active network attacks. From late July 2018, Chrome marks plaintext web sites as 'not secure'. We recommend that a redirection is added as soon as possible.

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://onionmail.info/

1
https://onionmail.info/
HTTP/1.0 200 Ok

Analysis

Powerup!
Information leakage in HTTP response header
A HTTP response provided by this server includes a server that reveals potentially sensitive information about the software running on it. There is no reason why this information should be provided to the public and we recommend that it is removed.

Header value: PHP/4.1.2

Header name: X-Powered-By

URL: https://www.onionmail.info/

1
https://www.onionmail.info/
HTTP/1.0 200 Ok

Analysis

Powerup!
Information leakage in HTTP response header
A HTTP response provided by this server includes a server that reveals potentially sensitive information about the software running on it. There is no reason why this information should be provided to the public and we recommend that it is removed.

Header value: PHP/4.1.2

Header name: X-Powered-By

WWW TLS

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

Test passed, but there are warnings
Some aspect of your site's configuration require your attention.

TLS Configuration: www.onionmail.info (188.165.137.181)

Encryption protocol version determines what features are
available for negotiation between client and server.
Supported protocols
TLS v1.2
TLS v1.1
TLS v1.0
Servers should always enforce their own cipher
suite preference, as that is the only approach
that guarantees that the best possible suite is
selected.
Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.2
Server preference
Suite: TLS_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: 1024 bits (WEAK)
Forward secrecy: Yes
PRF: SHA384
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
 256 bits (DHE 1024 bits)
Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA256
Suite ID: 0x6b
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 1024 bits (WEAK)
Forward secrecy: Yes
PRF: SHA256
TLS_DHE_RSA_WITH_AES_256_CBC_SHA256
 256 bits (DHE 1024 bits)
Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x39
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 1024 bits (WEAK)
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (DHE 1024 bits)
Suite: TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA
Suite ID: 0x88
Cipher name: CAMELLIA
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 1024 bits (WEAK)
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA
 256 bits (DHE 1024 bits)
Suite: TLS_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0x9d
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA384
TLS_RSA_WITH_AES_256_GCM_SHA384
 256 bits
Suite: TLS_RSA_WITH_AES_256_CBC_SHA256
Suite ID: 0x3d
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_256_CBC_SHA256
 256 bits
Suite: TLS_RSA_WITH_CAMELLIA_256_CBC_SHA
Suite ID: 0x84
Cipher name: CAMELLIA
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_CAMELLIA_256_CBC_SHA
 256 bits
Suite: TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA
Suite ID: 0x16
Cipher name: 3DES (WEAK)
Cipher strength: 112 bits
Cipher block size: 64 bits (WEAK)
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 1024 bits (WEAK)
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA
 112 bits (DHE 1024 bits)
Suite: TLS_RSA_WITH_3DES_EDE_CBC_SHA
Suite ID: 0xa
Cipher name: 3DES (WEAK)
Cipher strength: 112 bits
Cipher block size: 64 bits (WEAK)
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_3DES_EDE_CBC_SHA
 112 bits
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: 1024 bits (WEAK)
Forward secrecy: Yes
PRF: SHA256
TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
 128 bits (DHE 1024 bits)
Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA256
Suite ID: 0x67
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 1024 bits (WEAK)
Forward secrecy: Yes
PRF: SHA256
TLS_DHE_RSA_WITH_AES_128_CBC_SHA256
 128 bits (DHE 1024 bits)
Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x33
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 1024 bits (WEAK)
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (DHE 1024 bits)
Suite: TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA
Suite ID: 0x45
Cipher name: CAMELLIA
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 1024 bits (WEAK)
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA
 128 bits (DHE 1024 bits)
Suite: TLS_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0x9c
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_128_GCM_SHA256
 128 bits
Suite: TLS_RSA_WITH_AES_128_CBC_SHA256
Suite ID: 0x3c
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_128_CBC_SHA256
 128 bits
Suite: TLS_RSA_WITH_CAMELLIA_128_CBC_SHA
Suite ID: 0x41
Cipher name: CAMELLIA
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_CAMELLIA_128_CBC_SHA
 128 bits
Shows cipher suite configuration for this protocol version.TLS v1.1
Server preference
Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x39
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 1024 bits (WEAK)
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (DHE 1024 bits)
Suite: TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA
Suite ID: 0x88
Cipher name: CAMELLIA
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 1024 bits (WEAK)
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA
 256 bits (DHE 1024 bits)
Suite: TLS_RSA_WITH_CAMELLIA_256_CBC_SHA
Suite ID: 0x84
Cipher name: CAMELLIA
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_CAMELLIA_256_CBC_SHA
 256 bits
Suite: TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA
Suite ID: 0x16
Cipher name: 3DES (WEAK)
Cipher strength: 112 bits
Cipher block size: 64 bits (WEAK)
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 1024 bits (WEAK)
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA
 112 bits (DHE 1024 bits)
Suite: TLS_RSA_WITH_3DES_EDE_CBC_SHA
Suite ID: 0xa
Cipher name: 3DES (WEAK)
Cipher strength: 112 bits
Cipher block size: 64 bits (WEAK)
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_3DES_EDE_CBC_SHA
 112 bits
Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x33
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 1024 bits (WEAK)
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (DHE 1024 bits)
Suite: TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA
Suite ID: 0x45
Cipher name: CAMELLIA
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 1024 bits (WEAK)
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA
 128 bits (DHE 1024 bits)
Suite: TLS_RSA_WITH_CAMELLIA_128_CBC_SHA
Suite ID: 0x41
Cipher name: CAMELLIA
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_CAMELLIA_128_CBC_SHA
 128 bits
Shows cipher suite configuration for this protocol version.TLS v1.0
Server preference
Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x39
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 1024 bits (WEAK)
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (DHE 1024 bits)
Suite: TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA
Suite ID: 0x88
Cipher name: CAMELLIA
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 1024 bits (WEAK)
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA
 256 bits (DHE 1024 bits)
Suite: TLS_RSA_WITH_CAMELLIA_256_CBC_SHA
Suite ID: 0x84
Cipher name: CAMELLIA
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_CAMELLIA_256_CBC_SHA
 256 bits
Suite: TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA
Suite ID: 0x16
Cipher name: 3DES (WEAK)
Cipher strength: 112 bits
Cipher block size: 64 bits (WEAK)
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 1024 bits (WEAK)
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA
 112 bits (DHE 1024 bits)
Suite: TLS_RSA_WITH_3DES_EDE_CBC_SHA
Suite ID: 0xa
Cipher name: 3DES (WEAK)
Cipher strength: 112 bits
Cipher block size: 64 bits (WEAK)
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_3DES_EDE_CBC_SHA
 112 bits
Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x33
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 1024 bits (WEAK)
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (DHE 1024 bits)
Suite: TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA
Suite ID: 0x45
Cipher name: CAMELLIA
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 1024 bits (WEAK)
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA
 128 bits (DHE 1024 bits)
Suite: TLS_RSA_WITH_CAMELLIA_128_CBC_SHA
Suite ID: 0x41
Cipher name: CAMELLIA
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_CAMELLIA_128_CBC_SHA
 128 bits

Analysis

Notice
Deprecated protocols supported
TLS 1.0 and TLS 1.1 are deprecated protocols that should be disabled if possible. TLS 1.0, in particular, is a weak older protocol that has many weaknesses. Sites that aim at a wide audience might still need to support TLS 1.0 for the time being, because many older clients don't support newer protocol versions. Sites with a modern user base might be able to disable TLS 1.0 even now. We recommend that you enable logging of encryption parameters, after which you can examine your protocol usage and make a decision with confidence. As of July 2018, PCI DSS doesn't allow use of TLS 1.0. Exceptions apply in some cases.
Powerup!
TLS 1.3 not supported
TLS 1.3 is the latest revision of the TLS protocol and a significant improvement over earlier versions. Developed over a period of several years and extensively analyzed prior to the release, TLS 1.3 removed insecure features, and improved both security and performance. This version of TLS should be the main protocol used with modern clients.
Good
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.
Warning
Weak key exchange
This server uses key exchange parameters that are weak. When using the ephemeral Diffie-Hellman key exchange (DHE), parameters below 2048 bits are considered weak. For sufficient security, use 2048-bit parameters. It is generally not advisable to use stronger DHE key exchange because there is a measurable performance penalty and there is no meaningful increase in security. A well-configured TLS server should generally prefer the faster ECDHE key exchange anyway. When it comes to ECDHE, aim for at least 256 bits; anything below 200 bits is weak. For best results, use secp256r1 and secp384r1, which are required in practice, and x25519 as an emerging standard.

Weak parameters: DH 1024

Warning
Reconfigure server to use forward secrecy and authenticated encryption
Even though this server supports TLS 1.2, the cipher suite configuration is suboptimal. We recommend that you reconfigure the server so that the cipher suites providing forward secrecy (ECDHE or DHE in the name, in this order of preference) and authenticated encryption (GCM or CHACHA20 in the name) are at the top. The server must also be configured to select the best-available suite.
Good
Server enforces cipher suite preferences
Excellent. This server enforces server cipher suite preference, which means that it is able to select the best suite from the options submitted by clients. Combined with a well designed list of supported cipher suites, this settings enables negotiation of best security.
Good
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

Good
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

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

TLS Configuration: onionmail.info (188.165.137.181)

Encryption protocol version determines what features are
available for negotiation between client and server.
Supported protocols
TLS v1.2
TLS v1.1
TLS v1.0
Servers should always enforce their own cipher
suite preference, as that is the only approach
that guarantees that the best possible suite is
selected.
Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.2
Server preference
Suite: TLS_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: 1024 bits (WEAK)
Forward secrecy: Yes
PRF: SHA384
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
 256 bits (DHE 1024 bits)
Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA256
Suite ID: 0x6b
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 1024 bits (WEAK)
Forward secrecy: Yes
PRF: SHA256
TLS_DHE_RSA_WITH_AES_256_CBC_SHA256
 256 bits (DHE 1024 bits)
Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x39
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 1024 bits (WEAK)
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (DHE 1024 bits)
Suite: TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA
Suite ID: 0x88
Cipher name: CAMELLIA
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 1024 bits (WEAK)
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA
 256 bits (DHE 1024 bits)
Suite: TLS_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0x9d
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA384
TLS_RSA_WITH_AES_256_GCM_SHA384
 256 bits
Suite: TLS_RSA_WITH_AES_256_CBC_SHA256
Suite ID: 0x3d
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_256_CBC_SHA256
 256 bits
Suite: TLS_RSA_WITH_CAMELLIA_256_CBC_SHA
Suite ID: 0x84
Cipher name: CAMELLIA
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_CAMELLIA_256_CBC_SHA
 256 bits
Suite: TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA
Suite ID: 0x16
Cipher name: 3DES (WEAK)
Cipher strength: 112 bits
Cipher block size: 64 bits (WEAK)
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 1024 bits (WEAK)
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA
 112 bits (DHE 1024 bits)
Suite: TLS_RSA_WITH_3DES_EDE_CBC_SHA
Suite ID: 0xa
Cipher name: 3DES (WEAK)
Cipher strength: 112 bits
Cipher block size: 64 bits (WEAK)
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_3DES_EDE_CBC_SHA
 112 bits
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: 1024 bits (WEAK)
Forward secrecy: Yes
PRF: SHA256
TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
 128 bits (DHE 1024 bits)
Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA256
Suite ID: 0x67
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 1024 bits (WEAK)
Forward secrecy: Yes
PRF: SHA256
TLS_DHE_RSA_WITH_AES_128_CBC_SHA256
 128 bits (DHE 1024 bits)
Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x33
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 1024 bits (WEAK)
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (DHE 1024 bits)
Suite: TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA
Suite ID: 0x45
Cipher name: CAMELLIA
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 1024 bits (WEAK)
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA
 128 bits (DHE 1024 bits)
Suite: TLS_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0x9c
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_128_GCM_SHA256
 128 bits
Suite: TLS_RSA_WITH_AES_128_CBC_SHA256
Suite ID: 0x3c
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_128_CBC_SHA256
 128 bits
Suite: TLS_RSA_WITH_CAMELLIA_128_CBC_SHA
Suite ID: 0x41
Cipher name: CAMELLIA
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_CAMELLIA_128_CBC_SHA
 128 bits
Shows cipher suite configuration for this protocol version.TLS v1.1
Server preference
Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x39
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 1024 bits (WEAK)
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (DHE 1024 bits)
Suite: TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA
Suite ID: 0x88
Cipher name: CAMELLIA
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 1024 bits (WEAK)
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA
 256 bits (DHE 1024 bits)
Suite: TLS_RSA_WITH_CAMELLIA_256_CBC_SHA
Suite ID: 0x84
Cipher name: CAMELLIA
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_CAMELLIA_256_CBC_SHA
 256 bits
Suite: TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA
Suite ID: 0x16
Cipher name: 3DES (WEAK)
Cipher strength: 112 bits
Cipher block size: 64 bits (WEAK)
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 1024 bits (WEAK)
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA
 112 bits (DHE 1024 bits)
Suite: TLS_RSA_WITH_3DES_EDE_CBC_SHA
Suite ID: 0xa
Cipher name: 3DES (WEAK)
Cipher strength: 112 bits
Cipher block size: 64 bits (WEAK)
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_3DES_EDE_CBC_SHA
 112 bits
Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x33
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 1024 bits (WEAK)
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (DHE 1024 bits)
Suite: TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA
Suite ID: 0x45
Cipher name: CAMELLIA
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 1024 bits (WEAK)
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA
 128 bits (DHE 1024 bits)
Suite: TLS_RSA_WITH_CAMELLIA_128_CBC_SHA
Suite ID: 0x41
Cipher name: CAMELLIA
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_CAMELLIA_128_CBC_SHA
 128 bits
Shows cipher suite configuration for this protocol version.TLS v1.0
Server preference
Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x39
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 1024 bits (WEAK)
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (DHE 1024 bits)
Suite: TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA
Suite ID: 0x88
Cipher name: CAMELLIA
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 1024 bits (WEAK)
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA
 256 bits (DHE 1024 bits)
Suite: TLS_RSA_WITH_CAMELLIA_256_CBC_SHA
Suite ID: 0x84
Cipher name: CAMELLIA
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_CAMELLIA_256_CBC_SHA
 256 bits
Suite: TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA
Suite ID: 0x16
Cipher name: 3DES (WEAK)
Cipher strength: 112 bits
Cipher block size: 64 bits (WEAK)
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 1024 bits (WEAK)
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA
 112 bits (DHE 1024 bits)
Suite: TLS_RSA_WITH_3DES_EDE_CBC_SHA
Suite ID: 0xa
Cipher name: 3DES (WEAK)
Cipher strength: 112 bits
Cipher block size: 64 bits (WEAK)
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_3DES_EDE_CBC_SHA
 112 bits
Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x33
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 1024 bits (WEAK)
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (DHE 1024 bits)
Suite: TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA
Suite ID: 0x45
Cipher name: CAMELLIA
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: DHE_RSA
Key exchange strength: 1024 bits (WEAK)
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA
 128 bits (DHE 1024 bits)
Suite: TLS_RSA_WITH_CAMELLIA_128_CBC_SHA
Suite ID: 0x41
Cipher name: CAMELLIA
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_CAMELLIA_128_CBC_SHA
 128 bits

Analysis

Notice
Deprecated protocols supported
TLS 1.0 and TLS 1.1 are deprecated protocols that should be disabled if possible. TLS 1.0, in particular, is a weak older protocol that has many weaknesses. Sites that aim at a wide audience might still need to support TLS 1.0 for the time being, because many older clients don't support newer protocol versions. Sites with a modern user base might be able to disable TLS 1.0 even now. We recommend that you enable logging of encryption parameters, after which you can examine your protocol usage and make a decision with confidence. As of July 2018, PCI DSS doesn't allow use of TLS 1.0. Exceptions apply in some cases.
Powerup!
TLS 1.3 not supported
TLS 1.3 is the latest revision of the TLS protocol and a significant improvement over earlier versions. Developed over a period of several years and extensively analyzed prior to the release, TLS 1.3 removed insecure features, and improved both security and performance. This version of TLS should be the main protocol used with modern clients.
Good
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.
Warning
Weak key exchange
This server uses key exchange parameters that are weak. When using the ephemeral Diffie-Hellman key exchange (DHE), parameters below 2048 bits are considered weak. For sufficient security, use 2048-bit parameters. It is generally not advisable to use stronger DHE key exchange because there is a measurable performance penalty and there is no meaningful increase in security. A well-configured TLS server should generally prefer the faster ECDHE key exchange anyway. When it comes to ECDHE, aim for at least 256 bits; anything below 200 bits is weak. For best results, use secp256r1 and secp384r1, which are required in practice, and x25519 as an emerging standard.

Weak parameters: DH 1024

Warning
Reconfigure server to use forward secrecy and authenticated encryption
Even though this server supports TLS 1.2, the cipher suite configuration is suboptimal. We recommend that you reconfigure the server so that the cipher suites providing forward secrecy (ECDHE or DHE in the name, in this order of preference) and authenticated encryption (GCM or CHACHA20 in the name) are at the top. The server must also be configured to select the best-available suite.
Good
Server enforces cipher suite preferences
Excellent. This server enforces server cipher suite preference, which means that it is able to select the best suite from the options submitted by clients. Combined with a well designed list of supported cipher suites, this settings enables negotiation of best security.
Good
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

Good
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

Good
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: onionmail.info

Leaf certificate onionmail.info
Issuer: Let's Encrypt
Not Before: 27 May 2021 21:28:30 UTC
Not After: 25 Aug 2021 21:28:30 UTC (expires in 2 months 6 days)
Key: RSA 2048 bits
Signature: SHA256withRSA
 View details

Analysis

Good
Strong private key
Good. The private key associated with this certificate is secure.
Good
Strong signature algorithm
Good. This certificate uses a strong signature algorithm.
Good
Certificate matches hostname
Good. The provided certificate matches the expected hostnames.
Good
Certificate dates match
Good. The certificate is valid for use at this point of time.
Good
Certificate has not been revoked
Good. This certificate has not been revoked.
Good
Certificate satisfies Apple's CT compliance requirements
Good. This certificate satisfies Apple's CT requirements at present.
Good
Certificate satisfies Chrome's CT compliance requirements
Good. This certificate satisfies Chrome's CT requirements at present.

Certificate Trust

Determining whether a certificate is considered valid is a complicated process that depends on the exact configuration of the validating party. For trust to be established, the certificate must form a chain that ends with a trusted root. In this section we evaluate the server's certificate against major root stores.

Platform Trusted
Apple
Google AOSP
Microsoft
Mozilla

Certificate Chain

For a server certificate to be valid, it must be presented as part of a complete and valid certificate chain. The last certificate in the chain should be the root and is usually not included in the configuration.

Leaf certificate
onionmail.info | 74efd27
Not After: 25 Aug 2021 21:28:30 UTC (expires in 2 months 6 days)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Intermediate certificate
R3 | 67add11
Not After: 15 Sep 2025 16:00:00 UTC (expires in 4 years 2 months)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Intermediate certificate
ISRG Root X1 | 6d99fb2
Not After: 30 Sep 2024 18:14:03 UTC (expires in 3 years 3 months)
Authentication: RSA 4096 bits (SHA256withRSA)
 View details
Root certificate
DST Root CA X3 | 0687260
Not After: 30 Sep 2021 14:01:15 UTC (expires in 3 months 10 days)
Authentication: RSA 2048 bits (SHA1withRSA)
 View details

Analysis

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

Certificate: www.onionmail.info

Leaf certificate onionmail.info
Issuer: Let's Encrypt
Not Before: 27 May 2021 21:28:30 UTC
Not After: 25 Aug 2021 21:28:30 UTC (expires in 2 months 6 days)
Key: RSA 2048 bits
Signature: SHA256withRSA
 View details

Analysis

Good
Strong private key
Good. The private key associated with this certificate is secure.
Good
Strong signature algorithm
Good. This certificate uses a strong signature algorithm.
Good
Certificate matches hostname
Good. The provided certificate matches the expected hostnames.
Good
Certificate dates match
Good. The certificate is valid for use at this point of time.
Good
Certificate has not been revoked
Good. This certificate has not been revoked.
Good
Certificate satisfies Apple's CT compliance requirements
Good. This certificate satisfies Apple's CT requirements at present.
Good
Certificate satisfies Chrome's CT compliance requirements
Good. This certificate satisfies Chrome's CT requirements at present.

Certificate Trust

Determining whether a certificate is considered valid is a complicated process that depends on the exact configuration of the validating party. For trust to be established, the certificate must form a chain that ends with a trusted root. In this section we evaluate the server's certificate against major root stores.

Platform Trusted
Apple
Google AOSP
Microsoft
Mozilla

Certificate Chain

For a server certificate to be valid, it must be presented as part of a complete and valid certificate chain. The last certificate in the chain should be the root and is usually not included in the configuration.

Leaf certificate
onionmail.info | 74efd27
Not After: 25 Aug 2021 21:28:30 UTC (expires in 2 months 6 days)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Intermediate certificate
R3 | 67add11
Not After: 15 Sep 2025 16:00:00 UTC (expires in 4 years 2 months)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Intermediate certificate
ISRG Root X1 | 6d99fb2
Not After: 30 Sep 2024 18:14:03 UTC (expires in 3 years 3 months)
Authentication: RSA 4096 bits (SHA256withRSA)
 View details
Root certificate
DST Root CA X3 | 0687260
Not After: 30 Sep 2021 14:01:15 UTC (expires in 3 months 10 days)
Authentication: RSA 2048 bits (SHA1withRSA)
 View details

Analysis

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

DANE (443)

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

Feature not implemented or disabled
Your server doesn't support this feature.

Cookies

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

Test passed
Everything seems to be well configured. Well done.

Mixed Content

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

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

Embedded Resources

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

1 script(s)
  0 out of 1 are secure
http://codice.shinystat.com/cgi-bin/getcod.cgi
 View all
0 CSS file(s)
  0 out of 0 are secure
1 media file(s)
  0 out of 1 are secure
http://www.shinystat.com/...gi-bin/shinystat.cgi
 View all

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.

8 link(s)
  5 out of 8 are encrypted
http://mes3hacklab.org
http://tramaci.org
http://www.shinystat.com/it
 View all

Analysis

Error
Mixed active content present
Not good. Mixed active content enables network attackers to defeat encryption by injecting malicious code into unprotected page resources (e.g., scripts).
Warning
Mixed passive content present
Although mixed passive content (for example images and videos) is not as easy to exploit, network attackers can still abuse it to confuse your users and perform social engineering attacks.
Powerup!
Plaintext outbound links in HTTPS page
When outbound links are not encrypted, a passive network attacker can see where your users go after visiting your web site.

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.

Feature not implemented or disabled
Your server doesn't support this feature.

HSTS Policy

URL from which this policy was obtained.Location https://www.onionmail.info/

Analysis

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

Analysis

Powerup!
Deploy HSTS on this host
This host doesn't use HSTS, which means that its users can be easily attacked via MITM attacks. Consider deploying HSTS to disable certificate warnings and increase content and cookie security.
Powerup!
No HSTS on apex hostname
Even though the main host uses HSTS, the protection is not as good as it could be because the apex hostname doesn't have HSTS deployed. Without robust HSTS, attackers can sometimes abuse cookies and make up plaintext subdomains to use for phishing.

Location: https://onionmail.info

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 implemented or disabled
Your server doesn't support this feature.

Content Security Policy

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

Feature not implemented or disabled
Your server doesn't support this feature.

Subresource Integrity

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

Feature not implemented or disabled
Your server doesn't support this feature.
1 script(s)
  0 out of 1 are secure
http://codice.shinystat.com/cgi-bin/getcod.cgi
 View all
No external stylesheets
  SRI not needed

Analysis

Powerup!
SRI required
This page contains remote resources that are under the control of third parties. Deploy SRI to protect them from modification.

Expect CT

Expect-CT is a response HTTP header that web sites can use to monitor problems related to their Certificate Transparency (CT) compliance. Should any CT issues arise, browsers that support this header will submit reports to the specified reporting endpoint.

Feature not implemented or disabled
Your server doesn't support this feature.

Analysis

Powerup!
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 become 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.

Feature not implemented or disabled
Your server doesn't support this feature.

XSS Protection

Modern browsers ship with built-in defenses against Cross-Site Scripting (XSS), usually known as XSS Auditors. Web sites are allowed to control the defenses if they specify an X-XSS-Protection header in their HTTP responses. Recommended policies are either to block XSS attacks, or disable the defenses if you think false positives are possible. Filtering, where offending fragments of data are removed, is not recommended because it can be abused by attackers to selectively deactivate script files.

Feature not implemented or disabled
Your server doesn't support this feature.

Content Type Options

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

Feature not implemented or disabled
Your server doesn't support this feature.

HTML Analysis

Analysis of page content, including SRI.

Test passed
Everything seems to be well configured. Well done.

Base URL

https://www.onionmail.info/

Active Content

Type Status Location
script Third-party codice.shinystat.com

Passive Content

Type Status Link
media Third-party www.shinystat.com

Links

Type Status Link
link Plaintext mes3hacklab.org
link Plaintext tramaci.org
link Encrypted it-it.facebook.com
link Encrypted it-it.facebook.com
link Encrypted it-it.facebook.com
link Plaintext www.shinystat.com
link Encrypted en.onionmail.info
link Encrypted it.onionmail.info