SSL-Tools

SSL check results of peaceforall.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for peaceforall.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, 25 May 2023 17:58:45 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
jworld.jehle-net.de
2a03:4000:2:d68::1
 10
supported
*.jehle-net.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
1 s
jworld.jehle-net.de
46.38.236.200
 10
supported
*.jehle-net.de
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 @peaceforall.de address so far. Test mail delivery

Certificates

First seen at:

CN=*.jehle-net.de

Certificate chain
  • *.jehle-net.de
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • *.jehle-net.de
Alternative Names
  • *.jehle-net.de
  • *.jeyarts.de
  • *.lerngeschehen.de
  • jehle-net.de
  • jeyarts.de
  • lerngeschehen.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2023-04-07
Not valid after
2023-07-06
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
A3:14:59:A8:2D:90:7F:28:00:46:88:91:43:50:DE:5E:13:AA:45:85:1A:3E:1E:5C:42:DD:C9:89:C3:CB:32:91
SHA1
A2:D2:0F:BE:55:9F:05:64:4A:E5:66:7B:C6:91:F3:06:2A:E2:58:F3
X509v3 extensions
subjectKeyIdentifier
  • 72:47:1B:FC:30:42:D0:B1:C7:DC:33:EC:DC:71:C9:A6:2B:74:16:00
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 : 7A:32:8C:54:D8:B7:2D:B6:20:EA:38:E0:52:1E:E9:84:
  • 16:70:32:13:85:4D:3B:D2:2B:C1:3A:57:A3:52:EB:52
  • Timestamp : Apr 7 23:04:27.396 2023 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:BE:88:FE:25:48:C2:62:AE:E4:BB:95:
  • DD:6B:2C:7E:43:69:84:D7:AC:B1:87:34:3D:64:3C:DB:
  • 40:BB:2E:62:53:02:21:00:D6:DC:56:16:8B:0D:47:93:
  • 90:57:44:57:52:77:80:0D:00:FC:5B:64:5F:DF:E7:BD:
  • 9D:11:3F:2D:0D:81:1B:E7
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : AD:F7:BE:FA:7C:FF:10:C8:8B:9D:3D:9C:1E:3E:18:6A:
  • B4:67:29:5D:CF:B1:0C:24:CA:85:86:34:EB:DC:82:8A
  • Timestamp : Apr 7 23:04:27.447 2023 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:96:3D:58:6C:26:7A:1D:F3:A8:1B:D4:
  • 9E:09:BB:20:3B:7F:B8:BF:47:6A:6C:11:3C:F9:E7:70:
  • 25:22:3F:99:36:02:21:00:E1:CB:20:21:13:0E:A6:03:
  • 8F:44:9E:B8:74:E4:F0:32:72:67:93:F1:8F:AA:09:C2:
  • FE:09:23:7E:6B:8A:72:94