SSL-Tools

SSL check results of koppenol.net

NEW You can also bulk check multiple servers.

Discover if the mail servers for koppenol.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 Tue, 21 Jan 2025 21:03:07 +0000

The mailservers of koppenol.net can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @koppenol.net addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.visfabriek.com
2a01:4f8:210:1243::2
 41
supported
mail.visfabriek.com
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
5 s
mail.visfabriek.com
148.251.122.103
 41
supported
mail.visfabriek.com
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
5 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.visfabriek.com

Certificate chain
  • mail.visfabriek.com
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.visfabriek.com
Alternative Names
  • autoconfig.koppenol.net
  • autodiscover.koppenol.net
  • mail.koppenol.net
  • mail.visfabriek.com
  • webmail.koppenol.net
  • webmail.visfabriek.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2025-01-04
Not valid after
2025-04-04
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
11:1E:7F:00:EE:6C:24:39:53:A1:C7:09:C9:50:93:26:9E:E8:F7:08:74:2E:15:67:37:DE:D4:93:CB:35:84:81
SHA1
3E:7E:C9:8A:BA:A1:20:C8:A5:87:3C:4B:F9:DC:E7:91:21:08:DC:C9
X509v3 extensions
subjectKeyIdentifier
  • B8:37:2F:6E:EB:82:75:00:E2:FE:18:B4:20:7B:AA:B4:28:73:B0:8E
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • OCSP - URI:http://r11.o.lencr.org
  • CA Issuers - URI:http://r11.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A2:E3:0A:E4:45:EF:BD:AD:9B:7E:38:ED:47:67:77:53:
  • D7:82:5B:84:94:D7:2B:5E:1B:2C:C4:B9:50:A4:47:E7
  • Timestamp : Jan 4 21:56:33.280 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:E0:93:54:8C:4C:42:DA:63:6C:5E:8A:
  • FE:D1:E8:68:7F:03:03:6E:5B:DC:60:B6:B4:A1:82:B6:
  • 9D:18:F4:36:74:02:21:00:D0:D5:9C:01:23:E0:8B:05:
  • AB:79:44:3D:A5:38:7E:39:D3:34:39:6D:AF:11:BA:B8:
  • 1C:DF:23:29:09:AA:13:3A
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CC:FB:0F:6A:85:71:09:65:FE:95:9B:53:CE:E9:B2:7C:
  • 22:E9:85:5C:0D:97:8D:B6:A9:7E:54:C0:FE:4C:0D:B0
  • Timestamp : Jan 4 21:56:33.545 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:94:82:EE:17:16:1A:47:17:3F:E8:B7:
  • 99:AB:0A:70:77:FE:9B:2D:59:8D:B7:06:BB:24:35:CA:
  • 22:54:84:F9:A6:02:21:00:EF:9C:6B:C4:D4:05:44:22:
  • 10:52:3E:B6:B0:77:C5:9E:42:F9:36:89:02:3E:CC:18:
  • 2E:60:73:53:C8:93:62:F3

DANE

DNS-based Authentication of Named Entities (DANE) is a protocol to allow X.509 certificates to be bound to DNS using TLSA records and DNSSEC.

Name Options DNSSEC Matches
_25._tcp.mail.visfabriek.com
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
error
Debug
valid