Mastodon Β· Free Β· No sign-up
Mastodon Account Age Checker
Type any Mastodon handle in the @[email protected] format and we'll fetch the exact account creation date plus follower, following and post counts from that instance's public API.
Use the full handle, for example @[email protected].
π Never enter passwords, tokens, emails or any private information. This tool only uses public usernames or IDs.
How it works
- 1 Β· Copy the full Mastodon handleMastodon handles always have two parts: the username and the instance domain. Example: @[email protected]. Don't forget the second @ β it tells us which instance to query.
- 2 Β· Paste it hereDrop the full handle into the box above. We'll resolve it on the right instance and pull the public profile data.
- 3 Β· See the dataWe surface the exact created_at field from Mastodon's /api/v1/accounts/lookup endpoint, plus follower count, following count, post count, and bot status.
Why check a Mastodon account's age?
Mastodon's decentralized model means anyone can spin up an instance and create accounts in seconds, which makes account age the simplest defense against impersonators and brand-new accounts joining popular hashtags to spam. Researchers studying the Twitter-to-Mastodon migration use account age to map adoption waves. Instance moderators use it to gauge whether a federation partner is a long-established community or a week-old spam farm. Anyone considering following a new account uses it to spot accounts that exist purely to amplify a single post.
How does this work across different Mastodon instances?
Every Mastodon instance exposes a standardized public API at /api/v1/accounts/lookup. We parse your handle into username + instance domain, query that specific instance's API, and return the created_at field. This is the canonical creation timestamp the instance recorded when the account was registered. Because the API is mandated by the Mastodon protocol, the tool works on mastodon.social, fosstodon.org, hachyderm.io, and every other Mastodon instance equally.
Limitations to know
Some instances disable public API access for privacy β when that happens, the lookup will fail and there's no workaround other than asking the user directly. Federated accounts from non-Mastodon software (Pleroma, Misskey, etc.) usually work because they share the ActivityPub protocol, but a few quirky implementations don't expose created_at. We never store handles or results.
Frequently asked questions
What format should the handle be in?
Always @user@instance β for example, @[email protected]. If you only have the URL, the @user@instance form is in the profile under the display name.
Does this work on instances other than mastodon.social?
Yes β that's the whole point. We query whatever instance is in your handle. Works on mastodon.social, fosstodon.org, hachyderm.io, mas.to, infosec.exchange, and every other Mastodon instance.
How accurate is the creation date?
Exact to the second. It's the created_at timestamp the instance recorded when the account was registered, pulled live from the official API.
Does this work for Pleroma, Misskey, GoToSocial accounts?
Usually yes β these projects implement the Mastodon API for compatibility, so /api/v1/accounts/lookup returns a created_at field most of the time. A handful of forks omit it; in that case we'll return an error rather than guess.
Can I check a deleted Mastodon account?
No. Once an account is deleted on its home instance, the API returns 404 and there's no decode trick like Discord's snowflake β Mastodon IDs are sequential per instance and don't encode a timestamp.
Why do I sometimes get a 404 when the account clearly exists?
Most often it's a typo in the instance domain β make sure it's the home instance, not a remote one where you saw a boosted post. You can also get 404 if the instance has disabled public account lookup.