SSL-Tools

SSL check results of kom-solution.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for kom-solution.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, 04 May 2021 12:28:08 +0000

We can not guarantee a secure connection to the mailservers of kom-solution.de!

Please contact the operator of kom-solution.de and ask him or her to solve this problem. This result stays accessible under the following address:

/mailservers/kom-solution.de

Servers

Incoming Mails

These servers are responsible for incoming mails to @kom-solution.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail01.kom-solution.de
62.96.107.37
 10
supported
kom-solution.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
supported
  • SSL_RSA_WITH_RC4_128_SHA
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
12 s
mail02.kom-solution.de
88.198.251.75
Results incomplete
200 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s

Outgoing Mails

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

Certificates

First seen at:

CN=kom-solution.de

Certificate chain
  • kom-solution.de
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • DST Root CA X3 (Certificate is self-signed.)
            • remaining
            • 2048 bit
            • sha1WithRSAEncryption
Subject
Common Name (CN)
  • kom-solution.de
Alternative Names
  • *.kom-solution.de
  • kom-solution.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-05-04
Not valid after
2021-08-02
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
CF:D3:8D:45:1A:66:FE:17:53:BE:B2:81:CB:CC:B3:81:1F:D3:92:FA:D1:5F:17:D9:EF:E6:C4:CD:63:A9:3A:5C
SHA1
29:43:E8:E6:12:FD:55:FF:3D:70:3A:DE:61:C7:60:23:85:CC:9E:B8
X509v3 extensions
subjectKeyIdentifier
  • 64:01:CA:50:81:E6:EB:1C:FF:36:97:1C:27:3D:71:E7:5C:7F:8F:FB
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 : 94:20:BC:1E:8E:D5:8D:6C:88:73:1F:82:8B:22:2C:0D:
  • D1:DA:4D:5E:6C:4F:94:3D:61:DB:4E:2F:58:4D:A2:C2
  • Timestamp : May 4 11:59:54.263 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:83:17:DB:2A:E9:08:56:D4:66:E2:64:
  • C7:10:70:D7:C0:6B:43:50:97:68:00:EC:42:21:5E:6A:
  • 4F:FF:A3:8A:6E:02:21:00:DA:6A:BD:71:65:82:D4:03:
  • 0B:32:E1:47:87:A1:38:74:6B:66:77:64:32:80:96:5B:
  • C0:8A:C1:A9:F7:82:4A:0F
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : F6:5C:94:2F:D1:77:30:22:14:54:18:08:30:94:56:8E:
  • E3:4D:13:19:33:BF:DF:0C:2F:20:0B:CC:4E:F1:64:E3
  • Timestamp : May 4 11:59:54.255 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:A5:DF:37:FF:AC:92:F1:9A:50:E7:8E:
  • 51:5A:35:FA:94:59:DB:C0:5E:A2:5C:E4:E4:B9:A7:DE:
  • CA:1C:E6:19:C8:02:21:00:90:97:AB:DB:15:C1:22:B7:
  • A4:AD:62:1A:E4:08:78:02:B4:F5:55:82:26:3D:84:5F:
  • F8:3D:DB:10:F9:2F:2F:32