SSL-Tools

SSL check results of mx.pickulsky.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for mx.pickulsky.com 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 Sun, 09 Aug 2026 00:30:46 +0000

The mailservers of mx.pickulsky.com can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @mx.pickulsky.com addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mx.pickulsky.com
51.15.34.111
 -
supported
*.pickulsky.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
3 s

Outgoing Mails

We have not received any emails from a @mx.pickulsky.com address so far. Test mail delivery

Certificates

First seen at:

CN=*.pickulsky.com

Certificate chain
  • *.pickulsky.com
    • remaining
    • 256 bit
    • ecdsa-with-SHA384
      • YE1
        • remaining
        • 384 bit
        • ecdsa-with-SHA384
          • Root YE
            • remaining
            • 384 bit
            • ecdsa-with-SHA384
              • ISRG Root X2 (Certificate is self-signed.)
                • remaining
                • 384 bit
                • ecdsa-with-SHA384
Subject
Common Name (CN)
  • *.pickulsky.com
Alternative Names
  • *.pickulsky.com
  • pickulsky.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • YE1
validity period
Not valid before
2026-06-30
Not valid after
2026-09-28
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
Fingerprints
SHA256
EE:93:3B:CC:98:20:60:C8:B9:3C:4D:89:AD:B4:48:D9:AA:22:7B:33:DA:0F:07:D1:B6:38:C8:B7:1E:89:D2:C3
SHA1
CA:34:35:B7:16:E4:BB:80:2E:AC:6E:BB:16:6B:51:1B:06:73:BA:90
X509v3 extensions
subjectKeyIdentifier
  • 09:E1:B3:BC:51:51:EE:8D:C4:24:85:2F:CD:BD:8B:02:11:D3:2C:2A
authorityKeyIdentifier
  • keyid:BB:20:CA:47:0B:FE:D7:E5:9C:F9:8F:09:2A:A3:8C:37:45:B1:BC:D8
authorityInfoAccess
  • CA Issuers - URI:http://ye1.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://ye1.c.lencr.org/87.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : D8:09:55:3B:94:4F:7A:FF:C8:16:19:6F:94:4F:85:AB:
  • B0:F8:FC:5E:87:55:26:0F:15:D1:2E:72:BB:45:4B:14
  • Timestamp : Jun 30 09:41:54.467 2026 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:79:F7:A2:C6:6D:4A:8B:95:8A:95:80:DD:
  • 87:25:F8:AA:86:FF:AA:88:CD:81:F6:22:9D:4B:6C:24:
  • BB:64:B3:87:02:21:00:8C:88:EB:76:69:11:92:61:B8:
  • 89:D9:08:86:6A:73:BC:34:53:9D:E9:C7:83:B9:BF:D0:
  • D9:53:2E:BB:20:66:A1
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 6C:FE:50:19:43:A8:5E:A9:16:BC:52:D1:33:E4:DC:C9:
  • 1E:F1:41:1C:7D:25:84:20:D1:73:80:9E:18:18:EB:3A
  • Timestamp : Jun 30 09:41:55.188 2026 GMT
  • Extensions: 00:00:05:00:12:C5:83:09
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:5D:68:B0:2C:AB:07:F9:BD:0E:8C:78:54:
  • 68:5D:CF:70:85:0A:9C:2B:AC:51:CE:80:7C:A4:1E:32:
  • F5:E0:E4:CC:02:21:00:E0:96:0C:B8:FB:F8:51:82:4C:
  • 3E:20:84:B1:A7:E7:C2:09:75:B3:B2:F6:A1:49:7F:67:
  • D5:40:4B:54:DA:1A:4A