5 ms·
Well, that trick won't last long either. It's trivial to verify that an IP indeed belongs to Google: https://support.google.com/webmasters/answer/80553?hl=en h
by sylvinus 11y ago
Well, that trick won't last long either. It's trivial to verify that an IP indeed belongs to Google:
https://support.google.com/webmasters/answer/80553?hl=en https://support.google.com/webmasters/answer/80553?hl=en
- deleted 11y ago[deleted]
- dogma1138 11y agoSeems to work if you deploy a proxy on Google's app engine and use it to access WSJ ;)
- slig 11y agoA App Engine wouldn't have a IP with a reverse DNS *.googlebot.com, would it?
- dogma1138 11y agoNope, but it does resolve to something .google and if you check netblocks.google.com it will appear there so they might not be limiting it to googlebot only at this point. https://support.google.com/a/answer/60764?hl=en https://support.google.com/a/answer/60764?hl=en
- dsl 11y ago_netblocks.google.com includes only the servers that handle Gmail and corporate email.
- greglindahl 11y agoI don't think that any server that random people can start a proxy on is in Google's SPF record.
- dogma1138 11y agonot on the spf list, but on google's domain/ip blocks list.
- greglindahl 11y agoThe link you yourself posted says "The most effective means of finding the current range of Google IP addresses is to query Google's SPF record." While this is intended to be mailservers only, it has always appeared to me that the SPF list is all of their servers that 3rd parties can't run proxies on.
- slig 11y agoYes, but if one is interested whether an IP is from Googlebot or not, they would check if it resolves to .googlebot.com and not to .google.