We all know the importance of testing your site after a migration to your hosting account. More often than not we wish to do this prior to updating the domain’s DNS nameservers to Arvixe. We have a few options that allow us to do this – via the control panel, as well as by modifying your local PC’s hosts file.
Both cPanel and Website Panel provide temporary URLs via the hostname.
As a 6Scan customer, you can proudly display the 6Scan Security Seal on your website. The 6Scan Security Seal conveys to your users that you take your site’s security seriously, and is proven to increase trust and boost conversion rates.
You can get the appropriate code for the security seal by logging into your cPanel, clicking on 6Scan icon, then Dashboard. Finally, click on settings and the ‘Security Seal’ tab. Simply code the entire code block inside of the
tag of your website.
By now, you’ve probably already had 6Scan enabled on your website for some time. Chances are you’ve received some sort of notification (SMS, or via Email) that vulnerabilities have been found on your website. Don’t panic, as 6Scan makes resolving these issues easy. As you can see from the screenshot below, I’ve created a test website using an older version of WordPress. 6 vulnerabilities have been found.
Now feels like a good time to mention why you need to keep your scripts/applications updated to the latest version at all times. There’s a few reasons these applications are updated quite often.
- Release new features and improvements
- Patch vulnerabilities, and further secure the code
With a subscription to 6Scan (not required) these vulnerabilities can be fixed automatically upon discovery. Otherwise, the free version you simply click each vulnerability and get a detailed explanation of the problem, and how to fix it. See below —
Clicking the ‘Manual Fix’ button opens a popup window that tells you which file to edit, and how to edit it. In the case of this example WordPress installation, upgrading to the latest version would be the best choice rather than manually editing the files. There is also a ‘Technical Details’ link that provides information (if available) about the technical issue related to the vulnerability.
Easy right? That’s it for managing vulnerabilities.