SSL-Tools

SSL check results of librezale.eus

NEW You can also bulk check multiple servers.

Discover if the mail servers for librezale.eus 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, 24 Apr 2021 08:59:19 +0000

The mailservers of librezale.eus can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @librezale.eus addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
librezale.eus
2a01:7e00::f03c:91ff:fe24:de1
 10
supported
librezale.eus
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
3 s
librezale.eus
178.79.159.90
 10
supported
librezale.eus
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s

Outgoing Mails

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

Certificates

First seen at:

CN=librezale.eus

Certificate chain
  • librezale.eus
    • 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)
  • librezale.eus
Alternative Names
  • librezale.eus
  • wiki.librezale.eus
  • www.librezale.eus
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-03-08
Not valid after
2021-06-06
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
4B:DA:D7:9A:CF:53:BF:D5:3F:D0:02:4D:5A:DC:1A:3D:01:D6:DD:FD:43:77:9D:91:3C:67:D6:24:E8:C6:3E:FC
SHA1
0C:47:13:F5:1E:C8:78:73:89:09:4D:96:70:5D:F0:98:26:F1:7D:1B
X509v3 extensions
subjectKeyIdentifier
  • D2:6A:E3:80:67:FF:AA:CF:7A:F8:BD:7C:79:86:31:59:04:6D:88:73
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 : 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 : Mar 8 10:07:43.405 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:5B:7B:0B:F3:3F:D4:4F:75:4D:18:33:2D:
  • 27:6E:FD:82:16:6F:0E:D4:E4:7F:86:F9:FE:F8:0E:C7:
  • 9F:64:9A:AB:02:20:3E:C4:0D:EB:2A:45:A3:F1:D6:02:
  • 23:3E:2F:71:2A:4E:36:A0:11:0F:95:7A:21:4B:32:57:
  • 25:2B:CA:3E:40:36
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 94:20:BC:1E:8E:D5:8D:6C:88:73:1F:82:8B:22:2C:0D:
  • D1:DA:4D:5E:6C:4F:94:3D:61:DB:4E:2F:58:4D:A2:C2
  • Timestamp : Mar 8 10:07:43.416 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:D0:2C:7D:C6:99:4B:1B:7D:DF:9C:D8:
  • 74:6F:4E:6E:89:0B:4A:19:01:C1:05:05:5D:D5:D6:CF:
  • B9:00:5C:74:96:02:21:00:91:39:41:23:8D:65:46:F3:
  • 89:3E:D4:6D:56:12:0E:75:99:2B:48:0E:09:6E:41:33:
  • 16:8B:AE:AE:7F:94:4E:31