SSL-Tools

SSL check results of plesk.dvc.gmbh

NEW You can also bulk check multiple servers.

Discover if the mail servers for plesk.dvc.gmbh 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 Sun, 26 Jan 2025 01:31:21 +0000

The mailservers of plesk.dvc.gmbh can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @plesk.dvc.gmbh addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
plesk.dvc.gmbh
2a01:4f8:13a:d9::2
 0
supported
dvc.gmbh
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
plesk.dvc.gmbh
195.201.104.145
 0
supported
dvc.gmbh
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s

Outgoing Mails

We have not received any emails from a @plesk.dvc.gmbh address so far. Test mail delivery

Certificates

First seen at:

CN=dvc.gmbh

Certificate chain
  • dvc.gmbh
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • dvc.gmbh
Alternative Names
  • *.dvc.gmbh
  • dvc.gmbh
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2025-01-09
Not valid after
2025-04-09
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
B9:CF:85:55:F1:A7:92:F4:05:58:E4:86:EB:59:E4:CC:43:9E:F7:D9:35:CC:FC:14:FA:C8:3C:7F:E7:F1:86:7B
SHA1
E7:60:12:46:E3:44:F6:7F:78:69:52:DA:D8:FF:01:93:80:3D:91:1E
X509v3 extensions
subjectKeyIdentifier
  • E2:28:56:17:90:59:CB:45:08:95:02:DD:97:24:4C:DB:46:9B:E1:23
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • OCSP - URI:http://r11.o.lencr.org
  • CA Issuers - URI:http://r11.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 73:20:22:0F:08:16:8A:F9:F3:C4:A6:8B:0A:B2:6A:9A:
  • 4A:00:EE:F5:77:85:8A:08:4D:05:00:D4:A5:42:44:59
  • Timestamp : Jan 9 18:56:16.233 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:1A:DD:02:8F:CE:AA:2E:38:46:CE:45:BB:
  • 93:62:98:1A:E1:5C:45:BE:8B:28:2D:FC:12:D1:0B:27:
  • 5F:8F:CE:48:02:20:02:54:83:67:A8:D8:26:CF:DF:D3:
  • E2:92:E4:5A:E2:70:26:24:F8:25:53:C6:08:A4:55:86:
  • F6:EC:C0:D9:50:C5
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CC:FB:0F:6A:85:71:09:65:FE:95:9B:53:CE:E9:B2:7C:
  • 22:E9:85:5C:0D:97:8D:B6:A9:7E:54:C0:FE:4C:0D:B0
  • Timestamp : Jan 9 18:56:16.249 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:0F:37:8E:1B:4F:08:9F:95:62:B4:F8:E9:
  • B1:A0:14:AF:F7:2D:AD:D8:1F:F5:80:0A:61:53:22:FF:
  • 31:7D:CC:1F:02:20:1F:BF:A7:10:D3:43:65:B0:41:E0:
  • 4D:B8:98:B4:7C:3E:97:7D:60:BD:71:1F:A8:98:19:33:
  • CA:72:F4:1F:AE:23

DANE

DNS-based Authentication of Named Entities (DANE) is a protocol to allow X.509 certificates to be bound to DNS using TLSA records and DNSSEC.

Name Options DNSSEC Matches
_25._tcp.plesk.dvc.gmbh
  • DANE-EE: Domain Issued Certificate
  • Use full certificate
  • SHA-256 Hash
error
Debug
valid