SSL-Tools

SSL check results of poppy.my

NEW You can also bulk check multiple servers.

Discover if the mail servers for poppy.my 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 Fri, 20 Dec 2024 06:29:21 +0000

We can not guarantee a secure connection to the mailservers of poppy.my!

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

/mailservers/poppy.my

Servers

Incoming Mails

These servers are responsible for incoming mails to @poppy.my addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
poppy.my
45.77.169.14
Results incomplete
0 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s
mail.poppy.my
117.53.155.102
 10
supported
webmail.poppy.my
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
10 s

Outgoing Mails

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

Certificates

First seen at:

CN=webmail.poppy.my

Certificate chain
  • webmail.poppy.my
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
    • Hostname Mismatch
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • webmail.poppy.my
Alternative Names
  • webmail.poppy.my
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2024-10-28
Not valid after
2025-01-26
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
A8:57:28:04:6F:05:DD:8D:05:A8:43:66:B3:3F:9E:75:B2:14:5C:C0:C4:30:1B:94:13:9A:39:6B:7D:94:85:4C
SHA1
02:05:0D:65:EB:90:AB:4D:0D:08:6D:A2:79:EC:29:FE:E6:B7:59:66
X509v3 extensions
subjectKeyIdentifier
  • C0:2E:0A:E4:E1:82:D4:4F:F3:39:C5:82:BE:DC:26:72:60:D5:0D:38
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • OCSP - URI:http://r11.o.lencr.org
  • CA Issuers - URI:http://r11.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • 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 : Oct 28 06:57:15.928 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:BB:88:9E:F5:A4:7D:58:6C:77:3F:FC:
  • 5B:C3:4E:38:7F:B9:88:9D:B9:29:51:21:38:2A:AD:06:
  • 85:7C:94:61:51:02:20:15:47:4D:DB:3A:BB:5A:A1:20:
  • E6:99:4B:86:D4:A5:1B:C5:53:A0:9F:FD:F2:98:0E:AC:
  • 9F:DF:95:7A:F0:6D:B9
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : E0:92:B3:FC:0C:1D:C8:E7:68:36:1F:DE:61:B9:96:4D:
  • 0A:52:78:19:8A:72:D6:72:C4:B0:4D:A5:6D:6F:54:04
  • Timestamp : Oct 28 06:57:15.961 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:12:83:90:DC:B0:52:3D:8C:11:AF:CA:3F:
  • 1D:01:46:2A:17:23:61:06:6B:62:D2:89:AA:CB:CF:AC:
  • E1:A6:1A:B9:02:20:5E:99:5E:67:45:3D:B7:10:21:81:
  • 39:65:E9:4D:CA:B5:8F:51:8E:58:AA:62:99:E0:E2:86:
  • E0:B9:E8:BE:A7:6D