SSL-Tools

SSL check results of jmvz.net

NEW You can also bulk check multiple servers.

Discover if the mail servers for jmvz.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 Wed, 17 Sep 2025 03:16:44 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mx1.jmvz.net
212.24.101.28
Results incomplete
10 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s
mx2.jmvz.net
154.16.202.239
 20
supported
mail.jmvz.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
3 s
mx3.jmvz.net
194.135.84.117
Results incomplete
30 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.jmvz.net

Certificate chain
  • mail.jmvz.net
    • remaining
    • 256 bit
    • ecdsa-with-SHA384
      • E8
        • remaining
        • 384 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.jmvz.net
Alternative Names
  • mail.jmvz.net
  • mx1.jmvz.net
  • mx2.jmvz.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • E8
validity period
Not valid before
2025-08-22
Not valid after
2025-11-20
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
1E:CC:D1:87:56:11:20:48:7D:04:29:30:77:FA:7C:BD:70:A1:8B:7E:27:4C:48:84:A4:4B:9E:CA:FB:03:37:47
SHA1
76:33:2A:87:38:D3:6A:1E:4F:AE:2D:89:F5:A5:E2:50:F5:FF:4A:42
X509v3 extensions
subjectKeyIdentifier
  • FB:F0:C2:AC:BD:5B:5D:C5:DA:F3:D5:85:66:AC:08:4E:1C:77:29:3E
authorityKeyIdentifier
  • keyid:8F:0D:13:A2:F6:2E:7E:D1:50:6C:33:18:38:5D:59:8E:23:72:91:CA
authorityInfoAccess
  • CA Issuers - URI:http://e8.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://e8.c.lencr.org/81.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 0D:E1:F2:30:2B:D3:0D:C1:40:62:12:09:EA:55:2E:FC:
  • 47:74:7C:B1:D7:E9:30:EF:0E:42:1E:B4:7E:4E:AA:34
  • Timestamp : Aug 22 23:27:51.485 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:41:1C:9F:D2:CB:D3:3A:DB:23:E2:84:54:
  • 86:62:96:96:E0:5C:61:23:CD:D9:9A:3B:85:34:1D:31:
  • F0:4D:CE:5F:02:20:37:94:26:B8:1A:E0:34:84:39:33:
  • 16:81:47:01:0F:46:7B:FB:F5:0F:8F:D5:3A:B9:F0:CC:
  • 50:B1:62:D1:81:12
  • 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 : Aug 22 23:27:51.486 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:57:8A:FD:E6:E1:18:56:DE:8A:FA:E4:67:
  • 13:B8:34:52:56:76:AA:47:FD:CA:B9:84:28:B2:6D:57:
  • E5:AB:8F:39:02:21:00:82:3A:D3:D5:1B:C8:83:54:86:
  • F2:61:52:A7:BB:71:99:71:37:50:4C:F7:95:B8:EB:EA:
  • 35:C7:69:1D:84:98:8F