Using lookalike character symbols to circumvent HSTS and public-key pinning with DNS spoofing via MITM Attack.
Redirect: facebook.com --> faceḃook.com
--
I have seen SSLStrip+ using the technique of adding another "w" to domains {www.facebook.com --> wwww.facebook.com} to circumvent HSTS and public-key pinning. However, this clearly shows a modified address. I feel it would be more clandestine to use lookalike characters to perform DNS spoofing.
In my full conceptualised idea every letter will have a substitutable set of lookalike characters:
- a = a
- b = ḃ
- k = κ
Therefore, www.facebook.com --> {www.facebook.com, www.faceḃook.com, www.facebooκ.com} Any of the above three should circumvent HSTS.
I can see mitigations by having HSTS preloading with HSTS no_redirect, this idea of no_redirect would make the browser prevent an HTTP redirect for known HSTS websites.
My question is how can this model of lookalike characters for circumventing HSTS be strengthened for greater clandestine nature. As modern Google Chrome displays "Not Secure" for HTTP web pages, which would be a big red flag.