302s on cloaked redirects using Dmoz base data

Here is a variant on the"get the data from Open Directory and put on a 302" scam. This one does a cloaked 302, serving up different food to Googlebot, than to ordinary browsers. Googlebot gets the 302

Have a look at CBTravelGuide and take a state like Rhode Island on their guide, then take a entry on their index like American Historic Inns .

Now run a header check on their entry for American Historic Inns and you get

#1 Server Response: http://www.cbtravelguide.com/us_rhode_island/index.html?w=14&p=19867&s=3&l=2
HTTP Status Code: HTTP/1.1 302 Found
Location: http://www.bnbinns.com/states/RI.htm
Redirect Target: http://www.bnbinns.com/states/RI.htm

#2 Server Response:
http://www.bnbinns.com/states/RI.htm
HTTP Status Code: HTTP/1.1 200 OK

Neat, eh. Googlebot sees the 302, the rest of the world see the site in the unlikely event of them clicking on it. A cross check shows that the URLs come from Dmoz and the descriptions used on cbtravelguide are just the meta descriptions.

There are others of the same ilk, using DMOZ data

Ansme.com

yields in the header the cloaking info with a twist

#1 Server Response: http://dir.ansme.com/exec/dir/go.asp?u=www.mysite.com
HTTP Status Code: HTTP/1.1 302 Object moved
Location: http://www.mysite.com/
Redirect Target: http://www.mysite.com

#2 Server Response: http://www.mysite.com
HTTP Status Code: HTTP/1.1 200 OK