SSL-Tools

SSL check results of van-ginkel.net

NEW You can also bulk check multiple servers.

Discover if the mail servers for van-ginkel.net 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, 29 Jun 2025 07:17:39 +0000

The mailservers of van-ginkel.net can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @van-ginkel.net addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.van-ginkel.net
84.82.181.1
 10
supported
van-ginkel.net
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 @van-ginkel.net address so far. Test mail delivery

Certificates

First seen at:

CN=van-ginkel.net

Certificate chain
  • van-ginkel.net
    • remaining
    • 256 bit
    • ecdsa-with-SHA384
      • E6
        • remaining
        • 384 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • van-ginkel.net
Alternative Names
  • dzga.van-ginkel.net
  • ginkelware.nl
  • ginkelwear.nl
  • mail.van-ginkel.net
  • mmc.van-ginkel.net
  • nc.van-ginkel.net
  • ntfy.van-ginkel.net
  • stream.van-ginkel.net
  • van-ginkel.net
  • www.ginkelware.nl
  • www.ginkelwear.nl
  • www.van-ginkel.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • E6
validity period
Not valid before
2025-06-25
Not valid after
2025-09-23
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
E3:90:4C:48:35:54:FB:CE:E0:F1:74:F7:5F:09:EF:F3:BA:33:1E:75:00:53:19:2C:8D:AE:2B:EF:6B:68:0E:4F
SHA1
A8:BB:21:14:51:90:77:EC:72:80:22:26:68:F0:71:FB:03:28:A0:F7
X509v3 extensions
subjectKeyIdentifier
  • 5A:58:4F:D3:32:F1:A7:82:BB:55:30:69:C6:7B:36:5A:05:9D:D0:AA
authorityKeyIdentifier
  • keyid:93:27:46:98:03:A9:51:68:8E:98:D6:C4:42:48:DB:23:BF:58:94:D2
authorityInfoAccess
  • CA Issuers - URI:http://e6.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://e6.c.lencr.org/29.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 12:F1:4E:34:BD:53:72:4C:84:06:19:C3:8F:3F:7A:13:
  • F8:E7:B5:62:87:88:9C:6D:30:05:84:EB:E5:86:26:3A
  • Timestamp : Jun 25 21:47:51.006 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:F3:82:D7:1E:96:60:16:C8:1F:1E:39:
  • 2C:15:DE:4B:4E:88:83:B9:51:2A:5A:F0:8D:A3:86:70:
  • 5D:1B:DD:A2:56:02:21:00:89:F4:6C:10:48:AE:BB:99:
  • 5C:FF:F7:E1:47:D0:87:79:7F:39:42:50:05:6E:FF:96:
  • 3E:6C:B2:53:3C:AF:2D:23
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 1A:04:FF:49:D0:54:1D:40:AF:F6:A0:C3:BF:F1:D8:C4:
  • 67:2F:4E:EC:EE:23:40:68:98:6B:17:40:2E:DC:89:7D
  • Timestamp : Jun 25 21:47:51.128 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:AB:8A:41:AC:CB:9E:BC:D3:80:2E:38:
  • 31:9D:42:63:57:BE:B8:18:DD:98:6F:ED:CE:6F:02:BE:
  • 9E:85:52:0C:90:02:21:00:A1:A4:BE:7A:F8:51:60:1B:
  • 72:D0:2B:5E:BE:53:86:8C:86:5D:1E:92:73:6D:5D:96:
  • 1E:CA:32:DA:65:D0:25:72