SSL check results of brightled.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for brightled.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 Mon, 19 Jul 2021 21:36:41 +0000

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

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

/mailservers/brightled.de

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.brightled.de
80.151.85.154
10
supported
office.brightled.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
8 s
mailc.brightled.de
80.151.85.154
10
supported
office.brightled.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
8 s
mailb.brightled.de
91.203.111.40
Results incomplete
100
supported
not checked
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=office.brightled.de

Certificate chain
Subject
Common Name (CN)
  • office.brightled.de
Alternative Names
  • mail.brightled.de
  • nextcloud.brightled.de
  • office.brightled.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • Let's Encrypt Authority X3
validity period
Not valid before
2019-08-21
Not valid after
2019-11-19
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
FD:14:33:4D:B4:FE:3C:81:A6:CF:D3:23:B4:26:AA:7E:F7:C7:26:94:3E:56:18:FE:D0:99:BA:48:14:1C:58:80
SHA1
D5:E0:75:30:3A:44:29:9B:4B:F5:1B:3A:EC:35:8A:DD:7B:4A:11:DC
X509v3 extensions
subjectKeyIdentifier
  • 7E:67:7C:79:EF:CD:E4:77:26:54:A9:F7:FB:AA:9F:35:BA:EA:ED:4E
authorityKeyIdentifier
  • keyid:A8:4A:6A:63:04:7D:DD:BA:E6:D1:39:B7:A6:45:65:EF:F3:A8:EC:A1
authorityInfoAccess
  • OCSP - URI:http://ocsp.int-x3.letsencrypt.org
  • CA Issuers - URI:http://cert.int-x3.letsencrypt.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 : 6F:53:76:AC:31:F0:31:19:D8:99:00:A4:51:15:FF:77:
  • 15:1C:11:D9:02:C1:00:29:06:8D:B2:08:9A:37:D9:13
  • Timestamp : Aug 21 21:04:02.991 2019 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:DD:5A:72:97:24:D3:B7:6E:49:6F:C7:
  • 1B:12:B4:BE:0D:EE:4B:49:ED:DB:60:28:A9:54:D9:86:
  • 57:66:F5:81:2A:02:20:6A:D3:61:15:6A:04:42:42:73:
  • 98:88:DA:57:D0:77:E4:CE:30:32:8E:D6:87:B5:51:F8:
  • 51:92:6F:E5:71:3F:46
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 63:F2:DB:CD:E8:3B:CC:2C:CF:0B:72:84:27:57:6B:33:
  • A4:8D:61:77:8F:BD:75:A6:38:B1:C7:68:54:4B:D8:8D
  • Timestamp : Aug 21 21:04:02.557 2019 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:7F:0E:38:E3:4A:62:EE:61:E4:A5:D0:84:
  • 90:B5:A4:28:B6:AB:E6:3B:5D:D2:36:94:FA:E8:FE:2C:
  • 6F:41:31:49:02:21:00:84:A3:FE:E8:CC:6A:E0:A1:29:
  • D7:5B:30:68:97:18:FE:52:D5:F7:02:1D:2B:B1:A0:99:
  • 28:3B:33:F3:A7:CB:B9