SSL check results of saitsali.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for saitsali.de 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 Wed, 18 Sep 2019 14:53:07 +0000

The mailservers of saitsali.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @saitsali.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.saitsali.de
2a03:4000:28:d1::1
10
supported
*.saitsali.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
mail.saitsali.de
94.16.112.217
10
supported
*.saitsali.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s

Outgoing Mails

We have received emails from these servers with @saitsali.de sender addresses. Test mail delivery

Host TLS Version & Cipher
mail.saitsali.de (81.30.156.20)
TLSv1.2 AECDH-AES256-SHA
mail.saitsali.de (IPv6:2001:4ba0:cafe:b56::1)
TLSv1.2 AECDH-AES256-SHA
mail.saitsali.de (188.68.56.155)
TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384
mail.saitsali.de (IPv6:2a03:4000:6:f01f::1)
TLSv1.2 AECDH-AES256-SHA
mail.saitsali.de (94.16.112.217)
TLSv1.3 TLS_AES_256_GCM_SHA384

Certificates

First seen at:

CN=*.saitsali.de

Certificate chain
Subject
Common Name (CN)
  • *.saitsali.de
Alternative Names
  • *.saitsali.de
  • saitsali.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • Let's Encrypt Authority X3
validity period
Not valid before
2019-08-04
Not valid after
2019-11-02
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
09:9A:9C:DA:40:36:59:62:C8:1C:2A:8E:FA:A1:5A:D9:9B:4E:4A:95:2E:1D:7B:92:F6:71:24:DD:BD:80:63:D9
SHA1
8E:04:16:65:24:2F:FA:52:DD:2C:29:16:A8:64:D1:67:EE:2F:7F:02
X509v3 extensions
subjectKeyIdentifier
  • 4A:E6:14:CE:8F:DD:90:46:6A:27:55:F9:C4:47:AF:39:84:BA:1A:01
authorityKeyIdentifier
  • keyid:A8:4A:6A:63:04:7D:DD:BA:E6:D1:39:B7:A6:45:65:EF:F3:A8:EC:A1
authorityInfoAccess
  • OCSP - URI:http://ocsp.int-x3.letsencrypt.org
  • CA Issuers - URI:http://cert.int-x3.letsencrypt.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
  • Policy: 1.3.6.1.4.1.44947.1.1.1
  • CPS: http://cps.letsencrypt.org
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 74:7E:DA:83:31:AD:33:10:91:21:9C:CE:25:4F:42:70:
  • C2:BF:FD:5E:42:20:08:C6:37:35:79:E6:10:7B:CC:56
  • Timestamp : Aug 4 06:30:12.401 2019 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:A0:88:E5:DC:A9:89:51:69:7A:DE:20:
  • FD:98:76:0C:38:0E:41:34:48:76:41:C4:4B:48:65:A0:
  • 29:B1:2F:01:F5:02:20:11:4A:7F:39:E8:A7:0E:58:04:
  • 56:0B:37:B0:14:F4:A1:6E:B0:42:F8:51:F4:17:06:DD:
  • 98:08:81:3A:BE:59:E7
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 63:F2:DB:CD:E8:3B:CC:2C:CF:0B:72:84:27:57:6B:33:
  • A4:8D:61:77:8F:BD:75:A6:38:B1:C7:68:54:4B:D8:8D
  • Timestamp : Aug 4 06:30:12.884 2019 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:6B:F3:FD:BE:6E:72:C4:A4:05:61:2C:BB:
  • 33:2D:33:59:F2:25:2D:55:9D:31:EA:69:8A:08:C2:BA:
  • 60:0E:5B:F7:02:20:45:F8:E1:9D:62:A6:0D:58:30:43:
  • BD:61:99:F6:84:7B:FD:25:3B:AA:6A:8F:1B:1C:27:72:
  • 5D:EB:CE:76:17:38