DANGER Warning on clients site AGAIN!

My client is understandably completely FREAKING out~ !
His new website was getting danger errors when clicking on link of the domain name a few days ago. I believe I fixed the problem … I think I ahad stupidly added an extar .com when editing the .htaccess file in Rpid Weaver publishing (To get the little padlock in the address bar)

SO… I believed I had corrected it. All was well … until he sent the link to the big cheese … that he basicly had made the site for …in the hope of sellling art… He sent the link and … YUP… huge red warning page. Deceptive site ahead. BACK TO SAFTY !
OMG ! I just dont know what to do.

I host the site as an add on domain to my hosting pkg at Chillidog and they can see nothing wrong.
I dont dare contact my client again until I have some sort of answer

Looks fine from here in the USA.

1 Like

No warning here in Switzerland

1 Like

All good here in UK using Firefox, Safari, Chrome and Opera, padlock showing on all browsers.

Screenshot 2022-12-04 at 07.13.14

1 Like

All good here on iPad Germany

This is possibly, most likely, because the ISP or a service the ISP uses, has blacklisted the site.

This happened a year or two ago to one of my clients.

Anyone on BT internet couldn’t access the site. This included ISPs who piggy back on BT. Everyone else could access it.

The only solution that worked in the end was a change of domain, as no matter what we did, BT wouldn’t update their blacklist files.

Incidentally, it had nothing to do with the site, but because they attempted to send out bulk emails via their BT Internet email account.

1 Like

I notice that if you Google scottgriffinfineart you find this:


www.scottgriffinfineart.com.com. Coming soon.

So that may be what the client is doing. Google will forget this site soon.

Currently the site appears if http://scottgriffinfineart.com , https://scottgriffinfineart.com, http://www.scottgriffinfineart.com or https://www.scottgriffinfineart.com are entered into an address bar. So the htaccess redirects you created are working correctly.

I think what you were editing were these redirects and nothing to do with HTTPS, which is a function set in your cPanel.

What may have happened, is that when using the RW htaccess editor, you overwrote the existing htaccess file and important stuff which is often security related, was overwriten. Some hosts add this stuff to the end of the htaccess file and this should not be edited or deleted. As a fail safe, they may check each htasccess file and add in teh code if it missing or corrupted. During the time that the original file was replaced and the host restoring the security code, the client may have visited the site when the site was not secure. I suggest that instead of using RW to edit the htaccess file next time, use an FTP App to edit the file live in the server.

Anyway, now it appears to be working OK so I suggest sending the client a link to click on and to open in a new Private window to clear their cache.

Site’s is looking great by the way.

PS here a cool on line tool - https://www.htaccessbuilder.com

1 Like

Along the same lines, I had a similar, but different issue recently, that everyone should be aware of. I have a site that has been on the Internet for years, and has been HTTPS for many years as well. There has never been any security issues with the site, ever.

I recently sent the link to a friend, who immediately wrote me back saying he’d received a note saying it was a dangerous site and he elected not to proceed. I checked my Google Search Console- it was clean. The issue turned out to be that Norton was was reporting the site as a phishing site. So…the only people who were seeing alerts were people who have the Norton Safe Browsing extension installed. Grrrr. On the up-side there was a way to contest this to Norton, with a promise of a response within two days. Sure enough, within two days, they replied that they had inspected the site and had given it a clean bill of health / removed the alert.


Thank you everyone above so much for going above and beyond in helping me out here!
I think it must have been a case of very unfortunate timing … and after the hooha I created by not concentraing when I edited the htaccess last week … the big red caution page was a freak out! But thanksto you all I have been able to calm things down a bit!

1 Like