Need help understanding the Whatsmyname App features and setup

Apps
1

I’m trying to figure out how to properly use the Whatsmyname App for online username lookups, but I’m confused about some of the features and setup steps. I’m not sure if I’ve configured it correctly or if I’m missing required tools or data sources. Can someone explain how to install, configure, and effectively use the Whatsmyname App for OSINT and account discovery, and share any common troubleshooting tips for when it doesn’t return results?

2

Here is the quick rundown so you can check if you set Whatsmyname up right and use it without headaches.

  1. What Whatsmyname App does
    It takes one username and checks it across many sites.
    It uses the WhatsMyName project JSON file as a database of sites and URL patterns.
    If the pattern matches and the response code looks right, it marks the username as found or not found.

  2. Basic setup checklist
    Go through this list and fix anything that does not match.

• Install
Usually you either

  • Download the release from the GitHub repo, or
  • Clone the repo and run it with Python.

If it is Python based, you need:

  • Python 3.x
  • Requirements installed with something like:
    pip install -r requirements.txt

• WhatsMyName database file
Most forks use a JSON file like:
whatsmyname.websites.json
Check that this file exists in the app folder.
Open the config or settings file and confirm the path to the JSON file matches.
If the app has a “Update DB” button or command, run it once so you have the latest sites.

  1. Running your first query
    Common ways:

CLI style:
python whatsmyname.py -u target_username

Or app style:

  • Start the web interface or GUI
  • Type the username
  • Select “all sites” or a subset
  • Hit search / run

If nothing returns, check:

  • Your internet connection
  • Proxy or VPN settings
  • Any firewall that blocks outgoing HTTP/HTTPS
  1. Key features you are likely seeing and what they mean

• Site filters
Some builds let you filter by category, for example:

  • Social media
  • Forums
  • Code hosting
  • Adult
    If your results look too small, you likely filtered out many sites.
    Reset filters or select “all”.

• Status / codes
You will see things like:

  • Found / Not Found / Unknown
  • HTTP codes like 200, 301, 404, 403
    Quick rule of thumb:
  • 200 with a clean profile page usually means the username exists.
  • 404 often means no profile.
  • 301 or 302 means redirect, the tool logic decides from the final URL pattern.
  • 403 or 429 means blocked or rate limited, try a slower speed or proxy.

• Request delay / threading
Many tools have:

  • Threads or concurrency
  • Delay or timeout
    If you set threads too high, sites block you or rate limit you.
    Try 5 to 10 threads.
    Set a small delay like 0.5 to 1 second between requests if the tool supports it.
    If you see lots of errors or 429, lower the threads.

• Output formats
Look for options like:

  • CSV
  • JSON
  • HTML report
    Check where it saves files. Often there is an “output” folder in the project.
    Run a test on a known username like “github” or “facebook” so you can compare results to reality.
  1. Common misconfig issues

• Old JSON database
If the JSON DB is old, you get many false negatives.
Update the database from the original WhatsMyName repo.
Often there is a direct URL in the readme, for example:
https://raw.githubusercontent.com/WebBreacher/WhatsMyName/main/whatsmyname.websites.json
Replace your local file with the fresh one if the app does not auto update.

• Wrong JSON path
Check config file or command line flag. Some tools use:
–websites-file /path/to/whatsmyname.websites.json
If the path is wrong, you get zero or few sites.

• Proxy settings
If you turned on a proxy but it is misconfigured, nothing works.
Try running without proxy first.
If you need proxy, test it with curl or your browser, then copy settings.

  1. How to confirm your setup works

Do this step by step:

  1. Pick a unique username you own on a few platforms.

  2. Search that username in the app.

  3. Manually open a couple of “Found” URLs in your browser.

  4. If the URLs match your profiles, the logic works.

  5. If many sites show wrong profiles or error pages, your JSON DB or detection logic is off.

  6. Optional tips to use it better

• Use known test usernames
Try public usernames that exist on tons of sites, for example:

  • “github”
  • “google”
    You should see many hits.

• Save your configs
If the app supports a config file, save:

  • Thread count
  • Timeout
  • Proxy
  • Output folder
    So you do not retype every run.

• Respect rate limits
Spread out searches if you do many usernames.
Some sites block repeated automated checks.

If you share

  • How you installed it
  • The exact command or steps you run
  • A short sample of the output
    people can point to the exact issue faster.
3

Couple of things I’d add on top of what @himmelsjager already laid out, since you’re specifically unsure if it’s configured right and what some of the features actually mean in practice.

1. Quick “sanity check” to see if your setup is actually working

