SSL-Tools

SSL check results of myipv6lan.ws

NEW You can also bulk check multiple servers.

Discover if the mail servers for myipv6lan.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 Mon, 16 Jun 2025 00:30:32 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.myipv6lan.ws
2001:4dd0:3d44::5054:ff:febc:fa65
 10
supported
*.myipv6lan.ws
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
8 s
mail.myipv6lan.ws
87.79.79.60
 10
supported
*.myipv6lan.ws
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
7 s

Outgoing Mails

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

Certificates

First seen at:

CN=*.myipv6lan.ws

Certificate chain
  • *.myipv6lan.ws
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • *.myipv6lan.ws
Alternative Names
  • *.myipv6lan.ws
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2025-06-14
Not valid after
2025-09-12
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
FA:FD:37:46:25:EE:A1:81:61:81:6F:FE:1F:51:C7:7D:7F:3F:52:B7:88:18:F1:C9:37:CB:D5:AF:74:1F:98:3A
SHA1
F7:B5:E1:0D:1D:23:D4:BC:9E:5F:E6:4B:6C:6A:77:41:9D:30:D1:5A
X509v3 extensions
subjectKeyIdentifier
  • AB:FD:3A:F6:8F:F0:34:63:A7:D3:EE:4B:5C:AF:EC:36:9F:64:CD:E0
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • CA Issuers - URI:http://r11.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r11.c.lencr.org/48.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 12:F1:4E:34:BD:53:72:4C:84:06:19:C3:8F:3F:7A:13:
  • F8:E7:B5:62:87:88:9C:6D:30:05:84:EB:E5:86:26:3A
  • Timestamp : Jun 14 05:27:59.790 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:BD:25:1A:FA:C0:57:29:64:2E:F7:4D:
  • 33:FA:26:2E:E4:B9:07:F3:F8:FD:CC:B3:A6:F9:C1:69:
  • 12:D4:F7:C9:9F:02:20:0A:86:7B:01:D7:94:1D:C1:41:
  • B9:A3:2F:C1:1F:94:F3:1F:FB:02:B6:6C:3C:A0:05:78:
  • BF:80:37:A9:C3:5E:E8
  • 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 : Jun 14 05:28:01.816 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:E5:F6:DC:4E:63:99:20:34:70:95:ED:
  • 2D:CD:B4:01:2F:4A:33:7E:6B:4C:35:19:98:EC:C5:B8:
  • 6A:18:CD:B4:A1:02:21:00:FE:D0:27:7A:BA:8D:46:8B:
  • 8F:64:96:12:B5:E8:9B:D3:CF:5B:E7:9A:1C:2B:E1:5B:
  • 12:A6:F6:CC:70:9C:B3:7A