SSL-Tools

SSL check results of vkmedv.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for vkmedv.de 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 Wed, 19 Jun 2024 12:07:24 +0000

The mailservers of vkmedv.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @vkmedv.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.vkmedv.de
185.170.114.32
 10
supported
mail.vkmedv.de
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 @vkmedv.de address so far. Test mail delivery

Certificates

First seen at:

CN=mail.vkmedv.de

Certificate chain
  • mail.vkmedv.de
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.vkmedv.de
Alternative Names
  • mail.vkmedv.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-05-16
Not valid after
2024-08-14
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
74:B0:9C:1E:C4:2D:D1:D2:2A:CE:7D:11:00:36:50:67:14:24:75:BD:C9:0D:BB:BB:E6:33:07:00:CC:CA:F5:73
SHA1
55:6A:3C:D8:4D:E4:30:26:4B:6E:67:A0:6C:0A:CF:13:18:D7:67:BE
X509v3 extensions
subjectKeyIdentifier
  • 5A:2D:9A:21:C8:25:73:E1:96:1F:A6:2C:D3:CA:11:35:07:FA:31:A9
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 : 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 : May 16 08:16:17.671 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:3A:97:B9:EC:02:7F:19:8A:80:3D:61:FF:
  • DA:85:31:3A:51:2F:26:29:67:D0:51:7A:D8:86:AC:50:
  • 78:A7:C8:D8:02:20:00:BC:57:AB:15:4E:26:48:45:D8:
  • AA:51:75:D1:DD:01:BF:A0:EB:35:4A:E4:C4:87:19:3B:
  • CC:8E:C9:99:2C:C3
  • 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 : May 16 08:16:17.867 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:2F:43:50:98:BF:9B:3A:8E:78:24:99:61:
  • B8:FC:27:44:53:88:27:BB:53:1E:72:96:3C:3D:2E:66:
  • E6:C4:4C:71:02:21:00:FA:03:72:DB:64:FE:32:76:DE:
  • 41:2E:A3:48:17:2E:A0:EE:C6:3A:EE:10:E7:90:5A:A3:
  • D3:4D:95:E6:7A:01:66