Instead of just trusting the tool, try this:

  1. Pick a username that:
    • You know exists on at least 3–4 big platforms (social, dev, forum, etc.).
  2. Run Whatsmyname on it.
  3. Look at:
    • Total number of sites scanned.
    • How many “Found” results you get.
  4. Manually click 3–5 of those “Found” URLs:
    • If they open actual profile pages that match your expectations, your detection logic + JSON are probably fine.
    • If the URLs look weird, go to generic homepages, or error pages, your JSON might be outdated or the app is not using the JSON correctly.

If you run a username and you’re only seeing like 5–10 sites checked, that’s a red flag your JSON file is not loaded, even if the program “runs” without crashing.

2. Interpreting the results beyond simple Found / Not Found

This is where a lot of folks get confused:

  • “Found” does not always mean “correct profile.”

    • Some sites return 200 on any profile URL, even if it doesn’t exist.
    • Some respond with a generic “user not found” page but still HTTP 200.
    • The JSON file contains logic to handle that using “error” keywords, URL patterns, etc. If that logic drifts out of date, you get false positives.

  • “Not Found” can also be wrong:

    • If the site changed its URL structure, the pattern in the JSON no longer matches.
    • Or the site added Cloudflare / WAF that returns some unexpected response.

So, treat the tool as triage, not proof. Always manually verify critical hits.

3. Features that usually confuse people

You didn’t paste screenshots, but a few features often trip people up:

  • “Unknown” / “Error” statuses
    Those often just mean:

    • The site timed out.
    • The HTTP code or response content did not match any of the “found” or “not found” patterns in the JSON.
      These are not necessarily “broken config,” just cases the tool cannot classify. You’re supposed to manually inspect those if they matter.

  • Category filters / tags
    If your results feel too few:

    • Check if categories like “NSFW,” “forums,” or “low-priority” are disabled.
    • Some builds ship with certain categories unchecked by default so that the output is less noisy.

  • “Only active sites” or similar toggles
    Some forks let you hide dead or flaky sites. If that’s turned on, you won’t see everything in the JSON, which can be confusing when you compare your results to screenshots from other people.

4. Concurrency and “I think I broke it” behavior

I slightly disagree with @himmelsjager on numbers here. On slow or flaky connections, 10 threads can be overkill and just give you a wall of errors. For testing your config:

  • Start with:
    • 1–3 threads
    • Reasonable timeout like 10–15 seconds
  • Once you know it works, then raise to 5–10 threads if you really need speed.

If your first test run is already with 20+ threads, it can look like the tool is misconfigured when in reality sites are just rate limiting you.

5. How to tell if the JSON DB is actually being used

A subtle but important check:

  • Open the JSON in a text editor and search for a clearly named site (for example, a major social platform).
  • Then run a search in the app.
  • If that site never appears in the results list at all (not even as Not Found), either:
    • The app is pointing to the wrong JSON, or
    • The app has its own baked-in DB and isn’t using the file you think it is.

Some forks have both:

  • A default internal DB.
  • An option to override with a custom JSON path.

If you change the external JSON but the app ignores it, you’ll swear you “updated the DB” when you actually didn’t.

6. Troubleshooting logic vs network

To separate “my network is broken” from “my config is broken”:

  • If every site shows “Error,” “Unknown,” or similar:
    • Check network, VPN, proxy, firewall first.
  • If some sites show clean Not Found / Found, and some show Unknown:
    • Your network is probably fine. Those Unknowns are pattern / JSON issues, not setup issues.
  • If the tool finishes in like 1–2 seconds for hundreds of sites:
    • That often means it never really requested anything and bailed early due to a config problem, missing JSON, or crash in the background.

7. When you’re still not sure

If you want more targeted help, post:

  • Exact command you’re using or the steps you click in the GUI.
  • A short snippet of the output:
    • Example of one “Found”
    • One “Not Found”
    • One “Unknown/Error”
  • The number of total sites it says it checked.

With just those three data points, people can usually tell:

  • Whether the DB is loaded
  • Whether your filters are too strict
  • Whether your network/proxy is killing the requests

You’re probably not “missing a secret step”; it’s usually:

  • Old DB
  • Wrong JSON path
  • Too aggressive filters
  • Or just misreading what Found / Not Found / Unknown actually mean.
4

Let’s zoom in on the stuff that often still feels “off” even after you follow what @sternenwanderer and @himmelsjager already laid out.

1. How to tell if your copy of Whatsmyname App is behaving normally

Instead of more setup steps, look at behavioral signs:

  • A typical full run:
    • Takes at least several seconds, often longer, depending on threads and timeouts.
    • Shows a mix of statuses: some Found, plenty Not Found, and a handful of Unknown / Error.
  • Red flags:
    • Every single site is “Error” or “Unknown” → usually network, proxy, or firewall.
    • Only a tiny handful of sites appear (like under ~30) even though the JSON is large → the app is likely not loading the main database file.
    • The scan finishes almost instantly and reports “0 sites checked” or some tiny number → often a bad path to the JSON or a parsing error.

