Hardenize has joined Red Sift! Find out more in our blog post.
Web Security Overview
Unable to determine
No HTTP servers

This host doesn't seem to have any HTTP servers. We'll focus on evaluating the DNS and email configuration instead.

Email Security Overview
Error
STARTTLS

All hosts that receive email need encryption to ensure confidentiality of email messages. Email servers thus need to support STARTTLS, as well as provide decent TLS configuration and correct certificates.
There are issues with this site's SMTP configuration.

For all sites VERY IMPORTANT low EFFORT
Supported and well configured
SPF

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

For important sites IMPORTANT low EFFORT
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

DNS Zone

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

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

Nameserver Names

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

Nameserver Operational IPv4 IPv6 Sources
ns-1138.awsdns-14.org.
205.251.196.114
2600:9000:5304:7200::1
The server is online. Name resolves to an IPv4 address. Name resolves to an IPv6 address. NS REFERRAL
ns-150.awsdns-18.com.
205.251.192.150
2600:9000:5300:9600::1
The server is online. Name resolves to an IPv4 address. Name resolves to an IPv6 address. NS REFERRAL
ns-1967.awsdns-53.co.uk. PRIMARY
205.251.199.175
2600:9000:5307:af00::1
The server is online. Name resolves to an IPv4 address. Name resolves to an IPv6 address. NS REFERRAL SOA
ns-724.awsdns-26.net.
205.251.194.212
2600:9000:5302:d400::1
The server is online. Name resolves to an IPv4 address. Name resolves to an IPv6 address. NS REFERRAL

Nameserver Addresses

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

Nameserver Operational Authoritative Recursive UDP TCP Sources Payload Size
205.251.192.150
ns-150.awsdns-18.com.
PTR: ns-150.awsdns-18.com.
The server appears to be online. Nameserver provides authoritative responses Nameserver doesn't provide recursive service Nameserver responds to UDP queries Nameserver responds to TCP queries NAME, GLUE 4096
205.251.194.212
ns-724.awsdns-26.net.
PTR: ns-724.awsdns-26.net.
The server appears to be online. Nameserver provides authoritative responses Nameserver doesn't provide recursive service Nameserver responds to UDP queries Nameserver responds to TCP queries NAME 4096
205.251.196.114
ns-1138.awsdns-14.org.
PTR: ns-1138.awsdns-14.org.
The server appears to be online. Nameserver provides authoritative responses Nameserver doesn't provide recursive service Nameserver responds to UDP queries Nameserver responds to TCP queries NAME 4096
205.251.199.175 PRIMARY
ns-1967.awsdns-53.co.uk.
PTR: ns-1967.awsdns-53.co.uk.
The server appears to be online. Nameserver provides authoritative responses Nameserver doesn't provide recursive service Nameserver responds to UDP queries Nameserver responds to TCP queries NAME 4096
2600:9000:5300:9600::1
ns-150.awsdns-18.com.
PTR: ns-150.awsdns-18.com.
The server appears to be online. Nameserver provides authoritative responses Nameserver doesn't provide recursive service Nameserver responds to UDP queries Nameserver responds to TCP queries NAME 4096
2600:9000:5302:d400::1
ns-724.awsdns-26.net.
PTR: ns-724.awsdns-26.net.
The server appears to be online. Nameserver provides authoritative responses Nameserver doesn't provide recursive service Nameserver responds to UDP queries Nameserver responds to TCP queries NAME 4096
2600:9000:5304:7200::1
ns-1138.awsdns-14.org.
PTR: ns-1138.awsdns-14.org.
The server appears to be online. Nameserver provides authoritative responses Nameserver doesn't provide recursive service Nameserver responds to UDP queries Nameserver responds to TCP queries NAME 4096
2600:9000:5307:af00::1 PRIMARY
ns-1967.awsdns-53.co.uk.
PTR: ns-1967.awsdns-53.co.uk.
The server appears to be online. Nameserver provides authoritative responses Nameserver doesn't provide recursive service Nameserver responds to UDP queries Nameserver responds to TCP queries NAME 4096

Start of Authority (SOA) Record

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

