SSL-Tools

SSL check results of kmu-loft.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for kmu-loft.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, 20 Jan 2022 19:07:59 +0000

The mailservers of kmu-loft.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @kmu-loft.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mx00.pcom.de
194.25.152.16
 10
supported
pcom.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
7 s
mx10.pcom.de
194.25.152.15
 30
supported
pcom.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
8 s

Outgoing Mails

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

Certificates

First seen at:

CN=pcom.de

Certificate chain
  • pcom.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)
  • pcom.de
Alternative Names
  • *.pcom.de
  • pcom.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2022-01-12
Not valid after
2022-04-12
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
3A:37:CC:64:32:82:BE:C3:A1:25:93:63:73:3F:2F:A6:ED:C5:8E:CB:3E:C6:B4:EB:99:1F:F7:BE:56:05:BD:83
SHA1
50:AA:6A:D6:9C:EB:AD:DA:40:40:3E:4E:7D:D3:D9:E3:97:69:2C:D2
X509v3 extensions
subjectKeyIdentifier
  • C8:CB:17:E5:FF:85:96:51:A1:DA:37:8B:D5:D1:16:A0:39:15:A0:AF
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 : 41:C8:CA:B1:DF:22:46:4A:10:C6:A1:3A:09:42:87:5E:
  • 4E:31:8B:1B:03:EB:EB:4B:C7:68:F0:90:62:96:06:F6
  • Timestamp : Jan 12 16:56:26.429 2022 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:3E:5B:3D:3C:05:EB:13:75:DA:B0:ED:7E:
  • 72:0C:FA:73:AB:F9:6D:84:37:F3:9E:DD:31:F9:B4:A9:
  • BA:B0:DD:7D:02:20:03:52:10:2C:0A:55:49:78:32:9D:
  • 0D:A5:DD:45:75:BE:50:8F:4E:8B:95:39:3E:D3:A1:B2:
  • C4:48:5E:90:71:78
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 29:79:BE:F0:9E:39:39:21:F0:56:73:9F:63:A5:77:E5:
  • BE:57:7D:9C:60:0A:F8:F9:4D:5D:26:5C:25:5D:C7:84
  • Timestamp : Jan 12 16:56:26.904 2022 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:E1:3E:3A:EC:C5:0B:E8:16:15:B2:B9:
  • 92:F4:B0:87:90:98:01:65:B4:10:3B:1B:F8:9A:E1:0A:
  • 7D:2E:09:CC:35:02:20:46:F6:66:15:4E:45:AD:6A:C8:
  • 97:80:CB:E1:C7:FE:D3:19:DA:44:D3:03:58:57:A6:D4:
  • 61:BC:B2:2B:EA:75:33