SSL-Tools

SSL check results of vleov.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for vleov.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 Sat, 11 Jan 2025 03:27:18 +0000

The mailservers of vleov.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @vleov.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.vleov.de
45.93.251.223
 10
supported
vleov.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
1 s

Outgoing Mails

We have not received any emails from a @vleov.de address so far. Test mail delivery

Certificates

First seen at:

CN=vleov.de

Certificate chain
  • vleov.de
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • vleov.de
Alternative Names
  • admin.vleov.de
  • autoconfig.vleov.de
  • autodiscover.vleov.de
  • mail.vleov.de
  • vleov.de
  • webmail.vleov.de
  • www.vleov.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2025-01-11
Not valid after
2025-04-11
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
28:EE:22:34:0D:BB:25:03:5E:A4:76:ED:2E:80:24:0B:0D:B3:CF:7E:72:B3:B3:D0:92:CD:DD:AC:6C:97:76:C8
SHA1
C1:C0:CB:BF:04:A3:3E:1E:48:94:6A:2E:CC:9E:19:0F:BE:D5:58:17
X509v3 extensions
subjectKeyIdentifier
  • C6:BB:A7:FA:DA:1E:F0:96:FA:A1:DD:21:E9:37:1E:57:D9:31:F2:E9
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 : A2:E3:0A:E4:45:EF:BD:AD:9B:7E:38:ED:47:67:77:53:
  • D7:82:5B:84:94:D7:2B:5E:1B:2C:C4:B9:50:A4:47:E7
  • Timestamp : Jan 11 03:26:04.367 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:07:CB:5E:51:38:61:47:C3:5C:BB:F6:0F:
  • 11:17:70:59:0E:55:10:A9:7E:BF:1C:D3:3F:9C:BD:3A:
  • 11:44:25:8B:02:21:00:AC:1A:5D:9E:44:0F:FD:09:49:
  • 32:4D:1C:00:71:5D:C4:F0:96:48:DD:41:11:B0:8E:B4:
  • 93:3C:67:6A:BD:7A:E1
  • 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 11 03:26:04.387 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:04:2B:F8:11:DC:FD:28:EE:A0:93:52:1A:
  • 39:DD:02:DB:71:2D:FE:5E:0C:A0:23:73:39:BB:88:A2:
  • F4:BE:61:DD:02:20:5D:E5:24:E1:E9:96:5F:33:81:C1:
  • F2:0E:08:89:98:67:18:E9:8D:58:50:61:40:A1:3C:F4:
  • 73:36:43:DB:5C:55