The domain name of the primary nameserver for the zone. Also known as MNAME.Primary nameserver ns-1967.awsdns-53.co.uk.
Email address of the persons responsible for this zone. Also known as RNAME.Admin email awsdns-hostmaster.amazon.com.
Zone serial or version number.Serial number 1
The length of time secondary nameservers should wait before querying the primary for changes.Refresh interval 7,200 seconds (about 2 hours)
The length of time secondary nameservers should wait before querying an unresponsive primary again.Retry interval 900 seconds (about 15 minutes)
The length of time after which secondary nameservers should stop responding to queries for a zone, assuming no updates were obtained from the primary.Expire interval 1,209,600 seconds (about 14 days)
TTL for purposes of negative response caching. Negative cache TTL 86,400 seconds (about 1 day)
Time To Live (TTL) indicates for how long a record remains valid. SOA record TTL 600 seconds (about 10 minutes)

Analysis

Good
No problems detected with the zone configuration
Excellent. This DNS zone is in a good working order. No problems detected.

Backing DNS Queries

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

ID Server Transport Question Name Type Status

DNS Records

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

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

DNS Records

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

Name TTL Type Data
tuta.com.     600 A 185.205.69.12            
www.tuta.com.     300 A 185.205.69.12            
tuta.com.     600 AAAA 2a10:e000:1:0:0:0:0:12            
www.tuta.com.     300 AAAA 2a10:e000:1:0:0:0:0:12            
tuta.com.     600 CAA 0 issue "letsencrypt.org"            
tuta.com.     600 CAA 0 issue "sectigo.com"            
tuta.com.     3600 DNSKEY 256 3 13 Yr0dx9xpKyukOU8wotPmtxgQ9YAhgInq5AUfsUApJtAax8rUfcNi0uBq2UNKN0FFWmLhdMecbHejBRiTSTrGqA==            
tuta.com.     3600 DNSKEY 257 3 13 os2q8ALQGmPkTNlO5NIMo8ahIfRHCWEE/whvXl5WnAedqON21t9n9eINOmfs6HctNkOcLSlpl06nRnP5z9XhbQ==            
tuta.com.     3600 DNSKEY 256 3 13 +X1y9OuQUyFk44b1MF6F3KLnQgwjC6YCBx1rFQY4bn+EwHuNsKXDClZC6VKWtYO/UQRWJfxpcAdpeuHHuFrolw==            
tuta.com.     600 MX 0 mail.tutanota.de.            
tuta.com.     600 NS ns-1138.awsdns-14.org.            
tuta.com.     600 NS ns-150.awsdns-18.com.            
tuta.com.     600 NS ns-1967.awsdns-53.co.uk.            
tuta.com.     600 NS ns-724.awsdns-26.net.            
tuta.com.     600 SOA ns-1967.awsdns-53.co.uk. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400            
tuta.com.     600 TXT "google-site-verification=tsH9g7KEFw9oimUXXbhRw4VKc1hQ9KXOmozGUju5dgI"            
tuta.com.     600 TXT "v=spf1 include:spf.tutanota.de -all"            
_dmarc.tuta.com.     600 TXT "v=DMARC1; p=quarantine; adkim=s"            
_mta-sts.tuta.com.     300 CNAME _mta-sts.tutanota.com.            
_mta-sts.tutanota.com.     600 TXT "v=STSv1; id=20190723;"            
_smtp._tls.tuta.com.     600 CNAME _smtp._tls.tutanota.com.            
_smtp._tls.tutanota.com.     600 TXT "v=TLSRPTv1;rua=mailto:mta-sts-reports@tutanota.com"            

Backing DNS Queries

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

ID Server Question Name Type Status

DNSSEC

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

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

Analysis

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

Useful DNSSEC Tools

Certification Authority Authorization

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

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

CAA Policy Information

The DNS hostname where this policy is located.Policy host tuta.com
The issue property tag is used to request that certificate
issuers perform CAA issue restriction processing for the domain
and to grant authorization to specific certificate issuers.
issue
letsencrypt.org  flags: 0
The issue property tag is used to request that certificate
issuers perform CAA issue restriction processing for the domain
and to grant authorization to specific certificate issuers.
issue
sectigo.com  flags: 0

