SSL-Tools

SSL check results of solusar.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for solusar.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

JSON Refresh

Report created Tue, 23 Apr 2024 06:09:08 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.solusar.de
89.58.48.28
 100
supported
mail.solusar.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
7 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.solusar.de

Certificate chain
  • mail.solusar.de
    • remaining
    • 256 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.solusar.de
Alternative Names
  • imap.mail.slg-uetze.de
  • imap.mail.solusar.de
  • imap.slg-uetze.de
  • imap.solusar.de
  • mail.slg-uetze.de
  • mail.solusar.de
  • smtp.mail.slg-uetze.de
  • smtp.mail.solusar.de
  • smtp.slg-uetze.de
  • smtp.solusar.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-23
Not valid after
2024-06-21
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
32:11:B2:63:0F:82:D8:7E:1D:D8:6A:93:26:5A:4E:F6:5A:E3:83:6C:B3:7C:39:BF:2E:1B:0C:59:48:05:52:7C
SHA1
99:28:BB:64:22:37:C3:80:2F:74:5E:48:90:4A:7E:29:E8:C1:8C:D5
X509v3 extensions
subjectKeyIdentifier
  • 31:6D:49:A9:73:4C:1D:56:FA:39:4D:9E:2D:51:C9:F0:EB:61:15:B2
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 : Mar 23 11:07:29.729 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:3E:59:78:11:B9:08:7E:69:BF:24:A6:AF:
  • ED:47:D9:25:51:A6:17:25:6D:DB:E8:09:17:A9:2D:D3:
  • 32:77:A6:7D:02:20:1A:97:92:73:7B:6A:66:E2:AC:A8:
  • 10:6D:7C:92:49:57:0B:2E:B8:D6:71:56:32:39:FC:00:
  • 93:08:B7:AB:08:3F
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 3B:53:77:75:3E:2D:B9:80:4E:8B:30:5B:06:FE:40:3B:
  • 67:D8:4F:C3:F4:C7:BD:00:0D:2D:72:6F:E1:FA:D4:17
  • Timestamp : Mar 23 11:07:31.716 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:04:9A:2E:7F:5E:A4:0F:F0:0F:18:4D:E7:
  • 84:5A:64:87:69:3D:5F:34:17:FE:3E:7E:A9:34:D7:E8:
  • 88:2A:F5:49:02:21:00:C6:CA:1D:A3:E0:A7:13:31:E8:
  • 81:D4:DB:5C:37:7D:1F:80:BE:4F:AF:F8:E8:D3:F7:22:
  • 44:C2:2C:81:BF:2A:21