DNS Forward Reverse Lookup

[Connie]

Using a php script are we allowed on a shared server to do a Forward Reverse DNS Lookup?

I'm asking for several reasons.

1) I have tried a script and it does not work. That problem could be on my end. No need to try and work the problems out if Jag does not allow this.

2) Google suggest you verify Googlebot.

Why is this needed?

1) Sometimes Google (and other SEs) may access your site through a proxie server. If they do they may replace your URL in the SERPs with the URL of the proxie server.

2) There are a lot of rogue bots out their that claim to be Googlebot. They are trying to steal you content, replace you in the SERPS, and plaster the new pages with Adsense adds.

Either way, whether intentional or unintentional, your site can end up being hijacked.

[Ron]

To answer your question, yes you can.

To ask you a question -- how would that work.... Google accessing your site through a proxy server? Why would they replace my URL in the serps -- you mean that the blackhat page would rank better, or my actual url would be somehow replaced?

thx

[Connie]

To answer your question, yes you can.

To ask you a question -- how would that work.... Google accessing your site through a proxy server? Why would they replace my URL in the Serps -- you mean that the blackhat page would rank better, or my actual url would be somehow replaced?

thx

Happens frequently Ron. It's more of a glitch on Google part. Sometimes the offending site is completely innocent. Sometimes it is a black hat operation

The way people find this has happened is with doing a site:domain.com check. They will notice that all the URLs displayed in the SERPs are not theirs. The description is theirs.

The URL displayed with the listing would be something like http://www.somedomain.com/http://www.yourdomain.com.

A few years ago my entire site, along with several hundred others were hijacked through a bad proxy script. Fortunately it was caught before any damage was done. Every site listed in a Directory was being scrapped. Fortunately the owner of the Directory caught it and announced the problem.

We simply blocked the offending IP in .htaccess and those hijacked pages started showing a 403 error.

The best prevention to potential problems is to stop them before they happen.

I can't explain the exact details. Here are a couple of threads from WMW in regard to the subject. Perhaps they will make the details a little clearer.

http://www.webmasterworld.com/apache/3381827.htm
http://www.webmasterworld.com/google/3306064.htm

I'll post the script I have and see if you php guys/gals can tell me what is wrong with it.

[Ron]

The way people find this has happened is with doing a site:domain.com check. They will notice that all the URLs displayed in the SERPs are not theirs. The description is theirs.

The URL displayed with the listing would be something like http://www.somedomain.com/http://www.yourdomain.com.

Never heard of that problem before. Wow. I knew about 302 hijacks.

Any examples of this actually happening nowadays?

[Connie]

Oops. I missed posting a thread at WMW. This is currant. http://www.webmasterworld.com/google/3378200.htm