SSL check results of jeffmail.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for jeffmail.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

Report created Sun, 30 May 2021 08:37:02 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.jeffmail.de
2a03:4000:21:80d::1
10
supported
jeffmail.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
8 s
mail.jeffmail.de
94.16.122.210
10
supported
jeffmail.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
7 s

Outgoing Mails

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

Certificates

First seen at:

CN=jeffmail.de

Certificate chain
  • jeffmail.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)
  • jeffmail.de
Alternative Names
  • imap.jeffmail.de
  • jeffmail.de
  • mail.jeffmail.de
  • smtp.jeffmail.de
  • web.jeffmail.de
  • webmail.jeffmail.de
  • www.jeffmail.de
  • www.mail.jeffmail.de
  • www.web.jeffmail.de
  • www.webmail.jeffmail.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-04-18
Not valid after
2021-07-17
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
0B:1B:D0:8E:DC:03:8D:D0:82:1D:11:29:73:FC:AB:D2:FB:1A:EA:9C:90:0A:77:18:8D:E0:12:53:B2:D1:0E:61
SHA1
2E:5C:98:DE:77:09:56:FB:A7:00:1B:9E:0A:78:36:4A:61:42:52:F1
X509v3 extensions
subjectKeyIdentifier
  • D4:3E:E0:56:EF:63:67:66:76:A9:BA:8E:A1:44:5D:43:94:FD:6D:B4
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 : 5C:DC:43:92:FE:E6:AB:45:44:B1:5E:9A:D4:56:E6:10:
  • 37:FB:D5:FA:47:DC:A1:73:94:B2:5E:E6:F6:C7:0E:CA
  • Timestamp : Apr 18 05:02:51.047 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:43:D0:0A:75:89:AB:B3:3D:5C:A9:CC:DE:
  • D8:E7:9C:65:FE:92:DF:54:EC:7E:A6:2B:69:A9:DF:9A:
  • 0C:E5:2D:46:02:21:00:C9:8D:B3:24:AE:0D:5D:B7:B9:
  • ED:BB:FE:1B:1A:8C:39:09:F7:11:2C:EC:4A:B5:7B:32:
  • 37:5A:64:AE:07:8D:33
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : F6:5C:94:2F:D1:77:30:22:14:54:18:08:30:94:56:8E:
  • E3:4D:13:19:33:BF:DF:0C:2F:20:0B:CC:4E:F1:64:E3
  • Timestamp : Apr 18 05:02:51.083 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:70:67:74:5A:7B:AA:12:10:E8:22:51:8D:
  • 1F:4B:A3:63:DD:C2:11:B7:D4:59:18:BF:13:6A:A4:F8:
  • 96:27:6F:6B:02:21:00:A2:86:79:8B:84:B7:0F:BB:06:
  • A9:34:F8:05:44:A0:39:92:BA:68:11:38:D2:54:23:D2:
  • 4F:F0:4C:8B:C7:B8:54