You do not need to be 100 percent sure about every detection rule to know if the tool is configured. You just need to see:

  • A realistic site count.
  • Mixed results.
  • Live HTTP responses (codes not all identical).

2. “Why does this site not show up at all?” is a config clue

A trick I use that’s a bit different from what was suggested before:

  • In the Whatsmyname App, look at the site listing if it has one:
    • Some builds let you view all known sites or search by site name before you even run a username query.
  • If a well known platform is missing from that list:
    • The JSON file loaded by Whatsmyname App is incomplete or an older fork.
  • If the site is visible in the list, but:
    • It never appears in results for any username, that often indicates:
      • It is disabled in filters.
      • Or the app crashed on that site internally and silently skipped it.

So, instead of only checking URLs in a browser, first confirm that the internal site registry looks sane.

3. Filters & categories can be more confusing than the JSON

I slightly disagree with the idea that filters are just about “too few results.” Filters can also fake a config problem:

  • If you enable only a narrow category like “code hosting,” the app might show you something like “Scanned 50 sites” and you’ll think the DB is tiny.
  • Some forks of Whatsmyname App default to:
    • Disabling certain “unstable” or “NSFW” categories.
    • Hiding sites tagged as deprecated.
  • To test configuration, ignore fine grained targeting:
    • Temporarily turn everything on.
    • Disable only categories that clearly do not apply to your use case later.

If you are trying to diagnose setup, you want as noisy and complete an output as possible first.

4. Distinguishing “tool limitations” from “your setup is wrong”

There is a subtle but important distinction that people miss:

  • Tool limitation:
    • Some websites are protected by strong anti bot tech.
    • Some give JavaScript dependent responses.
    • Whatsmyname App is largely a simple HTTP client, not a browser.
    • Those targets can endlessly show “Unknown” or “Error” even with perfect configuration.
  • Your misconfiguration:
    • Repeated SSL errors on almost everything.
    • Connection refused or network unreachable messages.
    • Identical response patterns on every site regardless of username.

So if you see errors only on a few tricky platforms and everything else behaves normally, your config is probably fine and you are just hitting tool limits.

5. Result interpretation shortcut for sanity checks

Instead of inspecting full HTML, try this workflow:

  1. After a run, sort or group results by status if the UI supports it.
  2. Pick:
    • 2 entries from “Found”
    • 2 from “Not Found”
    • 2 from “Unknown” or “Error”
  3. Open their URLs in a browser and ask:
    • For Found: “Is this clearly a user profile, not a generic page or search result?”
    • For Not Found: “Do I see explicit ‘user not found’ messaging or something similar?”
    • For Unknown/Error: “Is the site showing CAPTCHAs, login gates, or generic protection pages?”

You do not need to check everything. If your small sample looks logically consistent with the status labels, the Whatsmyname App detection logic is at least roughly in sync.

6. Where I’d handle threads & timeouts differently

Both other answers already mentioned concurrency, but I’ll emphasize a different angle:

  • Instead of thinking “What is a safe thread number globally,” think:
    • “What setting gives me stable behavior on my connection?”
  • Start with:
    • Timeout: 8 to 12 seconds.
    • Threads: 3 to 5.
  • If you see mostly clean responses and few rate limits:
    • Inch up threads slowly.
  • If your output suddenly fills with HTTP 429 or intermittent timeouts when you increase threads:
    • Dial back. The optimal number for you might be lower than what someone on a fast, stable connection can use.

This incremental approach tells you that the app is working and shows you your personal ceiling, instead of guessing a magic number.

7. Pros & cons of using Whatsmyname App for what you are doing

Pros

  • Centralized username checking instead of visiting dozens of platforms manually.
  • Uses a shared JSON database so improvements can propagate quickly when updated.
  • Makes it easier to visually see the “footprint” of a handle across social, forums, and other services.
  • Many forks allow exporting results, which is useful if you are documenting findings.

Cons

  • Dependent on the freshness and correctness of the JSON file. If nobody updated entries for a site, detections can be wrong.
  • Limited by simple HTTP request logic. It struggles with JS heavy or strongly protected sites.
  • Can be noisy. Even when correctly configured, you still need manual verification.
  • Different forks behave a bit differently, which can be confusing when reading instructions or advice from other users.

Compared with what @sternenwanderer and @himmelsjager already laid out, the main thing I would add is that you should stop worrying about “secret” hidden configuration steps. If:

  • Your site count is realistic,
  • You see a mix of statuses,
  • A spot check of several URLs matches the labels,

then your Whatsmyname App is functionally configured, and any remaining weirdness is either specific site behavior or inherent tool limitations, not something you forgot to toggle.