Typorithm · medium

Username Enumeration

username-enumosintusernamesherlockexposure

Saved on this device

Full lesson · 8 learning steps Open any exercise for focused practice

Step 1 of 8 · intro card

Learn Username Enumeration

Corporate Footprint

Because people reuse usernames, tools like Sherlock and Maigret check a handle across hundreds of platforms to build an account footprint. In security, this measures an organization's or executive's public exposure so it can be protected — strictly within an authorized scope, never to harass.

Most people reuse the same username everywhere, so a single handle often links accounts across hundreds of sites. Sherlock takes one username and checks each platform for it, returning where it exists.

Maigret and WhatsMyName cover the same ground with their own site lists, widening the picture. Together they produce an account map showing how far a handle's public footprint reaches.

In authorized security work this measures the exposure of the organization or its executives so that footprint can be reduced and protected. It is performed strictly within the agreed scope and is never used to harass or target an individual.

Sherlock checks one handle across hundreds of sites.

Maigret and WhatsMyName broaden the same coverage.

Reused handles link accounts — the exposure to measure and reduce.

sherlock username
# maigret and whatsmyname
# same handle reused across sites
# build an account map (authorized)

Read the implementation

Connect each part of the code to the concept before you type.

1. Handle lookup

Sherlock checks one handle across hundreds of platforms to see where it appears — measuring public reach.

sherlock username

2. Sibling tools

Maigret and WhatsMyName do the same cross-platform check, broadening the coverage of the account map.

# maigret and whatsmyname

3. Handle reuse

People reuse the same username, which is the behavior that links scattered accounts together.

# same handle reused across sites

4. Authorized scope

The map quantifies public exposure for the in-scope organization; it is built only under authorization and never to harass.

# build an account map (authorized)

A complete learning loop

Understand

Read the concept map and follow the code breakdown.

Reconstruct

Type the implementation, repair mistakes and work through every recall exercise.

Verify

Use the final check without hints; revisit weak concepts in short practice sessions.