title: Phishing Detected! warning in Chrome
body: <p>I have encountered the "Phishing Detected" warning in Chrome browser on my dev site. Interestingly I don't encounter the same warning in Firefox or Safari even though, as far I can tell, they are using the same phishing database (although in Safari preferences it says "google safe browsing service is unavailable"). I also don't encounter the warning on the same page of the production sites.</p>
  
  <p>It first popped up on a new account verification page I created which amongst other things asked users to confirm their PayPal account with the <a href="https://developer.paypal.com/webapps/developer/docs/classic/api/adaptive-accounts/GetVerifiedStatus_API_Operation/" rel="noreferrer">GetVerifiedStatus API</a>. This requires only name and email.</p>
  
  <p>I have also encountered the warning on a configuration page which asks for the PayPal email address which the user wishes to receive payments to. </p>
  
  <p>Neither page requests a password or any other data that would be considered a secret. </p>
  
  <p>As you might gather I have zeroed in on a potential false positive on the PayPal portion of the content as if perhaps I am phishing for PayPal information beyond the payers email address. There has been no malicious code injection or any such thing. Even when i've removed all content from the page the warning is still present. </p>
  
  <p>I <a href="http://www.google.com/safebrowsing/report_error/" rel="noreferrer">reported</a> the first incorrect detection to Google, and intend to do the same for the second incident, however what I really want to clear up is:</p>
  
  <ol>
  <li>What content can lead to this warning?</li>
  <li>How can I avoid it in the future? </li>
  <li>How can I get some info from the "authorities" on which urls are blocked? (Webmaster Tools is not showing warnings for the dev site)</li>
  <li>How can I flush my local cache of "bad sites" in case I want to re-test?</li>
  </ol>
  
  <p>Clearly having a massive red alert presented to a user on a production site would be disastrous, and there is a (perhaps deliberate) lack of information about how this safe browsing service actually works.</p>