Name Validation API

Catch fake and junk names, flag profanity, gibberish and obviously fake names before they reach your CRM.

What it checks

Name Validation looks at a submitted name and flags the obvious junk, profanity, keyboard-mash gibberish, and clearly fake entries, before it lands in your CRM. It won't tell you a name is genuinely that person's, but it will catch the 'asdfgh', the test entries and the abuse that pollute lead and sign-up data. For each name it returns a validity flag, a risk level and supporting notes, so you can decide what to accept, review or reject on any name field.

What it returns

Valid , whether the name passes basic plausibility checks
Profanity flag , whether the name contains profanity
Risk level , an overall low / medium / high read on the name
Type , the classification of the entry where available
Notes , supporting detail on why the name was flagged

When to use it

At sign-up and on lead forms, to reject profanity, gibberish and obvious test entries at the point of capture.
To improve CRM hygiene, keeping junk names out of the records your team works from.
As a lightweight quality signal on lead-gen and form data, alongside email and phone checks.
In bulk, to flag the worst entries in an existing list.

When not to use it

As identity verification, it flags obviously fake names, but it does not confirm a name belongs to a real, specific person. Use breach, IP and other signals for that.
As the sole reason to reject a record, unusual but legitimate names exist; treat a flag as a prompt to review, not an automatic fail.
For culturally diverse names without care, plausibility checks can misread valid names, so combine the flag with other signals before acting.
As a fraud verdict, junk names are a quality signal, not proof of fraud on their own.

How to read the result

Use it to filter obvious junk, and treat edge cases as a prompt for review rather than a hard reject.

Valid, low risk: Looks like a plausible name. Accept and proceed.
Profanity flagged: Almost always junk or abuse. Safe to reject at the form.
Gibberish / high risk: Likely a test entry or bot. Reject or route for review, especially alongside other risk signals.
Flagged but plausible: Some legitimate names trip plausibility checks. Review rather than auto-reject, and weigh your other signals.

Pricing

Start Free

API & bulk usage

Run Name Validation in real time on every name field, or in bulk to check a whole list in one pass. Each name comes back with a validity flag, a profanity flag, a risk level, a type and supporting notes, so you can decide what to accept, review or reject. Combine it with other checks in a single request when you want name, email and phone quality together.

Read the API reference →

Request

{
  "name": {
    "name": "Simon Delaney"
  }
}

Response

{
  "name": {
    "valid": true,
    "profanity": false,
    "risk": "low",
    "type": "personal",
    "notes": "Plausible name, no issues detected"
  }
}

Common Questions

Name Validation FAQ

Does name validation prove a name is real?

No. It flags obviously fake, profane or gibberish names. It doesn't confirm that a plausible name belongs to a specific real person, for that, combine it with breach, IP and other identity signals.

Is it free?

Name Validation is free to start, so you can filter junk names on submission without adding cost.

Will it reject unusual but real names?

It can flag uncommon names, which is why a flag is best treated as a prompt for review rather than an automatic reject. Weigh it alongside your other checks.

What does it catch best?

Profanity, keyboard-mash gibberish and obvious test entries, the junk that pollutes lead and sign-up data, caught at the point of capture before it reaches your CRM.

Start with this check

Create a free account, claim your credits and run Name Validation as a real-time API or a bulk upload. No card required.