Have a look at this scenario. This scenario has nothing to do with Google or Chrome (yet).
Assume: User is using their ISP's DNS service, and the ISP uses DNS wildcards to redirect users to a branded search page.
1) User types notifyo.com in to a web browser; a misspelling of notifo.com
2) ISP DNS finds no match for notifyo.com upstream, so returns their own web server's ip
3) User is shown a web page with search results when they really wanted a specific website
ISP's do this by specifying wild cards at the TLD level. This means .com, .net, .org, etc will all return the IP of their search servers if nothing else matches.
Google Chrome checks for these wildcards only. It does not check for wildcards on your domain. For example, Google Chrome would not find, nor object to .notifyo.com.
Personally, I find the use of wildcards at the TLD level to be flat out offensive. It's a break in the basic protocols of the internet. If a website doesn't exist, I need to know. I don't want a search page, I want an error that reflects the status of the domain I have attempted to visit. That's why I use the 4.2.2.x DNS servers.