"Just FYI everybody, there's been a response from a Google employee [on the user forums page](https://productforums.google.com/d...). It appears that they've concluded that this is purely a DNS poisoning issue and they're encouraging users to switch to Google DNS. [I responded as best I could](https://productforums.google.com/d...) suggesting that it might not be a bad idea to keep investigating. It might be worth it for others to chime in on that thread as well. **EDIT (unrelated but possibly interesting):** Remember how someone -- I forget who -- noticed that the original chrome-navigation-error page, the destination for the redirect, appeared to be attempting to load a Chrome extension? Well, Google is an amazing thing, and I finally figured out that that part of the source code (which you can see [in this pastebin](http://pastebin.com/kR5J29du)) duplicates [part of the network error rendering..." - Nathan Rein