AcademicEmploymentProfessionalHow it worksUniversitiesSchoolsEmployers & BGVPlatformsIntelligenceDevelopersTrust & SecurityCandidate RightsPlansSign in
Employer Intelligence

Resolve the company behind the experience claim.

Legal Identity · Domains · HR Routes · Corporate History

The employer registry is designed to answer a different question from document forensics: what company existed, under what identity, at what time, and which official channel can independently confirm the claim?

Employer intelligence graphIdentity before claim
Employercanonical entity
Official domainscurrent + historical
HR channelsemail + phone routes
Corporate historymerge · rename · defunct
Locationsregistered + operating
Source-firstAuthoritative routes outrank appearanceMinimum evidenceEscalate only what can resolve uncertaintyHuman gateSerious adverse outcomes require reviewAuditableMaterial actions preserve lineage
WHAT BONAFIDE DOES

Purpose-built verification capabilities.

Each capability is a visible part of the verification workflow—not a hidden AI score.

Legal identity

Legal name, aliases, public registration identifiers where relevant, incorporation date, registered address and entity status.

Corporate relationships

Parent, subsidiary, merger/acquisition, rebrand and defunct/struck-off history.

Digital identity

Official websites, official/current/historical domains and careers domains.

HR verification routes

Official HR email #1/#2, phone #1/#2, careers/verification portals and source class.

Operational intelligence

Last checked, response success, median/p90 reply time and follow-up counts.

Document patterns

Known repeated experience/relieving/offer patterns only where enough trusted evidence exists; no assumption every employer has a stable template.

EVIDENCE MODEL

Corporate existence is not proof of individual employment.

Company registries and official corporate sources can confirm the entity and its historical status. Individual employment still needs independent confirmation, chronology or other lawful corroboration.

  • Applicant-provided contact stays separate from trusted registry contacts
  • Phone callbacks use official registry numbers
  • Domain age is a risk signal only—not proof
  • Employer response history is versioned by route
CORPORATE GRAPHResolve history before claim
Claimed employercanonical identity
Former namehistorical alias
Parent & grouprelationship
HR domainA1/A2 channel
Status historyactive, merged or defunct
WORKFLOW

From input to defensible evidence.

Bonafide follows the strongest available verification route and resumes only the affected lane when new evidence arrives.

01Resolve entity
02Resolve claimed period
03Resolve trusted HR route
04Verify chronology/source
05Record response evidence
DESIGNED FOR

One evidence model. Role-specific operations.

The same underlying case can be viewed differently by institutions, employers, reviewers, operations and candidates.

01

BGV teams

Independent route resolution

02

Employers

Candidate experience verification

03

Universities/platforms

Employment evidence inside broader cases

DECISION DISCIPLINE

Unknown fake.

Unmapped issuer, new template, legacy document or unavailable source must route to uncertainty/manual verification rather than an automatic accusation.

Authority VerifiedAuthoritative source evidence is consistent.
Highly ConsistentStrong supporting evidence; independent source not complete.
Evidence RequiredA targeted item can likely resolve the case.
Unable to DetermineEvidence remains insufficient; no fraud conclusion.
DCS BONAFIDE · CREDENTIAL INTELLIGENCE PLATFORM

Establish what is bona fide.
Preserve the evidence.

Verify a credentialOpen portal