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, 22 Oct 2024 15:49:14 +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
3 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
3 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
2024-09-23
Not valid after
2024-12-22
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
53:BE:7A:D6:6F:20:FD:18:FD:08:FB:96:12:C2:53:3E:BC:34:12:60:92:7E:BA:9B:10:51:74:DA:EA:02:B8:FD
SHA1
ED:A6:96:66:B9:67:80:AC:81:8C:E2:14:2B:02:15:72:04:0E:DA:50
X509v3 extensions
subjectKeyIdentifier
  • 45:3F:E7:89:84:D3:89:EC:C5:0A:14:E8:6E:0E:AE:29:E7:FD:42:CF
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 : 48:B0:E3:6B:DA:A6:47:34:0F:E5:6A:02:FA:9D:30:EB:
  • 1C:52:01:CB:56:DD:2C:81:D9:BB:BF:AB:39:D8:84:73
  • Timestamp : Sep 23 04:18:04.845 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:1A:51:A4:3A:23:A5:7C:4C:55:00:59:53:
  • 14:8A:FA:3A:F2:71:99:AE:55:4A:62:04:95:0B:3F:37:
  • 60:E7:3C:A6:02:20:6E:3C:06:3C:BE:72:C8:AF:4C:B8:
  • 73:EC:E1:74:27:5B:90:BD:B7:78:8D:64:52:EE:AF:6F:
  • E9:02:26:4E:D3:7C
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : EE:CD:D0:64:D5:DB:1A:CE:C5:5C:B7:9D:B4:CD:13:A2:
  • 32:87:46:7C:BC:EC:DE:C3:51:48:59:46:71:1F:B5:9B
  • Timestamp : Sep 23 04:18:04.843 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:15:5C:B0:98:82:96:92:1F:92:6B:73:FD:
  • 47:E8:52:89:E1:37:09:49:32:1D:60:D8:5E:62:43:89:
  • 31:7F:4E:13:02:21:00:FE:A5:66:00:EF:D5:EF:F4:9B:
  • 57:C1:21:8A:31:F2:52:51:B2:3C:2C:F3:71:AC:54:55:
  • 7B:0E:FE:69:2A:94:88