SSL-Tools

SSL check results of smarthost.dns.co.ke

NEW You can also bulk check multiple servers.

Discover if the mail servers for smarthost.dns.co.ke 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, 06 Sep 2026 10:48:54 +0000

We can not guarantee a secure connection to the mailservers of smarthost.dns.co.ke!

Please contact the operator of smarthost.dns.co.ke and ask him or her to solve this problem. This result stays accessible under the following address:

/mailservers/smarthost.dns.co.ke

Servers

Incoming Mails

These servers are responsible for incoming mails to @smarthost.dns.co.ke addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
smarthost.dns.co.ke
52.16.246.14
 -
supported
*.dns.co.ke
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s
smarthost.dns.co.ke
52.31.131.156
Results incomplete
-
unsupported
not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
2 s

Outgoing Mails

We have not received any emails from a @smarthost.dns.co.ke address so far. Test mail delivery

Certificates

First seen at:

CN=*.dns.co.ke

Certificate chain
  • *.dns.co.ke
    • remaining
    • 256 bit
    • ecdsa-with-SHA384
      • YE1
        • remaining
        • 384 bit
        • ecdsa-with-SHA384
          • Root YE
            • remaining
            • 384 bit
            • ecdsa-with-SHA384
              • ISRG Root X2 (Certificate is self-signed.)
                • remaining
                • 384 bit
                • ecdsa-with-SHA384
Subject
Common Name (CN)
  • *.dns.co.ke
Alternative Names
  • *.dns.co.ke
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • YE1
validity period
Not valid before
2026-08-21
Not valid after
2026-11-19
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
Fingerprints
SHA256
57:EC:69:D3:95:11:D9:55:75:0D:EA:E5:8F:75:F5:41:0B:11:54:76:E5:F6:4A:0A:0B:78:05:5A:55:2B:21:38
SHA1
BF:FB:AC:F7:FD:3C:1B:8D:8C:AE:95:E9:3A:55:AC:5B:6E:AD:D7:4C
X509v3 extensions
subjectKeyIdentifier
  • CF:25:21:54:66:32:53:6F:74:EC:F0:A8:2C:30:06:F5:F1:A9:DB:77
authorityKeyIdentifier
  • keyid:BB:20:CA:47:0B:FE:D7:E5:9C:F9:8F:09:2A:A3:8C:37:45:B1:BC:D8
authorityInfoAccess
  • CA Issuers - URI:http://ye1.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://ye1.c.lencr.org/81.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : D7:6D:7D:10:D1:A7:F5:77:C2:C7:E9:5F:D7:00:BF:F9:
  • 82:C9:33:5A:65:E1:D0:B3:01:73:17:C0:C8:C5:69:77
  • Timestamp : Aug 21 18:08:17.323 2026 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:3B:87:6F:E4:2C:83:CF:C3:C9:82:B0:78:
  • 06:42:52:E8:56:E9:77:40:DC:1B:29:36:A2:CC:23:52:
  • 8D:54:BD:C0:02:20:3F:8A:FD:55:EF:EB:C2:5B:1E:91:
  • BC:B6:B8:0A:C4:75:B4:66:86:82:44:33:F7:A2:EF:6C:
  • F4:95:9C:D2:08:73
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A8:26:CB:E3:0A:C6:35:12:46:53:3F:E0:65:F1:4F:19:
  • D9:6E:19:08:13:C4:1D:D9:6D:79:00:B3:12:3C:55:27
  • Timestamp : Aug 21 18:08:17.692 2026 GMT
  • Extensions: 00:00:05:00:20:B8:CF:45
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:1F:9F:89:98:25:7F:A4:90:BE:30:4B:79:
  • 8C:10:78:8A:1F:84:74:97:38:84:45:24:72:0C:63:81:
  • F1:A3:D0:62:02:20:63:63:8F:10:22:55:56:48:03:BF:
  • 72:9A:B1:BC:FB:CA:F7:37:09:A6:6D:CF:A3:74:D0:45:
  • 31:C4:C1:8F:2A:3C