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 Thu, 25 May 2023 08:11:34 +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
2023-05-22
Not valid after
2023-08-20
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
67:1C:4D:59:5C:34:57:17:9C:2C:63:FB:9D:0A:F9:7D:91:52:7B:97:E7:D9:89:0A:4E:BB:00:E7:72:D0:BE:B0
SHA1
7E:13:D9:D9:C4:74:DC:39:3B:BB:E2:85:62:48:90:E6:DF:8A:B2:4B
X509v3 extensions
subjectKeyIdentifier
  • 3B:F3:E6:0A:08:26:28:A2:A8:88:14:21:03:84:79:A6:A8:96:03:EB
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
  • Policy: 1.3.6.1.4.1.44947.1.1.1
  • CPS: http://cps.letsencrypt.org
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : B7:3E:FB:24:DF:9C:4D:BA:75:F2:39:C5:BA:58:F4:6C:
  • 5D:FC:42:CF:7A:9F:35:C4:9E:1D:09:81:25:ED:B4:99
  • Timestamp : May 22 01:07:54.337 2023 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:9F:2D:CE:C2:0E:AC:55:74:5C:90:CF:
  • BD:00:9F:94:EF:39:B7:4D:12:08:86:49:F1:71:8F:9C:
  • 27:44:41:21:4D:02:20:54:9C:47:54:89:97:1B:0B:FD:
  • 07:A1:33:EF:FA:67:A7:F3:E5:A1:4B:39:E0:71:F8:B9:
  • 80:E0:8D:70:6F:8E:91
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : E8:3E:D0:DA:3E:F5:06:35:32:E7:57:28:BC:89:6B:C9:
  • 03:D3:CB:D1:11:6B:EC:EB:69:E1:77:7D:6D:06:BD:6E
  • Timestamp : May 22 01:07:54.330 2023 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:7D:ED:D5:7C:C8:01:56:B6:40:DF:E8:8A:
  • D4:14:D8:91:3D:91:07:DA:61:2A:14:72:52:0E:38:8C:
  • C6:F3:EC:06:02:21:00:C8:C1:E4:08:53:43:79:F5:DA:
  • 14:4E:33:48:30:D9:6D:95:9E:56:A2:11:E5:A6:4A:17:
  • C9:CA:5E:4E:8B:C4:07