Google Maps API Key: Inconsistency or Safeguard?

Filed in: Google, Tools, Web 2.0, Webmaster Add comments

For those who doesn’t know it yet, the Google Maps (API Key Signup here) uses different keys for domains appended with http:// and http://www. even though the domain name is the same.

I’m not exactly sure about the explanation, but here’s an example:

http://allanjosephbatac.com
API Key:
ABQIAAAAyfTN7Bk5Bn2nK6gcX0pz1hTiURkvBKy5aNM5Al
VjaMth86XzbRTUvwn0Wvi31Vf_GU4MM9_RLsT-7w

http://www.allanjosephbatac.com
API Key:
ABQIAAAAyfTN7Bk5Bn2nK6gcX0pz1hR8oJctqc-WteYRkaV
y6J7pQb9KGhR0e77LMAYCzXTob3_CwTVHlnNNLg

I also think that the encrypted hash came from reversing the domain name e.g. “moc.catabhpesojnalla//:ptth” since the last part of the API key is the one different.

Is it inconsistency or safeguard?

Comments are closed.