Enter the exact ID
Keep any periods, digits, domains, and prefixes that belong to the identifier.
Find a public Mastodon profile using its complete federated handle, then review the server, profile links, and visible public identity signals.
Keep any periods, digits, domains, and prefixes that belong to the identifier.
Check the URL and visible signals without treating missing data as proof.
Confirm the match through an official site, reciprocal link, or known channel.
A Mastodon username lookup works differently from a search on a centralized social network. Every account belongs to a specific server, so the complete address includes both the local username and the server domain. Enter a handle such as @alex@mastodon.social or paste a full profile URL to locate the public account and review its visible identity signals.
Our lookup resolves the server, checks the public profile associated with the address, and searches for relevant public references. It never opens follower-only posts, bypasses server rules, or exposes private conversations.
A complete Mastodon address has two essential parts: a local username and the domain of the server that hosts the account. The format resembles an email address: @username@server.example. On the account’s own server, the interface may shorten this to @username, but that shorter form is not globally unique.
For example, @alex@mastodon.social and @alex@techhub.social are separate accounts. They may belong to different people even though the local username is identical. A display name is less precise still: it can contain spaces, emoji, capitalization, or any wording chosen by the account owner.
Most Mastodon profile URLs follow a structure similar to https://server.example/@username. For a reliable lookup, use the full address or profile URL whenever possible.
The lookup separates the username from the host domain and attempts to resolve the public profile on that server. When the account is reachable, results can include its canonical profile link and publicly displayed information such as the display name, avatar, biography, profile metadata, public post count, and visible recent activity.
Results can differ between servers. Mastodon is federated: there is no single database containing every account and every post. One server may already know about a remote account, while another may need to fetch it from the account’s home server. An instance can also be offline, defederated, renamed, or closed.
Directory visibility and search-engine visibility are separate choices. A valid public profile may be absent from both, so a missing search result does not prove that the address is unused.
Start with the most specific identifier available. Paste the complete handle, including the domain, into the lookup field. A full profile URL is equally useful because it identifies both the server and the local username.
@.Inside Mastodon, a logged-in user can also paste a remote account’s full address or profile URL into search. A broad name search is less reliable because it may show only accounts already known to that server.
The server domain is part of the identity, not a decorative suffix. Always compare the entire address. A familiar local name on an unrelated instance should not be assumed to represent the same person.
Mastodon supports verified profile links through the open-web rel="me" mechanism. When a website links back to the Mastodon profile correctly, the corresponding profile field can receive a verification indicator. A verified link to a known personal site, organization, portfolio, or publication is stronger evidence than a matching avatar.
Useful checks include the linked domain, biography, posting history, profile metadata, previous-handle notices, and links published through an already trusted channel.
A locked account requires the owner to approve new followers, but the lock does not automatically make every part of the profile invisible. Each post has its own audience setting, and only content made public should appear in public lookup results.
Account owners can decide whether to participate in profile directories and whether search engines may index their profiles. Server administrators can impose additional moderation, federation, or retention rules.
This lookup respects those boundaries. It cannot reveal follower-only posts, private mentions, hidden collections, IP addresses, login details, or deleted content.
The key to an accurate Mastodon lookup is the domain. Search the complete @username@server address, confirm the canonical profile, and use verified links and consistent public context to distinguish the correct account from namesakes on other servers.
You can try, but the result is ambiguous because the same local username can exist on many servers. Add the server domain or use the full profile URL for an exact lookup.
No. The domain is part of the address, so identical local usernames on different servers represent distinct accounts unless other evidence connects them.
It may appear in server search, but display names are not unique and can change freely. The complete account address is the reliable identifier.
The owner may not have opted into discovery, the server may not know the remote account yet, or the instance may limit federation or indexing.
It means Mastodon found a qualifying link from the external website back to that profile. It supports control of the linked site, but is not a government identity check.
No. It uses only information that the account and its server expose publicly.
Enter the exact identifier and preserve every detail that belongs to the handle.