SSL-Tools

SSL check results of niversoft.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for niversoft.com 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, 31 Aug 2026 00:30:30 +0000

We can not guarantee a secure connection to the mailservers of niversoft.com!

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

/mailservers/niversoft.com

Servers

Incoming Mails

These servers are responsible for incoming mails to @niversoft.com addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
niversoft.3sys.qc.ca
207.134.55.86
Results incomplete
0
supported
not checked
DANE
missing
PFS
not checked
Heartbleed
not vulnerable
Weak ciphers
not checked
11 s
mail.contactlist.us
66.94.118.177
 5
supported
contactlist.us
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
21 s

Outgoing Mails

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

Certificates

First seen at:

CN=contactlist.us

Certificate chain
  • contactlist.us
    • remaining
    • 3072 bit
    • sha256WithRSAEncryption
      • YR1
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
        • Unknown Authority
          Root YR
Subject
Common Name (CN)
  • contactlist.us
Alternative Names
  • contactlist.us
  • mail.contactlist.us
  • www.contactlist.us
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • YR1
validity period
Not valid before
2026-08-21
Not valid after
2026-11-19
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
Fingerprints
SHA256
72:1D:78:11:50:CB:2A:4F:AC:24:DC:4F:79:FB:32:9F:35:A7:C0:BF:78:3C:DF:0E:58:98:FB:DF:72:ED:56:B2
SHA1
4D:07:0C:F1:F7:DA:59:0B:2C:EE:52:C4:0D:FD:38:2B:A8:2B:0B:B8
X509v3 extensions
subjectKeyIdentifier
  • AD:DD:6A:C5:9E:74:DC:F8:F3:B7:C1:E9:B8:BB:1D:CE:B3:0A:D1:27
authorityKeyIdentifier
  • keyid:1F:2F:35:BE:46:14:82:CD:40:B1:AE:79:2C:55:78:FA:F7:D4:68:FB
authorityInfoAccess
  • CA Issuers - URI:http://yr1.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://yr1.c.lencr.org/115.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 6C:FE:50:19:43:A8:5E:A9:16:BC:52:D1:33:E4:DC:C9:
  • 1E:F1:41:1C:7D:25:84:20:D1:73:80:9E:18:18:EB:3A
  • Timestamp : Aug 21 18:45:20.993 2026 GMT
  • Extensions: 00:00:05:00:22:3F:92:89
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:F1:BF:45:72:6C:51:87:2B:2B:16:22:
  • 6D:64:5F:5F:B6:01:4C:42:B2:EF:C9:64:4A:57:70:5C:
  • 29:D1:6E:48:CA:02:20:03:3F:47:3D:F8:01:8B:9D:81:
  • 60:77:87:CD:FE:7A:56:ED:6D:E2:44:B3:4F:7D:B1:CB:
  • F0:6E:6B:94:7E:23:FA
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 94:4E:43:87:FA:EC:C1:EF:81:F3:19:24:26:A8:18:65:
  • 01:C7:D3:5F:38:02:01:3F:72:67:7D:55:37:2E:19:D8
  • Timestamp : Aug 21 18:45:22.131 2026 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:ED:2A:0C:88:57:C5:F9:36:DC:CB:39:
  • AF:75:E7:93:45:7F:E6:E2:9A:CA:9C:95:49:D6:12:48:
  • 33:19:8D:B5:D5:02:20:4A:3F:E3:33:33:40:C6:E4:D0:
  • 02:7C:7C:EA:1E:C1:62:6F:08:CE:03:25:CE:1B:C4:A7:
  • DD:61:1E:2D:37:67:A7