11–20 of 85 posts
Hmm that sucks. All I can suggest is you systematically remove content from the page until the error stops - this way perhaps you can identify the offending content (or combination of content which aggregates to an "offence")
Report an incorrect phishing warning at http://www.google.com/safebrowsing/report_error/ . If you received a phishing warning but believe that this is actually a legitimate page, please complete the form below to report the error to Google. Information about your report will be maintained in accordance with Google's privacy policy. Try posting a thread on the Google forums and decribe the false positive in neutral te…
Unfortunately we have done all that. It is not a domain issue or safe browsing issue. The best analogy here is let us say lot of customers run a default drupal or joomla site under their domain and Google chrome show these sites as phishing site.
maybe you caught a malware on your computer. did you try from different machines?
External dependencies on that page? Anything being pulled from a domain that might have made the list? It might not be specific to your page, it might be on a JS library you are including.
The irony is we use GWT for our UI which is used by many google products. when we search in web the closest issue we found if from a joomla forum: http://forum.joomla.org/viewtopic.php?f=621&t=802284
Hey there, I actually worked for a "competitor" of yours at one time in my career. We had a very similar problem, turned out that one of our users shared(probably unknowingly) a file containing malware and probably posted it to their twitter or facebook(we had that feature built-in at the time). This URL was caught by a very popular anti-virus company, which posted it on their site. I guess the software phones-home t…
Hi, Our software is little different. It is a self-hosted software. It is hosted by our customers under different domain names in their infrastructure. So it is not the same domain or URL. For Example: Customer 1: fileshare.abcplumbing.com Customer 2: dataanywhere.peterlawfirm.com Thats the real problem here. It affects our customer installations under different domains. To some extent, we are fine if google is block…
External dependencies on that page? Anything being pulled from a domain that might have made the list? It might not be specific to your page, it might be on a JS library you are including.
You may also be interested in this article: https://medium.com/surveillance-state/32ba2b38c219
The next step for us is to hire PR and go public. We are spending 1500$ per month on google adwords now.
May be use that money to get some legal help. In a physical world it is a clear public defamation case.
Earlier quoted context omitted.
Hi, Our software is little different. It is a self-hosted software. It is hosted by our customers under different domain names in their infrastructure. So it is not the same domain or URL. For Example: Customer 1: fileshare.abcplumbing.com Customer 2: dataanywhere.peterlawfirm.com Thats the real problem here. It affects our customer installations under different domains. To some extent, we are fine if google is block…
Ah, we did have a feature sorta-kinda like that too... if you had your own domain you login on our webUI, enter in your own domain and if no other user had it, you'd get it. Then, you add a CNAME record pointing to us and we'd do certain things when we received the request depending on settings the customer provided during the domain-name setup. I think we used the Referrer in the request-headers. So I could point po…
The warning appears even in local IP/debug page.
Have you tried to produce a minimal version of the software to show the problem? If not do it now and post it on the Google Chrome Bug tracker: http://code.google.com/p/chromium/issues/list Other contact forms: Mailing Lists: http://www.chromium.org/developers/discussion-groups IRC Channel: http://dev.chromium.org/developers/irc
That failing, get money for them blocking a competitor. before downvoting, take the time to explain how this would be different from old good Google suing Microsoft just for not making their product use Google easier than it already allowed.
Earlier quoted context omitted.
Ah, we did have a feature sorta-kinda like that too... if you had your own domain you login on our webUI, enter in your own domain and if no other user had it, you'd get it. Then, you add a CNAME record pointing to us and we'd do certain things when we received the request depending on settings the customer provided during the domain-name setup. I think we used the Referrer in the request-headers. So I could point po…
We are not a SaaS or PaaS business. The software itself is hosted by the end customer in thier infrastructure. The warning appears even in local IP/debug page.