SSL-Tools

SSL check results of mail.cooltec-systems.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for mail.cooltec-systems.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 Thu, 23 Mar 2023 09:11:08 +0000

The mailservers of mail.cooltec-systems.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @mail.cooltec-systems.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.cooltec-systems.de
80.152.142.103
 -
supported
remote.cooltec-systems.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
4 s

Outgoing Mails

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

Certificates

First seen at:

CN=remote.cooltec-systems.de

Certificate chain
  • remote.cooltec-systems.de
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • remote.cooltec-systems.de
Alternative Names
  • adfs.cooltec-systems.de
  • autodiscover.cooltec-systems.de
  • mail.cooltec-systems.de
  • nas.cooltec-systems.de
  • rds.cooltec-systems.de
  • remote.cooltec-systems.de
  • transfer.cooltec-systems.de
  • wiki.cooltec-systems.de
  • wsus.cooltec-systems.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2023-03-20
Not valid after
2023-06-18
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
9F:AE:46:1E:AE:12:FD:DF:F3:BC:D8:C4:C4:C8:C2:80:34:98:9A:72:7C:C2:65:A6:8E:0A:7F:BC:B8:32:EB:73
SHA1
FE:3F:80:40:9D:2F:BB:04:62:B8:84:4E:23:BB:91:38:07:8A:43:B0
X509v3 extensions
subjectKeyIdentifier
  • AD:22:51:24:E6:26:D2:94:D3:CD:64:51:2C:9D:7E:9A:A1:10:BD:F5
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
  • 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 : B7:3E:FB:24:DF:9C:4D:BA:75:F2:39:C5:BA:58:F4:6C:
  • 5D:FC:42:CF:7A:9F:35:C4:9E:1D:09:81:25:ED:B4:99
  • Timestamp : Mar 20 08:28:09.422 2023 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:0B:AE:69:87:C9:50:A1:0C:FE:15:FD:2A:
  • 4A:99:7E:96:8B:39:B3:C0:02:81:61:55:BD:C3:F4:F8:
  • 64:F1:37:75:02:20:0D:15:F1:0A:37:4F:EC:8C:04:3E:
  • AB:B8:2C:9A:96:9E:2E:23:1C:39:A8:AA:B1:67:5C:D6:
  • 53:7B:09:E8:CA:8F
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 7A:32:8C:54:D8:B7:2D:B6:20:EA:38:E0:52:1E:E9:84:
  • 16:70:32:13:85:4D:3B:D2:2B:C1:3A:57:A3:52:EB:52
  • Timestamp : Mar 20 08:28:09.437 2023 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:09:DE:CD:F2:B4:AB:5D:78:18:D2:95:99:
  • 1C:8D:00:6A:1E:6E:7A:7E:A3:44:72:18:E4:C3:CF:83:
  • 15:4C:84:96:02:20:15:86:04:A8:FD:6A:B8:61:00:33:
  • BE:C3:69:46:37:91:0F:6A:E3:E9:03:F5:BB:17:FE:9D:
  • ED:B8:78:28:29:24