No, and it never will. It only decodes the fields and recomputes the check digit from the pasted key itself, entirely in your browser.
Carregando ferramenta… / Loading tool…
Decode and validate the 44-digit Brazilian NFe/NFCe access key locally, without querying SEFAZ.
The access key is the 44-digit numeric unique identifier of an NFe or NFCe, defined by the Manual de Orientação do Contribuinte (MOC) and used with the same layout by CTe and MDFe. It concatenates, with no separators, the issuer's state IBGE code (2 digits), the issuance year and month in AAMM format (4 digits), the issuer's CNPJ (14 digits), the document model (2 digits, 55 for NFe and 65 for NFCe), the series (3 digits), the invoice number (9 digits), the emission type (1 digit), a numeric code chosen by the issuer (8 digits), and finally a check digit computed in modulo 11 over the previous 43 digits. The digit calculation multiplies each of the 43 digits, right to left, by the multipliers 2, 3, 4, 5, 6, 7, 8 and 9 in a cycle, sums everything, takes the remainder of dividing by 11, and the check digit is 0 when the remainder is 0 or 1, or 11 minus the remainder otherwise. This tool performs exactly that decoding and recalculation in your browser; it never queries the SEFAZ web service and does not confirm whether the invoice was actually authorized, issued or canceled, that is what the official public NFe lookup is for.
The access key concatenates 9 fixed-length fields with no visible separator: positions 1-2 are the state IBGE code (cUF), 3-6 are the issuance year/month (AAMM), 7-20 are the issuer's CNPJ (14 digits), 21-22 are the document model (mod, 55 = NFe, 65 = NFCe), 23-25 are the series, 26-34 are the document number (nNF, 9 digits), 35 is the emission type (tpEmis), 36-43 are a numeric code generated by the issuer (cNF, 8 digits), and 44 is the check digit (cDV).
The emission type (tpEmis) shows whether the invoice went through the normal channel (code 1) or one of the contingency modes used when SEFAZ's system is unavailable: FS-IA (2), SCAN (3, discontinued), DPEC (4, discontinued), FS-DA (5), SVC-AN (6), SVC-RS (7), or NFCe offline contingency (9). Code 8 is not used.
The check digit matching means the 44 digits form a mathematically consistent key, it does not prove the invoice was actually issued, authorized, canceled, or is still active at SEFAZ. A key can have a correct check digit and still have never been submitted for authorization, or have been canceled afterward. To confirm the real status of an NFe, you need the official public NFe lookup for the issuing state or the National Portal, something this tool deliberately does not do, so it can stay 100% local and free of third-party dependencies.
Paste the code into your HTML and the tool shows up on your page, without J-Kit's navigation and ads. It still runs in the browser of whoever visits your site.
<iframe
src="https://jkit.tools/embed/en-US/nfe-access-key-validator"
width="100%"
height="600"
style="border:0"
loading="lazy"
title="Brazilian NFe Access Key Validator"
></iframe>These references help contextualize formulas, standards, APIs and limitations used on this page. They do not replace professional validation when a result has legal, financial, medical or operational impact.
No, and it never will. It only decodes the fields and recomputes the check digit from the pasted key itself, entirely in your browser.
Paste the 44-digit access key to decode its fields.
Decoding happens locally in your browser. The key is never sent to a server; analytics receives only the validation status.