Copy the handle's actual text, put it in a plain-text note, and compare it character by character with the other handle rather than relying on a screenshot. Different characters can look the same depending on the font and surrounding text, and Unicode guidance notes that confusable detection can flag legitimate text, so a visually similar or unusual handle is not by itself proof of malicious intent. Record what you observed and what remains uncertain, then decide whether a limited public-profile check is appropriate or whether to stop at the access boundary.
Find public social profile clues with our TraceSeek app.
Start with the text, not the picture
A screenshot freezes one rendering of a name. The underlying text may contain different characters that look alike in that font, at that size, on that screen. Copy the handle as plain text where it is publicly visible, paste it into a plain-text note, and keep it separate from any URL wrapper or surrounding sentence. That copy is your working artifact. It is a personal reference, not proof of identity or intent. [Unicode UTS 39: confusable identifiers]
- Copy the handle from the public page itself, not from a forwarded image.
- Paste into a plain-text editor so formatting is stripped.
- Label the note with where and when you saw the handle.
Account for confusables and font differences
Unicode guidance on confusable identifiers explains that visually confusable text can use different characters or scripts, and that appearance depends in part on fonts and contextual shaping. Two handles can therefore look identical while their stored text differs. The same guidance cautions that confusable detection can be overly inclusive and flag legitimate text. Treat a difference as an observation about characters, not a conclusion about the person behind them. [Unicode UTS 39: confusable identifiers]
A comparison worksheet (advice)
Use a small table to keep what you saw apart from what you infer.
| Observation | Limit | Next step |
|---|---|---|
| The two handles render the same | Rendering depends on font and context; identical appearance does not prove identical text | Compare pasted plain-text copies side by side |
| The pasted copies contain different characters | A difference shows the text differs, not why or who made it | Note the exact positions that differ and keep the record |
| One handle looks unusual compared with the other | Unusual characters are not evidence of malicious intent; legitimate text can trip confusable detection | Avoid accusations; decide whether any public check is needed |
Worked example (hypothetical)
Suppose two public profiles display what looks like the same name. You paste both into a plain-text note and find that one position differs. That tells you the stored text is not identical. It does not tell you which profile is authentic, which came first, or whether anyone intended confusion. Record that observed difference and the date, and leave it there.
When to stop and what to do next
If the public artifact you wanted is no longer available, note it as unavailable rather than substituting a guess. Use the platform's official current help if you need to understand a naming rule, or ask the owner for a voluntary current link. Do not access private accounts, track anyone, or contact strangers to fill the gap. A username comparison answers only one narrow question: whether the text you are looking at is the same text.
- Write down the observed difference and the date.
- Mark anything you could not verify as unavailable.
- Choose a limited, permitted next step or stop.
A couple more questions
Does an unusual or mixed-script username mean someone is impersonating another account?
No. Mixed or unusual scripts can appear in legitimate names, and Unicode guidance warns that confusable detection can flag legitimate text. An unusual handle is an observation about characters, not proof of impersonation or malicious intent.
Can I compare handles from screenshots alone?
Screenshots are useful as context but weak as evidence of exact text, because appearance depends on fonts and rendering. Copy the handle as plain text where it is publicly visible and compare the characters directly; if you only have an image, record that limit.
What should I do if I cannot access the public handle?
Record it as unavailable and stop at that access boundary. Use the platform's official current help for naming rules or ask the owner for a voluntary current link rather than substituting a guess.
Sources & editorial notes
Official references checked on October 23, 2026. Checklists, comparison tables and example wording are DateClues editorial tools, not official tests or validated risk scores.
General information. No guide or tool can certify a person’s identity, intentions or safety. Read our editorial standards.