Spot lookalike domains: punycode and Unicode, mixed scripts and UTS #39 confusables.
New
String Obfuscator for Filter Testing
Runs locally
Use String Obfuscator for Filter Testing
What it does
Create lookalike versions of a word or domain to test whether spam filters, brand-protection rules or your own detectors notice Cyrillic letters and invisible characters. The Homoglyph Checker and the Invisible Character Detector show how such text is flagged.
It runs entirely in your browser: nothing you enter is uploaded.
Example
Lookalike example.com
example.comехаmрlе.соmThe homoglyph row reads ехаmрlе.соm: e, x, a, p, c and o are replaced with Cyrillic letters, while m, l and the dot stay Latin.
FAQ
What does each output contain?
The homoglyph row swaps 11 lower-case and 12 upper-case Latin letters for Cyrillic lookalikes (a becomes U+0430, o becomes U+043E and so on), the zero-width row puts an invisible character between the letters, and the char-code row writes every character as a \uXXXX escape.
What is it meant for?
Testing: check that a mail filter, a brand-monitoring rule or a detector you wrote treats ехаmрlе.соm differently from example.com. Paste the result into the Homoglyph Checker or the Invisible Character Detector to see how the trick is flagged; do not use it to disguise content.
Is the text sent anywhere?
No. The substitutions happen in your browser, and nothing is uploaded.