Weblog
10/02/05 04:50 PM: What up web browsers?
Okay.
So, I open Safari and instead of getting my normal homepage of Google, I get:
Now this is interesting, as this is clearly NOT Google.
So, I’m thinking, what the hell? Then I remember someone mentioned something about this happening before. So I bring up google.co.uk which works fine, and search for it. They talk about Google having some kind of DNS error.
Knowing a little bit about DNS, I do a dig on google.com to see if something has been compromised or what have you. ‘Cept the results for Google.com are fine and normal:
So I try doing www.google.com. in my browser. And it works, getting me back to Google.
Apparantly, this Google pretend site is actually located at google.com.net, and for some reason I am being redirected there. I have to ask, what the fuck? I open up telnet:
$ telnet telnet> open www.google.com 80 Trying 206.125.101.12... Connected to www.google.com.net.
???
Now tell me how hard it would be for this fake google.com.net to set up a fake gmail page at mail.google.com.net, and collect my username and password? Or better yet, why not just set up a bankofamerica.com.net and get my banking info. Because if my connection is automatically being redirected there, and the site looks the same, how the fuck would I know? If Sogo’s homepage looked like google, I would have never thought to check if it was really Google or not.
So, will someone who is apparantly smarter about DNS than I am, please explain to me why I shouldn’t be really pissed off about this?
Some people are saying it’s an issue where a browser automatically appends other suffixes onto a domain name that can’t be found. And telnet does this too? And who came up with this idea of automatically appending other suffixes? That’s really stupid. And then let the server mod_rewrite www.google.com or whatever? I’m not even sure how they are doing that.
And Firefox is no better.
