SSL-Tools

SSL check results of familybiebrich.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for familybiebrich.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 Fri, 11 Jun 2021 16:15:18 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.familybiebrich.de
195.192.76.45
 10
supported
familybiebrich.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
3 s

Outgoing Mails

We have received emails from these servers with @familybiebrich.de sender addresses. Test mail delivery

Host TLS Version & Cipher
195-192-76-45.dyn.cablelink.at (195.192.76.45)
TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384

Certificates

First seen at:

CN=familybiebrich.de

Certificate chain
  • familybiebrich.de
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • DST Root CA X3 (Certificate is self-signed.)
            • remaining
            • 2048 bit
            • sha1WithRSAEncryption
Subject
Common Name (CN)
  • familybiebrich.de
Alternative Names
  • autodiscover.familybiebrich.de
  • familybiebrich.de
  • kopano.familybiebrich.de
  • mail.familybiebrich.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-06-06
Not valid after
2021-09-04
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
89:C0:7F:DE:7B:88:48:EF:DB:0A:EC:46:61:34:0D:B4:8B:12:23:CF:AB:4E:24:A6:63:3A:75:DD:44:11:7C:4B
SHA1
2D:22:FA:24:66:8A:24:92:8A:88:6B:97:0A:6A:B2:B5:B2:52:B5:44
X509v3 extensions
subjectKeyIdentifier
  • 8B:59:A3:74:95:9B:89:77:AC:34:FF:9E:6C:80:E0:4B:B5:91:AE:EA
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
  • Policy: 1.3.6.1.4.1.44947.1.1.1
  • CPS: http://cps.letsencrypt.org
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 5C:DC:43:92:FE:E6:AB:45:44:B1:5E:9A:D4:56:E6:10:
  • 37:FB:D5:FA:47:DC:A1:73:94:B2:5E:E6:F6:C7:0E:CA
  • Timestamp : Jun 6 06:26:49.571 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:A2:14:E2:FF:56:15:4E:5B:D0:90:2D:
  • 18:1D:16:35:AC:4F:26:A0:F9:5D:67:72:06:79:DA:4E:
  • C1:6A:1C:64:17:02:20:0A:B8:42:A9:FA:2C:AE:C7:71:
  • B3:F5:88:06:26:02:2E:17:09:AA:FF:AD:54:AE:74:C0:
  • FA:86:14:13:BD:01:BD
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : F6:5C:94:2F:D1:77:30:22:14:54:18:08:30:94:56:8E:
  • E3:4D:13:19:33:BF:DF:0C:2F:20:0B:CC:4E:F1:64:E3
  • Timestamp : Jun 6 06:26:49.581 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:7C:94:9B:D0:21:E4:5E:AF:2A:FD:E4:C6:
  • 23:BA:82:5C:7D:F7:B7:F7:8B:5B:12:3E:AC:AF:F8:2B:
  • 54:9E:1B:B9:02:20:6E:B0:7D:DE:63:41:CF:04:DE:CE:
  • 7B:EA:EF:95:60:09:FB:D8:A9:E7:E2:BE:0D:02:11:CB:
  • 12:14:78:28:59:57