SSL-Tools

SSL check results of hackerspacenijmegen.nl

NEW You can also bulk check multiple servers.

Discover if the mail servers for hackerspacenijmegen.nl 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, 10 Mar 2026 11:29:21 +0000

The mailservers of hackerspacenijmegen.nl can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @hackerspacenijmegen.nl addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
altair.hackerspacenijmegen.nl
2a0c:8900:2:19ec::1
 10
supported
*.hackerspacenijmegen.nl
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
6 s
altair.hackerspacenijmegen.nl
45.86.125.21
 10
supported
*.hackerspacenijmegen.nl
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 @hackerspacenijmegen.nl address so far. Test mail delivery

Certificates

First seen at:

CN=*.hackerspacenijmegen.nl

Certificate chain
  • *.hackerspacenijmegen.nl
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R12
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • *.hackerspacenijmegen.nl
Alternative Names
  • *.hackerspacenijmegen.nl
  • hackerspacenijmegen.nl
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R12
validity period
Not valid before
2026-03-08
Not valid after
2026-06-06
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
Fingerprints
SHA256
C6:F6:48:C6:45:F4:62:D0:D0:BF:C9:A4:EE:BB:EF:D5:3C:BD:EB:DC:2D:56:95:02:D9:29:46:C9:1B:A0:37:F0
SHA1
D2:E9:2C:1F:16:0C:9D:D8:E0:39:1D:14:69:6B:7A:CE:CF:F6:23:29
X509v3 extensions
subjectKeyIdentifier
  • 47:8E:DF:A7:B8:AE:FD:0E:C9:7B:0C:45:5F:34:41:1E:D7:86:9A:4A
authorityKeyIdentifier
  • keyid:00:B5:29:F2:2D:8E:6F:31:E8:9B:4C:AD:78:3E:FA:DC:E9:0C:D1:D2
authorityInfoAccess
  • CA Issuers - URI:http://r12.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r12.c.lencr.org/74.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 64:11:C4:6C:A4:12:EC:A7:89:1C:A2:02:2E:00:BC:AB:
  • 4F:28:07:D4:1E:35:27:AB:EA:FE:D5:03:C9:7D:CD:F0
  • Timestamp : Mar 8 18:42:57.014 2026 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:BE:67:AA:98:77:F5:04:BF:CC:1E:51:
  • CA:33:3F:C3:FD:FF:4A:8E:A6:1C:23:CB:DA:F3:93:C8:
  • 3F:00:2B:AB:0E:02:21:00:95:3A:EF:BC:38:E9:19:7A:
  • E2:82:6B:B9:2E:1D:E2:B6:2E:5A:1B:ED:D5:80:4B:72:
  • 41:FA:ED:52:BF:5B:F3:24
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 96:97:64:BF:55:58:97:AD:F7:43:87:68:37:08:42:77:
  • E9:F0:3A:D5:F6:A4:F3:36:6E:46:A4:3F:0F:CA:A9:C6
  • Timestamp : Mar 8 18:42:57.092 2026 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:7D:D2:3C:2B:AB:2B:79:00:B3:25:8F:B5:
  • C7:96:7B:71:5D:03:85:8B:6B:D8:94:20:0C:D2:BF:4B:
  • B3:18:65:5F:02:21:00:BB:6A:E1:BB:0D:24:BA:0A:6C:
  • 62:26:6C:94:AE:20:4B:3A:92:C2:2D:3A:87:58:22:8F:
  • F8:F4:22:B9:33:A0:4A