How to Remove a Google Security Warning From Your Website

Remove a Google security warning

Clean the complete compromise and close the entry point before requesting a review

Google Search Console’s Security issues report is the source of truth for a warning on a verified site. Review the issue type and sample URLs, preserve evidence, clean every affected area and fix the vulnerable password, account or software that allowed the compromise.

DIAGNOSESecurity issues reportUse issue types and sample URLs
CLEANRemove all compromiseThen close the original weakness
REVIEWSubmit after fixingGoogle controls review timing

How do I recover a site flagged by Google?

  1. 1
    Open Security issues

    Verify ownership in Search Console, check for unknown owners and record each listed issue type and sample URL.

  2. 2
    Protect evidence and access

    Save useful logs, change compromised credentials from a clean device and remove unfamiliar administrators or access keys.

  3. 3
    Clean the whole site

    Remove injected pages, redirects, scripts, downloads and backdoors. Restore known-good files where appropriate and check databases and scheduled tasks.

  4. 4
    Fix the cause

    Update the CMS and extensions, remove abandoned software, correct permissions and secure every account that could reintroduce the problem.

How do I request a Google review?

Test the reported URLs

Confirm the harmful content, redirect or download is gone and that the pages now return the intended result.

Check beyond the samples

Google may show only examples. Search files, database content, users and indexed pages for related compromise.

Explain the repair

Describe what was compromised, what you removed and how the original access route was secured.

Submit once

Use the review control in Search Console. Review timing varies, so do not promise a same-day removal or repeatedly resubmit.

Why can the browser warning remain after a clean review?

Search Console, Safe Browsing data and browser caches are separate systems. Status changes can take time to appear everywhere. Confirm the Search Console result, test the exact hostname and URL, and avoid making unrelated DNS or certificate changes while waiting.

Reduce the chance of another warning

Update applications and extensions promptly.

Remove unused accounts, plugins, themes and old test sites.

Use unique passwords and multi-factor authentication where available.

Keep tested off-site backups and monitor unexpected file changes.

Review Search Console messages and security reports regularly.

Need recovery help?

Send the warning type, sample URL and incident time

Do not include passwords in the ticket.

Why do I get a blank page or 500 Internal Server error?

Re: Blank page or 500 Internal Server error

The problems are caused by your code failing. A blank page is usually a PHP error so checking your PHP error_log within your Plesk panel will provide causes as to what the problem is. Usually the best course of action is to re-upload your website or restore from a recent backup.

A 500 internal server error is usually related to a scripting issue using CGI or Perl scripts. Again, this means the script is unable to execute and this generic error which does not give much away means you need to check your scripts or simply upload / restore to your last working copy.

Both of these errors means a quick call to your web designer or just restore from your latest backup in the Backup manager (You do take backups right?!)

UK-Cheapest Ends Ensim Support

As of June 1st, 2012, UK Cheapest no longer be providing support for Ensim powered servers. If you are currently using Ensim, we highly recommend you migrate to Parallels Plesk.

Ensim End Of Life

The last version of Ensim was released on 4/16/2009. Since then there have been a few hot patches but no significant upgrades. Ensim 4 has not been updated since 2007. If you are still using these versions of Ensim, you likely are using an outdated OS. We recommend Red Hat Enterprise 5 and will soon be moving to Red Hat Enterprise 6 once software vendors release their updates for the new RHEL version.

Ensim Mandatory Migrations

We have been offering free upgrades to Plesk since December 2010  but now it’s time to make the final push.

Starting 1st June, any accounts remaining on Ensim will be automatically migrated to Parallels Plesk 10.x. This covers all remaining accounts on Microlite18 to 24 Ensim servers. This process will be complete by June 28th.

All Ensim accounts will remain accessable using your old login details until June 30th when they will be deleted.

If your domain name is not hosted with UK Cheapest, please change your domain name servers to:

  • ns.microlite11.com
  • ns2.microlite11.com

Your new Control Panel URL (still using your old login and password) will be:

Your username and password will remain unchanged.

The old Ensim control panels will still be available until June 30th using the links below:

Additional Differences

FTP – Use ftp.yourdomain.com instead of server.microliteXX.com as your FTP hostname. Your FTP username is now in the format “adminXXXXX” and not “adminXXXXX@yourdomain.com”.

Email – Your email passwords and usernames will remain unchanged.

Webmail – Your default webmail (Horde) can be accessed through http://webmail.yourdomain.com. You will no longer find webmail at www.yourdomain.com/webmail.

Squirrelmail – This application is no longer automatically installed. You can install squirrelmail using the web applications installer within your new Plesk control panel.

Backups – Your old backups will be incompatible with Plesk, please make additiona FTP copies of your data if required.

Frontpage – It is no longer possible to upload using FrontPage HTTP. If you still use Frontpage, you must upload using FrontPage FTP or any other FTP client to upload your files.

Migration – we will handle the conversion and migration of your data as efficiently as possible. If you are using Ensim specific code you will need to make changes to your code to continue functionality in Plesk.

Support – If you require any help or support after the migration, please log a ticket with the helpdesk and ask for “Ensim Migration” support. Ensim support is not available through the Live Support facility.

How to parse PHP in HTML

To parse PHP code inside a .html file you will need to a create a .htaccess file in your document root directory /httpdocs and insert the following code:

AddHandler php-script .html .htm

How to import a MySQL database using phpMyAdmin

To import a MySQL database you can use phpMyAdmin which is available in your Plesk control panel.

1) Firstly, you will need  to create the database in Plesk that you would like to import the SQL file to.

– Video tutorial: How to create a database in Plesk

2) Open up phpMyAdmin inside Plesk

– Go to Databases

– Select the Database

– Go to Webadmin

3) Once you are in phpMyAdmin, Select the Database on the left hand bar.

4) Go to import

5) Click the ‘Choose’ button to browse the location of the text file

6) Click “Go” to import the SQL file

If you experience any problems, please log a ticket with our Help Desk.