SSL-Tools

SSL check results of mail.libovsky.eu

NEW You can also bulk check multiple servers.

Discover if the mail servers for mail.libovsky.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 Tue, 22 Oct 2024 09:39:58 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.libovsky.eu
176.66.66.24
 -
supported
rc.ingh2.eu
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
12 s

Outgoing Mails

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

Certificates

First seen at:

CN=rc.ingh2.eu

Certificate chain
  • rc.ingh2.eu
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • rc.ingh2.eu
Alternative Names
  • mail.audiosysteme.at
  • mail.bitechnik.at
  • mail.briggsworld.at
  • mail.ingh2.eu
  • mail.libovsky.eu
  • mail.mlaw.at
  • rapunzel.ingh2.eu
  • rc.ingh2.eu
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2024-08-25
Not valid after
2024-11-23
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
C3:EB:30:DA:A7:97:FE:90:10:DC:D0:94:6A:E3:46:02:83:9A:F3:B0:DB:5D:69:56:95:BD:A2:B5:39:39:E4:19
SHA1
CC:82:A7:11:67:EB:2D:84:85:BB:27:E2:6C:80:5D:65:53:13:A2:FC
X509v3 extensions
subjectKeyIdentifier
  • B7:E5:ED:53:34:F8:8F:39:50:60:1B:FA:CB:E0:EE:06:FD:95:5D:60
authorityKeyIdentifier
  • keyid:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
authorityInfoAccess
  • OCSP - URI:http://r10.o.lencr.org
  • CA Issuers - URI:http://r10.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 48:B0:E3:6B:DA:A6:47:34:0F:E5:6A:02:FA:9D:30:EB:
  • 1C:52:01:CB:56:DD:2C:81:D9:BB:BF:AB:39:D8:84:73
  • Timestamp : Aug 25 13:48:31.252 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:ED:85:DC:2C:A9:CE:3B:F9:29:00:AA:
  • BD:FC:D4:C7:40:03:A1:39:85:4D:85:11:2F:9B:56:1D:
  • 7C:AD:F1:52:4B:02:21:00:94:2B:3B:57:2D:51:88:5F:
  • CD:FA:FF:2E:35:E6:52:57:52:DD:F7:43:47:DA:E8:74:
  • 31:6B:13:A4:A4:F5:E8:A9
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 3F:17:4B:4F:D7:22:47:58:94:1D:65:1C:84:BE:0D:12:
  • ED:90:37:7F:1F:85:6A:EB:C1:BF:28:85:EC:F8:64:6E
  • Timestamp : Aug 25 13:48:31.245 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:EF:C7:68:3F:05:6E:8B:B1:76:80:80:
  • 25:B4:18:3E:44:8A:CB:C9:AB:C4:2F:B8:A7:0C:5A:2C:
  • 74:4B:01:A6:7B:02:21:00:8B:BC:53:6D:2A:39:BF:C4:
  • 0F:8C:53:5B:5F:42:7E:C6:5C:FD:F7:EC:41:53:E8:ED:
  • FA:47:8E:93:9D:74:B8:7B