SSL-Tools

SSL check results of zeimke.cloud

NEW You can also bulk check multiple servers.

Discover if the mail servers for zeimke.cloud 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 Wed, 11 Dec 2024 01:32:18 +0000

The mailservers of zeimke.cloud can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @zeimke.cloud addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
my.zeimke.cloud
2a01:4f8:171:15de::2
 10
supported
*.zeimke.cloud
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
3 s
my.zeimke.cloud
136.243.147.115
 10
supported
*.zeimke.cloud
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=*.zeimke.cloud

Certificate chain
  • *.zeimke.cloud
    • remaining
    • 256 bit
    • ecdsa-with-SHA384
      • E6
        • remaining
        • 384 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • *.zeimke.cloud
Alternative Names
  • *.zeimke.cloud
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • E6
validity period
Not valid before
2024-12-06
Not valid after
2025-03-06
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
51:2C:0D:72:4E:82:8E:AA:0F:1F:01:E3:69:C5:BE:A6:FF:47:74:90:0A:0C:FE:53:23:3B:7D:0E:D4:60:5C:35
SHA1
B1:84:E1:21:97:A2:B2:84:06:D1:99:A4:6C:55:01:F0:A1:AE:BD:AA
X509v3 extensions
subjectKeyIdentifier
  • F3:BF:62:A1:1C:12:22:45:7C:BD:E0:F8:FC:E9:E9:ED:B6:22:73:AF
authorityKeyIdentifier
  • keyid:93:27:46:98:03:A9:51:68:8E:98:D6:C4:42:48:DB:23:BF:58:94:D2
authorityInfoAccess
  • OCSP - URI:http://e6.o.lencr.org
  • CA Issuers - URI:http://e6.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A2:E3:0A:E4:45:EF:BD:AD:9B:7E:38:ED:47:67:77:53:
  • D7:82:5B:84:94:D7:2B:5E:1B:2C:C4:B9:50:A4:47:E7
  • Timestamp : Dec 6 17:04:21.183 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:F0:7F:B2:66:48:1B:F9:73:0A:0D:02:
  • F9:76:F2:EE:BD:AB:13:E1:CF:B9:75:40:32:DF:1B:ED:
  • 22:9A:EF:22:80:02:21:00:95:EA:BF:5C:75:FE:39:66:
  • D8:42:66:D1:C7:69:D4:02:1E:9E:BB:01:53:9A:88:A0:
  • 21:B2:24:DD:CD:59:A0:32
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CC:FB:0F:6A:85:71:09:65:FE:95:9B:53:CE:E9:B2:7C:
  • 22:E9:85:5C:0D:97:8D:B6:A9:7E:54:C0:FE:4C:0D:B0
  • Timestamp : Dec 6 17:04:21.199 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:4D:C2:B4:46:28:71:A4:1F:F1:12:0B:F4:
  • 68:09:14:F7:1A:61:22:3A:A0:4B:3B:9B:F0:66:13:B3:
  • CA:25:11:EC:02:21:00:D1:C6:5B:C2:3B:A3:86:F0:64:
  • 09:C0:82:E5:75:C6:21:56:73:31:78:CC:6D:42:E2:AE:
  • 27:8C:BD:FE:97:ED:7E