SSL-Tools

SSL check results of vertigo.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for vertigo.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 Tue, 05 Nov 2024 19:07:27 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.vertigo.de
217.13.201.233
 10
supported
vertigo.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 @vertigo.de address so far. Test mail delivery

Certificates

First seen at:

CN=vertigo.de

Certificate chain
  • vertigo.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)
  • vertigo.de
Alternative Names
  • imap.vertigo.de
  • mail.vertigo.de
  • mx.vertigo.de
  • pop3.vertigo.de
  • smtp.vertigo.de
  • vertigo.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2024-09-26
Not valid after
2024-12-25
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
CA:D1:B9:3B:7A:C1:A2:62:3A:05:6C:AF:A8:35:F9:96:C3:F7:61:A9:E0:32:BB:67:7B:BC:D2:F4:9A:AC:FC:20
SHA1
95:D5:6E:C3:B7:BE:D8:54:F4:B2:84:B1:85:CB:5B:D4:07:67:95:EF
X509v3 extensions
subjectKeyIdentifier
  • 0D:CD:CD:5C:A4:14:23:F7:1C:DB:DE:E8:DE:20:C0:15:09:57:D4:22
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 : Sep 26 22:44:41.977 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:60:C9:F8:20:A9:4A:16:C3:FE:BB:28:B9:
  • 00:8D:FE:7E:54:62:65:36:BD:77:E5:03:18:C7:B7:50:
  • 5D:45:E8:E6:02:21:00:A7:B1:CB:0D:4E:25:A3:94:04:
  • A5:74:D5:73:33:7E:AE:80:38:65:4D:05:F9:9D:C2:2F:
  • EB:DC:A7:0C:6A:46:51
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 76:FF:88:3F:0A:B6:FB:95:51:C2:61:CC:F5:87:BA:34:
  • B4:A4:CD:BB:29:DC:68:42:0A:9F:E6:67:4C:5A:3A:74
  • Timestamp : Sep 26 22:44:42.011 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:FE:04:C8:66:C8:40:66:2F:4E:FA:56:
  • 3D:FF:EA:3E:A6:50:68:45:96:13:59:E9:E1:A8:B5:65:
  • 82:6A:F3:89:D0:02:20:48:4F:AE:89:E2:BF:20:F8:48:
  • CD:FF:C1:11:FF:F3:BF:C2:A2:B3:66:4E:97:0C:A1:DB:
  • 43:CB:91:15:91:1B:20