SSL-Tools

SSL check results of leiko.eu

NEW You can also bulk check multiple servers.

Discover if the mail servers for leiko.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, 04 Feb 2025 20:34:46 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mars.leiko.eu
2a03:4000:b:14d::1
 0
supported
leiko.eu
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
6 s
mars.leiko.eu
46.38.250.236
 0
supported
leiko.eu
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 @leiko.eu sender addresses. Test mail delivery

Host TLS Version & Cipher
mail.leiko-server.de (178.254.34.206)
TLSv1.3 TLS_AES_256_GCM_SHA384
mail.leiko.eu (185.207.104.211)
TLSv1.3 TLS_AES_256_GCM_SHA384

Certificates

First seen at:

CN=leiko.eu

Certificate chain
  • leiko.eu
    • remaining
    • 384 bit
    • ecdsa-with-SHA384
      • E6
        • remaining
        • 384 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • leiko.eu
Alternative Names
  • *.leiko.eu
  • *.ullrich-info.de
  • *.ullrich-vt.de
  • leiko.eu
  • ullrich-info.de
  • ullrich-vt.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • E6
validity period
Not valid before
2025-01-28
Not valid after
2025-04-28
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
06:8D:DB:2C:83:AE:79:70:B7:9D:95:4D:DF:9C:51:C2:FD:4C:2D:6A:CE:46:18:4B:D6:8E:10:6F:98:B5:F5:B8
SHA1
16:23:37:BF:01:14:E5:29:6B:28:AA:F9:6B:B2:A7:E6:A7:49:43:82
X509v3 extensions
subjectKeyIdentifier
  • 4C:AB:8E:EE:A7:3F:80:A4:C6:5D:E2:CA:FB:24:BB:11:34:79:8B:DF
authorityKeyIdentifier
  • keyid:93:27:46:98:03:A9:51:68:8E:98:D6:C4:42:48:DB:23:BF:58:94:D2
authorityInfoAccess
  • OCSP - URI:http://e6.o.lencr.org
  • CA Issuers - URI:http://e6.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CF:11:56:EE:D5:2E:7C:AF:F3:87:5B:D9:69:2E:9B:E9:
  • 1A:71:67:4A:B0:17:EC:AC:01:D2:5B:77:CE:CC:3B:08
  • Timestamp : Jan 29 00:09:35.904 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:AB:A7:54:42:48:3A:8F:EB:71:4C:A3:
  • 7A:6C:CF:2F:86:13:1B:6B:F4:A8:5A:35:E3:47:30:0A:
  • 34:3F:F3:F7:31:02:20:22:77:A0:F8:1C:5B:8A:F1:9A:
  • FE:53:0F:0F:A2:CB:A4:0B:E7:78:84:A1:BD:09:2F:96:
  • 12:56:A1:69:5C:C3:FC
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 13:4A:DF:1A:B5:98:42:09:78:0C:6F:EF:4C:7A:91:A4:
  • 16:B7:23:49:CE:58:57:6A:DF:AE:DA:A7:C2:AB:E0:22
  • Timestamp : Jan 29 00:09:36.171 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:15:D6:EC:F8:E5:99:FD:BF:E8:6D:6F:0A:
  • B2:7E:19:9B:A2:0A:58:A1:D6:71:C1:F8:30:CF:EF:6F:
  • FB:24:C0:CD:02:20:2A:77:95:FB:82:50:05:72:A3:25:
  • 3B:5F:8E:5B:9E:22:26:35:85:C3:42:82:2B:49:F4:86:
  • A4:3F:58:D5:26:B2