SSL-Tools

SSL check results of jabbicloud.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for jabbicloud.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 Feb 2021 16:21:58 +0000

The mailservers of jabbicloud.de can be reached through a secure connection.

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.jabbicloud.de
78.94.245.161
 2
supported
jabbicloud.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
6 s

Outgoing Mails

We have received emails from these servers with @jabbicloud.de sender addresses. Test mail delivery

Host TLS Version & Cipher
mail.jabbicloud.de (78.94.245.161)
TLSv1.3 TLS_AES_256_GCM_SHA384

Certificates

First seen at:

CN=jabbicloud.de

Certificate chain
  • jabbicloud.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)
  • jabbicloud.de
Alternative Names
  • jabbicloud.de
  • lewis-im-stadtpark.de
  • ludis-esport.de
  • mail.jabbicloud.de
  • vpn.jabbicloud.de
  • wrapitup-krefeld.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-01-31
Not valid after
2021-05-01
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
74:CD:99:23:57:05:99:57:C9:FB:13:46:70:73:27:CB:E6:DE:64:F9:F1:8A:32:FF:3E:52:C0:2E:F5:60:36:1F
SHA1
46:37:1A:3F:40:C7:BC:23:9D:4A:FB:9D:A2:3C:3F:41:B8:51:61:6D
X509v3 extensions
subjectKeyIdentifier
  • 62:9A:78:80:47:09:EF:E2:10:CE:4C:23:D2:44:D3:35:83:20:32:EE
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 : Jan 31 23:04:44.795 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:9C:53:8C:D7:A4:05:86:60:11:9D:48:
  • CD:69:29:5B:83:7D:C4:9A:39:37:8C:3E:5B:10:D5:5C:
  • C8:52:FD:7F:5E:02:21:00:D4:64:72:7E:E2:FA:AA:72:
  • BD:63:E4:7E:79:97:9E:28:E8:98:7B:F9:96:8F:D3:67:
  • BB:D6:C7:08:8A:19:E7:1D
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 7D:3E:F2:F8:8F:FF:88:55:68:24:C2:C0:CA:9E:52:89:
  • 79:2B:C5:0E:78:09:7F:2E:6A:97:68:99:7E:22:F0:D7
  • Timestamp : Jan 31 23:04:44.871 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:C4:D7:5F:27:BA:55:83:83:2E:EC:48:
  • 81:C9:2B:40:DB:42:31:06:5A:A8:23:91:E2:98:D7:84:
  • 67:FE:C5:7F:7B:02:21:00:9C:94:B0:55:95:04:74:21:
  • D6:5F:BE:DC:F2:65:36:4A:B9:3F:D4:2B:90:9D:9F:F9:
  • 7A:81:D9:F3:38:6E:CD:17