SSL-Tools

SSL check results of eislinger.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for eislinger.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, 06 Apr 2024 18:11:52 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.box80.de
2a01:4f8:c012:7240::100
 10
supported
mail.box80.de
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
6 s
mail.box80.de
88.99.121.170
 10
supported
mail.box80.de
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
5 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.box80.de

Certificate chain
  • mail.box80.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.box80.de
Alternative Names
  • mail.box80.de
  • mail.box80.net
  • webmail.box80.de
  • webmail.box80.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-02-11
Not valid after
2024-05-11
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
99:02:61:80:AA:5A:0D:E1:D6:2C:0D:A9:F0:5E:41:27:E7:71:86:4E:6D:77:64:B6:31:AC:F8:C7:53:A3:B6:07
SHA1
AB:E2:0F:0B:33:B4:F6:25:C6:03:0C:89:ED:52:AB:D7:94:5A:64:8B
X509v3 extensions
subjectKeyIdentifier
  • F4:6B:5A:07:D7:21:06:34:6C:3B:A0:F3:BF:48:33:B1:1C:D8:C5:CB
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 : 3B:53:77:75:3E:2D:B9:80:4E:8B:30:5B:06:FE:40:3B:
  • 67:D8:4F:C3:F4:C7:BD:00:0D:2D:72:6F:E1:FA:D4:17
  • Timestamp : Feb 11 15:01:10.459 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:F2:38:C9:6B:3F:77:6C:25:92:DA:19:
  • 70:84:57:A1:29:44:4B:4D:2E:F4:D7:34:38:31:26:00:
  • 08:77:65:85:9E:02:21:00:81:B4:91:05:57:0A:25:A8:
  • 5B:2C:D3:69:51:A6:0B:06:47:06:09:FA:4D:ED:FA:05:
  • 4F:C2:50:9B:E5:ED:31:23
  • 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 11 15:01:10.534 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:1D:C8:86:5E:DB:0A:65:61:59:8C:48:AA:
  • CC:56:54:32:AD:3F:C4:B1:9E:73:19:E0:2C:C9:4A:52:
  • E3:98:E2:C7:02:20:0E:2F:7C:97:4C:DF:2D:9C:3E:4C:
  • C6:ED:B5:B9:8A:3E:28:4C:04:CD:26:BC:72:52:D2:0F:
  • 5E:69:0B:81:58:2A

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.mail.box80.de
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
valid
valid