SSL-Tools

SSL check results of deb-nbg-1.davocloud.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for deb-nbg-1.davocloud.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, 13 Jan 2021 19:05:07 +0000

The mailservers of deb-nbg-1.davocloud.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @deb-nbg-1.davocloud.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
deb-nbg-1.davocloud.de
78.47.166.128
 -
supported
deb-nbg-1.davocloud.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s
deb-nbg-1.davocloud.de
2a01:4f8:c2c:fd47::1
 -
supported
deb-nbg-1.davocloud.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s

Outgoing Mails

We have not received any emails from a @deb-nbg-1.davocloud.de address so far. Test mail delivery

Certificates

First seen at:

CN=deb-nbg-1.davocloud.de

Certificate chain
  • deb-nbg-1.davocloud.de
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • DST Root CA X3 (Certificate is self-signed.)
            • remaining
            • 2048 bit
            • sha1WithRSAEncryption
Subject
Common Name (CN)
  • deb-nbg-1.davocloud.de
Alternative Names
  • deb-nbg-1.davocloud.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-01-13
Not valid after
2021-04-13
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
B2:C9:6B:FB:58:FB:CA:FE:AF:8A:82:30:62:A2:B8:41:28:AC:76:71:CD:A5:6D:C6:52:E6:B9:67:5D:77:75:A8
SHA1
42:D6:BE:3C:9B:7D:01:9A:B0:78:D8:E1:B0:FC:BA:CA:0B:15:A0:8C
X509v3 extensions
subjectKeyIdentifier
  • 42:6B:E9:84:D8:F7:37:A5:64:67:43:D5:7D:63:16:AC:7B:C8:FE:A4
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 : 5C:DC:43:92:FE:E6:AB:45:44:B1:5E:9A:D4:56:E6:10:
  • 37:FB:D5:FA:47:DC:A1:73:94:B2:5E:E6:F6:C7:0E:CA
  • Timestamp : Jan 13 02:02:54.380 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:F8:0E:BD:89:91:67:D8:DA:F0:DD:AA:
  • 50:68:3E:58:0A:CE:84:6F:A9:50:1C:64:6B:F8:91:84:
  • 0C:BB:B9:D2:4B:02:21:00:FB:5E:A2:5C:69:DB:E3:76:
  • D2:AA:E8:41:15:30:0A:09:19:3F:B4:89:DB:8F:F3:9A:
  • F6:7B:3C:22:F6:93:85:1E
  • 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 : Jan 13 02:02:54.857 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:69:EB:76:7D:78:F3:73:D9:4E:A2:37:40:
  • 20:DC:E4:53:8B:40:25:41:82:15:81:96:D5:9E:83:8D:
  • 2C:6E:AF:61:02:20:42:33:D7:6A:D4:61:10:A7:36:D9:
  • BD:1A:1A:48:F6:86:F3:8A:D8:66:B9:FB:A0:E0:97:AE:
  • F7:80:7E:85:F0:87