SSL-Tools

SSL check results of plenet.org

NEW You can also bulk check multiple servers.

Discover if the mail servers for plenet.org 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 Tue, 23 Feb 2021 12:25:25 +0000

The mailservers of plenet.org can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @plenet.org addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.plenet.org
2a01:4f8:c2c:1e6::1
 50
supported
mail.plenet.org
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s
mail.plenet.org
116.203.20.26
 50
supported
mail.plenet.org
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.plenet.org

Certificate chain
  • mail.plenet.org
    • 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)
  • mail.plenet.org
Alternative Names
  • mail.plenet.org
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-02-03
Not valid after
2021-05-04
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
AA:9B:13:B4:3C:4F:C9:BC:19:75:36:05:31:74:41:C1:23:28:F6:1A:52:F9:C6:42:24:16:21:F6:27:D5:7C:8A
SHA1
11:7F:7B:5D:B0:AD:01:F7:58:0B:24:EE:64:AC:DD:5C:5A:96:B9:38
X509v3 extensions
subjectKeyIdentifier
  • 0B:19:C4:5C:59:7D:EB:42:45:EB:57:4F:CF:55:40:0B:C2:BD:5D:02
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 : 94:20:BC:1E:8E:D5:8D:6C:88:73:1F:82:8B:22:2C:0D:
  • D1:DA:4D:5E:6C:4F:94:3D:61:DB:4E:2F:58:4D:A2:C2
  • Timestamp : Feb 3 23:38:11.720 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:C4:8D:4C:88:25:AD:2F:6B:88:27:EF:
  • AA:2F:F1:3E:77:8B:18:56:3D:01:97:AF:63:FF:58:DE:
  • 3D:73:45:48:90:02:20:0D:0E:7E:D3:B3:DE:4D:A8:02:
  • E9:A0:32:38:64:7E:46:B0:B1:79:7C:A8:EE:B9:96:C7:
  • B8:5E:64:2A:24:B3:22
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 7D:3E:F2:F8:8F:FF:88:55:68:24:C2:C0:CA:9E:52:89:
  • 79:2B:C5:0E:78:09:7F:2E:6A:97:68:99:7E:22:F0:D7
  • Timestamp : Feb 3 23:38:11.764 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:84:AB:F3:08:72:25:A7:7D:D1:14:5A:
  • 7C:13:1F:D3:BD:33:45:CC:F3:55:29:89:F0:D6:C7:03:
  • A7:CA:6D:2B:C0:02:20:0D:4E:0F:13:87:1C:1B:BD:C7:
  • 3B:FC:FD:49:19:43:6E:7F:5C:5A:DF:E7:C7:7D:FA:9C:
  • F8:33:52:02:FB:66:A0