SSL check results of vd-kraan.nl

NEW You can also bulk check multiple servers.

Discover if the mail servers for vd-kraan.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

Report created Wed, 17 Apr 2024 15:33:50 +0000

The mailservers of vd-kraan.nl can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @vd-kraan.nl addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.tuxserve.net
2a10:3781:db9:1::25:0
10
supported
*.tuxserve.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
center01.tuxserve.net
2a10:3781:db9:1::ff
20
supported
*.tuxserve.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
center01.tuxserve.net
45.138.229.28
20
supported
*.tuxserve.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s

Outgoing Mails

We have not received any emails from a @vd-kraan.nl address so far. Test mail delivery

Certificates

First seen at:

CN=*.tuxserve.net

Certificate chain
  • *.tuxserve.net
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption

      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption

Subject
Common Name (CN)
  • *.tuxserve.net
Alternative Names
  • *.tuxserve.net
  • tuxserve.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-04-05
Not valid after
2024-07-04
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
A3:6A:FB:BC:0D:59:09:05:2E:D1:10:A2:A4:1F:BF:2E:15:A8:0C:BB:55:E1:04:E9:02:18:7C:94:B9:15:25:33
SHA1
8D:0F:B1:AC:3C:B9:CD:92:7A:E1:3A:33:9C:C6:C4:A1:5D:3A:D3:D8
X509v3 extensions
subjectKeyIdentifier
  • 92:54:FB:FC:13:EF:75:0C:8E:21:1F:E7:67:99:06:A9:E2:51:3B:42
authorityKeyIdentifier
  • keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
authorityInfoAccess
  • OCSP - URI:http://r3.o.lencr.org
  • CA Issuers - URI:http://r3.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • 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 : Apr 6 00:37:47.994 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:6F:03:19:EC:BC:61:B8:7B:89:0D:1F:3A:
  • EA:FF:83:0B:7F:CD:00:DE:45:2F:CF:CB:B2:4C:3F:C3:
  • C8:21:60:70:02:21:00:D6:50:85:C8:19:49:31:1C:E0:
  • 0F:C9:0E:95:6E:94:CD:53:37:4B:EB:B5:D2:A2:FF:DF:
  • 57:DA:92:07:52:B2:64
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 19:98:10:71:09:F0:D6:52:2E:30:80:D2:9E:3F:64:BB:
  • 83:6E:28:CC:F9:0F:52:8E:EE:DF:CE:4A:3F:16:B4:CA
  • Timestamp : Apr 6 00:37:48.120 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:C3:D4:9C:CE:72:B7:87:9C:E5:23:1E:
  • 0F:69:82:3F:1D:46:BA:C7:94:2A:FF:7B:71:E3:A9:C4:
  • 5F:D9:4B:2F:64:02:21:00:BB:7A:3D:78:EA:05:C3:5C:
  • C7:E5:C1:7D:B7:3F:73:94:0B:13:0C:16:FF:59:BB:0A:
  • 6A:BA:AD:3E:18:71:C1:D8