Open CuriousApe2020 opened 1 year ago
I have never experienced such fishing attacks with special unicode characters. I guess just blocking ą etc. would trigger lots of false positives (just like the anti RTL setting already does). Do you have an example of such a fishing message? Perhaps we could add a setting to block unusual unicode characters specifically in URLs?
The option to block all Unicode characters except the commonly used ones and the ones of your preferred languages like latin and or Cyrillic. This would mean an increased protection against attacks where a similar looking character is used in a domain to lead to a fishing site. For example using "а ạ ą ä à á ą" instead of a latin a.