Maigret Username OSINT — Public Footprint Dossier

Search a username across a large catalog of public websites and turn available matches into a structured digital-footprint dossier.

Review profile links, categories, countries, public identity fields, visibility signals, and an optional exposure score — without manually checking hundreds of sites one by one.

Use this Actor only for usernames you own or are authorized to investigate. It checks publicly accessible information and does not provide access to private accounts.

Public username checks for authorized footprint reviews

Use Maigret Username OSINT to organize publicly accessible account references for your own username, an authorized brand review or a documented security assessment. Start with a small named site set and inspect source links before expanding. The deliverable is a set of observed username matches and a dossier; a shared handle is not proof that accounts belong to the same person.

Review goal	Useful settings	Interpretation
Check one known public site	sites, one username	Site-specific observation, not universal identity verification
Review a ranked catalog subset	Small topSites	Coverage of the chosen subset only
Minimize unnecessary fields	extractData false, recursion off	Presence research without requesting extra profile parsing
Prepare a manual review table	perSiteRecords true, CSV export	Individual source links plus separate dossier context

Catalog membership is not a promise that every listed site is reachable or accurately classifiable today. Rate limits, renamed profiles and site changes can produce unknown or incorrect classifications; independently review consequential matches.

What you get

• A consolidated dossier for each submitted username.
• Found-profile records with site, URL, category, and available public fields.
• Category and country breakdowns for the observed footprint.
• Optional public names, bios, locations, avatars, websites, and contact fields when available.
• An explainable exposureScore and high-level visibility flags.
• JSON, CSV, Excel, XML, or RSS export through Apify.
• A run summary with profile counts and top categories.

Coverage evolves as websites change. A matching username does not prove that the same person controls every account.

Quick start

{
  "usernames": ["northstar_maya"],
  "topSites": 500,
  "extractData": true,
  "recursiveSearch": false,
  "perSiteRecords": true,
  "exportFormat": "default"
}

For a faster first pass, use topSites: 100 or 200. Increase coverage only when the initial results justify a broader authorized review.

Main options

Input	Purpose	Default
usernames	Usernames to review	required
topSites	Number of catalog sites to check; 0 selects all	500
tags	Include selected categories or countries	—
excludeTags	Exclude categories such as dating or NSFW	—
sites	Limit the run to selected site names	—
extractData	Include available public profile fields	true
deepEnrichment	Enable additional public-footprint fields	false
recursiveSearch	Include related public identifiers when available	false
maxProfilesPerUsername	Cap returned and billed profile matches	0
perSiteRecords	Save individual profile rows in addition to the dossier	true
exportFormat	Rich JSON or a flatter CSV-oriented row	default

Example dossier

The example below is entirely fictional. Values are illustrative and do not identify a real person.

{
  "recordType": "dossier",
  "username": "northstar_maya",
  "sitesChecked": 500,
  "profilesFound": 23,
  "exposureScore": 68,
  "exposureTier": "high",
  "exposureReasons": [
    "profiles found across multiple categories",
    "consistent public username presence",
    "additional public profile fields available"
  ],
  "categoryBreakdown": {
    "social": 8,
    "coding": 6,
    "gaming": 4,
    "forums": 3,
    "other": 2
  },
  "countries": ["global"],
  "riskFlags": {
    "realNameExposed": false,
    "locationExposed": false,
    "emailExposed": false,
    "sensitivePresence": false,
    "linkedAccountsFound": true
  },
  "foundProfiles": [
    {
      "siteName": "Example Coding Community",
      "profileUrl": "https://example.invalid/profile/northstar_maya",
      "tags": ["coding"]
    }
  ]
}

Example profile record

When perSiteRecords is enabled, each available match can also be saved as a separate row:

{
  "recordType": "profile",
  "username": "northstar_maya",
  "siteName": "Example Coding Community",
  "profileUrl": "https://example.invalid/profile/northstar_maya",
  "status": "Claimed",
  "tags": ["coding"],
  "bio": "Open-source contributor and developer tools enthusiast"
}

The Actor does not invent unavailable fields. Profile existence and extracted details should be independently verified before they are used in an investigation or report.

Understanding the exposure score

exposureScore is an explainable 0–100 research aid that summarizes how broadly a username and related public fields appear across the collected results.

It is not a threat score, identity proof, criminality assessment, or measure of a person's trustworthiness. Similar usernames may belong to unrelated people. Review source links, dates, content, and contextual evidence before connecting accounts to one identity.

Standard and Deep modes

Standard

Returns public profile matches, available identity fields, the dossier, category breakdowns, exposure score, and visibility flags.

Deep

When deepEnrichment: true, the output may include additional publicly exposed fields such as account-age signals, personal websites, phone numbers, and cross-platform reach where available.

Deep mode processes more data and uses a separate result event price. Collect these fields only when they are necessary and lawful for your authorized purpose.

Current pricing and previous rates

Each confirmed profile match is billed once. Dossier and summary records are not billed as profile matches.

Historical rates through September 6, 2026

Mode	Per profile	Per 1,000 profiles
Standard	$0.007	$7.00
Deep	$0.015	$15.00

Active since September 7, 2026

Mode	Per profile	Per 1,000 profiles
Standard	$0.0015	$1.50
Deep	$0.005	$5.00

Apify platform usage is paid separately by the user under the active configuration. The Actor Start event is $0.00005 per GB of allocated memory, minimum one event. Always review the pricing displayed by Apify before starting a large run.

Use maxProfilesPerUsername as a cost guard for common usernames.

Common use cases

• Audit your own username reuse and public exposure.
• Support authorized security assessments and incident response.
• Verify public attribution leads during responsible journalism.
• Review brand impersonation or account-squatting signals.
• Organize already-public profile references for a documented investigation.

Responsible-use requirements

• Obtain authorization before investigating another person's username.
• Do not use results to stalk, harass, intimidate, dox, discriminate, or locate private individuals.
• Do not infer sensitive traits from categories or profile membership.
• Treat matches as leads requiring verification, not confirmed identity links.
• Minimize collection of contact and location data and delete it when no longer needed.
• Follow applicable privacy laws, workplace policies, and the terms of checked websites.

FAQ

Does a found profile prove account ownership?

No. Username reuse and collisions are common. Verify identity using multiple independent contextual signals.

Are all 3,000+ sites checked by default?

No. The default checks a smaller ranked subset. Set topSites: 0 only when broader coverage is necessary and authorized.

Why can results change between runs?

Public profiles are created, renamed, removed, restricted, or temporarily unavailable. Website behavior and the supported catalog also evolve.

Are contact details guaranteed?

No. They appear only when supported public pages expose them and the corresponding option is enabled.

Can I export one row per match?

Yes. Enable perSiteRecords and download the run's Dataset in your preferred format. Use exportFormat: "csv" for a flatter output shape.

Attribution

This Actor integrates the open-source Maigret project, distributed under the MIT License. It is an independent integration and is not affiliated with or endorsed by the Maigret project or its authors.

Support

Open an issue on the Actor page with a non-sensitive sample username and run ID. Remove credentials, personal contact details, and private case information before sharing diagnostics.

---

⚖️ Legal, Compliance & Acceptable Use

Please read this section carefully. By running this Actor you accept these terms.

Bottom line: this is a neutral, general-purpose software tool. It only retrieves information that is already publicly available. You — the user — decide what to search for and how to use the results, so you alone are responsible and liable for that use. The developer/operator of this Actor merely provides the tool and does not control, endorse, or take responsibility for what you do with it.

1. Public data only. The Actor accesses only publicly available information. It does not log in on your behalf, bypass access controls, or retrieve private, paywalled, or password-protected data.

2. You are the responsible party (data controller). For every run you start, you act as the data controller and are solely responsible for using the output lawfully. This includes having a valid lawful basis (for business/B2B use this is typically legitimate interest), honoring data-subject rights (access, correction, deletion, opt-out), and complying with all applicable laws and regulations — including, where relevant, the GDPR, UK GDPR, CCPA/CPRA, and similar privacy, marketing, and anti-spam laws (e.g. ePrivacy, CAN-SPAM, CASL, TCPA).

3. Not a Consumer Reporting Agency. This Actor and its operator are not a consumer reporting agency (CRA), and the output is not a "consumer report" under the U.S. Fair Credit Reporting Act (FCRA) or similar laws. You must NOT use it, in whole or in part, to decide a person's eligibility for credit, employment, housing/tenancy, insurance, or any other FCRA-regulated purpose.

4. Respect third-party terms. You are responsible for complying with the terms of service of any website or platform whose public data you choose to process, and with any applicable intellectual-property rights.

5. No warranty. The Actor is provided "as is", without warranty of any kind. Public data may be incomplete, outdated, or inaccurate — verify independently before relying on it. Availability of sources and fields can change at any time.

6. Prohibited use. Do not use this Actor or its output for stalking, harassment, discrimination, fraud, spam, or any unlawful or harmful purpose.

7. Indemnification. You assume all risk and liability arising from your use of this Actor, and you agree to defend, indemnify and hold the operator harmless from any and all claims, losses, fines, or liabilities — including reasonable legal fees — resulting from your use or misuse of the Actor or its output, or from your breach of these terms or of any law.

This section is general information, not legal advice. If you are unsure whether your intended use is permitted, consult your own legal counsel before running this Actor.

Bounded username-search inputs

Replace the placeholder with a username you own or are authorized to review. The first recipe limits catalog scope and disables recursive/deep collection. A profile cap limits returned/billed matches, not the number of HTTP site checks already needed to find them.

{
  "usernames": [
    "your_own_username"
  ],
  "topSites": 100,
  "extractData": false,
  "recursiveSearch": false,
  "deepEnrichment": false,
  "maxProfilesPerUsername": 5,
  "perSiteRecords": true
}

For a named site, use its catalog name. A site omitted by catalog/tag filters cannot be interpreted as a tested negative.

{
  "usernames": [
    "your_own_username"
  ],
  "sites": [
    "GitHub"
  ],
  "topSites": 100,
  "extractData": false,
  "maxProfilesPerUsername": 1,
  "recursiveSearch": false
}

For a flat worksheet, use CSV-oriented profile records. Read the dossier separately; count profile rows rather than treating every Dataset item as a separately billed match.

{
  "usernames": [
    "your_own_username"
  ],
  "topSites": 100,
  "maxProfilesPerUsername": 5,
  "exportFormat": "csv",
  "perSiteRecords": true,
  "recursiveSearch": false
}

For an aggregate-first review, omit separate per-site rows. The dossier can still contain foundProfiles, and confirmed matches still use their normal result event. Disabling perSiteRecords is an output-shape choice, not a free-search mode.

{
  "usernames": [
    "your_own_username"
  ],
  "topSites": 100,
  "maxProfilesPerUsername": 5,
  "perSiteRecords": false,
  "extractData": false,
  "recursiveSearch": false
}

Read the dossier without turning signals into identity claims

Keep username, siteName, profileUrl and collection context together. A country/category label comes from catalog or observed profile information; it does not establish a person's location or sensitive traits. exposureScore summarizes observed visibility and available fields, not danger, criminality or trustworthiness. Do not combine unrelated accounts solely because they share a username or a display name.

includeNotFound can add free diagnostic rows when per-site output is enabled. A missing result can reflect source behavior or collection errors, not verified account absence. Recursive search can pivot to related public identifiers and expand collection; leave it off unless those pivots are necessary and within your authorization. Deep mode forces profile-page parsing even if extractData is false.

Username-search cost and export questions

What is currently charged? Standard matches use profile-found at $0.0015 each; deep matches use profile-deep at $0.005 each. At 256 MB, five standard matches create $0.0075 plus the minimum $0.00005 startup event, before platform usage. Startup is memory-weighted per GB with a minimum of one.

Are dossier and profile rows two paid results? No. A confirmed profile is the paid unit. Dossier, summary and optional not-found rows are separate output records without an additional profile event. Check the run's actual counters instead of equating total Dataset rows with profiles charged.

Does a match verify ownership? No. Open the source link and corroborate context independently. This service does not reveal private accounts, verify a legal identity or establish permission to contact someone.

Can an AI agent read the output? Yes, through the Actor API/MCP or existing integrations below. Preserve unknowns, evidence links and the authorization boundary. Avoid copying private case notes or unnecessary personal fields into public prompts or issue reports.

n8n and developer integrations

Use this Actor in your automation or application with the existing community integrations below. An Apify account and API token are required; Actor and platform charges follow the current pricing.

• n8n community node: n8n-nodes-apivault-maigret. Install package name n8n-nodes-apivault-maigret in a self-hosted n8n instance that permits community packages.
• Python client and examples: GitHub.
• n8n source and usage: GitHub.

These are community packages. Publication on npm does not establish n8n verification or availability in n8n Cloud. Review the linked package README for supported inputs and setup.