SSL-Tools

SSL check results of servpanel.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for servpanel.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 Thu, 25 Apr 2024 08:31:11 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.servpanel.de
2a01:4f8:c0c:718e::1
 0
supported
mail.servpanel.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
7 s
mail.servpanel.de
116.203.50.177
 0
supported
mail.servpanel.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
7 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.servpanel.de

Certificate chain
  • mail.servpanel.de
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.servpanel.de
Alternative Names
  • imap.servpanel.de
  • mail.servpanel.de
  • smtp.servpanel.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-02-25
Not valid after
2024-05-25
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
FE:85:79:D6:AC:3D:7A:D2:A4:B1:02:F5:D2:5D:C0:6E:49:FC:0F:A8:B2:C6:B0:B7:B3:6C:26:AF:39:9A:D3:53
SHA1
A0:ED:FA:06:0E:53:6C:6E:D8:D4:DC:12:46:C9:82:E3:53:C2:9F:E5
X509v3 extensions
subjectKeyIdentifier
  • 87:61:95:87:E9:2E:6D:50:76:9F:85:19:30:B1:D8:7F:D3:67:FE:A6
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
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 48:B0:E3:6B:DA:A6:47:34:0F:E5:6A:02:FA:9D:30:EB:
  • 1C:52:01:CB:56:DD:2C:81:D9:BB:BF:AB:39:D8:84:73
  • Timestamp : Feb 25 04:04:35.355 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:BD:0A:0B:2E:43:A6:DA:ED:75:D5:EC:
  • 03:89:65:35:54:C4:88:D3:5F:33:EB:67:B1:1C:F7:6A:
  • 92:0E:6C:C1:88:02:20:5C:A1:68:B5:11:90:8A:23:61:
  • 57:0E:18:78:FD:5A:CE:74:F1:EC:FD:7D:76:50:6C:70:
  • 37:34:73:28:76:61:4A
  • 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 : Feb 25 04:04:35.448 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:6B:F3:90:02:E7:08:30:71:39:65:7D:F5:
  • DC:25:C9:90:BD:A3:9C:B6:77:7B:F6:68:D2:87:C6:E3:
  • 69:92:94:E1:02:20:5D:9B:E7:D9:D6:41:B5:DF:D1:4C:
  • B7:1F:44:73:3E:EE:CA:13:FE:8A:5F:CC:08:55:67:79:
  • E2:AD:09:F7:3F:9A