| 2:58 pm on Dec 12, 2005 (gmt 0)|
Being ip banned is most often as result of rank checkers or running bots against Google.
| 3:09 pm on Dec 12, 2005 (gmt 0)|
Yes, I have notices this as well. While doing an allinurl search.
Never saw it before.
| 3:19 pm on Dec 12, 2005 (gmt 0)|
Could also be a proxy that your using
| 3:21 pm on Dec 12, 2005 (gmt 0)|
I found that anything I searched for with the word 'php' in it was blocked like that yesterday.
| 3:29 pm on Dec 12, 2005 (gmt 0)|
We ran into this as well last week. We were having a meeting on some discussion board pages that had gone supplemental. During the course of the discussion we searched about a dozen discussion board URLís to get them to show in Google, and then got that message and could not search any more.
Didnít think much of it at the time but all the URLís had PHP in them.
| 3:54 pm on Dec 12, 2005 (gmt 0)|
It can also happen when we search results using software.
| 3:57 pm on Dec 12, 2005 (gmt 0)|
Am getting it right now for some searches but not others. Also, if I switch to IE all searches run clear - so maybe not an IP marker? Haven't been running any rankcheckers or other API users.
| 5:24 pm on Dec 12, 2005 (gmt 0)|
I've had it before.
I think a specific IP is limited to something like 1000 searches within a specific time frame.
My co-workers weren't too happy when I triggered the block.
Oh well, I quit that dump anyway now so who gives!
| 5:32 pm on Dec 12, 2005 (gmt 0)|
Haha... it happen to me too!
Guess, what's happens when a phrases is searched too much and with a certain very suspecious pattern - it's not only related to the IP...
Did it to "blue widgets", I get same response to "dark blue widgets" (and so forth)!
However when I limit them number of rows to 10 it's cool.. but 10-1000... too bad!
| 5:38 pm on Dec 12, 2005 (gmt 0)|
It's a bug. It seems to occur randomly but if you see it once you're likely to see it a few times.
I have a vague idea that GG explained what triggered it a couple of years ago but I could be mistaken.
| 8:31 pm on Dec 12, 2005 (gmt 0)|
I was seeing it here for inurl: and site: searches. I deleted all Google cookies and everything seems to be back to normal.
| 8:37 pm on Dec 12, 2005 (gmt 0)|
There is a PHPBB worm going around. I'm assuming Google de-activated some of the words that the infecting worm was searching for to locate poor unsuspecting forum owners such as myself... a good move imo.
| 9:28 pm on Dec 12, 2005 (gmt 0)|
I think you can see it for terms relating to the PHP worm that went around, but I have run into it because of my search habits.
I was doing some competitor research one day and I had 10 instances of Optilink running backlink checks, as well as opening the first 10 results in tabs and checking their G backlinks, PR, etc. using the SEOpen extension.
I also use Fasterfox, which is supposed to cache the linked areas from your current page for faster browsing. All of those together seemed to make Google think I was a robot.
I have also "broken" Yahoo in this way. Both of the bans cleared up after leaving them alone for 20 minutes or so.
| 9:48 pm on Dec 12, 2005 (gmt 0)|
I've been getting a few of those in the last few days, only when doing allinurl: searches; I'd never seen it before. I've never used any automated checkers - only manual type-ins from my browser. I use a Mac, so I doubt there is any spyware involved.
| 10:09 pm on Dec 12, 2005 (gmt 0)|
I believe the PHPBB exploit that NoLimits mentioned looked for a specific file using the allinurl search parameter. I believe most PHPBB installations have now kept this certain file from being indexed and therefore easily accessed by the worm. Thus, an inurl search for specific keywords (possibly w/ a php extension?) might trigger Google to think twice about letting you see results.
Please correct me if I'm wrong.
| 12:57 am on Dec 13, 2005 (gmt 0)|
I've seen this when doing regular boring-fart searches.
As webmasters, we use advanced search methods and assume that these trigger the problem - in the words of Jimmy Somerville "It ain't necessarily so".
| 12:30 pm on Dec 13, 2005 (gmt 0)|
I too am finding that if "php" is in the search that the error message will appear. All other searches I've run seem fine.
| 12:43 pm on Dec 13, 2005 (gmt 0)|
I saw this a few hours back also.
My search for "input checkbox php" was bring up the 403 error.
Removing the php from the query allowed me access to the search results.
| 1:15 pm on Dec 13, 2005 (gmt 0)|
Hmm. Blast from the past.
A year or so ago Brazilian hackers began automated searches for phpBB2 forums [phpbb.com] (searching in google.br for every site with `phpBB2 v 2.0.10` on the page) and hacking them - page 11 on the link has the exploit used.
Google instituted a check at it's end to try to stop it. Unfortunately this was defective, and for quite some time *any* search that included "index.php" caused the result detailed in message#1 of this thread. After a week, or two, G fixed it and it became part of G history.
Ah yes. Deja Vu, all over again.
PS (vaguely related) has anyone else noticed just how many so-called cache entries are not (cached, that is)?
| 3:27 pm on Dec 13, 2005 (gmt 0)|
I kept hitting problems as soon as I added forum to the search term.
| 3:48 pm on Dec 13, 2005 (gmt 0)|
Strangely enough I hit the problem too when searching for "forum" and I'm searching for an extract with more than 10 rows...
| 7:05 pm on Dec 13, 2005 (gmt 0)|
I say this problem this morning, but with the term phpbb, not just php.
That was using the firefox search box. When I typed in google.com and searched for the same thing, the search went through fine.
All other searches in the search box, including ones with php in them, but not phpbb, also worked fine.
| 2:57 pm on Dec 14, 2005 (gmt 0)|
|A computer virus or spyware application is sending us automated requests, and it appears that your computer or network has been infected. |
I'm getting it now again. Google, it is not a virus or spyware application! Jeez! If you don't want to show results for a particular term then don't show them. But just keep mum instead of alarming the world that their machines have been infected!
What's wrong with these guys? :::shaking head:::
| 2:58 pm on Dec 14, 2005 (gmt 0)|
It would be nice to have some way to bypass this... i.e. typing the characters from an image to verify you aren't a bot and then allowing access to the results.
Sometimes people DO search for PHP related things!
| 3:30 pm on Dec 14, 2005 (gmt 0)|
Yep happening a lot for me recently, seems to happen when you use the terms forum or php in the query within a certain time frame. Try searching just for forum then click on search again. Its crazy and it has forced me to use Yahoo or Fast for php related searches.
| 3:48 pm on Dec 14, 2005 (gmt 0)|
We faced this problem many time but it is always solved in a Hour time.
| 4:29 pm on Dec 14, 2005 (gmt 0)|
We must all have owned boxen ;-).
Anyone got the list of what to look for if you run SuSE 10.0, use plain Mozilla, and don't have any services running that are availible to the wild side of a firewall?
| 5:04 pm on Dec 14, 2005 (gmt 0)|
I get the error message for any search that includes site: and inurl: and &num=100 in the search URL.
Removing any one parameter, allows the search to proceed.
If you remove the &num=100 parameter, make a search, and then click the "In order to show you the most relevant results, we have omitted some entries very similar to the 400 already displayed. If you like, you can repeat the search with the omitted results included." message (which adds the &num=100 parameter back on to the search URL) it then works OK. If you add the &num=100 parameter back on by hand, then you get the error message again.
| 5:16 pm on Dec 14, 2005 (gmt 0)|
Amazing new way to clean your PC of viruses: Change your Google search terms!
| This 40 message thread spans 2 pages: 40 (  2 ) > > |