Help! Quest user seeing cloaked pages

A user of the ISP Quest, sent my client a screenshot of a cloaked page

[Friday]

A user of the ISP Quest, sent my client a screenshot of a cloaked page from his IP adress of 209.180.139.226, which is NOT included in my database, nor is the block 209.180.*.

Anyone have any ideas about this? He's using a google browser but won't give details. I suspect he's an SEO looking to steal my client. Does Quest draw search results from Google cached pages (I found a "gremlin" in the "noarchive" header that may have caused google to cache the page.

This is really puzzling.
:-(

Any help would be appreciated.

[volatilegx]

If Google cached an optimized and cloaked page, then anybody can view the cache. Since Google caches, you can either use that NOARCHIVE meta tag or remove all of Googlebot's IPs from your database.

[Air]

The biggest cloak busters are translators, caches, and proxy servers. Believe it or not if you hunt around long enough on known search engine class "c" you can find open proxies from time to time, allowing you to surf with that SE's IP address. It has to be one of these three possibilities IMO ...

[Friday]

Actually, I did use the "noarchive" META tag, but later discovered that a "gremlin" had crept into it (instead of a space there was a non-ASCII character that looked like a lower-case "t").

[Friday]

>>>
Believe it or not if you hunt around long enough on known search engine class "c" you can find open proxies from time to time, allowing you to surf with that SE's IP address.
<<<

Dear AIR,

could you elaborate on this technique or point me to a discussion of how it's done?

TIA.?

[Air]

>could you elaborate on this technique

Basically you go through the known ranges of IP Addresses of search engines and either look for hostnames that resolve to proxy.some.name or try to use them as proxy servers in turn and see if they work. It's trial and error, the proxy once found is just defined in your browser as the proxy to use, usually on port 80 or 8080.

[Friday]

>>, usually on port 80 or 8080.

Thanks, sounds like fun.