Minecraft Username Lookup: A Practical Guide

What "looking up a Minecraft player" usually means

Most of the time it's one of: figuring out their UUID for a server allowlist, checking what skin they're using, or seeing their old usernames. NameMC has been the answer for a decade and it's still great for the heavy use case (community profiles, friends lists, capes leaderboard).

mc.dawg.bot does the lighter version: paste a name or UUID, get a clean shareable page with skin, UUID, name history, and joined date. No friends list, no comments, no community features, no signup. Just the lookup.

How mc.dawg.bot resolves a player

When you visit mc.dawg.bot/Notch:

1. The catch-all route asks the Dawg API to resolve Notch against the minecraft platform.
2. The API hits https://api.mojang.com/users/profiles/minecraft/Notch to convert the username to a UUID.
3. It then hits https://sessionserver.mojang.com/session/minecraft/profile/<uuid> for the canonical name + the encoded textures property.
4. In parallel, https://api.ashcon.app/mojang/v2/user/<uuid> enriches with name history, account creation date, and pre-decoded skin/cape URLs.
5. Both raw payloads land as ProviderSnapshot rows; normalized data feeds the rendered profile.
6. The lens fetches the normalized profile and renders the skin viewer + name history + UUID + joined date.

You see a profile page in maybe 400ms (first hit) or under 100ms (cached).

UUID input works the same way, just skipping step 2.

What's actually on the page

• 3D body render of the skin (Crafatar)
• Current username + 36-char dashed UUID
• Slim or classic skin model badge
• Cape badge if the account has one
• Name history table with timestamps
• Joined date when Mojang exposes it
• Direct links to NameMC, the raw skin PNG, and the cape PNG

For embeds: append .png to any URL for a screenshot card, or .json for the raw normalized profile data.

Username changes and the 37-day window

Mojang lets you change your Minecraft username every 30 days. When you change it, your old name enters a 37-day "cooldown" where nobody else can claim it. After that 37 days, the name is up for grabs.

This matters for username lookup: mc.dawg.bot/Notch today resolves to the original Notch account. If hypothetically Notch renamed and someone else grabbed Notch later, the lens would resolve mc.dawg.bot/Notch to the new owner. The route binding follows whatever Mojang says is current.

To track a specific player across renames, use the UUID URL instead. UUIDs are permanent.

Why a separate domain

Every platform in the Dawg architecture gets its own lens domain. Discord lives at discord.dog, GitHub at github.dawg.bot, Steam at steam.dawg.bot, Roblox at roblox.dawg.bot. They all read from one identity graph but render with the visual conventions of that platform.

Concretely:

• The same player can show up across multiple lenses if cross-platform connections exist. A Discord profile linking a Minecraft UUID creates a ConnectionEdge that surfaces on both lenses.
• Each domain gets its own SEO surface and tool pages, instead of cramming everything into one product.
• A future bot at the central account portal (dawg.bot) can run /lookup Notch and pick the right lens automatically based on what the input shape looks like.

When to use NameMC instead

NameMC is the right answer when you need: friends graph, community profile features, capes ranking, full skin gallery with vote counts, or to actually claim a profile and customize it.

mc.dawg.bot is for the read-only sharing case where the recipient just needs to see who this player is. Both URLs always coexist: every mc.dawg.bot page links straight to NameMC so nothing's hidden.

What's coming

The current lens is the minimum that's useful. Roadmap items, in rough order:

• Cross-lens connection rendering (showing the linked Discord, GitHub, Steam accounts on a profile)
• Skin gallery view with previous skins from snapshots
• Server-specific stats hooks (Hypixel, etc.)
• Cape archive page

If you want any of those sooner, the repo's open to PRs.