Analysis

Good
CAA policy found
Good. This domain name uses CAA to restrict which CAs are allowed to issue certificates for it.
Powerup!
Policy doesn't use reporting
This policy doesn't use reporting, which means that there is no way to contact you when a violation is detected. The CAA RFC defines the iodef property that can be used for this purpose. Do note that you're not guaranteed to be notified, given that CAs generally don't support notifications yet.

Email (SMTP)

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

Test passed
Everything seems to be well configured. Well done.
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
mail.tutanota.de
81.3.6.162
PTR: w1.tutanota.de
0
220 w1.tutanota.de ESMTP Tutanota

EHLO outbound.hardenize.com
250-w1.tutanota.de
250-PIPELINING
250-SIZE 36700160
250-ETRN
250-STARTTLS
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 CHUNKING

STARTTLS
220 2.0.0 Ready to start TLS
Supports STARTTLS.
mail.tutanota.de
81.3.6.165
PTR: w4.tutanota.de
0
220 w4.tutanota.de ESMTP Tutanota

EHLO outbound.hardenize.com
250-w4.tutanota.de
250-PIPELINING
250-SIZE 36700160
250-ETRN
250-STARTTLS
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 CHUNKING

STARTTLS
220 2.0.0 Ready to start TLS
Supports STARTTLS.
mail.tutanota.de
185.205.69.211
PTR: -
0
220 mail.w11.tutanota.de ESMTP Tutanota

EHLO outbound.hardenize.com
250-mail.w11.tutanota.de
250-PIPELINING
250-SIZE 36700160
250-ETRN
250-STARTTLS
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 CHUNKING

STARTTLS
220 2.0.0 Ready to start TLS
Supports STARTTLS.

Analysis

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: 13 May 2024 21:03 UTC

Earliest cache timestamp: 13 May 2024 21:03 UTC

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

Email TLS (SMTP)

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

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

TLS Configuration: mail.tutanota.de (81.3.6.162) Cached

Encryption protocol version determines what features are
available for negotiation between client and server.
Supported protocols
TLS v1.2
Shows cipher suite configuration for this protocol version.TLS v1.2 Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0xc030
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
 256 bits (ECDHE 384 bits)
These results have been retrieved from
our cache. This row indicates when was
that the original test ran.
Retrieved from cache
13 May 2024 21:03 UTC

Analysis

Good
TLS 1.2 supported
Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.
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.
Notice
Partial results shown
SMTP assessments usually take a long time. To get you some results faster, we initially perform shallow checks. If you come back later we may be able to show you complete results.
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: mail.tutanota.de (81.3.6.165) Cached

Encryption protocol version determines what features are
available for negotiation between client and server.
Supported protocols
TLS v1.2
Shows cipher suite configuration for this protocol version.TLS v1.2 Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0xc030
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
 256 bits (ECDHE 384 bits)
These results have been retrieved from
our cache. This row indicates when was
that the original test ran.
Retrieved from cache
13 May 2024 21:03 UTC

Analysis

Good
TLS 1.2 supported
Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.
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.
Notice
Partial results shown
SMTP assessments usually take a long time. To get you some results faster, we initially perform shallow checks. If you come back later we may be able to show you complete results.
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: mail.tutanota.de (185.205.69.211) Cached

