SSL-Tools

SSL check results of vdv.co.at

NEW You can also bulk check multiple servers.

Discover if the mail servers for vdv.co.at 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, 06 May 2021 20:11:03 +0000

We can not guarantee a secure connection to the mailservers of vdv.co.at!

Please contact the operator of vdv.co.at and ask him or her to solve this problem. This result stays accessible under the following address:

/mailservers/vdv.co.at

Servers

Incoming Mails

These servers are responsible for incoming mails to @vdv.co.at addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mx20a.vipweb.at
91.206.237.18
 0
supported
mx20.vipweb.at
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
9 s
mx30.vipweb.at
80.66.63.91
Results incomplete
30
unsupported
not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 s

Outgoing Mails

We have not received any emails from a @vdv.co.at address so far. Test mail delivery

Certificates

First seen at:

CN=mx20.vipweb.at

Certificate chain
  • mx20.vipweb.at
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
    • Hostname Mismatch
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • DST Root CA X3 (Certificate is self-signed.)
            • remaining
            • 2048 bit
            • sha1WithRSAEncryption
Subject
Common Name (CN)
  • mx20.vipweb.at
Alternative Names
  • mx20.vipweb.at
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-04-05
Not valid after
2021-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
44:18:01:03:4B:0B:6D:29:4C:76:DA:F2:8C:4D:BB:85:62:0E:43:66:C8:D5:BD:3D:0C:5F:72:0F:AE:49:4F:C5
SHA1
D1:F1:86:7A:2B:EE:FE:31:0C:54:38:AD:86:44:57:F8:F6:42:AF:34
X509v3 extensions
subjectKeyIdentifier
  • FF:42:D8:9F:B3:F8:98:7E:FC:50:42:30:35:DF:34:69:DA:A2:C8:CB
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 : F6:5C:94:2F:D1:77:30:22:14:54:18:08:30:94:56:8E:
  • E3:4D:13:19:33:BF:DF:0C:2F:20:0B:CC:4E:F1:64:E3
  • Timestamp : Apr 5 04:01:09.888 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:AF:81:8F:5F:B2:83:3E:E5:72:1D:07:
  • C8:EA:71:55:44:EA:C9:36:53:25:78:15:4F:75:5F:12:
  • 76:76:27:EB:C9:02:20:2A:66:1C:BF:7F:CF:46:EE:13:
  • 71:A2:71:AC:9A:96:4B:58:A8:9A:E4:39:B5:FD:DB:1D:
  • D9:BF:37:6A:ED:53:BC
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 6F:53:76:AC:31:F0:31:19:D8:99:00:A4:51:15:FF:77:
  • 15:1C:11:D9:02:C1:00:29:06:8D:B2:08:9A:37:D9:13
  • Timestamp : Apr 5 04:01:10.259 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:D9:B0:7B:64:DD:F0:26:E1:45:1B:40:
  • AB:F7:4A:74:8F:1B:F9:A9:BF:9D:B6:F1:AB:58:28:0A:
  • F9:6B:6B:B7:E8:02:20:6B:F0:01:49:53:4B:F0:EB:2D:
  • 98:44:43:46:78:CD:DB:80:07:D3:46:17:5E:5B:B6:C3:
  • 61:9B:8E:DC:38:1F:90