Web Security Overview
Supported and well configured
HTTPS

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

For all sites VERY IMPORTANT medium EFFORT
Supported and well configured
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
Supported and well configured
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
Supported and well configured
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
Supported and well configured
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
Supported and well configured
STARTTLS

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

For all sites VERY IMPORTANT low EFFORT
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
Supported and well configured
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
alainwolf.ch.     300 A 81.6.42.101            
alainwolf.ch.     3600 AAAA 2a02:168:f405:0:0:0:0:42            
alainwolf.ch.     86400 CAA 0 iodef "mailto:hostmaster@alainwolf.ch"            
alainwolf.ch.     86400 CAA 0 issue "letsencrypt.org"            
alainwolf.ch.     3600 MX 10 pace.urown.net.            
alainwolf.ch.     3600 MX 10 norris.urown.net.            
_mta-sts.alainwolf.ch.     3600 CNAME _mta-sts.urown.net.            
_smtp._tls.alainwolf.ch.     3600 CNAME _smtp._tls.urown.net.            
mta-sts.alainwolf.ch.     3600 CNAME mta-sts.urown.net.            
mta-sts.alainwolf.ch.     3600 CNAME mta-sts.urown.net.            
_dmarc.alainwolf.ch.     86400 TXT v=DMARC1; p=quarantine; sp=quarantine; rua=mailto:tzo7ic2l@alainwolf.ch; ruf=mailto:km3j0guo@alainwolf.ch; rf=iodef; pct=100; ri=86400            
alainwolf.ch.     3598 NS pace.urown.net.            
alainwolf.ch.     3598 NS puck.nether.net.            
alainwolf.ch.     3598 NS eko.urown.net.            
alainwolf.ch.     3600 SOA eko.alainwolf.ch. hostmaster.alainwolf.ch. 2019011001 28800 3600 2419200 300            
www.alainwolf.ch.     300 A 81.6.42.101            
www.alainwolf.ch.     3600 AAAA 2a02:168:f405:0:0:0:0:42            

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

Good
DNSSEC is well configured
Good. This domain name has well-configured DNSSEC.

Useful DNSSEC Tools

Certification Authority Authorization

CAA (RFC 6844) 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 alainwolf.ch
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:hostmaster@alainwolf.ch  flags: 0

Analysis

Good
CAA policy found
Good. This domain name uses CAA to restrict which CAs are allowed to issue certificates for it.
Good
Policy uses reporting
Great. This policy uses reporting, which means that your contact information is available should someone need to contact you about a CAA violation. Do note that you're not guaranteed to be notified, given that CAs generally don't support notifications yet.

Email (SMTP)

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

Test passed
Everything seems to be well configured. Well done.
Some TLS and PKI information shown may have been retrieved from cache. The notes provide more information.
Server Preference Operational STARTTLS TLS PKI DNSSEC DANE
norris.urown.net
2a01:7e01:0:0:f03c:91ff:fe8e:363e
PTR: norris.urown.net
10
< 220-norris.urown.net ESMTP Postfix (Linux)
< 220 norris.urown.net ESMTP Postfix (Linux)
> EHLO outbound.hardenize.com
< 250-norris.urown.net
< 250-SIZE 26214400
< 250-VRFY
< 250-ETRN
< 250-STARTTLS
< 250-ENHANCEDSTATUSCODES
< 250-8BITMIME
< 250-DSN
< 250 SMTPUTF8
> STARTTLS
< 220 2.0.0 Ready to start TLS
Supports STARTTLS.
norris.urown.net
172.104.252.15
PTR: norris.urown.net
10
< 220-norris.urown.net ESMTP Postfix (Linux)
< 220 norris.urown.net ESMTP Postfix (Linux)
> EHLO outbound.hardenize.com
< 250-norris.urown.net
< 250-SIZE 26214400
< 250-VRFY
< 250-ETRN
< 250-STARTTLS
< 250-ENHANCEDSTATUSCODES
< 250-8BITMIME
< 250-DSN
< 250 SMTPUTF8
> STARTTLS
< 220 2.0.0 Ready to start TLS
Supports STARTTLS.
pace.urown.net
2a03:b0c0:3:d0:0:0:bd:f001
PTR: pace.urown.net
10
< 220-pace.urown.net ESMTP Postfix (Linux)
< 220 pace.urown.net ESMTP Postfix (Linux)
> EHLO outbound.hardenize.com
< 250-pace.urown.net
< 250-SIZE 26214400
< 250-VRFY
< 250-ETRN
< 250-STARTTLS
< 250-ENHANCEDSTATUSCODES
< 250-8BITMIME
< 250-DSN
< 250 SMTPUTF8
> STARTTLS
< 220 2.0.0 Ready to start TLS
Supports STARTTLS.
pace.urown.net
46.101.130.222
PTR: pace.urown.net
10
< 220-pace.urown.net ESMTP Postfix (Linux)
< 220 pace.urown.net ESMTP Postfix (Linux)
> EHLO outbound.hardenize.com
< 250-pace.urown.net
< 250-SIZE 26214400
< 250-VRFY
< 250-ETRN
< 250-STARTTLS
< 250-ENHANCEDSTATUSCODES
< 250-8BITMIME
< 250-DSN
< 250 SMTPUTF8
> STARTTLS
< 220 2.0.0 Ready to start TLS
Supports STARTTLS.

Analysis

Good
Configuration satisfies advertised 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.
Notice
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: 11 Jan 2019 07:21 UTC

Earliest cache timestamp: 11 Jan 2019 04:04 UTC

Email TLS (SMTP)

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

Test passed
Everything seems to be well configured. Well done.
Some TLS and PKI information shown may have been retrieved from cache. The notes provide more information.

