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, 11 Feb 2025 20:42:47 +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:1::4f7d:24d0
 10
supported
*.hackerspacenijmegen.nl
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
8 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
4 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
      • R10
        • 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)
  • R10
validity period
Not valid before
2025-01-21
Not valid after
2025-04-21
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
78:C6:A7:CD:91:9F:57:D9:CC:C0:69:F8:A8:74:37:A2:9D:1B:D6:0E:AA:6C:7C:92:00:D1:E9:A9:90:53:8E:D9
SHA1
E7:88:63:1D:D8:6E:05:75:D6:4B:11:61:B2:9F:97:05:F1:04:81:55
X509v3 extensions
subjectKeyIdentifier
  • 28:67:7F:3F:18:3A:B3:D4:9E:C5:EB:C1:03:32:1C:8F:D2:5D:4C:43
authorityKeyIdentifier
  • keyid:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
authorityInfoAccess
  • OCSP - URI:http://r10.o.lencr.org
  • CA Issuers - URI:http://r10.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : DE:85:81:D7:50:24:7C:6B:CD:CB:AF:56:37:C5:E7:81:
  • C6:4C:E4:6E:D6:17:63:9F:8F:34:A7:26:C9:E2:BD:37
  • Timestamp : Jan 21 20:41:52.557 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:B1:32:0A:74:3B:C3:B2:DC:4F:1A:81:
  • 35:8C:45:74:EC:31:5E:23:E7:DB:A6:53:D5:0F:7F:4D:
  • B3:33:D0:00:62:02:20:09:39:97:71:19:73:A7:01:B6:
  • 90:3D:68:E6:9C:B4:82:FC:47:55:86:8F:F4:A9:3C:A7:
  • 41:E1:F5:98:0E:D4:F8
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 4E:75:A3:27:5C:9A:10:C3:38:5B:6C:D4:DF:3F:52:EB:
  • 1D:F0:E0:8E:1B:8D:69:C0:B1:FA:64:B1:62:9A:39:DF
  • Timestamp : Jan 21 20:41:52.558 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:5E:D3:8D:C2:1F:47:EE:FD:0D:F5:AA:9C:
  • 41:D0:BD:D2:F7:19:87:89:20:3D:5C:00:1F:F7:65:3D:
  • 2B:B5:39:2E:02:20:59:D6:2E:E9:DF:C2:A3:2E:89:0F:
  • 93:69:FB:80:4C:A1:C4:6F:65:99:54:F7:FD:69:28:BB:
  • 88:B2:19:B1:C0:04