July 1, 2008

Google Blocking Spectator [Dan Collins]

More Baracky Fairness Doctrine fun:

Safe Browsing
Diagnostic page for www.spectator.org/

What is the current listing status for www.spectator.org/?

Site is listed as suspicious – visiting this web site may harm your computer.

What happened when Google visited this site?

Of the 95 pages we tested on the site over the past 90 days, 1 page(s) resulted in malicious software being downloaded and installed without user consent. The last time Google visited this site was on 06/30/2008, and the last time suspicious content was found on this site was on 04/05/2008.

Malicious software is hosted on 2 domain(s), including h25.6600.org, dns5.8866.org.

Has this site acted as an intermediary resulting in further distribution of malware?

Over the past 90 days, www.spectator.org/ did not appear to function as an intermediary for the infection of any sites.

Has this site hosted malware?

No, this site has not hosted malicious software over the past 90 days.

How did this happen?

In some cases, third parties can add malicious code to legitimate sites, which would cause us to show the warning message.

Next steps:

* Return to the previous page.
* If you are the owner of this web site, you can request a review of your site using Google Webmaster Tools. More information about the review process is available in Google’s Webmaster Help Center.

Posted by Dan Collins @ 9:28pm

Comments (16)

  1. Jeeves and the Dogpile folks need to get off their asses and make their search engines as easy to use as Google, and like quick. I prefer to not use Google as my engine of choice, but often end up there after searching elsewhere and hitting a dead-end.

  2. You might try clusty.com. It seems to work fairly well. However, I almost always go to google out of habit.

  3. I turned off the “attack site” filter in Firefox because of that very same warning.

    I still use Google (for pretty much the same reasons as jmflynny), but I use ad-blocking extensions so I don’t see their ads. And I use the free version of Google Earth.

  4. I had that earlier tonight and after reading it I figured that the obamabots had flagged it. Both and LinkedIn and Google engineering teams are in the tank for Obama. What a bunch of maroons

  5. McAffee site advisor blocks it, too.

  6. http://www.altavista.com

    Particularly good with “sciencey” searches.


  7. Fairness Doctrine Trial Run number 2.

  8. Ya’ll are crazy. Wingnuts will be able to distribute malware after the election just fine.

  9. Make IxQuick your homepage. Since September 2006, this Dutch server has been untraceably deleting all clients’ browser traffic. Try “drilling down” for something that’s not there!

    As for YouTube and its ilk, or even cellphones for that matter, anyone who trusts privacy pledges is in for a rude shock. Absent encryption, there are ways to frustrate blanket intrusions but since they entail time and effort few prospective victims ever bother.

    Archie Bunker to the FBI: “I’m innocent!”
    FBI to Archie Bunker: “Innocent of what?”

  10. Thanks, John, for the IxQuick tip. And dittos on the privacy comments.

  11. Guys, not to spoil your fun, but as a computer security guy I got curious about this, went ahead through, and discovered the issue is one of the ad servers serving ads into Spectator. Google isn’t blocking Spectator per se, it’s reacting to one of the embedded adverts.

  12. http://www.clusty.com (mentioned above) works at least as well as google, and organizes results by topic in the left hand side bar.

    Here’s the results for protein wisdom:


    Notice the top result is the site itself.

    “Don’t be evil – don’t use Google.”

  13. Google isn’t blocking Spectator per se, it’s reacting to one of the embedded adverts.

    Bad implementation by Google (as in, blocking the entire site because of an ad)? I’m shocked.

  14. McGeehee, you tell me how Google is supposed to know whether an embedded ad is being served by some malicious advert company or being served from the owners of the website.

  15. They got the tinfoil hat crowd in a rush to install malware. Looks like they couldn’t have implemented it better.