SSL-Tools

SSL check results of charlie.jbtec.eu

NEW You can also bulk check multiple servers.

Discover if the mail servers for charlie.jbtec.eu 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 Mon, 22 Apr 2024 21:49:38 +0000

The mailservers of charlie.jbtec.eu can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @charlie.jbtec.eu addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
charlie.jbtec.eu
46.38.233.152
 -
supported
charlie.jbtec.eu
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
1 s
charlie.jbtec.eu
2a03:4000:2:87c:ab:ccc:47df:22ee
 -
supported
charlie.jbtec.eu
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
1 s

Outgoing Mails

We have not received any emails from a @charlie.jbtec.eu address so far. Test mail delivery

Certificates

First seen at:

CN=charlie.jbtec.eu

Certificate chain
  • charlie.jbtec.eu
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • charlie.jbtec.eu
Alternative Names
  • charlie.jbtec.eu
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-25
Not valid after
2024-06-23
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
6E:91:E3:BC:27:40:3C:C2:CB:98:41:A7:E6:96:17:27:EB:3A:FA:4B:7C:CA:CA:12:22:A1:25:0A:FA:97:C8:A5
SHA1
5D:54:84:23:47:FE:6C:96:9A:F5:7E:0E:1D:F4:6C:F2:53:E7:01:85
X509v3 extensions
subjectKeyIdentifier
  • 67:B2:A4:42:44:0F:72:C5:93:5C:04:6E:39:33:B5:55:7E:30:DC:89
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 : 3B:53:77:75:3E:2D:B9:80:4E:8B:30:5B:06:FE:40:3B:
  • 67:D8:4F:C3:F4:C7:BD:00:0D:2D:72:6F:E1:FA:D4:17
  • Timestamp : Mar 25 01:08:37.956 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:4E:79:4D:BF:74:46:5E:8A:87:D1:A4:5D:
  • 79:8B:8A:C0:2A:0C:3D:A9:4E:C3:E6:E8:D2:D0:09:31:
  • AF:56:0B:32:02:21:00:A9:49:FC:13:06:35:63:91:5F:
  • C2:AB:B1:AC:3B:18:CF:F3:7A:25:28:B6:CC:CF:52:CC:
  • 92:1B:4B:23:7C:55:D9
  • 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 25 01:08:40.020 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:4C:62:13:45:0E:8D:5D:75:5F:4F:1B:90:
  • 45:D8:A4:7B:46:9C:B7:25:F5:2F:4A:63:33:75:39:15:
  • E5:B7:6C:5C:02:20:4F:6E:36:7D:8B:F2:30:B0:50:B9:
  • 9C:06:EE:FD:7C:80:D4:66:5D:D4:F0:88:52:C5:5A:11:
  • 2E:84:28:6C:BC:AA