SSL-Tools

SSL check results of berndberger.eu

NEW You can also bulk check multiple servers.

Discover if the mail servers for berndberger.eu 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, 19 Jul 2026 00:31:14 +0000

The mailservers of berndberger.eu can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @berndberger.eu addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.berndberger.eu
2a0a:4cc0:c1:e6a7:7846:84ff:fe6a:2a04
 10
supported
mail.berndberger.eu
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s
mail.berndberger.eu
159.195.57.8
 10
supported
mail.berndberger.eu
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 @berndberger.eu address so far. Test mail delivery

Certificates

First seen at:

CN=mail.berndberger.eu

Certificate chain
  • mail.berndberger.eu
    • remaining
    • 256 bit
    • ecdsa-with-SHA384
      • YE1
        • remaining
        • 384 bit
        • ecdsa-with-SHA384
          • Root YE
            • remaining
            • 384 bit
            • ecdsa-with-SHA384
              • ISRG Root X2 (Certificate is self-signed.)
                • remaining
                • 384 bit
                • ecdsa-with-SHA384
Subject
Common Name (CN)
  • mail.berndberger.eu
Alternative Names
  • mail.berndberger.eu
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • YE1
validity period
Not valid before
2026-07-10
Not valid after
2026-10-08
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
Fingerprints
SHA256
71:1F:DB:49:45:DB:25:49:7E:51:C8:F9:C2:2F:9C:AB:33:7A:5E:1F:41:71:39:78:AA:8B:31:7A:93:8D:72:8C
SHA1
E0:88:B4:23:0C:FA:9E:81:6D:8E:AF:B8:3A:58:B1:0B:D7:01:C0:98
X509v3 extensions
subjectKeyIdentifier
  • 19:42:0B:9D:7F:37:3B:CE:BA:17:B8:09:28:6E:23:AE:EC:31:36:5D
authorityKeyIdentifier
  • keyid:BB:20:CA:47:0B:FE:D7:E5:9C:F9:8F:09:2A:A3:8C:37:45:B1:BC:D8
authorityInfoAccess
  • CA Issuers - URI:http://ye1.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://ye1.c.lencr.org/12.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : D8:09:55:3B:94:4F:7A:FF:C8:16:19:6F:94:4F:85:AB:
  • B0:F8:FC:5E:87:55:26:0F:15:D1:2E:72:BB:45:4B:14
  • Timestamp : Jul 10 17:51:11.612 2026 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:01:D3:9B:A5:31:DE:D2:9D:C7:B0:EC:89:
  • 22:B5:C4:97:6E:36:C9:83:93:7F:0A:11:AD:C5:32:7B:
  • 80:33:DC:CD:02:20:31:8D:2F:70:CA:26:90:13:38:FF:
  • CB:63:DA:40:83:C4:18:9D:D9:41:4F:2E:D4:59:98:85:
  • 54:6C:9C:47:66:AD
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A8:26:CB:E3:0A:C6:35:12:46:53:3F:E0:65:F1:4F:19:
  • D9:6E:19:08:13:C4:1D:D9:6D:79:00:B3:12:3C:55:27
  • Timestamp : Jul 10 17:51:12.287 2026 GMT
  • Extensions: 00:00:05:00:13:6E:CF:83
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:3B:EC:3F:F9:09:2D:D3:C0:6B:82:91:03:
  • 5B:E4:C8:FD:EE:BE:B4:F4:FC:33:0B:74:F4:3F:26:56:
  • E8:CD:17:1D:02:21:00:B9:34:5A:3B:B3:D0:9D:98:8E:
  • E8:E3:B0:B4:A5:92:CA:7F:0D:E1:52:B8:36:36:85:46:
  • F1:2A:7C:66:74:6D:5C

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.berndberger.eu
  • DANE-TA: Trust Anchor Assertion
  • Use subject public key
  • SHA-256 Hash
valid
valid
_25._tcp.mail.berndberger.eu
  • DANE-TA: Trust Anchor Assertion
  • Use subject public key
  • SHA-256 Hash
valid
valid