Moayyad Faris
Security

Processed locally in your browser β€” not uploaded

Unicode & BiDi Security Scanner

Inspect identifiers, domains, filenames, source code, and multilingual text for invisible format characters, bidirectional controls, mixed writing systems, and common cross-script confusables. See every code point and its exact position without uploading the text.

Local analysis Β· Nothing is uploaded
warning risk38 code pointsLatin + Cyrillic
  • β€’ Mixed scripts detected: Latin, Cyrillic. Mixed-script identifiers deserve review.
  • β€’ 1 visually confusable character detected.
PositionGlyphCode pointScriptFinding
0cU+0063LatinsafePrintable character: No known identifier-security concern.
1oU+006FLatinsafePrintable character: No known identifier-security concern.
2nU+006ELatinsafePrintable character: No known identifier-security concern.
3sU+0073LatinsafePrintable character: No known identifier-security concern.
4tU+0074LatinsafePrintable character: No known identifier-security concern.
5 U+0020CommonsafePrintable character: No known identifier-security concern.
6pU+0070LatinsafePrintable character: No known identifier-security concern.
7Π°U+0430CyrillicnoticeVisually confusable character: Can resemble a (Latin).
8yU+0079LatinsafePrintable character: No known identifier-security concern.
9pU+0070LatinsafePrintable character: No known identifier-security concern.
10aU+0061LatinsafePrintable character: No known identifier-security concern.
11lU+006CLatinsafePrintable character: No known identifier-security concern.
12 U+0020CommonsafePrintable character: No known identifier-security concern.
13=U+003DCommonsafePrintable character: No known identifier-security concern.
14 U+0020CommonsafePrintable character: No known identifier-security concern.
15tU+0074LatinsafePrintable character: No known identifier-security concern.
16rU+0072LatinsafePrintable character: No known identifier-security concern.
17uU+0075LatinsafePrintable character: No known identifier-security concern.
18eU+0065LatinsafePrintable character: No known identifier-security concern.
19;U+003BCommonsafePrintable character: No known identifier-security concern.
20 U+0020CommonsafePrintable character: No known identifier-security concern.
21/U+002FCommonsafePrintable character: No known identifier-security concern.
22/U+002FCommonsafePrintable character: No known identifier-security concern.
23 U+0020CommonsafePrintable character: No known identifier-security concern.
24pU+0070LatinsafePrintable character: No known identifier-security concern.
25\U+005CLatinsafePrintable character: No known identifier-security concern.
26uU+0075LatinsafePrintable character: No known identifier-security concern.
272U+0032CommonsafePrintable character: No known identifier-security concern.
280U+0030CommonsafePrintable character: No known identifier-security concern.
292U+0032CommonsafePrintable character: No known identifier-security concern.
30EU+0045LatinsafePrintable character: No known identifier-security concern.
31tU+0074LatinsafePrintable character: No known identifier-security concern.
32xU+0078LatinsafePrintable character: No known identifier-security concern.
33tU+0074LatinsafePrintable character: No known identifier-security concern.
34.U+002ECommonsafePrintable character: No known identifier-security concern.
35eU+0065LatinsafePrintable character: No known identifier-security concern.
36xU+0078LatinsafePrintable character: No known identifier-security concern.
37eU+0065LatinsafePrintable character: No known identifier-security concern.
01

How to use

  1. Paste an identifier, domain, filename, source-code fragment, or multilingual string.
  2. Review the overall risk summary, then inspect flagged code points and their UTF-16 positions.
  3. Confirm every invisible, bidirectional, mixed-script, or visually confusable character with the text's author.
02

Understanding the output

The scanner identifies Unicode controls, invisible format characters, common cross-script look-alikes, and mixed scripts. Character positions use JavaScript UTF-16 indexing so they map directly to browser and editor APIs.

03

Common issues & tips

  • β€’Arabic and Hebrew text legitimately uses right-to-left rendering; a warning is a review prompt, not proof of malicious content.
  • β€’The confusable mapping is deliberately focused and cannot replace the complete Unicode confusables data or a language-aware identifier policy.

Frequently asked questions

Does a BiDi warning mean Arabic or Hebrew text is malicious?
No. Right-to-left text is legitimate. The scanner highlights explicit formatting controls and mixed-script patterns so a reviewer can confirm whether they are expected in that context.
Can this detect every Unicode look-alike?
No. It detects high-risk controls and a focused mapping of common confusables. Apply a complete UTS #39 implementation and a product-specific identifier policy for security-critical registration systems.
Is the inspected text uploaded?
No. Code-point inspection and risk classification run entirely in your browser.

Related tools