Enter the exact ID
Keep any periods, digits, domains, and prefixes that belong to the identifier.
Public profile searchMessaging
Element / Matrix Username Lookup
Resolve a complete Matrix ID across a federated homeserver and distinguish account discovery from device and encryption verification.
Public profiles Responsible lookupNew guide
Direct lookup
Ready
Search Element / Matrix
Public data only
No password needed
Exact handle check
Username formatA full Matrix ID in the form @localpart:homeserver
Profile pattern@username:homeserver
CoveragePublic profile and signals
Privacy boundaryNo private-account access
Three clear steps
How to check a Element / Matrix username
Review the public profile
Check the URL and visible signals without treating missing data as proof.
Verify the context
Confirm the match through an official site, reciprocal link, or known channel.
Element is a client for the decentralized Matrix network, so an Element username lookup works differently from a search on a centralized social platform. The most reliable input is a complete Matrix ID such as @alex:matrix.org, not the display name or local username alone.
The server domain is part of the identity. Lookup coverage and public profile fields depend on the target homeserver’s policies and federation settings.
Understanding the full Matrix ID
A Matrix user ID, often called an MXID, has the structure @localpart:homeserver. In @alex:example.org, alex is the local part and example.org identifies the homeserver that issued the account.
The server portion is essential. @alex:matrix.org and @alex:example.org are different accounts even though they share the same local part.
Current MXID local parts use lowercase letters, digits, and a limited set of punctuation. Historical IDs may follow older rules.
What a Matrix lookup can return
Our lookup uses the complete MXID to identify the correct homeserver and check profile information the server makes available. A result may include the Matrix ID, display name, avatar, and a link that can open in a compatible client.
Matrix is federated, and each homeserver controls part of discovery. A server may omit profile fields, limit directory results, disable lookup across federation, or refuse to confirm whether an account exists.
The result should therefore distinguish between found, not found, and lookup restricted.
Finding a person in Element
Paste the entire Matrix ID whenever possible. Inside Element, it can be used to start a direct conversation or invite the account to a room. Search by display name is less dependable because display names are changeable and need not be unique.
Element user search is not a universal directory of every Matrix account. The homeserver determines the searchable subset, including users in shared rooms or public rooms known to that server.
Remote-user coverage can vary, so a missing broad-search result should be checked again with the complete MXID.
Account verification is different from device verification
Check the MXID character by character, including the homeserver. For an organization, a homeserver on its own domain can be a useful signal, but should still be compared with an official website.
Element also uses “verification” for cryptographic device or session verification. That process confirms encryption keys and protects an end-to-end-encrypted conversation.
It does not verify a legal name, employer, or real-world identity. A verified session and a verified person are separate claims.
Matrix discovery and privacy boundaries
A Matrix profile may contain a display name and avatar, but the homeserver decides what it discloses. Email and phone discovery may use an optional identity server when the user consents.
Room visibility is separate from profile lookup. Public-room participation may create discoverable context, while invitation-only and encrypted rooms do not become readable through username search.
The lookup cannot access private room histories, contact lists, encryption keys, passwords, access tokens, or messages.
Element lookup: the practical takeaway
Always search the complete @user:server identifier. A partial username can refer to many unrelated accounts, and a restricted response may reflect homeserver policy rather than non-existence.
FAQ
Element / Matrix lookup questions
Is Element the same thing as Matrix?
No. Matrix is the decentralized communication protocol and network. Element is one client used to access it.
What does a complete Matrix username look like?
A complete MXID looks like @username:homeserver.example. The homeserver is part of the identifier.
Can two Matrix users have the same username?
They can have the same local part on different homeservers. Their complete Matrix IDs remain different.
Why does a Matrix lookup say restricted?
The target homeserver may decline federation profile queries or omit information. Restricted is not the same as absent.
Does Element verification prove a person’s identity?
No. Device verification confirms cryptographic sessions or keys.
Can the lookup read encrypted Matrix rooms?
No. It cannot join private rooms, obtain encryption keys, or access encrypted messages.
Ready to check it?
Run another Element / Matrix lookup
Enter the exact identifier and preserve every detail that belongs to the handle.
Direct lookup
Ready
Search Element / Matrix
Public data only
No password needed
Exact handle check