# Google Weirdness?

**URL:** <https://boards.straightdope.com/t/google-weirdness/335210>\
**Category:** Factual Questions\
**Created:** [December 12, 2005, 3:37am UTC](https://boards.straightdope.com/t/google-weirdness/335210 "2005-12-12T03:37:05Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Q.E.D](https://avatars.discourse-cdn.com/v4/letter/q/51bf81/32.png) [@Q.E.D](https://boards.straightdope.com/u/Q.E.D)\
**Post date:** [December 12, 2005, 3:37am UTC](https://boards.straightdope.com/t/google-weirdness/335210/1 "2005-12-12T03:37:05Z")

</div>

Just a few minutes ago, I went to do some searching for some information pertaining to a GQ thread. My search parameter was: “nuclear powered satellite”, sans quotes. What came back was not the expected search results page, but this odd message:

> [@](#):
>
> ```
> **We're sorry...**
> 
> ... but we can't process your request right now. A computer virus or spyware application is sending us automated requests, and it appears that your computer or network has been infected.
> 
> We'll restore your access as quickly as possible, so try again soon. In the meantime, you might want to run a virus checker or spyware remover to make sure that your computer is free of viruses and other spurious software.
> 
> We apologize for the inconvenience, and hope we'll see you again on Google. 
> 
> ```

Da hell? Variations on that search parameter bring up a normal search results page. What little information I could find on there suggests that Google is blocking requests that are being used by some kind of worm, but I could not verify this through Google itself. What’s going on here?

---

<div class="post-metadata">

**Author:** ![Shagnasty](https://avatars.discourse-cdn.com/v4/letter/s/9dc877/32.png) [@Shagnasty](https://boards.straightdope.com/u/Shagnasty)\
**Post date:** [December 12, 2005, 3:44am UTC](https://boards.straightdope.com/t/google-weirdness/335210/2 "2005-12-12T03:44:53Z")

</div>

I don’t know. Your search worked for me.

---

<div class="post-metadata">

**Author:** ![What\_Exit](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/what_exit/32/10652_2.png) [@What\_Exit](https://boards.straightdope.com/u/What_Exit)\
**Post date:** [December 12, 2005, 3:47am UTC](https://boards.straightdope.com/t/google-weirdness/335210/3 "2005-12-12T03:47:11Z")

</div>

You might be infected with a virus that hi-jacks Google searches.

---

<div class="post-metadata">

**Author:** ![Q.E.D](https://avatars.discourse-cdn.com/v4/letter/q/51bf81/32.png) [@Q.E.D](https://boards.straightdope.com/u/Q.E.D)\
**Post date:** [December 12, 2005, 3:48am UTC](https://boards.straightdope.com/t/google-weirdness/335210/4 "2005-12-12T03:48:46Z")

</div>

Well, that’s even weirder, then. It’s still not working for me.

---

<div class="post-metadata">

**Author:** ![Q.E.D](https://avatars.discourse-cdn.com/v4/letter/q/51bf81/32.png) [@Q.E.D](https://boards.straightdope.com/u/Q.E.D)\
**Post date:** [December 12, 2005, 3:50am UTC](https://boards.straightdope.com/t/google-weirdness/335210/5 "2005-12-12T03:50:40Z")

</div>

> [@jrfranchi](#):
>
> You might be infected with a virus that hi-jacks Google searches.

Maybe, but why only that one? Every other search runs just fine.

---

<div class="post-metadata">

**Author:** ![Amp](https://avatars.discourse-cdn.com/v4/letter/a/6a8cbe/32.png) [@Amp](https://boards.straightdope.com/u/Amp)\
**Post date:** [December 12, 2005, 3:57am UTC](https://boards.straightdope.com/t/google-weirdness/335210/6 "2005-12-12T03:57:03Z")

</div>

Search works for me also.

---

<div class="post-metadata">

**Author:** ![What\_Exit](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/what_exit/32/10652_2.png) [@What\_Exit](https://boards.straightdope.com/u/What_Exit)\
**Post date:** [December 12, 2005, 3:57am UTC](https://boards.straightdope.com/t/google-weirdness/335210/7 "2005-12-12T03:57:13Z")

</div>

> [@Q.E.D.](#):
>
> Maybe, but why only that one? Every other search runs just fine.

A virus geek with a subtle sense of humor and mostly worried about a small trojan or backdoor to your PC? I don’t know, just a possibility.

Jim

---

<div class="post-metadata">

**Author:** ![mhendo](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/mhendo/32/3159_2.png) [@mhendo](https://boards.straightdope.com/u/mhendo)\
**Post date:** [December 12, 2005, 4:23am UTC](https://boards.straightdope.com/t/google-weirdness/335210/8 "2005-12-12T04:23:58Z")

</div>

I’ve had that message from Google once before.

Scans with various anti-malware programs, and an investigation of my HijackThis log showed nothing amiss with my system. After a few hours the problem went away and Google started working for me again.

I’ve no idea what the solution might be.

---

<div class="post-metadata">

**Author:** ![Nanoda](https://avatars.discourse-cdn.com/v4/letter/n/ce73a5/32.png) [@Nanoda](https://boards.straightdope.com/u/Nanoda)\
**Post date:** [December 12, 2005, 5:48am UTC](https://boards.straightdope.com/t/google-weirdness/335210/9 "2005-12-12T05:48:27Z")

</div>

Well if Google the error message (duh ;)), then you get pages like [this](http://computersandjunk.com/News/Tech-News/Google-Stops-Virus-Searches.html).

Apparently a virus infecting web servers is on the loose that uses Google to find more vulnerable web servers. It’s apparently called [Santy worm](http://news.com.com/Net+worm+using+Google+to+spread/2100-7349_3-5499725.html), and spreads through a service in phpBB.

I don’t know how Google would tell who is infected, so I don’t know why you’d get that error, other than perhaps Google is throttling queries by IP to slow the spread. Are you NATted, perhaps?

---

<div class="post-metadata">

**Author:** ![TellMeI\_mNotCrazy](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/tellmei_mnotcrazy/32/3419_2.png) [@TellMeI\_mNotCrazy](https://boards.straightdope.com/u/TellMeI_mNotCrazy)\
**Post date:** [December 12, 2005, 6:38am UTC](https://boards.straightdope.com/t/google-weirdness/335210/10 "2005-12-12T06:38:56Z")

</div>

I had the same problem a couple of months ago. I ran a spyware scan, removed a few things, and tried again, and it worked fine.

---

<div class="post-metadata">

**Author:** ![aldiboronti](https://avatars.discourse-cdn.com/v4/letter/a/9fc348/32.png) [@aldiboronti](https://boards.straightdope.com/u/aldiboronti)\
**Post date:** [December 12, 2005, 5:23pm UTC](https://boards.straightdope.com/t/google-weirdness/335210/11 "2005-12-12T17:23:14Z")

</div>

This message crops up on Google from time to time, often when their servers are overloaded. It has nothing at all to do with anything on your computer. Sure, you can scan for spyware, but you’ll find that even if you take no action Google will get back to normal.

---

<div class="post-metadata">

**Author:** ![SpectBrain](https://avatars.discourse-cdn.com/v4/letter/s/a87d85/32.png) [@SpectBrain](https://boards.straightdope.com/u/SpectBrain)\
**Post date:** [December 12, 2005, 6:55pm UTC](https://boards.straightdope.com/t/google-weirdness/335210/12 "2005-12-12T18:55:32Z")

</div>

it may be that that particular request and answer are cached on your computer. Try doing a reload with that query and see what happens.

---

<div class="post-metadata">

**Author:** ![Q.E.D](https://avatars.discourse-cdn.com/v4/letter/q/51bf81/32.png) [@Q.E.D](https://boards.straightdope.com/u/Q.E.D)\
**Post date:** [December 12, 2005, 8:54pm UTC](https://boards.straightdope.com/t/google-weirdness/335210/13 "2005-12-12T20:54:42Z")

</div>

Hmm. Still won’t work. It’s definitely nothing on my end. I’m not going to worry about it, since it’s only that one particular search that it barfs on.

---

<div class="post-metadata">

**Author:** ![Manduck](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/manduck/32/256_2.png) [@Manduck](https://boards.straightdope.com/u/Manduck)\
**Post date:** [December 12, 2005, 10:26pm UTC](https://boards.straightdope.com/t/google-weirdness/335210/14 "2005-12-12T22:26:01Z")

</div>

It’s my fault.

I bought Google stock this morning, so _naturally_ there is a thread about Google weirdness on the SDMB. It just had to happen.

---

<div class="post-metadata">

**Author:** ![Capt.Ridley\_s\_Shooting\_Party](https://avatars.discourse-cdn.com/v4/letter/c/cc9497/32.png) [@Capt.Ridley\_s\_Shooting\_Party](https://boards.straightdope.com/u/Capt.Ridley_s_Shooting_Party)\
**Post date:** [December 12, 2005, 11:56pm UTC](https://boards.straightdope.com/t/google-weirdness/335210/15 "2005-12-12T23:56:28Z")

</div>

Yeah, I’ve had this before. Trying again in a few minutes normally sorts it out.

---

<div class="post-metadata">

**Author:** ![alterego](https://avatars.discourse-cdn.com/v4/letter/a/6bbea6/32.png) [@alterego](https://boards.straightdope.com/u/alterego)\
**Post date:** [December 13, 2005, 12:39am UTC](https://boards.straightdope.com/t/google-weirdness/335210/16 "2005-12-13T00:39:43Z")

</div>

> [@Q.E.D.](#):
>
> My search parameter was: “nuclear powered satellite”, sans quotes.

Run your query through [here](http://www.webrankinfo.com/english/tools/google-data-centers.php) and see what the results are. Could be a single datacenter. I get that message quite often, but usually only when i’m using Google Calculator quite a bit in succession.

---

<div class="post-metadata">

**Author:** ![Mr.Blue\_Sky](https://avatars.discourse-cdn.com/v4/letter/m/d26b3c/32.png) [@Mr.Blue\_Sky](https://boards.straightdope.com/u/Mr.Blue_Sky)\
**Post date:** [December 13, 2005, 12:44am UTC](https://boards.straightdope.com/t/google-weirdness/335210/17 "2005-12-13T00:44:27Z")

</div>

I had a similar thing happen on the [Allmusic.com](http://Allmusic.com) site, but it went away after a few hours.

---

<div class="post-metadata">

**Author:** ![Q.E.D](https://avatars.discourse-cdn.com/v4/letter/q/51bf81/32.png) [@Q.E.D](https://boards.straightdope.com/u/Q.E.D)\
**Post date:** [December 13, 2005, 12:56am UTC](https://boards.straightdope.com/t/google-weirdness/335210/18 "2005-12-13T00:56:34Z")

</div>

> [@alterego](#):
>
> Run your query through [here](http://www.webrankinfo.com/english/tools/google-data-centers.php) and see what the results are. Could be a single datacenter.

Interesting. Seems to work on all of those. I also discovered that if I open a new window, load Google and run the search it works just fine. But it still will not run on the original instance of Firefox, which leads me to believe it’s a caching issue. Anyway, I’m good. Thanks for the info, folks.

---

<div class="post-metadata">

**Author:** ![ftg](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/ftg/32/2801_2.png) [@ftg](https://boards.straightdope.com/u/ftg)\
**Post date:** [December 13, 2005, 4:39am UTC](https://boards.straightdope.com/t/google-weirdness/335210/19 "2005-12-13T04:39:00Z")

</div>

“… it appears that your computer or _network_ has been infected.”

I got the same message for the first time today. Haven’t loaded any software lately nor run the usual holey MS software.

Methinks the key is the “network” part. Probably someone in the same IP block is infected and hitting Google a ton, so _that_ Google server is blocking that range. But since different servers might be blocking different ranges, it can appear erratic.

Note that generally your browser doesn’t like to do DNS host to IP lookup very often. Closing the browser and starting it again can sometimes do it (depending on other network apps and such).

Do some pings, get some IP addresses for Google servers. Try using the IP address instead of the name. When you get one that works, bookmark it.

(Waiting for Google to fix things can be tedious.)

---

<div class="post-metadata">

**Author:** ![Elendil\_s\_Heir](https://avatars.discourse-cdn.com/v4/letter/e/7cd45c/32.png) [@Elendil\_s\_Heir](https://boards.straightdope.com/u/Elendil_s_Heir)\
**Post date:** [December 13, 2005, 4:50pm UTC](https://boards.straightdope.com/t/google-weirdness/335210/20 "2005-12-13T16:50:40Z")

</div>

I had the same thing happen to me yesterday for the first time. But the Google no-go page referred to by the OP provided a link to another page, which asked me to type in a warped-looking nonsense word in a box. I was then automatically put through to the Google main page, and it worked fine after that.

Guess somebody’s trying to seriously mess with Google. Bizarre.
