Bug in URL look up, custom fonts break correct url look up

[Chas4]

For example (spam/scam comment http://www.youtube.com/comment?lc=Qd2oybThg6txVNIO_Oqz5Jz6x71Vv1BFQIeA9SGNNco) (direct link to the Youtube comment)

THIS SCAM/SPAM IS STILL LIVE:
"Hi, have you heard of BellyFATtack" yet? Simply copy and paste ＢｅｌｌｙＦＡＴｔａｃｋ.ｃｏｍ to your browser to check out their internet site! There you will find a beneficial free video presentation by a well established medical professional talking about the way to burn fat. This helped Khalid to burn his stomach fat. Why not give this a shot. Perhaps it will work for you also."

font-family: arial, sans-serif;
font-size: 13px;
font-style: normal;
font-variant: normal;
font-weight: normal;
line-height: normal;

sans-serif (You can double check, I think that is right, by looking at the page contents) is the font for the spam/scam link, yet WOT does not convert the custom font (sans-serif) back to a standard font (widely used), so it reads the sans-serif text with spaces

So https://www.mywot.com/en/scorecard/xn--mi7cabghg2bda6fa0d.com Should have been https://www.mywot.com/en/scorecard/bellyfattack.com

[c۞g]

xn--mi7cabghg2bda6fa0d
decodes to:
ｂｅｌｌｙｆａｔｔａｃｋ

ref: [url=http://www.charset.org/punycode.php?encoded=xn--mi7cabghg2bda6fa0d&decode=Punycode+to+normal+text t=_self]charset.org[/url]

You're correct, there should not be 2 scorecards.

Code: Select all

ｂｅｌｌｙｆａｔｔａｃｋ.com
canonical name: bellyfattack.com.
addresses" 192.185.154.16
Server: Apache
X-Pingback: hXXp://bellyfattack.com/xmlrpc.php
Link: <hXXp://bellyfattack.com/?p=1816>; rel=shortlink

ref [url=http://centralops.net/co/DomainDossier.aspx?addr=%ef%bd%82%ef%bd%85%ef%bd%8c%ef%bd%8c%ef%bd%99%ef%bd%86%ef%bd%81%ef%bd%94%ef%bd%94%ef%bd%81%ef%bd%83%ef%bd%8b.com&dom_whois=true&dom_dns=true&net_whois=true&svc_scan=true t=_self]CentralOps domain dossier[/url]

[Sami]

This has nothing to do with the font, these are fullwidth Unicode characters. Copying the text to your browser's address bar only works, because the browser folds the fullwidth characters back to normal ASCII, and our search field does not. However, should you open the scorecard from the add-on when visiting the page, it opens the correct one, obviously.