SSL check results of savvii.email

NEW You can also bulk check multiple servers.

Discover if the mail servers for savvii.email can be reached through a secure connection.

To establish a secure connection a mail server has to offer STARTTLS (SSL), a trustworthy SSL certificate, support for the Diffie-Hellman-Algorithm to guarantee Perfect Forward Secrecy and must not be vulnerable against the Heartbleed attack. Futhermore we recommend using end-to-end encryption with GnuPG.

Summary

Report created Fri, 19 Apr 2024 08:01:54 +0000

The mailservers of savvii.email can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @savvii.email addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mx1.savvii.email
2a10:de80:1:4091:b9e9:2220::1
1
supported
mail.savvii.email
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
8 s
mx1.savvii.email
185.233.34.32
1
supported
mail.savvii.email
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
7 s
mx2.savvii.email
2a10:de80:1:4091:b9e9:2221::1
2
supported
mail.savvii.email
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
7 s
mx2.savvii.email
185.233.34.33
2
supported
mail.savvii.email
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
7 s

Outgoing Mails

We have not received any emails from a @savvii.email address so far. Test mail delivery

Certificates

First seen at:

CN=mail.savvii.email

Certificate chain
  • mail.savvii.email
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption

      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption

Subject
Common Name (CN)
  • mail.savvii.email
Alternative Names
  • caldav.savvii.email
  • imap.savvii.email
  • mail.savvii.email
  • mx1.savvii.email
  • mx2.savvii.email
  • smtp.savvii.email
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-04-11
Not valid after
2024-07-10
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
F4:71:AE:20:A4:FC:EB:98:36:67:67:83:B3:22:E3:6D:69:6A:C1:5A:05:69:94:CB:E2:11:DF:83:59:E1:1C:2A
SHA1
C9:70:51:4B:75:AD:F3:95:6B:11:AF:31:22:C0:7A:FE:02:BD:CF:CB
X509v3 extensions
subjectKeyIdentifier
  • 91:9F:9F:60:5A:67:88:73:B1:0A:27:47:93:2D:08:63:C9:C9:B7:44
authorityKeyIdentifier
  • keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
authorityInfoAccess
  • OCSP - URI:http://r3.o.lencr.org
  • CA Issuers - URI:http://r3.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : EE:CD:D0:64:D5:DB:1A:CE:C5:5C:B7:9D:B4:CD:13:A2:
  • 32:87:46:7C:BC:EC:DE:C3:51:48:59:46:71:1F:B5:9B
  • Timestamp : Apr 11 14:15:28.725 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:52:9A:14:D5:F6:30:70:62:1B:FF:0E:29:
  • 41:04:A8:95:03:AF:D1:20:A4:66:FE:71:6C:14:C3:15:
  • 13:12:37:78:02:21:00:BF:32:AE:AC:59:AF:BD:37:1C:
  • 65:23:48:48:DE:A9:5C:5B:7B:88:78:8D:6E:C9:B7:5D:
  • FB:D3:3A:D0:B1:95:C6
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 19:98:10:71:09:F0:D6:52:2E:30:80:D2:9E:3F:64:BB:
  • 83:6E:28:CC:F9:0F:52:8E:EE:DF:CE:4A:3F:16:B4:CA
  • Timestamp : Apr 11 14:15:28.897 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:1A:36:36:92:8D:38:A3:9A:85:FF:CA:4C:
  • 4F:68:31:89:A5:4F:D3:5A:74:05:83:84:85:E9:59:3D:
  • DA:12:52:F6:02:21:00:8A:4A:6F:93:A0:47:06:52:7F:
  • 29:D0:DF:66:6F:57:2E:0F:AA:4E:91:5F:52:9C:5B:12:
  • 65:8C:BB:D8:55:62:33

DANE

DNS-based Authentication of Named Entities (DANE) is a protocol to allow X.509 certificates to be bound to DNS using TLSA records and DNSSEC.

Name Options DNSSEC Matches
_25._tcp.mx1.savvii.email
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
valid
valid
_25._tcp.mx2.savvii.email
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
valid
valid