Our website https://www.enquetesmaken.com is incomprehensibly being flagged with "Medium Risk". We have thus signed up at siteadvisor.com in order to rectify this false assessment. For that, we need to verify ownership by uploading a specific file to the root folder of our website. We have done so, but SiteAdvisor is not able to confirm ownership. It looks for following file:
But since our (secure) website is forcing all traffic to https / SSL, SiteAdvisor seems not to be able to verify our ownership, even though there is an automatic redirect to it.
Here is a screencast of the full problem: http://doc.enuvo.ch/d87e8510def276bab1380bf3db089e44.gif
Our website is absolutely secure, and we would like to remove this warning as soon as possible. Can anyone look into this?
Thank you very much.
PS: We cannot stop the automatic redirect to https.
We contacted them via their contact form, but we just received a bounce message:
Remote Server returned '550 5.1.1 RESOLVER.ADR.RecipNotFound; not found'
Here is a screenshot: http://doc.enuvo.ch/6d73f2398757bf2039346fdbd8d1a53a.jpg
I'm looking into it but I've not seen this happen before. I may have to wait until after the conference call on Monday before I can offer any advice. I'll make sure to add this to the call agenda.
I raised the question of SiteAdvisor not finding the file you placed in the topmost level of your server's file system on the conference call. There have been other cases in the past where the file could not be read or found by Siteadvisor, but there may be more than one reason why this happens. I'll let the SiteAdvisor team look at this and give you some suggestions.
As for the error 550 email bounce message, it seems this is quite a common occurrence. Microsoft's Outlook, Exchange and Office 365 forums have many questions about it, and I've found a typical Q+A exchange from a forum, and also a Microsoft document detailing a fix. Read these and try the suggested fixes, see if they work.
Ok, we will wait then. Thank you.
As for the bouce message: Outlook is only our email client. Our emails are sent and received via Google for Business, so it might have been something temporary.