SSL-Tools

SSL check results of kiwuweb.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for kiwuweb.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 20:21:52 +0000

We can not guarantee a secure connection to the mailservers of kiwuweb.de!

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

/mailservers/kiwuweb.de

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.kiwuweb.de
2001:8d8:1800:114:100::5
Results incomplete
10 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 s
mail.kiwuweb.de
212.227.203.59
 10
supported
admin.siam-net.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
17 s

Outgoing Mails

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

Certificates

First seen at:

CN=admin.siam-net.de

Certificate chain
  • admin.siam-net.de
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
    • Hostname Mismatch
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • admin.siam-net.de
Alternative Names
  • admin.siam-net.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-16
Not valid after
2024-06-14
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
42:E5:DE:75:EB:20:00:62:CB:8B:2E:5C:2D:4F:00:D4:D6:90:D8:C6:39:39:3C:E9:BE:A5:75:0D:FD:D0:BB:99
SHA1
42:1F:8F:00:D3:3C:B3:AB:42:78:3D:FE:32:2A:C9:2C:A7:7F:B8:95
X509v3 extensions
subjectKeyIdentifier
  • 11:BD:53:24:DA:31:E2:DA:C4:04:7D:A9:27:1C:C8:A1:51:CC:96:D9
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 : 48:B0:E3:6B:DA:A6:47:34:0F:E5:6A:02:FA:9D:30:EB:
  • 1C:52:01:CB:56:DD:2C:81:D9:BB:BF:AB:39:D8:84:73
  • Timestamp : Mar 16 23:03:42.837 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:E4:2A:34:E6:9F:03:A4:66:0A:E7:7A:
  • 7E:25:A3:11:C8:95:9B:2A:C7:51:C3:7F:E5:67:1F:1D:
  • EF:CA:B7:40:23:02:21:00:B7:49:E2:BB:B9:D5:3B:9C:
  • 8B:FD:A5:3E:D8:6C:6B:AE:9A:19:77:9F:E1:BB:85:C4:
  • 2A:BB:12:F8:E7:28:4F:09
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 76:FF:88:3F:0A:B6:FB:95:51:C2:61:CC:F5:87:BA:34:
  • B4:A4:CD:BB:29:DC:68:42:0A:9F:E6:67:4C:5A:3A:74
  • Timestamp : Mar 16 23:03:43.415 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:D1:0D:18:B0:3C:55:A6:C6:5F:CA:8F:
  • 1E:96:2C:54:C1:12:6F:88:54:C0:7C:63:E1:8A:17:DC:
  • A3:8E:8B:26:84:02:21:00:AE:8F:76:30:12:7E:06:68:
  • 1C:4B:2D:28:B8:2C:DE:45:3A:24:02:C0:38:CE:AC:66:
  • CA:79:52:50:08:38:05:16