SSL-Tools

SSL check results of jdahm.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for jdahm.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, 28 Mar 2024 11:17:15 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mailserver.jdahm.de
2a01:4f8:172:14e2::2
 10
supported
mailserver.enits.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
6 s
mailserver.jdahm.de
94.130.114.49
 10
supported
mailserver.enits.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
5 s

Outgoing Mails

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

Certificates

First seen at:

CN=mailserver.enits.de

Certificate chain
  • mailserver.enits.de
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mailserver.enits.de
Alternative Names
  • autodiscover.innovationszeug.de
  • autodiscover.jdahm.de
  • mailserver.enits.de
  • mailserver.innovationszeug.de
  • mailserver.jdahm.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-13
Not valid after
2024-06-11
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
F3:BE:DE:7F:B6:C3:B3:2B:5F:4F:44:26:AB:53:BE:09:A6:EB:C9:17:A2:56:99:E9:16:95:CA:3E:6B:36:DC:D6
SHA1
D5:12:49:BA:03:05:E7:6B:6C:25:4E:A9:EF:7E:C0:73:5E:80:7F:8A
X509v3 extensions
subjectKeyIdentifier
  • 3D:FD:03:FD:2C:97:CC:D2:EA:AD:FA:FD:7B:7A:72:24:57:2B:D4:AC
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 : 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 13 04:12:11.904 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:F3:77:81:9F:E7:67:53:BD:FC:A8:DE:
  • 4C:50:30:9D:D8:94:6F:BE:C7:65:7B:44:2A:15:AF:6D:
  • 62:3E:E8:9B:EA:02:21:00:BD:DC:58:95:20:9F:6F:53:
  • 3F:90:20:3E:50:45:9F:55:A7:45:B3:FA:14:0D:05:8D:
  • FC:9A:8D:1C:45:3C:CF:AE
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A2:E2:BF:D6:1E:DE:2F:2F:07:A0:D6:4E:6D:37:A7:DC:
  • 65:43:B0:C6:B5:2E:A2:DA:B7:8A:F8:9A:6D:F5:17:D8
  • Timestamp : Mar 13 04:12:11.900 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:05:07:58:92:3A:22:9F:0E:2E:EE:11:FE:
  • BA:EA:0F:51:74:CA:05:A0:86:05:CB:F4:8E:43:2E:5D:
  • 71:99:56:0F:02:21:00:96:F1:5F:86:D4:1B:C3:96:E0:
  • 19:0B:05:38:1D:37:CF:A0:DA:C0:FB:87:66:53:CC:F8:
  • F7:C3:E7:7B:FB:0D:64