SSL check results of www.becker8.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for www.becker8.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

Report created Tue, 14 Jan 2025 01:30:35 +0000

We can not guarantee a secure connection to the mailservers of www.becker8.de!

Please contact the operator of www.becker8.de and ask him or her to solve this problem. This result stays accessible under the following address:

/mailservers/www.becker8.de

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
www.becker8.de
79.247.49.145
-
supported
*.becker8.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
5 s
www.becker8.de
2003:da:b731::4024:d2ff:fe88:cb88
Results incomplete
- not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=*.becker8.de

Certificate chain
  • *.becker8.de
    • remaining
    • 384 bit
    • ecdsa-with-SHA384

      • E6
        • remaining
        • 384 bit
        • sha256WithRSAEncryption

          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption

Subject
Common Name (CN)
  • *.becker8.de
Alternative Names
  • *.becker8.de
  • becker8.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • E6
validity period
Not valid before
2025-01-01
Not valid after
2025-04-01
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
31:2C:AE:6F:E5:37:17:EF:0E:B2:68:5C:A4:CE:5E:EB:9C:21:6D:37:75:76:70:6C:95:F2:E3:84:20:8C:CF:3F
SHA1
9B:AF:D6:23:8A:13:F9:6F:D3:B6:28:AD:A0:B6:28:5C:5C:CE:A1:EC
X509v3 extensions
subjectKeyIdentifier
  • 23:05:5F:5B:A0:96:20:1E:F6:97:0A:2C:90:A7:50:6E:AD:DA:EA:06
authorityKeyIdentifier
  • keyid:93:27:46:98:03:A9:51:68:8E:98:D6:C4:42:48:DB:23:BF:58:94:D2
authorityInfoAccess
  • OCSP - URI:http://e6.o.lencr.org
  • CA Issuers - URI:http://e6.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • 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 1 12:34:56.310 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:1B:A3:BE:C1:86:76:4E:AC:19:BA:BD:C9:
  • 71:D3:FB:D6:86:FA:50:A5:4D:83:20:93:9F:67:97:AE:
  • 67:AC:55:23:02:20:25:5D:53:6C:92:C3:A0:AC:F3:43:
  • 91:99:6E:0E:C4:39:F8:86:A3:26:32:2A:81:16:13:0B:
  • B1:DE:6E:1E:A1:34
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CF:11:56:EE:D5:2E:7C:AF:F3:87:5B:D9:69:2E:9B:E9:
  • 1A:71:67:4A:B0:17:EC:AC:01:D2:5B:77:CE:CC:3B:08
  • Timestamp : Jan 1 12:34:56.335 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:7F:FD:A8:7E:1D:25:F7:39:4A:6E:EB:D1:
  • 70:42:82:92:B5:5D:DB:E0:DE:7A:55:EF:62:E3:ED:57:
  • 53:46:87:A1:02:21:00:DF:A8:14:80:ED:32:F6:06:49:
  • 70:95:C6:18:80:40:BE:1D:98:06:37:07:47:86:3F:8B:
  • 3D:F1:7F:C3:53:F8:A1