en

CURP/RFC Mexico

Check the check digit of a Mexican CURP or the format of an RFC number and read off the birthdate it encodes - locally in your browser, with no upload.

Running locally on your device ...

This tool performs only a mathematical checksum/format check. It is not an official identity, existence, or registry verification and not a request to any authority. Any additional information derived from the number's structure is based solely on the publicly documented encoding logic of the issuing authority. In addition: for the RFC, only format and date are checked - the 3-character homoclave is assigned by SAT via non-publicly-documented internal software and is therefore not recomputed.

Running locally on your device ...

0%

Is my file uploaded?

No. Everything runs in your browser - your file never leaves your device. How this is verifiable

No upload100% local
Your content stays with youno third-party access
Hosted in GermanyGlobal Content Delivery
Independently auditedTLS A+ · HTTP headers A+

The CURP (Clave Unica de Registro de Poblacion, 18 characters) identifies people in Mexico and encodes birthdate, sex and state of birth directly in its structure. A final check character is computed from a fixed value table and a weighted digit sum - this tool recomputes it and, at the same time, reads off the birthdate, sex and state of birth from the structure.

The RFC (Registro Federal de Contribuyentes, 12-13 characters) identifies taxpayers: 4 letters plus a birthdate for natural persons, 3 letters plus an incorporation date for companies, each followed by a 3-character homoclave. That homoclave is assigned by the Mexican tax authority SAT via internal, non-publicly-documented software - this tool therefore honestly checks only format and date, without recomputing the homoclave itself or faking a check it cannot perform.

The whole calculation runs entirely locally in your browser in pure JavaScript - the CURP or RFC is not uploaded, not stored, and no foreign library is loaded from a CDN. You can download the result as a JSON file or read it directly.

Specifications

Specifications
Input formatsText input
Output formatJSON
Batch processingNo
ProcessingLocally in your browser (JavaScript)
File uploadNone

In 3 steps

  1. Paste a CURP (18 characters) or RFC (12-13 characters) into the text field.
  2. The tool auto-detects the type from the length.
  3. Read the result including the decoded details, or download it as JSON.

Limitations: This tool performs only a mathematical checksum/format check. It is not an official identity, existence, or registry verification and not a request to any authority. Any additional information derived from the number's structure is based solely on the publicly documented encoding logic of the issuing authority. In addition: for the RFC, only format and date are checked - the 3-character homoclave is assigned by SAT via non-publicly-documented internal software and is therefore not recomputed.

FAQ

Is my CURP or RFC uploaded?

No. The check runs entirely locally in your browser; the number never leaves your device and is not stored.

Does the tool also verify an RFC's homoclave?

No, honestly not: SAT assigns the homoclave via internal, non-publicly-documented software. This tool only checks format and date, never the homoclave itself.

Why does the RFC check show two possible date years?

Because the RFC only carries the year as two digits - the century is not unambiguously derivable from that alone. The tool honestly shows both readings instead of guessing one.

What does the tool decode from a valid CURP?

Birthdate (including the century, which a dedicated marker in the code fixes unambiguously), sex (H for male, M for female) and the 2-letter state code - no registry lookup, only the publicly documented encoding logic.

How does the tool tell a CURP from an RFC apart?

By length: 18 characters are checked as a CURP, 12 or 13 characters as an RFC.

Related tools

DNI/NIE Spain · Calculate a checksum · UUID generator