Brazilian CNH Generator

Continue in the tool

More pages for this tool

Synthetic CNH number in a privacy-first sandbox

Synthetic CNH in a privacy-first sandbox

A CNH number identifies a specific driver and usually travels together with license category, points and infraction history, a data bundle far more sensitive than the isolated number suggests. Copying a real driver's CNH to populate a test environment spreads that sensitive bundle outside the place it was meant to be protected. This page explains why generating the value locally avoids that problem.

What travels alongside a CNH number

On its own, a CNH number is already a direct identifier, but in practice it rarely circulates alone: HR, logistics and mobility systems commonly attach the CNH to license category, points, validity and, in some cases, infraction records. A staging environment that replicates those entire tables with real drivers' data, even just to "test the relationship between tables", ends up reproducing a sensitive traffic-data bundle inside an environment that typically has longer retention, looser access control and less auditing than production.
This site's generator draws a 9-digit base in the browser and computes the two check digits with the modulo-11 formula described on the rules page, without querying any traffic authority, driving record or database of issued licenses. The value is born from the calculation, not from a copy, which breaks the link between the synthetic number and any specific real driver; the filter that discards repeated sequences further reduces the chance of the value accidentally colliding with an obvious pattern like 11111111111.
The practical recommendation is the same for any synthetic identifier: generate the value at test time, avoid persisting it in a long-lived database, and mark it in some way, a prefix in the test environment, a metadata field, as fictional. That matters because, once inside a staging "registered drivers" table, the system that processes the data cannot tell a synthetic CNH from a real one; the care taken at origin, generating instead of copying, is what keeps a real person from ending up represented in that table.

Where a synthetic CNH avoids exposing a real driver

Driver sign-up in a test logistics app

Input: campo obrigatório de CNH num formulário de cadastro de entregador
Expected output: CNH sintética gerada no navegador, sem relação com nenhum entregador real

Prevents the "test couriers" table from carrying the same driving identifier that would appear in production.

Simulated point-tracking spreadsheet

Input: coluna "CNH" numa planilha de teste de regra de suspensão por pontos
Expected output: valores sintéticos que nunca correspondem a um condutor com pontuação real

If the spreadsheet is shared beyond the team, no real person's actual driving-point record is exposed alongside it.

Commercial demo environment

Input: tela de exemplo mostrando cadastro de "motorista modelo" para um cliente
Expected output: CNH sintética visível na demonstração, desvinculada de qualquer funcionário ou motorista real

In a live demo, using a coworker's real CNH as a placeholder exposes that person's driving history to whoever is watching, even unintentionally.

Full tool FAQ

Is the generated CNH a real document?

No. It only follows the mathematical format used by form validators.

Does the tool query an official database?

Why do check digits matter in tests?

Can I use it in staging?

Does CNH include a state code like voter ID?

Is the number stored locally?

Does this replace official validation?

When should I use fixed fixtures?

Frequently asked questions

Does a synthetic CNH still count as sensitive personal data?

Not if it does not correspond to any real driver: without a link to an identifiable person, the generated number is not anyone's personal data; the sensitive-processing risk exists when the value is a real CNH, or when a synthetic one is mistakenly linked to a record that represents an actual person.

Why not use an employee's CNH as an example in internal documentation?

Because it spreads that person's number, and possibly their license category and associated history, across documents, screenshots and repositories in a way they almost certainly never authorized; a synthetic value fills the same example role without carrying anyone along with it.

Does generating the synthetic CNH locally avoid an unnecessary network call?

Yes, the entire calculation, drawing 9 digits and computing two modulo-11 check digits, runs in the browser; a generation endpoint would be an unnecessary network surface, and it would still leave a server record of every value issued.

Does a staging environment with a synthetic CNH still need access control?

Yes, the basic care that applies to any environment, access control, limited retention, still holds; what changes is that if this environment leaks, no real driver has their license number, category or history exposed alongside the rest of the test data.

Next steps

Continue in the tool

Open full tool

Synthetic CNH number in a privacy-first sandbox

Synthetic CNH in a privacy-first sandbox

What travels alongside a CNH number

On its own, a CNH number is already a direct identifier, but in practice it rarely circulates alone: HR, logistics and mobility systems commonly attach the CNH to license category, points, validity and, in some cases, infraction records. A staging environment that replicates those entire tables with real drivers' data, even just to "test the relationship between tables", ends up reproducing a sensitive traffic-data bundle inside an environment that typically has longer retention, looser access control and less auditing than production.

This site's generator draws a 9-digit base in the browser and computes the two check digits with the modulo-11 formula described on the rules page, without querying any traffic authority, driving record or database of issued licenses. The value is born from the calculation, not from a copy, which breaks the link between the synthetic number and any specific real driver; the filter that discards repeated sequences further reduces the chance of the value accidentally colliding with an obvious pattern like 11111111111.

The practical recommendation is the same for any synthetic identifier: generate the value at test time, avoid persisting it in a long-lived database, and mark it in some way, a prefix in the test environment, a metadata field, as fictional. That matters because, once inside a staging "registered drivers" table, the system that processes the data cannot tell a synthetic CNH from a real one; the care taken at origin, generating instead of copying, is what keeps a real person from ending up represented in that table.

Where a synthetic CNH avoids exposing a real driver

Driver sign-up in a test logistics app

Input: campo obrigatório de CNH num formulário de cadastro de entregador
Expected output: CNH sintética gerada no navegador, sem relação com nenhum entregador real

Prevents the "test couriers" table from carrying the same driving identifier that would appear in production.

Simulated point-tracking spreadsheet

Input: coluna "CNH" numa planilha de teste de regra de suspensão por pontos
Expected output: valores sintéticos que nunca correspondem a um condutor com pontuação real

If the spreadsheet is shared beyond the team, no real person's actual driving-point record is exposed alongside it.

Commercial demo environment

Input: tela de exemplo mostrando cadastro de "motorista modelo" para um cliente
Expected output: CNH sintética visível na demonstração, desvinculada de qualquer funcionário ou motorista real

In a live demo, using a coworker's real CNH as a placeholder exposes that person's driving history to whoever is watching, even unintentionally.

Full tool FAQ

Is the generated CNH a real document?

No. It only follows the mathematical format used by form validators.

Does the tool query an official database?

Why do check digits matter in tests?

Can I use it in staging?

Does CNH include a state code like voter ID?

Is the number stored locally?

Does this replace official validation?

When should I use fixed fixtures?

Frequently asked questions