UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36

Steps to reproduce the problem:
1. Type in an otherwise valid URL starting with http:// or https://, replacing one of the periods in the FQDN with more than one period
2. Press enter
3. Get search results

What is the expected behavior?
Collapse adjacent periods and attempt a DNS lookup before performing a search.

What went wrong?
While that is an invalid URL, a user who's typed in the protocol portion of a URL is unlikely to intend for a search to be performed.  Really, any single string ending with a current TLD (or which looks URL-y) which contains multiple periods is likely to be intended as a domain name rather than a search string, but definitely anything which starts with a protocol.  It would be convenient if the browser could do that quick DNS lookup prior to going to search.

Did this work before? No 

Chrome version: 68.0.3440.106  Channel: stable
OS Version: 10.0
Flash Version: 

This is arguably a minor security issue, as internal URLs end up in the user's search history and end up in a larger pool of data used for future search suggestions.  I suspect that's an infinitesimal risk, but I suppose it's worth considering.