SSL-Tools

SSL check results of myipv6tlan.ws

NEW You can also bulk check multiple servers.

Discover if the mail servers for myipv6tlan.ws 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, 14 Jun 2025 05:31:36 +0000

The mailservers of myipv6tlan.ws can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @myipv6tlan.ws addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.hope-mail.com
5.161.182.241
 1
supported
mail.hope-mail.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.0
  • SSLv3
25 s
mail.hope-mail.com
159.65.192.215
 1
supported
mail.hope-mail.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
21 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.hope-mail.com

Certificate chain
  • mail.hope-mail.com
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.hope-mail.com
Alternative Names
  • mail.hope-mail.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2025-04-07
Not valid after
2025-07-06
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
1C:FD:05:DC:09:1E:1D:34:55:E9:18:86:88:5A:C9:4B:A0:09:B2:37:B0:B7:12:0B:5D:90:25:58:D2:BD:D3:FE
SHA1
FB:31:A6:43:6F:02:21:69:EA:E7:51:D7:EF:3B:44:F5:45:DD:7E:E4
X509v3 extensions
subjectKeyIdentifier
  • E3:AB:B6:41:E4:A6:77:EB:AA:D7:1B:88:FB:F1:71:97:B3:B5:9B:DC
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
crlDistributionPoints
  • Full Name:
  • URI:http://r10.c.lencr.org/3.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : DD:DC:CA:34:95:D7:E1:16:05:E7:95:32:FA:C7:9F:F8:
  • 3D:1C:50:DF:DB:00:3A:14:12:76:0A:2C:AC:BB:C8:2A
  • Timestamp : Apr 7 06:06:49.953 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:2D:C4:A5:5F:A9:30:85:7D:39:E3:4A:36:
  • 29:14:3E:FB:AA:33:61:FC:1A:57:34:61:D6:41:91:75:
  • DC:6D:12:60:02:21:00:87:6E:6C:49:98:79:C4:B0:A7:
  • 64:DC:37:13:3A:05:23:4F:CF:C7:54:E2:16:07:32:6B:
  • 2F:58:40:01:3F:08:7C
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CC:FB:0F:6A:85:71:09:65:FE:95:9B:53:CE:E9:B2:7C:
  • 22:E9:85:5C:0D:97:8D:B6:A9:7E:54:C0:FE:4C:0D:B0
  • Timestamp : Apr 7 06:06:51.906 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:2A:6A:25:92:3B:32:35:1C:15:84:B1:9F:
  • 71:AB:8F:5F:00:11:06:42:34:50:E9:F5:63:0D:C3:01:
  • 46:A1:FE:FD:02:21:00:90:37:4D:F8:54:2D:5F:8C:C0:
  • 45:31:81:4C:C3:E9:89:E5:0D:3D:E7:77:78:30:6D:1D:
  • CB:C9:5D:EF:24:D2:FB