UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36

Steps to reproduce the problem:
.invalid TLD error review

1. type in a valid IETF reserved TLD (e.g. git.invalid)
2. browser doesn't automatically search for domain via http protocol
3. brings user to default search engine instead

What is the expected behavior?
compared with working .test tld

1. type in a .test domain (e.g. git.test)
2. browser will attempt http communication with .test domain

What went wrong?
Browser didn't assume .invalid was a TLD and redirected to search engine.

Did this work before? N/A 

Chrome version: 67.0.3396.99  Channel: stable
OS Version: OS X 10.12.6
Flash Version: