Skip to content

ZeroTrace OSINT

Email & Username Permutators

Generate plausible email and username variants for a person — fed directly into username search and email analysis.

The permutator tools generate the candidate identifiers a person might use, given the identifiers you already know. They are the "list-builder" tools that feed into username search and email analysis.

Two permutators ship in this category:

  • Email permutator — given a name and a domain, generate the email-address variants the person plausibly uses.
  • Username permutator — given a name (and optional birth year, optional known handles), generate the handle variants the person plausibly uses.

Email permutator

Inputs:

  • First name.
  • Last name.
  • Optional middle name / initial.
  • Optional birth year.
  • The target domain (example.com).

The tool generates the standard ~25 patterns:

  • firstname@, lastname@, firstname.lastname@, firstnamelastname@, firstname_lastname@, firstname-lastname@.
  • flastname@, firstnamel@, f.lastname@, firstname.l@.
  • Initials (fl@, f.l@, fl_lastname@).
  • Year-suffixed variants (firstname1990@, firstname.lastname1990@).
  • Aggressive variants (firstname.middle.lastname@, firstname-middle-lastname@, social-handle-style).

For each candidate, the tool runs a quick check against the email analyzer:

  • MX exists for the domain.
  • Disposable / free-provider / role-account flags.
  • Catch-all status (if the domain is catch-all, every variant "exists" by definition).

Result table shows the candidate, the analyzer's flags, and a deliverability hint per variant.

For target domains that are catch-all, the email permutator is less useful as an existence check — every variant exists. It is still useful as a list-builder for enumerating which variants the subject likely actually uses.

Username permutator

Inputs:

  • First name.
  • Last name.
  • Optional birth year.
  • Optional known handles (the tool will preserve the patterns that match what you already know).

The tool generates ~80 deterministic permutations:

  • Mechanical combinations (firstname.lastname, fnlastname, fl, etc.).
  • Year-in-various-positions variants.
  • L33t-substitution variants (a@, e3, i1, o0, s5).
  • Cultural-pattern presets (English-style, Spanish-style, French-style, Asian-style — different conventions for given-name vs. family-name ordering).

The result list is sorted by likelihood. If you supplied known handles, the patterns matching what you already know are surfaced first.

A one-click action auto-composes into the username search — the entire permutation list runs through the cross-platform sweep automatically.

Why permutators matter

A typical investigation pattern:

  1. You have a name and a domain.
  2. Email permutator generates 25 candidates.
  3. The analyzer's MX + role-account check filters to ~10 plausible variants.
  4. You pick the most likely 2-3 and use them in your follow-up.

Or:

  1. You have a name and a known handle from one platform.
  2. Username permutator generates 80 candidates, sorted by similarity to the known handle.
  3. Auto-compose into username search.
  4. Cross-platform sweep tells you which variants appear on which platforms.

This is the workflow that makes "find someone across platforms" tractable rather than a series of one-off Google searches.

Pivots

The permutators do not produce facts that pivot — they produce candidates. The pivots come from running the candidates through the next tool:

Bulk permutation

Bulk paste accepts a list of names. Each name produces its own permutation set. Aggregate table shows the full candidate list for triage.

For target lists generated against many names, the auto-compose-into-search action handles the entire batch as one job.

Sources

  • All permutation logic runs locally. No external sources are queried.
  • The cultural-pattern presets are bundled with the application.
  • Auto-compose into the analyzer / search uses the respective tools' sources.

Command Palette

Search for a command to run...