It was a server issue. I've been told the problem has been solved but it can take some time (24 hrs) for browsers to acknowledge this and stop posting the warning. As of this morning I was still getting the warning when using Chrome browser but had no problems with IE.

Dan-at-North wrote:It was a server issue. I've been told the problem has been solved but it can take some time (24 hrs) for browsers to acknowledge this and stop posting the warning. As of this morning I was still getting the warning when using Chrome browser but had no problems with IE.