TLS Configuration: norris.urown.net (2a01:7e01:0:0:f03c:91ff:fe8e:363e) Cached

Encryption protocol version determines what features are
available for negotiation between client and server.
Supported protocols
TLS v1.2
TLS v1.1
TLS v1.0
Servers should always enforce their own cipher
suite preference, as that is the only approach
that guarantees that the best possible suite is
selected.
Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.2
Server preference
Suite: TLS_ECDHE_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 secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 384 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 secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
 128 bits (ECDHE 384 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 secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
 256 bits (ECDHE 384 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_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_128_CBC_SHA256
Suite ID: 0xc027
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
 128 bits (ECDHE 384 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
Suite ID: 0xc028
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
 256 bits (ECDHE 384 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 384 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 384 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: 4096 bits
Forward secrecy: Yes
PRF: SHA256
TLS_DHE_RSA_WITH_AES_128_CBC_SHA256
 128 bits (DHE 4096 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: 4096 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (DHE 4096 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: 4096 bits
Forward secrecy: Yes
PRF: SHA256
TLS_DHE_RSA_WITH_AES_256_CBC_SHA256
 256 bits (DHE 4096 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: 4096 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (DHE 4096 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_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_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
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.1
Server preference
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 384 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 384 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: 4096 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (DHE 4096 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: 4096 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (DHE 4096 bits)
Suite: TLS_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x2f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_128_CBC_SHA
 128 bits
Suite: TLS_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x35
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits
Shows cipher suite configuration for this protocol version.TLS v1.0
Server preference
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 384 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 384 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: 4096 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (DHE 4096 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: 4096 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (DHE 4096 bits)
Suite: TLS_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x2f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_128_CBC_SHA
 128 bits
Suite: TLS_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
These results have been retrieved from
our cache. This row indicates when was
that the original test ran.
Retrieved from cache
11 Jan 2019 04:04 UTC

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.
Good
TLS 1.2 supported
Excellent. This server support TLS 1.2, which is currently the only SSL and TLS protocol version that provides modern encryption facilities and doesn't have serious weaknesses.
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
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.
Good
Server prefers forward secrecy and authenticated encryption suites
Excellent. Not only does this server enforce its server preference, but it also has at the top of the list suites that support both forward secrecy and authenticated encryption. This is the best TLS 1.2 can offer.
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.

TLS Configuration: norris.urown.net (172.104.252.15) Cached

Encryption protocol version determines what features are
available for negotiation between client and server.
Supported protocols
TLS v1.2
TLS v1.1
TLS v1.0
Servers should always enforce their own cipher
suite preference, as that is the only approach
that guarantees that the best possible suite is
selected.
Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.2
Server preference
Suite: TLS_ECDHE_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 secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 384 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 secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
 128 bits (ECDHE 384 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 secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
 256 bits (ECDHE 384 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_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_128_CBC_SHA256
Suite ID: 0xc027
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
 128 bits (ECDHE 384 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
Suite ID: 0xc028
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
 256 bits (ECDHE 384 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 384 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 384 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: 4096 bits
Forward secrecy: Yes
PRF: SHA256
TLS_DHE_RSA_WITH_AES_128_CBC_SHA256
 128 bits (DHE 4096 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: 4096 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (DHE 4096 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: 4096 bits
Forward secrecy: Yes
PRF: SHA256
TLS_DHE_RSA_WITH_AES_256_CBC_SHA256
 256 bits (DHE 4096 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: 4096 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (DHE 4096 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_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_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
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.1
Server preference
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 384 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 384 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: 4096 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (DHE 4096 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: 4096 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (DHE 4096 bits)
Suite: TLS_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x2f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_128_CBC_SHA
 128 bits
Suite: TLS_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x35
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits
Shows cipher suite configuration for this protocol version.TLS v1.0
Server preference
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 384 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 384 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: 4096 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (DHE 4096 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: 4096 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (DHE 4096 bits)
Suite: TLS_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x2f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_128_CBC_SHA
 128 bits
Suite: TLS_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
These results have been retrieved from
our cache. This row indicates when was
that the original test ran.
Retrieved from cache
11 Jan 2019 05:16 UTC

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.
Good
TLS 1.2 supported
Excellent. This server support TLS 1.2, which is currently the only SSL and TLS protocol version that provides modern encryption facilities and doesn't have serious weaknesses.
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
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.
Good
Server prefers forward secrecy and authenticated encryption suites
Excellent. Not only does this server enforce its server preference, but it also has at the top of the list suites that support both forward secrecy and authenticated encryption. This is the best TLS 1.2 can offer.
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.

TLS Configuration: pace.urown.net (2a03:b0c0:3:d0:0:0:bd:f001) Cached

Encryption protocol version determines what features are
available for negotiation between client and server.
Supported protocols
TLS v1.2
TLS v1.1
TLS v1.0
Servers should always enforce their own cipher
suite preference, as that is the only approach
that guarantees that the best possible suite is
selected.
Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.2
Server preference
Suite: TLS_ECDHE_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 secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 384 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 secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
 128 bits (ECDHE 384 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 secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
 256 bits (ECDHE 384 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_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_128_CBC_SHA256
Suite ID: 0xc027
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
 128 bits (ECDHE 384 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
Suite ID: 0xc028
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
 256 bits (ECDHE 384 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 384 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 384 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: 4096 bits
Forward secrecy: Yes
PRF: SHA256
TLS_DHE_RSA_WITH_AES_128_CBC_SHA256
 128 bits (DHE 4096 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: 4096 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (DHE 4096 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: 4096 bits
Forward secrecy: Yes
PRF: SHA256
TLS_DHE_RSA_WITH_AES_256_CBC_SHA256
 256 bits (DHE 4096 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: 4096 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (DHE 4096 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_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_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
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.1
Server preference
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 384 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 384 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: 4096 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (DHE 4096 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: 4096 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (DHE 4096 bits)
Suite: TLS_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x2f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_128_CBC_SHA
 128 bits
Suite: TLS_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x35
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits
Shows cipher suite configuration for this protocol version.TLS v1.0
Server preference
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 384 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 384 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: 4096 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (DHE 4096 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: 4096 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (DHE 4096 bits)
Suite: TLS_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x2f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_128_CBC_SHA
 128 bits
Suite: TLS_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
These results have been retrieved from
our cache. This row indicates when was
that the original test ran.
Retrieved from cache
11 Jan 2019 06:18 UTC

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.
Good
TLS 1.2 supported
Excellent. This server support TLS 1.2, which is currently the only SSL and TLS protocol version that provides modern encryption facilities and doesn't have serious weaknesses.
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
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.
Good
Server prefers forward secrecy and authenticated encryption suites
Excellent. Not only does this server enforce its server preference, but it also has at the top of the list suites that support both forward secrecy and authenticated encryption. This is the best TLS 1.2 can offer.
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.

TLS Configuration: pace.urown.net (46.101.130.222) Cached

Encryption protocol version determines what features are
available for negotiation between client and server.
Supported protocols
TLS v1.2
TLS v1.1
TLS v1.0
Servers should always enforce their own cipher
suite preference, as that is the only approach
that guarantees that the best possible suite is
selected.
Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.2
Server preference
Suite: TLS_ECDHE_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 secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 384 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 secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
 128 bits (ECDHE 384 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 secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
 256 bits (ECDHE 384 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_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_128_CBC_SHA256
Suite ID: 0xc027
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
 128 bits (ECDHE 384 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
Suite ID: 0xc028
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
 256 bits (ECDHE 384 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 384 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 384 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: 4096 bits
Forward secrecy: Yes
PRF: SHA256
TLS_DHE_RSA_WITH_AES_128_CBC_SHA256
 128 bits (DHE 4096 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: 4096 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (DHE 4096 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: 4096 bits
Forward secrecy: Yes
PRF: SHA256
TLS_DHE_RSA_WITH_AES_256_CBC_SHA256
 256 bits (DHE 4096 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: 4096 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (DHE 4096 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_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_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
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.1
Server preference
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 384 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 384 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: 4096 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (DHE 4096 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: 4096 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (DHE 4096 bits)
Suite: TLS_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x2f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_128_CBC_SHA
 128 bits
Suite: TLS_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x35
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits
Shows cipher suite configuration for this protocol version.TLS v1.0
Server preference
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 384 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 384 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: 4096 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (DHE 4096 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: 4096 bits
Forward secrecy: Yes
PRF: SHA
TLS_DHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (DHE 4096 bits)
Suite: TLS_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x2f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_128_CBC_SHA
 128 bits
Suite: TLS_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
These results have been retrieved from
our cache. This row indicates when was
that the original test ran.
Retrieved from cache
11 Jan 2019 07:21 UTC

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.
Good
TLS 1.2 supported
Excellent. This server support TLS 1.2, which is currently the only SSL and TLS protocol version that provides modern encryption facilities and doesn't have serious weaknesses.
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
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.
Good
Server prefers forward secrecy and authenticated encryption suites
Excellent. Not only does this server enforce its server preference, but it also has at the top of the list suites that support both forward secrecy and authenticated encryption. This is the best TLS 1.2 can offer.
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.

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 norris.urown.net
Issuer: Let's Encrypt
Not Before: 29 Dec 2018 13:06:49 UTC
Not After: 29 Mar 2019 13:06:49 UTC (2 months 17 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 satisfies Chrome's CT requirements
This certificate contains embedded CT signatures and satisfies Chrome's CT requirements at this time.
Powerup!
Certificate doesn't require OCSP stapling
This certificate doesn't require OCSP stapling. If enabled, this feature increases the probability that a certificate will be considered revoked. This is a fairly new feature that is not yet very widely supported by various TLS clients. More information is available in RFC 7633.

Certificate Chain

Leaf certificate
norris.urown.net | 9657775
Not After: 29 Mar 2019 13:06:49 UTC (2 months 17 days)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Intermediate certificate
Let's Encrypt Authority X3 | 25847d6
Not After: 17 Mar 2021 16:40:46 UTC (2 years 2 months)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Root certificate
DST Root CA X3 | 0687260
Not After: 30 Sep 2021 14:01:15 UTC (2 years 8 months)
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 #2  Cached

Leaf certificate pace.urown.net
Issuer: Let's Encrypt
Not Before: 29 Dec 2018 12:37:42 UTC
Not After: 29 Mar 2019 12:37:42 UTC (2 months 17 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 satisfies Chrome's CT requirements
This certificate contains embedded CT signatures and satisfies Chrome's CT requirements at this time.
Powerup!
Certificate doesn't require OCSP stapling
This certificate doesn't require OCSP stapling. If enabled, this feature increases the probability that a certificate will be considered revoked. This is a fairly new feature that is not yet very widely supported by various TLS clients. More information is available in RFC 7633.

Certificate Chain

Leaf certificate
pace.urown.net | 79b9247
Not After: 29 Mar 2019 12:37:42 UTC (2 months 17 days)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Intermediate certificate
Let's Encrypt Authority X3 | 25847d6
Not After: 17 Mar 2021 16:40:46 UTC (2 years 2 months)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Root certificate
DST Root CA X3 | 0687260
Not After: 30 Sep 2021 14:01:15 UTC (2 years 8 months)
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.

Email DANE (SMTP)

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

Test passed
Everything seems to be well configured. Well done.
Some TLS and PKI information shown may have been retrieved from cache. The notes provide more information.

DANE: norris.urown.net (2a01:7e01:0:0:f03c:91ff:fe8e:363e)

Specifies which certificate in the chain
is being pinned and how validation should
be performed.
Certificate Usage
Domain-issued certificate / DANE-EE (3) Creates a leaf pin for a certificate that must be
present in the certificate chain. PKIX validation is
not performed and the pinned certificate is assumed
to be trusted.
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 f82278986dfd4d4c1761a123e8e143d862ed3b5bae473e2bb2a6f0b2a5f20b09

Leaf certificate: RSA 2048 bits
Subject: CN=norris.urown.net
Issuer: CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
norris.urown.net (RSA 2048 bits)

Analysis

Good
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: norris.urown.net (172.104.252.15)

Specifies which certificate in the chain
is being pinned and how validation should
be performed.
Certificate Usage
Domain-issued certificate / DANE-EE (3) Creates a leaf pin for a certificate that must be
present in the certificate chain. PKIX validation is
not performed and the pinned certificate is assumed
to be trusted.
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 f82278986dfd4d4c1761a123e8e143d862ed3b5bae473e2bb2a6f0b2a5f20b09

Leaf certificate: RSA 2048 bits
Subject: CN=norris.urown.net
Issuer: CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
norris.urown.net (RSA 2048 bits)

Analysis

Good
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: pace.urown.net (2a03:b0c0:3:d0:0:0:bd:f001)

Specifies which certificate in the chain
is being pinned and how validation should
be performed.
Certificate Usage
Domain-issued certificate / DANE-EE (3) Creates a leaf pin for a certificate that must be
present in the certificate chain. PKIX validation is
not performed and the pinned certificate is assumed
to be trusted.
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 52eedff79a12aee0aab1c27fdb21f89ecbd40f2125bca4f1923fc2a18eaea301

Leaf certificate: RSA 2048 bits
Subject: CN=pace.urown.net
Issuer: CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
pace.urown.net (RSA 2048 bits)

Analysis

Good
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: pace.urown.net (46.101.130.222)

Specifies which certificate in the chain
is being pinned and how validation should
be performed.
Certificate Usage
Domain-issued certificate / DANE-EE (3) Creates a leaf pin for a certificate that must be
present in the certificate chain. PKIX validation is
not performed and the pinned certificate is assumed
to be trusted.
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 52eedff79a12aee0aab1c27fdb21f89ecbd40f2125bca4f1923fc2a18eaea301

Leaf certificate: RSA 2048 bits
Subject: CN=pace.urown.net
Issuer: CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
pace.urown.net (RSA 2048 bits)

Analysis

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

SPF

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

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

SPF Policy Information Main policy

Host where this policy is located.Location alainwolf.ch
SPF version used by this policy.v spf1
Evaluates SPF policy specified in another DNS location. This
directive is typically used to allow hosts controlled by
another organization.
include
_spf.urown.net
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
mailman012.mail.hostpoint.ch
This policy element always matches. It's normally used
at the end of a policy to specify the handling of hosts
that don't match earlier mechanisms.
~all

Analysis

Info
SPF policy found

Policy text: v=spf1 include:_spf.urown.net a:mailman012.mail.hostpoint.ch ~all

Location: alainwolf.ch

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

SPF Policy Information Included policy

Host where this policy is located.Location _spf.urown.net
SPF version used by this policy.v spf1
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
172.104.252.15/32
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
46.101.130.222/32
This mechanism tests whether the IP address being
tested is contained within a given IPv6 network.
ip6
2a01:7e01::f03c:91ff:fe8e:363e/128
This mechanism tests whether the IP address being
tested is contained within a given IPv6 network.
ip6
2a03:b0c0:3:d0::f001/128
This policy element always matches. It's normally used
at the end of a policy to specify the handling of hosts
that don't match earlier mechanisms.
~all

DMARC

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

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

DMARC Policy Information

The location from which we obtained this policy.Policy location _dmarc.alainwolf.ch
DMARC version used by this policy.v DMARC1
Indicates the policy to be enacted by the receiver at
the request of the domain owner. Possible values are:
none, quarantine, and reject.
p
quarantine
Requested mail receiver policy for all subdomains.
Same format as for the p tag.
sp
quarantine
Addresses to which aggregate feedback is to be sent.rua mailto:tzo7ic2l@alainwolf.ch
Addresses to which message-specific failure
information is to be reported.
ruf
mailto:km3j0guo@alainwolf.ch
Specifies the format to be used when reporting failures.rf iodef
Percentage of messages from mail stream to
which the DMARC policy is to be applied.
pct
100
Interval between aggregate reports. Defaults to 86400.ri 86400

Analysis

Info
DMARC policy found

Policy: v=DMARC1; p=quarantine; sp=quarantine; rua=mailto:tzo7ic2l@alainwolf.ch; ruf=mailto:km3j0guo@alainwolf.ch; rf=iodef; pct=100; ri=86400

Host: _dmarc.alainwolf.ch

Good
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.alainwolf.ch
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
20180712033150Z

Analysis

Good
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.alainwolf.ch/.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
10,368,000 seconds (about 4 months)
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
norris.urown.net
One 'mx' directive specifies one email server
pattern that's allowed for this host.
mx
pace.urown.net
One 'mx' directive specifies one email server
pattern that's allowed for this host.
mx
mail.urown.net

Analysis

Good
MTA-STS policy is valid
Good. Your MTA-STS policy is valid.
Good
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.
Notice
Policy HTTPS response information

Status code: 200

Length: 106 bytes

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

Certificate: mta-sts.alainwolf.ch

Leaf certificate mta-sts.urown.net
Issuer: Let's Encrypt
Not Before: 24 Nov 2018 04:27:00 UTC
Not After: 22 Feb 2019 04:27:00 UTC (1 month 10 days)
Key: EC 256 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 satisfies Chrome's CT requirements
This certificate contains embedded CT signatures and satisfies Chrome's CT requirements at this time.
Good
Certificate requires OCSP stapling ("must-staple")
Excellent. This certificate is considered valid only with a stapled OCSP response, which must also be valid. This feature is specified in RFC 7633 and is better known under the name "must-staple". It's fairly new at this point, but, in time, when it becomes more widely supported by various TLS clients, it will make reliable certificate revocation possible.

Certificate Chain

Leaf certificate
mta-sts.urown.net | 9ffe6cc
Not After: 22 Feb 2019 04:27:00 UTC (1 month 10 days)
Authentication: EC 256 bits (SHA256withRSA)
 View details
Intermediate certificate
Let's Encrypt Authority X3 | 25847d6
Not After: 17 Mar 2021 16:40:46 UTC (2 years 2 months)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Root certificate
DST Root CA X3 | 0687260
Not After: 30 Sep 2021 14:01:15 UTC (2 years 8 months)
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.

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.alainwolf.ch
TLS-RPT standard version used by this policy indicator.Version TLSRPTv1
Reporting endpoints specified in the policy.Reporting Endpoints mailto:postmaster@urown.net

Analysis

Good
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://alainwolf.ch

1
http://alainwolf.ch
HTTP/1.1 301 Moved Permanently
2
https://alainwolf.ch/
HTTP/1.1 200 OK

Analysis

Good
HTTP server redirects to HTTPS
Good. This plaintext HTTP server redirects to HTTPS.

URL: http://www.alainwolf.ch

1
http://www.alainwolf.ch
HTTP/1.1 301 Moved Permanently
2
https://www.alainwolf.ch/
HTTP/1.1 301 Moved Permanently
3
https://alainwolf.ch/
HTTP/1.1 200 OK

Analysis

Good
HTTP server 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://alainwolf.ch

1
https://alainwolf.ch
HTTP/1.1 200 OK

URL: https://www.alainwolf.ch

1
https://www.alainwolf.ch
HTTP/1.1 301 Moved Permanently
2
https://alainwolf.ch/
HTTP/1.1 200 OK

WWW TLS

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

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

TLS Configuration: www.alainwolf.ch (2a02:168:f405:0:0:0:0:42)

Encryption protocol version determines what features are
available for negotiation between client and server.
Supported protocols
TLS v1.3
TLS v1.2
Servers should always enforce their own cipher
suite preference, as that is the only approach
that guarantees that the best possible suite is
selected.
Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3
Server preference
Suite: TLS_AES_256_GCM_SHA384
Suite ID: 0x1302
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_AES_256_GCM_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_CHACHA20_POLY1305_SHA256
Suite ID: 0x1303
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_AES_128_GCM_SHA256
Suite ID: 0x1301
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_AES_128_GCM_SHA256
 128 bits (ECDHE 256 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2
Server preference
Suite: TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
Suite ID: 0xcca9
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
Suite ID: 0xc02c
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
Suite ID: 0xc02b
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
Suite ID: 0xc024
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
Suite ID: 0xc023
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
 128 bits (ECDHE 256 bits)

Analysis

Good
TLS 1.2 supported
Excellent. This server support TLS 1.2, which is currently the only SSL and TLS protocol version that provides modern encryption facilities and doesn't have serious weaknesses.
Good
Deprecated protocols not supported
Excellent. This server doesn't support any of the deprecated protocol (TLS 1.1 and earlier).
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.
Good
Server prefers forward secrecy and authenticated encryption suites
Excellent. Not only does this server enforce its server preference, but it also has at the top of the list suites that support both forward secrecy and authenticated encryption. This is the best TLS 1.2 can offer.
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 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 transport: CERT

TLS Configuration: www.alainwolf.ch (81.6.42.101)

Encryption protocol version determines what features are
available for negotiation between client and server.
Supported protocols
TLS v1.3
TLS v1.2
Servers should always enforce their own cipher
suite preference, as that is the only approach
that guarantees that the best possible suite is
selected.
Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3
Server preference
Suite: TLS_AES_256_GCM_SHA384
Suite ID: 0x1302
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_AES_256_GCM_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_CHACHA20_POLY1305_SHA256
Suite ID: 0x1303
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_AES_128_GCM_SHA256
Suite ID: 0x1301
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_AES_128_GCM_SHA256
 128 bits (ECDHE 256 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2
Server preference
Suite: TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
Suite ID: 0xcca9
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
Suite ID: 0xc02c
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
Suite ID: 0xc02b
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
Suite ID: 0xc024
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
Suite ID: 0xc023
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
 128 bits (ECDHE 256 bits)

Analysis

Good
TLS 1.2 supported
Excellent. This server support TLS 1.2, which is currently the only SSL and TLS protocol version that provides modern encryption facilities and doesn't have serious weaknesses.
Good
Deprecated protocols not supported
Excellent. This server doesn't support any of the deprecated protocol (TLS 1.1 and earlier).
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.
Good
Server prefers forward secrecy and authenticated encryption suites
Excellent. Not only does this server enforce its server preference, but it also has at the top of the list suites that support both forward secrecy and authenticated encryption. This is the best TLS 1.2 can offer.
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 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 transport: CERT

TLS Configuration: alainwolf.ch (2a02:168:f405:0:0:0:0:42)

Encryption protocol version determines what features are
available for negotiation between client and server.
Supported protocols
TLS v1.3
TLS v1.2
Servers should always enforce their own cipher
suite preference, as that is the only approach
that guarantees that the best possible suite is
selected.
Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3
Server preference
Suite: TLS_AES_256_GCM_SHA384
Suite ID: 0x1302
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_AES_256_GCM_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_CHACHA20_POLY1305_SHA256
Suite ID: 0x1303
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_AES_128_GCM_SHA256
Suite ID: 0x1301
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_AES_128_GCM_SHA256
 128 bits (ECDHE 256 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2
Server preference
Suite: TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
Suite ID: 0xcca9
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
Suite ID: 0xc02c
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
Suite ID: 0xc02b
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
Suite ID: 0xc024
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
Suite ID: 0xc023
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
 128 bits (ECDHE 256 bits)

Analysis

Good
TLS 1.2 supported
Excellent. This server support TLS 1.2, which is currently the only SSL and TLS protocol version that provides modern encryption facilities and doesn't have serious weaknesses.
Good
Deprecated protocols not supported
Excellent. This server doesn't support any of the deprecated protocol (TLS 1.1 and earlier).
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.
Good
Server prefers forward secrecy and authenticated encryption suites
Excellent. Not only does this server enforce its server preference, but it also has at the top of the list suites that support both forward secrecy and authenticated encryption. This is the best TLS 1.2 can offer.
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 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 transport: CERT

TLS Configuration: alainwolf.ch (81.6.42.101)

Encryption protocol version determines what features are
available for negotiation between client and server.
Supported protocols
TLS v1.3
TLS v1.2
Servers should always enforce their own cipher
suite preference, as that is the only approach
that guarantees that the best possible suite is
selected.
Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3
Server preference
Suite: TLS_AES_256_GCM_SHA384
Suite ID: 0x1302
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_AES_256_GCM_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_CHACHA20_POLY1305_SHA256
Suite ID: 0x1303
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_AES_128_GCM_SHA256
Suite ID: 0x1301
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_AES_128_GCM_SHA256
 128 bits (ECDHE 256 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2
Server preference
Suite: TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
Suite ID: 0xcca9
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
Suite ID: 0xc02c
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
Suite ID: 0xc02b
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
Suite ID: 0xc024
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
Suite ID: 0xc023
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_ECDSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
 128 bits (ECDHE 256 bits)

Analysis

Good
TLS 1.2 supported
Excellent. This server support TLS 1.2, which is currently the only SSL and TLS protocol version that provides modern encryption facilities and doesn't have serious weaknesses.
Good
Deprecated protocols not supported
Excellent. This server doesn't support any of the deprecated protocol (TLS 1.1 and earlier).
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.
Good
Server prefers forward secrecy and authenticated encryption suites
Excellent. Not only does this server enforce its server preference, but it also has at the top of the list suites that support both forward secrecy and authenticated encryption. This is the best TLS 1.2 can offer.
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 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 transport: CERT

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: alainwolf.ch

Leaf certificate alainwolf.ch
Issuer: Let's Encrypt
Not Before: 16 Nov 2018 04:31:53 UTC
Not After: 14 Feb 2019 04:31:53 UTC (1 month 2 days)
Key: EC 384 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 satisfies Chrome's CT requirements
This certificate contains embedded CT signatures and satisfies Chrome's CT requirements at this time.
Good
Certificate requires OCSP stapling ("must-staple")
Excellent. This certificate is considered valid only with a stapled OCSP response, which must also be valid. This feature is specified in RFC 7633 and is better known under the name "must-staple". It's fairly new at this point, but, in time, when it becomes more widely supported by various TLS clients, it will make reliable certificate revocation possible.

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 iOS
Apple MacOS
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
alainwolf.ch | f016082
Not After: 14 Feb 2019 04:31:53 UTC (1 month 2 days)
Authentication: EC 384 bits (SHA256withRSA)
 View details
Intermediate certificate
Let's Encrypt Authority X3 | 25847d6
Not After: 17 Mar 2021 16:40:46 UTC (2 years 2 months)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Root certificate
DST Root CA X3 | 0687260
Not After: 30 Sep 2021 14:01:15 UTC (2 years 8 months)
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.alainwolf.ch

Leaf certificate alainwolf.ch
Issuer: Let's Encrypt
Not Before: 16 Nov 2018 04:31:53 UTC
Not After: 14 Feb 2019 04:31:53 UTC (1 month 2 days)
Key: EC 384 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 satisfies Chrome's CT requirements
This certificate contains embedded CT signatures and satisfies Chrome's CT requirements at this time.
Good
Certificate requires OCSP stapling ("must-staple")
Excellent. This certificate is considered valid only with a stapled OCSP response, which must also be valid. This feature is specified in RFC 7633 and is better known under the name "must-staple". It's fairly new at this point, but, in time, when it becomes more widely supported by various TLS clients, it will make reliable certificate revocation possible.

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 iOS
Apple MacOS
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
alainwolf.ch | f016082
Not After: 14 Feb 2019 04:31:53 UTC (1 month 2 days)
Authentication: EC 384 bits (SHA256withRSA)
 View details
Intermediate certificate
Let's Encrypt Authority X3 | 25847d6
Not After: 17 Mar 2021 16:40:46 UTC (2 years 2 months)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Root certificate
DST Root CA X3 | 0687260
Not After: 30 Sep 2021 14:01:15 UTC (2 years 8 months)
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.

HTTP Cookie: WPSESSID  Session cookie

Cookie value. As far as the cookie RFC is concerned, the value
is an opaque string which only the application should interpret.
Value
hgqg23d0k6uuqa40h8uvbon7ss
Cookie domain. When domain is implied (not explicitly set in a cookie),
most browsers (but not IE) treat the cookie as host-only, meaning that
no other server can overwrite it.
Domain
Implied (alainwolf.ch)
Cookie path. This field can't be used as security measure,
but it could be of use to avoid cookie name collision
in non-adversarial contexts.
Path
/
The HttpOnly flag prevents the cookie from being accessed
from JavaScript, thus making them more difficult
to obtain after a successful XSS attack.
HttpOnly
The Secure flag signals to browsers that the cookie
should be transmitted only over an encrypted channel.
Secure
Normally, when a browser makes a request to a web site,
it sends all associated cookies. This is not always
desirable, because it might allow third-party sites
to perform site actions under the identity of the user.
This attack is known as Cross-Site Request Forgery.
With SameSite cookies (still in development, but already
supported in some browsers), you can choose to be more
strict. The possible values are 'lax' and 'strict'.
SameSite

Analysis

Good
Session cookie is secure
Good. This session cookie is marked secure, which means that it won't ever be transmitted over plaintext. As such, it's not vulnerable to the Sidejacking attack.
Good
Session cookie is HttpOnly
Good. This session cookie is marked as HttpOnly, which means that it can't be accessed from JavaScript. Such cookies are more difficult to obtain after a successful XSS attack.
Powerup!
SameSite attribute not used
An upcoming standard, SameSite cookies, creates more secure cookies that are sent only on requests that originate from the same site that issued them. They are designed to prevent Cross-Site Request Forgery (CSRF) or at least make it more difficult.
Powerup!
Name prefix not used
Cookie name prefixes are a recent improvement that enable web application developers to opt-in into a more secure type of cookies. Virtually all cookies would benefit from using either the '__Secure-' or the '__Host-' prefix. The former ensures that a plaintext cookie can't overwrite a secure cookie. The latter ensures that the cookie is sent back only to the host that issued it.

HTTP Cookie: qtrans_front_language

Cookie value. As far as the cookie RFC is concerned, the value
is an opaque string which only the application should interpret.
Value
en
Cookie domain. When domain is implied (not explicitly set in a cookie),
most browsers (but not IE) treat the cookie as host-only, meaning that
no other server can overwrite it.
Domain
Implied (alainwolf.ch)
Cookie path. This field can't be used as security measure,
but it could be of use to avoid cookie name collision
in non-adversarial contexts.
Path
/
Cookies are designed to always expire. Session cookies
are truly ephemeral and remain cached until the browser
is closed. The Expires and Max-Age cookie attributes can
be used to specify that a cookie should stay alive for
longer.
Expires
Sat Jan 11 13:49:22 UTC 2020 (11 months 30 days)
The HttpOnly flag prevents the cookie from being accessed
from JavaScript, thus making them more difficult
to obtain after a successful XSS attack.
HttpOnly
The Secure flag signals to browsers that the cookie
should be transmitted only over an encrypted channel.
Secure
Normally, when a browser makes a request to a web site,
it sends all associated cookies. This is not always
desirable, because it might allow third-party sites
to perform site actions under the identity of the user.
This attack is known as Cross-Site Request Forgery.
With SameSite cookies (still in development, but already
supported in some browsers), you can choose to be more
strict. The possible values are 'lax' and 'strict'.
SameSite

Analysis

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

Analysis

Good
All cookies are secure
Great. All observed cookies are marked secure.

Mixed Content

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

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

Embedded Resources

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

0 script(s)
  0 out of 0 are secure
0 CSS file(s)
  0 out of 0 are secure
2 media file(s)
  2 out of 2 are secure  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.

44 link(s)
  22 out of 44 are encrypted
http://www.jmonae.com/
http://www.speedtest.net/...my-result/3928294483
http://www.speedtest.net/...my-result/4417676841
http://netwars-project.com/webdoc
http://twitter.com/_nvmr
http://twitter.com/init7_noc
http://twitter.com/.../1082972487896436736
http://twitter.com/.../1080090742255771649
http://twitter.com/CptnDan
http://twitter.com/init7
http://twitter.com/padfrey
http://twitter.com/.../1082959151205150720
http://twitter.com/.../1082906970431078400
http://twitter.com/init7
http://twitter.com/padfrey
http://twitter.com/.../1082574657008607233
http://twitter.com/.../1081700310018596866
http://twitter.com/_nvmr
http://twitter.com/init7_noc
http://twitter.com/.../1080090742255771649
http://twitter.com/.../1077157089112403969
http://wordpress.org/
 View all

Analysis

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.

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

HSTS Policy  Main host

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

Analysis

Good
Policy is valid
OK. Your HSTS policy uses correct syntax.
Good
Long policy age
Your HSTS policy has a long max-age value, which offers better protection.
Good
Policy covers subdomains
When subdomains are included, network attackers are unable to manufacture arbitrary subdomains to manipulate cookies and trick users.
Good
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.
Good
Policy preloaded
Excellent. This host is covered by a preloaded HSTS policy.

Preloaded host: alainwolf.ch; includeSubDomains=true

HSTS Policy  Apex host

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

Analysis

Good
Policy is valid
OK. Your HSTS policy uses correct syntax.
Good
Long policy age
Your HSTS policy has a long max-age value, which offers better protection.
Good
Policy covers subdomains
When subdomains are included, network attackers are unable to manufacture arbitrary subdomains to manipulate cookies and trick users.
Good
Preload intent declared
Good. With the preload directive set, browsers have a green light to embed the HSTS policy.
Good
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.
Good
Policy preloaded
Excellent. This host is covered by a preloaded HSTS policy.

Preloaded host: alainwolf.ch; 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 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

base-uri 'self'  
default-src 'none'
connect-src 'self'   https://*.w.org   https://*.wordpress.org  
font-src 'self'   data:  
form-action 'self'  
frame-ancestors 'none'  
frame-src 'self'   https://maps.google.ch   https://www.google.com   https://www.komoot.de   https://player.vimeo.com   https://*.w.org   https://*.wordpress.org   https://wordpress.org   https://www.youtube-nocookie.com   https://www.youtube.com  
img-src 'self'   https://androidflip.com   https://archive.ban.org   https://uk-img.ciao.com   https://secure.gravatar.com   https://www.greenpeace.org   https://badge.hardenize.com   https://licensebuttons.net   https://www.samba.org   https://spicebird.org   https://teslacoilsw.com   https://*.urown.net   https://*.w.org   https://wordpress.org   https://s.w.org   https://www.ynetnews.com   data:  
media-src 'self'  
script-src 'self'   https://cdnjs.cloudflare.com   https://*.urown.net   This parameter shouldn't be used because it reenables
insecure behavior that CSP disables by default.
'unsafe-inline'
  This parameter shouldn't be used because it reenables
insecure behavior that CSP disables by default.
'unsafe-eval'
 
style-src 'self'   https://cdnjs.cloudflare.com   https://code.jquery.com   This parameter shouldn't be used because it reenables
insecure behavior that CSP disables by default.
'unsafe-inline'
 
report-uri https://urown.report-uri.com/r/default/csp/enforce  
upgrade-insecure-requests

Analysis

Good
Mixed content upgraded
Good. This CSP policy instructs browsers to seamlessly upgrade plaintext resources to encryption.
Powerup!
Inline scripts are allowed
By default, CSP doesn't allow inline script execution, but this policy overrides that behavior by specifying 'unsafe-inline' in the 'script-src' directive. As a result, all XSS defenses provided by CSP are significantly weakened.
Powerup!
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.
Powerup!
Dynamic code execution is allowed
By default, CSP doesn't allow dynamic script execution via eval and friends, but this policy overrides that behavior by specifyin 'unsafe-eval' in the 'script-src' directive. As a result, XSS defenses provided by CSP are significantly weakened.

Analysis

Info
CSP policy detected

Header: Content-Security-Policy

Value: base-uri 'self'; default-src 'none'; connect-src 'self' https://*.w.org https://*.wordpress.org; font-src 'self' data:; form-action 'self'; frame-ancestors 'none'; frame-src 'self' https://maps.google.ch https://www.google.com https://www.komoot.de https://player.vimeo.com https://*.w.org https://*.wordpress.org https://wordpress.org https://www.youtube-nocookie.com https://www.youtube.com; img-src 'self' https://androidflip.com https://archive.ban.org https://uk-img.ciao.com https://secure.gravatar.com https://www.greenpeace.org https://badge.hardenize.com https://licensebuttons.net https://www.samba.org https://spicebird.org https://teslacoilsw.com https://*.urown.net https://*.w.org https://wordpress.org https://s.w.org https://www.ynetnews.com data:; media-src 'self'; script-src 'self' https://cdnjs.cloudflare.com https://*.urown.net 'unsafe-inline' 'unsafe-eval'; style-src 'self' https://cdnjs.cloudflare.com https://code.jquery.com 'unsafe-inline'; report-uri https://urown.report-uri.com/r/default/csp/enforce; upgrade-insecure-requests

Location: https://alainwolf.ch/

Subresource Integrity

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

Test passed
Everything seems to be well configured. Well done.
No external scripts
  SRI not needed
No external stylesheets
  SRI not needed

Analysis

Good
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 response HTTP header that web sites can use to monitor problems related to their Certificate Transparency (CT) compliance. Additionally, they can also instruct browsers to reject any certificates in their name that are are not CT-compliant.

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

Expect-CT Policy

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

Analysis

Info
Header information

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

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

Frame Options

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

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

Analysis

Info
Header information

Name: X-Frame-Options

Value: DENY

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

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.

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

Analysis

Info
Header information

Name: X-XSS-Protection

Value: 1; mode=block

Good
Valid configuration
Good. Your configuration enforces blocking when XSS attacks are detected.

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

Info
Header information

Name: X-Content-Type-Options

Value: nosniff

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

HTML Analysis

Analysis of page content, including SRI.

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

Base URL

https://alainwolf.ch/

Active Content

Type Status Location
None

Passive Content

Type Status Link
media Third-party www.youtube.com
media Third-party badge.hardenize.com

Links

Type Status Link
link Encrypted www.youtube.com
link Encrypted www.youtube.com
link Plaintext www.jmonae.com
link Encrypted www.savenetneutrality.eu
link Encrypted donottrack-doc.com
link Encrypted donottrack-doc.com
link Plaintext www.speedtest.net
link Plaintext www.speedtest.net
link Plaintext netwars-project.com
link Encrypted prism-break.org
link Plaintext twitter.com
link Plaintext twitter.com
link Encrypted t.co
link Plaintext twitter.com
link Plaintext twitter.com
link Plaintext twitter.com
link Plaintext twitter.com
link Plaintext twitter.com
link Encrypted t.co
link Plaintext twitter.com
link Plaintext twitter.com
link Plaintext twitter.com
link Plaintext twitter.com
link Encrypted t.co
link Encrypted t.co
link Encrypted t.co
link Plaintext twitter.com
link Plaintext twitter.com
link Plaintext twitter.com
link Plaintext twitter.com
link Encrypted t.co
link Plaintext twitter.com
link Plaintext twitter.com
link Encrypted www.hardenize.com
link Encrypted keybase.io
link Encrypted github.com
link Encrypted twitter.com
link Encrypted soundcloud.com
link Encrypted libre.fm
link Encrypted www.openbroadcast.org
link Encrypted www.komoot.de
link Encrypted app.velohero.com
link Encrypted nextcloud.com
link Plaintext wordpress.org