Encryption protocol version determines what features are
available for negotiation between client and server.
Supported protocols
TLS v1.2
Shows cipher suite configuration for this protocol version.TLS v1.2 Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0xc030
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC secp384r1 (384 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
 256 bits (ECDHE 384 bits)
These results have been retrieved from
our cache. This row indicates when was
that the original test ran.
Retrieved from cache
13 May 2024 21:03 UTC

Analysis

Good
TLS 1.2 supported
Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.
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.
Notice
Partial results shown
SMTP assessments usually take a long time. To get you some results faster, we initially perform shallow checks. If you come back later we may be able to show you complete results.
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 mail.tutanota.de
Issuer: Sectigo
Not Before: 17 Jul 2023 00:00:00 UTC
Not After: 10 Aug 2024 23:59:59 UTC (expires in 2 months 26 days)
Key: RSA 2048 bits
Signature: SHA256withRSA
 View details

Analysis

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

Certificate Chain

Leaf certificate
mail.tutanota.de | 36be6c8
Not After: 10 Aug 2024 23:59:59 UTC (expires in 2 months 26 days)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Intermediate certificate
Sectigo RSA Domain Validation Secure Server CA | 7fa4ff6
Not After: 31 Dec 2030 23:59:59 UTC (expires in 6 years 7 months)
Authentication: RSA 2048 bits (SHA384withRSA)
 View details
Intermediate certificate
USERTrust RSA Certification Authority | 68b9c76
Not After: 31 Dec 2028 23:59:59 UTC (expires in 4 years 7 months)
Authentication: RSA 4096 bits (SHA384withRSA)
 View details
Root certificate
AAA Certificate Services | d7a7a0f
Not After: 31 Dec 2028 23:59:59 UTC (expires in 4 years 7 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: mail.tutanota.de (81.3.6.162)

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
Certificate (0)
Determines how matching is done; directly or via a hash. Matching Type SHA2-256 (1)
Contains the data necessary to perform the matching. Data 5eb3a224ad39e1423f3a30a0fb5082cc3e716a763b59588311cc551664bc38f5
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
Certificate (0)
Determines how matching is done; directly or via a hash. Matching Type SHA2-256 (1)
Contains the data necessary to perform the matching. Data f8e4f4ed7b8cbd72f0d04217099d19f3b534ae71ee8005f354c2caef2abecda4
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
Certificate (0)
Determines how matching is done; directly or via a hash. Matching Type SHA2-256 (1)
Contains the data necessary to perform the matching. Data 36be6c83a1404577f0ef1054ef6a9ca845387fb87e2714156a8c67fc1d515aaf

Leaf certificate: RSA 2048 bits
Subject: CN=mail.tutanota.de
Issuer: CN=Sectigo RSA Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, ST=Greater Manchester, C=GB
mail.tutanota.de (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: mail.tutanota.de (81.3.6.165)

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
Certificate (0)
Determines how matching is done; directly or via a hash. Matching Type SHA2-256 (1)
Contains the data necessary to perform the matching. Data 5eb3a224ad39e1423f3a30a0fb5082cc3e716a763b59588311cc551664bc38f5
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
Certificate (0)
Determines how matching is done; directly or via a hash. Matching Type SHA2-256 (1)
Contains the data necessary to perform the matching. Data f8e4f4ed7b8cbd72f0d04217099d19f3b534ae71ee8005f354c2caef2abecda4
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
Certificate (0)
Determines how matching is done; directly or via a hash. Matching Type SHA2-256 (1)
Contains the data necessary to perform the matching. Data 36be6c83a1404577f0ef1054ef6a9ca845387fb87e2714156a8c67fc1d515aaf

Leaf certificate: RSA 2048 bits
Subject: CN=mail.tutanota.de
Issuer: CN=Sectigo RSA Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, ST=Greater Manchester, C=GB
mail.tutanota.de (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: mail.tutanota.de (185.205.69.211)

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
Certificate (0)
Determines how matching is done; directly or via a hash. Matching Type SHA2-256 (1)
Contains the data necessary to perform the matching. Data 5eb3a224ad39e1423f3a30a0fb5082cc3e716a763b59588311cc551664bc38f5
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
Certificate (0)
Determines how matching is done; directly or via a hash. Matching Type SHA2-256 (1)
Contains the data necessary to perform the matching. Data f8e4f4ed7b8cbd72f0d04217099d19f3b534ae71ee8005f354c2caef2abecda4
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
Certificate (0)
Determines how matching is done; directly or via a hash. Matching Type SHA2-256 (1)
Contains the data necessary to perform the matching. Data 36be6c83a1404577f0ef1054ef6a9ca845387fb87e2714156a8c67fc1d515aaf

Leaf certificate: RSA 2048 bits
Subject: CN=mail.tutanota.de
Issuer: CN=Sectigo RSA Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, ST=Greater Manchester, C=GB
mail.tutanota.de (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 tuta.com
SPF version used by this policy.v spf1
Evaluates SPF policy specified in another DNS location. This
directive is typically used to allow hosts controlled by
another organization.
include
spf.tutanota.de
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.tutanota.de -all

Location: tuta.com

Good
SPF policy is valid
Good. Your SPF policy is syntactically valid.
Good
Policy uses default fail
Excellent. This policy fails hosts that are not allowed to send email for this domain name.
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: 1

SPF Policy Information Included policy

Host where this policy is located.Location spf.tutanota.de
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
81.3.6.160/28
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.tuta.com
DMARC version used by this policy.v DMARC1
Indicates the policy to be enacted by the receiver at
the request of the domain owner. Possible values are:
none, quarantine, and reject.
p
quarantine
Indicates whether strict or relaxed DKIM
alignment mode is required.
adkim
s

Analysis

Info
DMARC policy found

Policy: v=DMARC1; p=quarantine; adkim=s

Host: _dmarc.tuta.com

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

MTA-STS Policy Indicator

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

Analysis

Good
MTA-STS policy indicator valid
Good. Your MTA-STS policy indicator is valid.

Analysis

Error
Failed to fetch your indicated MTA-STS policy
We have been unable to retrieve the indicated MTA-STS policy due to a network error.

Error: Failed to fetch policy: Connect to mta-sts.tuta.com:443 [mta-sts.tutanota.com./185.205.69.10] failed: Connect timed out

Location: https://mta-sts.tuta.com/.well-known/mta-sts.txt

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

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.

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

URL: http://tuta.com/

Analysis

Warning
HTTP connection failed
We were not able to successfully complete this request.

Message: Connect to tuta.com:80 [tuta.com./185.205.69.12] failed: Connect timed out

URL: http://www.tuta.com/

Analysis

Warning
HTTP connection failed
We were not able to successfully complete this request.

Message: Connect to www.tuta.com:80 [www.tuta.com./185.205.69.12] failed: Connect timed out

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.

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

URL: https://tuta.com/

Analysis

Warning
HTTP connection failed
We were not able to successfully complete this request.

Message: Connect to tuta.com:443 [tuta.com./185.205.69.12] failed: Connect timed out

URL: https://www.tuta.com/

Analysis

Warning
HTTP connection failed
We were not able to successfully complete this request.

Message: Connect to www.tuta.com:443 [www.tuta.com./185.205.69.12] failed: Connect timed out

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.

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

TLS Configuration: tuta.com (2a10:e000:1:0:0:0:0:12)

Analysis

Error
TLS connection failed
We failed to connect to the server using TLS.

Error message: Connect timed out

TLS Configuration: tuta.com (185.205.69.12)

Analysis

Error
TLS connection failed
We failed to connect to the server using TLS.

Error message: Connect timed out

TLS Configuration: www.tuta.com (2a10:e000:1:0:0:0:0:12)

Analysis

Error
TLS connection failed
We failed to connect to the server using TLS.

Error message: Connect timed out

TLS Configuration: www.tuta.com (185.205.69.12)

Analysis

Error
TLS connection failed
We failed to connect to the server using TLS.

Error message: Connect timed out

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.

Unable to test (dependency failed)
This test depends on the results of another test, which hasn't completed.

DANE (443)

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

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

Cookies

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

Unable to test (dependency failed)
This test depends on the results of another test, which hasn't completed.

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.

Unable to test (dependency failed)
This test depends on the results of another test, which hasn't completed.

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.

Unable to test (dependency failed)
This test depends on the results of another test, which hasn't completed.

HSTS Policy  Main host

URL from which this policy was obtained.Location https://tuta.com

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.

Unable to test (dependency failed)
This test depends on the results of another test, which hasn't completed.

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.

Unable to test (dependency failed)
This test depends on the results of another test, which hasn't completed.

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.

Unable to test (dependency failed)
This test depends on the results of another test, which hasn't completed.

Expect CT

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

Unable to test (dependency failed)
This test depends on the results of another test, which hasn't completed.

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.

Unable to test (dependency failed)
This test depends on the results of another test, which hasn't completed.

XSS Protection

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

Unable to test (dependency failed)
This test depends on the results of another test, which hasn't completed.

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.

Unable to test (dependency failed)
This test depends on the results of another test, which hasn't completed.