SSL-Tools

SSL check results of haecksen.org

NEW You can also bulk check multiple servers.

Discover if the mail servers for haecksen.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 Wed, 02 Sep 2026 08:30:03 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
post.haecksen.org
2a01:4f8:242:5b9e::1
 0
supported
post.haecksen.org
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
post.haecksen.org
49.12.130.78
 0
supported
post.haecksen.org
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
5 s

Outgoing Mails

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

Certificates

First seen at:

CN=post.haecksen.org

Certificate chain
  • post.haecksen.org
    • 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)
  • post.haecksen.org
Alternative Names
  • post.haecksen.org
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • YE1
validity period
Not valid before
2026-07-15
Not valid after
2026-10-13
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
Fingerprints
SHA256
F6:2D:5F:D1:8D:FB:73:00:C0:6E:DC:0A:69:53:E9:CE:27:32:BC:85:C5:87:43:96:BC:AA:C8:3D:80:EC:74:B1
SHA1
89:7C:CD:05:88:3A:17:16:EB:9E:91:63:99:A7:02:88:64:B4:D8:1A
X509v3 extensions
subjectKeyIdentifier
  • B2:9C:B7:16:6E:7D:CA:AB:8F:EB:8D:EA:BA:70:76:53:03:99:18:08
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/97.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : AF:67:88:3B:57:B0:4E:DD:8F:A6:D9:7E:F6:2E:A8:EB:
  • 81:0A:C7:71:60:F0:24:5E:55:D6:0C:2F:E7:85:87:3A
  • Timestamp : Jul 15 12:33:08.409 2026 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:8F:B2:0E:28:BC:FA:90:AD:28:E5:24:
  • C1:4E:32:B6:F3:7B:DF:B5:E9:9F:66:A5:3C:2F:5F:10:
  • E8:5A:57:94:86:02:20:53:D3:25:EA:95:DC:92:C4:4F:
  • E9:AD:90:6C:C5:F0:A5:2D:71:1E:26:54:AD:08:9B:27:
  • 80:3C:16:F7:2A:21:82
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 1A:8B:9D:6B:0F:FE:BF:81:B4:79:39:C6:D2:31:0A:86:
  • D6:D1:02:D4:F0:46:E2:18:2C:9D:E3:5F:5E:26:25:EF
  • Timestamp : Jul 15 12:33:08.725 2026 GMT
  • Extensions: 00:00:05:00:29:EA:1F:77
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:81:40:56:1A:B3:F2:A8:2F:D0:78:3B:
  • 6B:F7:B1:54:E9:6D:AA:93:69:68:4B:5C:19:73:0E:7C:
  • 30:93:3D:E8:54:02:20:59:2E:07:D9:98:F8:14:49:BE:
  • 20:98:E7:5D:0D:98:BD:AA:01:51:6E:70:7F:90:7F:E9:
  • 90:B3:42:78:97:08:DB