SSL-Tools

SSL check results of ziegler.pironex-portal.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for ziegler.pironex-portal.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 Fri, 19 Apr 2024 09:02:44 +0000

The mailservers of ziegler.pironex-portal.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @ziegler.pironex-portal.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
ziegler.pironex-portal.de
168.119.70.239
 20
supported
ziegler.pironex-portal.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 @ziegler.pironex-portal.de address so far. Test mail delivery

Certificates

First seen at:

CN=ziegler.pironex-portal.de

Certificate chain
  • ziegler.pironex-portal.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)
  • ziegler.pironex-portal.de
Alternative Names
  • ziegler.pironex-portal.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-04-15
Not valid after
2024-07-14
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
8F:9C:95:D0:87:9C:FA:51:8A:2E:B5:A3:C3:05:6B:F0:08:8B:A7:6B:6B:7B:06:57:27:49:07:76:27:2E:3D:BD
SHA1
34:FC:89:4F:13:8B:51:BB:81:5E:B5:E1:79:14:AD:1A:14:09:37:4C
X509v3 extensions
subjectKeyIdentifier
  • 1B:B2:EA:5D:A8:44:27:D4:AD:58:56:16:C3:6F:3F:AE:E6:A1:85:42
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
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 3B:53:77:75:3E:2D:B9:80:4E:8B:30:5B:06:FE:40:3B:
  • 67:D8:4F:C3:F4:C7:BD:00:0D:2D:72:6F:E1:FA:D4:17
  • Timestamp : Apr 15 14:30:04.761 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:DC:92:3A:A4:24:3C:09:4C:80:B4:FF:
  • CF:B2:2D:01:9B:50:4D:5C:92:D2:54:53:BD:8A:D1:48:
  • 87:20:77:EC:83:02:20:15:4D:48:51:23:FB:13:A8:12:
  • 15:72:2F:80:69:3E:0B:86:18:EE:4C:42:55:13:D2:20:
  • A0:4E:54:DE:63:88:10
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 76:FF:88:3F:0A:B6:FB:95:51:C2:61:CC:F5:87:BA:34:
  • B4:A4:CD:BB:29:DC:68:42:0A:9F:E6:67:4C:5A:3A:74
  • Timestamp : Apr 15 14:30:04.789 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:1D:99:D5:F7:22:61:37:90:91:95:87:8B:
  • 5B:26:9A:1C:51:A8:D0:7A:AA:A4:5D:E1:C9:C1:6D:38:
  • 47:DA:A7:66:02:21:00:D9:A4:2D:28:EE:F4:DC:A7:76:
  • E9:2E:E7:41:92:94:13:40:C1:4A:F4:92:E6:23:31:04:
  • 0C:CC:40:4A:71:81:AE