SSL-Tools

SSL check results of netsyms.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for netsyms.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 Wed, 18 Dec 2024 08:12:58 +0000

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

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

/mailservers/netsyms.com

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.netsyms.net
206.127.79.90
 10
supported
mail.netsyms.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
7 s
mail2.netsyms.net
172.232.161.82
Results incomplete
50
unsupported
not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
2 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.netsyms.net

Certificate chain
  • mail.netsyms.net
    • 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.netsyms.net
Alternative Names
  • mail.netsyms.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2024-11-18
Not valid after
2025-02-16
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
38:79:EC:D9:16:48:9B:E8:20:7D:D8:0E:DB:6A:7F:56:BD:C6:4A:B1:8A:7F:D3:5B:E2:D6:CA:57:41:08:90:3B
SHA1
67:E4:C5:02:9C:D6:9B:5E:24:BB:FF:1C:33:E8:A8:D7:9F:30:04:CD
X509v3 extensions
subjectKeyIdentifier
  • F9:4C:2A:96:76:8F:80:26:24:7B:44:00:70:A9:EE:5A:79:27:9F:82
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
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CF:11:56:EE:D5:2E:7C:AF:F3:87:5B:D9:69:2E:9B:E9:
  • 1A:71:67:4A:B0:17:EC:AC:01:D2:5B:77:CE:CC:3B:08
  • Timestamp : Nov 18 10:05:12.365 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:5A:40:8C:C3:18:86:9D:72:DA:2A:90:7B:
  • A5:CD:D6:19:C4:EA:2F:FE:9F:97:33:D1:AE:EE:9A:6C:
  • B0:8D:D1:B4:02:21:00:E0:B7:EC:57:EF:B0:B0:7D:09:
  • A9:56:12:3E:1C:DF:60:6C:E7:C0:8B:93:9D:10:16:E8:
  • 4B:63:9D:03:DA:38:9E
  • 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 : Nov 18 10:05:12.704 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:E0:17:46:00:0D:CA:16:30:21:8A:F0:
  • B0:55:51:68:D5:DD:0B:8C:EE:49:70:8E:5F:C6:E4:E1:
  • 55:D4:04:3D:EB:02:20:07:D9:CA:68:B2:0C:79:CE:A5:
  • CE:B3:98:B9:3F:4A:AD:99:02:34:25:9A:43:57:AD:8D:
  • BD:5F:75:7C:4D:1E:D5