SSL-Tools

SSL check results of vki.at

NEW You can also bulk check multiple servers.

Discover if the mail servers for vki.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 Wed, 03 Jun 2020 00:31:23 +0000

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

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

/mailservers/vki.at

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mg01.vki.at
2001:858:2:36::1005
 10
supported
mg01.vki.at
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
9 s
mg01.vki.at
86.59.28.17
 10
supported
mg01.vki.at
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
9 s
terminal.sil.at
2001:858:2:1::f2
Results incomplete
100
unsupported
not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
6 s
terminal.sil.at
213.235.253.198
Results incomplete
100
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 @vki.at address so far. Test mail delivery

Certificates

First seen at:

CN=mg01.vki.at

Certificate chain
Subject
Common Name (CN)
  • mg01.vki.at
Alternative Names
  • mg01.vki.at
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • Let's Encrypt Authority X3
validity period
Not valid before
2020-05-16
Not valid after
2020-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
9E:CC:CE:F9:C9:DC:67:39:BB:E2:C0:E9:2F:92:D5:EC:2F:43:FB:C1:BA:6A:C3:17:73:03:7B:BE:3E:A4:C1:69
SHA1
A1:D4:9B:D9:22:93:BB:CF:DE:BC:7C:E2:94:53:CD:86:B7:71:12:67
X509v3 extensions
subjectKeyIdentifier
  • FE:37:E7:9F:1F:42:9E:55:0B:06:39:BD:66:D1:9B:6E:5A:79:E9:0B
authorityKeyIdentifier
  • keyid:A8:4A:6A:63:04:7D:DD:BA:E6:D1:39:B7:A6:45:65:EF:F3:A8:EC:A1
authorityInfoAccess
  • OCSP - URI:http://ocsp.int-x3.letsencrypt.org
  • CA Issuers - URI:http://cert.int-x3.letsencrypt.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 : B2:1E:05:CC:8B:A2:CD:8A:20:4E:87:66:F9:2B:B9:8A:
  • 25:20:67:6B:DA:FA:70:E7:B2:49:53:2D:EF:8B:90:5E
  • Timestamp : May 16 22:48:40.556 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:5E:FE:41:AB:EB:58:3F:89:CD:B8:EC:0D:
  • 38:B1:30:EE:0B:D8:67:F2:CA:04:51:E6:72:02:69:4B:
  • F8:E6:BC:29:02:20:0F:E4:15:C3:B0:38:F4:B6:5C:CD:
  • 05:25:1C:F6:06:58:6E:2F:21:D6:28:39:81:0E:CF:49:
  • C9:18:1D:71:80:39
  • 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 : May 16 22:48:40.609 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:C9:B8:C1:74:58:75:F8:A8:D0:4B:89:
  • FF:FA:7A:52:58:F8:E2:A2:13:7D:48:AB:02:BE:0D:B5:
  • 48:F6:3B:72:B7:02:20:55:6B:2F:F1:0D:92:17:2F:F4:
  • D8:49:76:87:B0:A9:23:47:9E:A9:B7:5E:99:55:DC:74:
  • 7A:6D:EC:93:B8:99:3D