SSL-Tools

SSL check results of juan4d.net

NEW You can also bulk check multiple servers.

Discover if the mail servers for juan4d.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 Sat, 15 Feb 2025 17:49:25 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
juan4d.net
103.21.221.26
 0
supported
www.juan4d.com.tehhijau456.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
11 s

Outgoing Mails

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

Certificates

First seen at:

CN=www.juan4d.com.tehhijau456.com

Certificate chain
  • www.juan4d.com.tehhijau456.com
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • www.juan4d.com.tehhijau456.com
Alternative Names
  • *.atta77.net
  • *.atta88slot.org
  • *.com.tehhijau456.com
  • *.juan4d.com
  • *.juan4d.net
  • *.juan4d.org
  • *.net.tehhijau456.com
  • *.org.tehhijau456.com
  • atta77.net
  • atta88slot.org
  • juan4d.com
  • juan4d.net
  • juan4d.org
  • www.atta77.net.tehhijau456.com
  • www.atta88slot.org.tehhijau456.com
  • www.juan4d.com.tehhijau456.com
  • www.juan4d.net.tehhijau456.com
  • www.juan4d.org.tehhijau456.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2025-01-23
Not valid after
2025-04-23
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
1B:FA:94:BE:4E:48:9C:CE:A8:30:3D:01:EE:97:BC:4E:88:50:BE:7F:62:99:C4:23:C4:44:0F:B7:3F:18:0B:31
SHA1
7B:A5:98:89:85:96:DF:55:2A:C0:86:B3:EB:A8:8A:4D:EE:27:72:39
X509v3 extensions
subjectKeyIdentifier
  • F7:06:00:32:B1:E8:7A:57:7E:F3:29:4C:C1:7E:E2:32:13:E5:5A:9E
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 : 7D:59:1E:12:E1:78:2A:7B:1C:61:67:7C:5E:FD:F8:D0:
  • 87:5C:14:A0:4E:95:9E:B9:03:2F:D9:0E:8C:2E:79:B8
  • Timestamp : Jan 23 20:12:16.622 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:80:B7:2F:A6:1A:42:1A:A7:B0:99:05:
  • 5E:65:75:39:79:66:CA:D6:D0:32:C4:19:3E:66:29:34:
  • C5:95:1D:E7:E4:02:21:00:EA:37:23:91:30:E8:B2:92:
  • B1:03:BC:3F:0E:71:19:D8:D2:0B:61:85:7F:75:E5:87:
  • E5:5A:EF:8D:4A:61:F2:14
  • 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 23 20:12:16.874 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:94:54:CF:29:20:F4:DC:7E:32:3A:C8:
  • D6:DB:A3:93:90:B8:40:A2:88:51:F6:50:0D:45:8E:4D:
  • 87:D3:DA:25:9E:02:20:29:77:E0:FC:FB:59:7C:71:E4:
  • 9D:FA:8C:57:B4:DF:D5:86:B8:5B:59:CD:DA:34:86:A7:
  • F5:BE:05:E2:87:6B:BF