SSL check results of jollausers.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for jollausers.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 Mon, 28 Dec 2020 15:09:02 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail3.privater-postbote.de
2a02:c207:3002:1233::1
10
supported
privater-postbote.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
12 s
mail3.privater-postbote.de
173.212.240.214
10
supported
privater-postbote.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
11 s

Outgoing Mails

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

Certificates

First seen at:

CN=privater-postbote.de

Certificate chain
  • privater-postbote.de
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption

      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

          • DST Root CA X3 (Certificate is self-signed.)
            • remaining
            • 2048 bit
            • sha1WithRSAEncryption

Subject
Common Name (CN)
  • privater-postbote.de
Alternative Names
  • *.privater-postbote.de
  • privater-postbote.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2020-12-27
Not valid after
2021-03-27
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
21:91:06:08:5B:04:26:6D:12:9D:B8:87:AF:2F:F7:29:B9:CF:BA:BC:0E:35:1F:7D:38:DD:BA:AD:30:37:68:72
SHA1
80:E9:68:CE:8E:A1:FC:C8:15:F2:4C:A2:C4:C8:76:FB:38:A3:DA:CF
X509v3 extensions
subjectKeyIdentifier
  • 73:99:A4:66:56:C7:E2:86:EA:67:38:0B:CF:DA:74:27:E6:A1:AD:2F
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 : Dec 27 20:03:30.805 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:6E:9A:72:FD:3C:C2:D6:CD:E1:86:01:28:
  • 70:7F:E0:A3:7A:B4:38:1D:57:49:A6:9B:95:8F:8A:75:
  • 1C:5E:69:FA:02:21:00:C2:B7:FD:DE:98:E3:C0:BF:68:
  • 93:A0:C3:F7:0D:02:E1:12:01:C2:E7:24:50:EE:A8:77:
  • 16:06:7A:E0:08:D6:97
  • 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 : Dec 27 20:03:30.804 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:67:54:EF:50:99:F8:6E:62:7A:93:05:C4:
  • 1C:8E:4D:AC:97:B4:A4:7F:EB:79:00:9A:F1:9A:5F:71:
  • 15:41:82:66:02:20:73:01:38:F9:D1:C0:19:4C:DB:27:
  • F1:FE:38:DB:A1:52:69:06:E4:F4:EA:EA:08:43:22:B5:
  • 54:E5:E8:8F:53:FD