SSL-Tools

SSL check results of laschinsky.eu

NEW You can also bulk check multiple servers.

Discover if the mail servers for laschinsky.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 Sun, 24 Sep 2023 15:15:23 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.laschinsky.eu
2a12:8641:7:30f8::
 10
supported
mail.laschinsky.eu
DANE
errors
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
8 s
mail.laschinsky.eu
45.84.196.96
 10
supported
mail.laschinsky.eu
DANE
errors
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
5 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.laschinsky.eu

Certificate chain
  • mail.laschinsky.eu
    • remaining
    • 384 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.laschinsky.eu
Alternative Names
  • mail.laschinsky.eu
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2023-07-30
Not valid after
2023-10-28
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
59:BE:7B:0C:8A:A7:6B:8C:56:ED:C5:9E:60:59:74:5E:D3:6A:B2:07:20:16:7A:60:0C:F6:4D:61:A7:EB:5A:21
SHA1
1C:A5:6C:37:E3:AD:67:3B:B3:3C:84:AB:24:DD:9A:74:6D:C8:AA:0E
X509v3 extensions
subjectKeyIdentifier
  • 7D:7D:4B:50:70:B0:7E:1F:26:76:FE:15:80:03:25:A1:4D:6F:31:36
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
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 7A:32:8C:54:D8:B7:2D:B6:20:EA:38:E0:52:1E:E9:84:
  • 16:70:32:13:85:4D:3B:D2:2B:C1:3A:57:A3:52:EB:52
  • Timestamp : Jul 30 22:47:57.542 2023 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:58:CF:87:91:51:B7:25:84:A8:0E:33:EC:
  • EB:91:0C:B8:CA:1B:A4:0E:F3:A7:C2:EA:72:D4:45:A3:
  • A6:CB:B6:B6:02:21:00:E4:2B:76:C1:99:55:6C:BF:EF:
  • 16:8F:84:27:D6:7D:19:66:30:FC:36:99:FE:9B:B0:AD:
  • F9:43:AC:C4:3A:0A:8D
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : AD:F7:BE:FA:7C:FF:10:C8:8B:9D:3D:9C:1E:3E:18:6A:
  • B4:67:29:5D:CF:B1:0C:24:CA:85:86:34:EB:DC:82:8A
  • Timestamp : Jul 30 22:47:57.573 2023 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:F8:01:24:85:8A:62:F1:CE:14:76:24:
  • 67:BD:15:42:5F:E1:50:66:EF:C2:5E:BF:D1:2C:52:F3:
  • D1:16:A8:B0:B3:02:20:29:2A:44:BC:00:93:36:45:5E:
  • 7C:D6:CB:EF:19:DE:EA:4A:63:71:A5:A3:81:FF:E0:A9:
  • 3C:A3:E2:87:80:58:52

DANE

DNS-based Authentication of Named Entities (DANE) is a protocol to allow X.509 certificates to be bound to DNS using TLSA records and DNSSEC.

Name Options DNSSEC Matches
_25._tcp.mail.laschinsky.eu
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
error
Debug
—