SSL-Tools

SSL check results of plitc.eu

NEW You can also bulk check multiple servers.

Discover if the mail servers for plitc.eu 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, 30 May 2023 13:03:18 +0000

The mailservers of plitc.eu can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @plitc.eu addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.plitc.eu
2a01:4f8:d0:7803::d17
 10
supported
mail.plitc.eu
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
4 s
mail.plitc.eu
49.12.161.66
 10
supported
mail.plitc.eu
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 @plitc.eu address so far. Test mail delivery

Certificates

First seen at:

CN=mail.plitc.eu

Certificate chain
  • mail.plitc.eu
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.plitc.eu
Alternative Names
  • mail.plitc.eu
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2023-05-30
Not valid after
2023-08-28
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
67:AB:18:E5:40:90:01:96:7C:F9:86:B3:3E:14:83:0E:20:C8:B9:67:90:C1:F0:96:DF:98:97:B4:90:A3:11:ED
SHA1
4C:01:F5:28:CE:A1:29:E2:0B:26:D0:A6:7F:F4:9B:47:BC:B5:FD:25
X509v3 extensions
subjectKeyIdentifier
  • 82:F4:18:3D:77:46:13:DD:E8:D5:02:7D:A7:D4:01:8C:8B:3A:6A:10
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 : B7:3E:FB:24:DF:9C:4D:BA:75:F2:39:C5:BA:58:F4:6C:
  • 5D:FC:42:CF:7A:9F:35:C4:9E:1D:09:81:25:ED:B4:99
  • Timestamp : May 30 12:51:26.785 2023 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:3D:25:0F:F4:D3:14:D0:65:A4:8F:3E:A4:
  • 07:37:58:AC:18:D1:8D:60:9A:A5:A2:CA:C9:BF:B8:02:
  • 91:B7:1F:A8:02:21:00:B7:52:CA:0B:42:23:E7:B8:4F:
  • 4E:2D:0C:C2:6C:44:9E:5E:25:86:20:FB:8D:E0:65:76:
  • C2:38:9F:F1:ED:EB:D1
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : E8:3E:D0:DA:3E:F5:06:35:32:E7:57:28:BC:89:6B:C9:
  • 03:D3:CB:D1:11:6B:EC:EB:69:E1:77:7D:6D:06:BD:6E
  • Timestamp : May 30 12:51:26.776 2023 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:93:11:C0:7B:5B:C0:A8:CD:59:39:F3:
  • 24:7A:3E:FC:7A:57:F8:79:41:01:03:1C:B1:AA:BF:E1:
  • EF:A6:79:3C:5A:02:21:00:D5:03:7D:D0:9C:A9:95:05:
  • D5:21:43:D0:34:87:8F:CC:51:D6:AA:08:5F:67:CF:5B:
  • 20:91:FE:F5:B1:27:67:D7