Forum Discussion

Former Employee

Mar 04, 2020

Dev channel update to 82.0.439.1 is live

Hello Insiders, today we’re releasing build 82.0.439.1 to the Dev Channel. We also posted a new blog post last week detailing our work to protect you from potentially unwanted applications. Check i...

rjpaulsen

Brass Contributor

Mar 05, 2020

What would be even better is checking when you enter something that is a misspelling of a "real" website.

Example: When entering "ebaay.com" the user would be prompted with "Before we navigate there, did you mean ebay.com?"

Example: When entering "whitehouse.com" the user would be prompted with "Before we navigate there, did you mean whitehouse.gov?"

HotCakeX

MVP

Mar 05, 2020

rjpaulsen

Spoiler

rjpaulsen wrote:
What would be even better is checking when you enter something that is a misspelling of a "real" website.

Example: When entering "ebaay.com" the user would be prompted with "Before we navigate there, did you mean ebay.com?"

Example: When entering "whitehouse.com" the user would be prompted with "Before we navigate there, did you mean whitehouse.gov?"

wrote:What would be even better is checking when you enter something that is a misspelling of a "real" website. Example: When entering "ebaay.com" the user would be prompted with "Before we navigate there, did you mean ebay.com?" Example: When entering "whitehouse.com" the user would be prompted with "Before we navigate there, did you mean whitehouse.gov?"

this sounds good, would prevent lots of phishing attacks 🙂