SSL-Tools

SSL check results of ikostomlaty.net

NEW You can also bulk check multiple servers.

Discover if the mail servers for ikostomlaty.net 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 Wed, 17 Apr 2024 20:37:37 +0000

The mailservers of ikostomlaty.net can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @ikostomlaty.net addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
bruno.ikostomlaty.net
46.167.242.10
 10
supported
smtp.ikostomlaty.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
ferda.ikostomlaty.net
46.167.242.15
 30
supported
smtp.ikostomlaty.net
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 @ikostomlaty.net address so far. Test mail delivery

Certificates

First seen at:

CN=smtp.ikostomlaty.net

Certificate chain
  • smtp.ikostomlaty.net
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • smtp.ikostomlaty.net
Alternative Names
  • bruno.ikostomlaty.net
  • ferda.ikostomlaty.net
  • smtp.ikostomlaty.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-04-15
Not valid after
2024-07-14
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
2C:78:57:81:12:4C:6F:46:38:54:2B:CF:B0:C5:E9:B5:3C:3E:2C:0A:A1:6C:1A:5B:43:65:D4:01:75:77:50:83
SHA1
E3:0F:5C:4B:07:4E:6E:CE:C5:BB:9D:AF:B0:1B:EE:D5:A2:62:FB:F6
X509v3 extensions
subjectKeyIdentifier
  • 05:BF:48:0F:1F:0B:89:3F:89:7C:68:8A:2C:47:0F:65:90:8D:C6:B0
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 : 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 : Apr 15 22:41:49.683 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:23:DA:33:C6:CB:3F:06:9C:7D:E8:79:D7:
  • FB:D6:26:75:52:8F:B3:70:B6:AC:B8:4C:B8:95:4E:6B:
  • 39:61:7E:A5:02:20:1B:A2:3A:AF:2F:4A:B5:80:83:10:
  • C6:9B:2C:5A:99:BE:97:F6:11:D8:90:87:F9:25:6C:2A:
  • 20:60:C9:D6:95:8B
  • 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 : Apr 15 22:41:49.769 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:8D:93:97:A5:90:90:81:7E:7F:FE:86:
  • BE:95:1B:38:F3:44:58:8A:47:06:A1:CF:8E:73:8C:E1:
  • 0C:F3:83:D2:96:02:21:00:D0:B6:AB:A9:A7:41:8B:37:
  • BE:81:AC:16:DA:A6:C5:04:13:84:CA:33:CE:AD:77:2B:
  • F4:2E:34:D0:72:35:5E:BF