SSL-Tools

SSL check results of unicomp.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for unicomp.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 Mon, 07 Sep 2026 18:07:43 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.unicomp.de
80.151.227.192
 10
supported
mail.unicomp.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • SSLv3
2 s

Outgoing Mails

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

Host TLS Version & Cipher
mail.unicomp.de (80.151.227.192)
TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384
mail.unicomp.de (94.79.178.38)
TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384

Certificates

First seen at:

CN=mail.unicomp.de

Certificate chain
  • mail.unicomp.de
    • remaining
    • 384 bit
    • ecdsa-with-SHA384
      • YE2
        • remaining
        • 384 bit
        • ecdsa-with-SHA384
          • Root YE
            • remaining
            • 384 bit
            • ecdsa-with-SHA384
              • ISRG Root X2 (Certificate is self-signed.)
                • remaining
                • 384 bit
                • ecdsa-with-SHA384
Subject
Common Name (CN)
  • mail.unicomp.de
Alternative Names
  • autodiscover.unicomp.de
  • download.mail.unicomp.de
  • mail.unicomp.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • YE2
validity period
Not valid before
2026-07-21
Not valid after
2026-10-19
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
Fingerprints
SHA256
22:2F:AB:A8:03:52:86:EE:C4:A8:6B:3F:98:FF:65:E4:E2:38:F1:62:5C:8C:8B:C1:D6:BD:BC:B9:AD:B6:D2:65
SHA1
5C:36:64:A5:4B:9B:08:C2:EE:C3:FF:04:89:99:B0:2B:27:C0:1C:38
X509v3 extensions
subjectKeyIdentifier
  • 91:A5:83:6D:0A:01:61:5B:A6:8C:74:65:95:92:58:E9:13:46:4B:9D
authorityKeyIdentifier
  • keyid:B9:59:F2:8E:CF:22:F0:86:D3:37:48:FF:76:14:18:BA:82:D8:55:87
authorityInfoAccess
  • CA Issuers - URI:http://ye2.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://ye2.c.lencr.org/99.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CB:38:F7:15:89:7C:84:A1:44:5F:5B:C1:DD:FB:C9:6E:
  • F2:9A:59:CD:47:0A:69:05:85:B0:CB:14:C3:14:58:E7
  • Timestamp : Jul 21 03:45:59.778 2026 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:63:7F:A9:35:ED:82:33:EB:3C:09:FC:B6:
  • FB:70:39:7E:64:53:08:8A:B8:A2:67:86:80:B1:59:FD:
  • 4A:E7:DE:04:02:21:00:F2:05:19:2A:0A:F4:2C:81:59:
  • 36:11:CF:F3:D6:27:39:C7:72:E2:0B:A5:1E:17:30:39:
  • 85:49:19:CD:3A:14:C0
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 1A:8B:9D:6B:0F:FE:BF:81:B4:79:39:C6:D2:31:0A:86:
  • D6:D1:02:D4:F0:46:E2:18:2C:9D:E3:5F:5E:26:25:EF
  • Timestamp : Jul 21 03:46:00.593 2026 GMT
  • Extensions: 00:00:05:00:2B:EF:DA:DD
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:B2:FE:71:A2:BF:EF:C0:2B:FE:09:D3:
  • 37:2D:0B:87:02:ED:EB:8C:93:9C:D2:D1:2A:39:4C:85:
  • B0:BA:66:D1:0C:02:21:00:B4:D9:A2:E9:68:75:3E:49:
  • 7F:7D:5A:FD:60:DB:BF:3D:00:85:08:04:B8:4A:35:85:
  • 78:84:4C:3E:51:56:93:C4