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 Sat, 06 Jul 2019 15:25:42 +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
  • TLSv1.1
  • 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
  • TLSv1.1
  • 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-06-04
Not valid after
2019-09-02
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
A1:24:70:1B:F0:AB:C1:15:C7:6A:65:38:AE:4B:F8:94:B9:0D:B2:8C:DA:CC:EB:8C:7C:B5:38:09:79:6B:30:D1
SHA1
BA:D8:6C:0D:B7:C9:53:5C:4E:41:45:EE:83:CD:43:27:69:FD:FC:C4
X509v3 extensions
subjectKeyIdentifier
  • 42:6C:AB:89:65:4C:CE:62:DE:1D:3B:65:81:F2:93:D0:6D:E3:29:4F
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 : E2:69:4B:AE:26:E8:E9:40:09:E8:86:1B:B6:3B:83:D4:
  • 3E:E7:FE:74:88:FB:A4:8F:28:93:01:9D:DD:F1:DB:FE
  • Timestamp : Jun 4 23:47:31.228 2019 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:A0:EB:82:41:D3:BD:65:56:7F:97:88:
  • 1B:32:BB:A5:64:11:C9:AE:D0:7B:1F:C9:38:3F:92:C8:
  • A1:EB:97:68:C9:02:21:00:8D:F6:FB:F6:2D:84:0C:C9:
  • 3C:80:6F:3C:0F:5A:DC:31:04:64:0D:47:CB:FF:08:48:
  • 4C:FF:D6:0D:95:E4:D2:A5
  • 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 : Jun 4 23:47:31.713 2019 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:AD:5B:7D:D9:8E:5F:20:20:F2:E0:99:
  • 34:A6:C8:D7:BD:84:4D:76:B1:C9:61:2C:69:67:D2:0E:
  • D0:88:B3:E0:D8:02:21:00:EC:F3:DD:8F:57:39:49:10:
  • C2:9E:B2:E2:EF:54:FA:8E:21:E0:7C:2E:5C:4A:93:4C:
  • 84:69:AA:13:FB:DD:EE:57