Insecure server and WordPress on GoDaddy site...

See abuse going on: https://www.abuseipdb.com/check/198.20.107.26
See: http://toolbar.netcraft.com/site_report?url=http%3A%2F%2Fserver122.shopaserver.com%2Fcgi-sys%2Fdefaultwebpage.cgi
Insecurity: Warnings
RC4
Your server’s encryption settings are vulnerable. This server uses the RC4 cipher algorithm which is not secure. More information.
SSLv3
Your server’s encryption settings are vulnerable. This server uses the SSLv3 protocol, which is not secure. More information.
TLS1.2
This server is vulnerable to a TLS renegotiation attack.
This server is vulnerable to:
Poodle (SSLv3 protocol)
This server is vulnerable to a Poodle (SSLv3) attack.

F-Status and recommended change: https://observatory.mozilla.org/analyze.html?host=shopaserver.com

WordPress Version
4.5.8
Version does not appear to be latest

Warning User Enumeration is possible
The first two user ID’s were tested to determine if user enumeration is possible.

ID User Login
1 shopaserver shopaserver
2 None
It is recommended to rename the admin user account to reduce the chance of brute force attacks occurring. As this will reduce the chance of automated password attackers gaining access. However it is important to understand that if the author archives are enabled it is usually possible to enumerate all users within a WordPress installation.

Warning Directory Indexing Enabled
In the test we attempted to list the directory contents of the uploads and plugins folders to determine if Directory Indexing is enabled. This is an information leakage vulnerability that can reveal sensitive information regarding your site configuration or content.

/wp-content/uploads/ enabled
/wp-content/plugins/ disabled
Directory indexing was tested on the /wp-content/uploads/ and /wp-content/plugins/ directores. Note that other directories may have this web server feature enabled, so ensure you check other folders in your installation. It is good practice to ensure directory indexing is disabled for your full WordPress installation either through the web server configuration or .htaccess.

polonus (volunteer website security analyst and website error-hunter)