SSL check results of lekko.com.br

NEW You can also bulk check multiple servers.

Discover if the mail servers for lekko.com.br 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

Report created Sat, 29 Mar 2025 08:19:19 +0000

We can not guarantee a secure connection to the mailservers of lekko.com.br!

Please contact the operator of lekko.com.br and ask him or her to solve this problem. This result stays accessible under the following address:

/mailservers/lekko.com.br

Servers

Incoming Mails

These servers are responsible for incoming mails to @lekko.com.br addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.lekko.com.br
2804:9c4:2f:19::100
Results incomplete
10 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s
mail.lekko.com.br
186.227.196.102
10
supported
lekko.com.br
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 @lekko.com.br address so far. Test mail delivery

Certificates

First seen at:

CN=lekko.com.br

Certificate chain
  • lekko.com.br
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
    • Hostname Mismatch

      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption

Subject
Common Name (CN)
  • lekko.com.br
Alternative Names
  • lekko.com.br
  • webmail.lekko.com.br
  • www.lekko.com.br
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2025-02-26
Not valid after
2025-05-27
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
B4:C7:80:6A:1F:AF:94:1F:C3:F6:49:39:BA:34:15:81:DD:CC:7C:1F:66:FD:F1:96:C3:4A:00:9E:E4:A8:A1:28
SHA1
FE:1A:C3:85:76:C0:81:D8:F3:81:D0:81:0D:51:16:7B:5F:DB:BF:18
X509v3 extensions
subjectKeyIdentifier
  • E0:0F:E7:31:6A:92:4D:0C:99:E2:D2:4E:A5:6D:D0:57:17:47:0F:36
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 : E6:D2:31:63:40:77:8C:C1:10:41:06:D7:71:B9:CE:C1:
  • D2:40:F6:96:84:86:FB:BA:87:32:1D:FD:1E:37:8E:50
  • Timestamp : Feb 26 14:19:30.550 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:E0:9C:5B:0C:6C:8E:6C:77:83:C8:5D:
  • D8:30:F3:20:5A:21:72:34:7E:37:7A:E2:A1:CF:36:96:
  • 23:93:2D:1B:60:02:20:70:7B:0D:9E:D0:5B:8A:B7:A7:
  • D4:0E:06:0E:7D:94:11:54:57:75:37:92:E6:38:ED:D8:
  • 50:69:A7:CC:C7:DB:D6
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A2:E3:0A:E4:45:EF:BD:AD:9B:7E:38:ED:47:67:77:53:
  • D7:82:5B:84:94:D7:2B:5E:1B:2C:C4:B9:50:A4:47:E7
  • Timestamp : Feb 26 14:19:30.546 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:33:0A:18:79:C9:8D:66:B8:E2:01:E1:0B:
  • D6:B0:9A:D6:1E:21:6B:40:EA:D9:FD:60:FE:61:3E:C1:
  • 02:4D:B5:A6:02:20:32:DD:65:5F:AC:07:B9:03:6B:30:
  • D6:91:F0:17:97:2F:BB:57:49:3C:62:49:7E:EE:88:2D:
  • 05:98:E2:BC:CF:72