NXP NTAG 224 DNA

NTAG 224 DNA is a passive 13.56 MHz tag IC compliant with ISO/IEC 14443-A Parts 1-4, using the standard's Type A load-modulation scheme and bit-rate-106 anti-collision for single-tag selection. Once selected, it operates as an NFC Forum Type 4 Tag, exposing an ISO/IEC 7816-4-style file system addressed via APDUs over the ISO 14443-4 half-duplex block transmission protocol.

The 224 bytes of user EEPROM are organized into files rather than flat memory, letting designers separate public NDEF content from protected data. Authentication uses AES-128 mutual authentication across up to three independent keys, with CMAC and full encryption available for file read/write operations. A key differentiator is Secure Unique NFC (SUN) messaging: each tap can generate a dynamic, cryptographically signed URL containing tamper and authentication counters, which backend systems or apps validate without needing a live AES session — enabling tap-to-verify flows on unmodified smartphones.

NTAG 224 DNA targets high-volume, cost-sensitive authentication rather than data storage, so its 224-byte memory is deliberately small. It's a strong fit for brand-protection seals on packaging, pharmaceuticals, and luxury goods where a single NFC tap must cryptographically prove genuineness. The same SUN-message mechanism maps directly onto NFC marketing campaigns that need tamper-evidence baked into a promotional tap, and onto supply-chain item-level tracking where tamper counters flag opened or re-used packaging.

Typical form factors are dry/wet inlays and small label tags laminated into cartons, blister packs, bottle necks, or security seals. Compared with non-cryptographic alternatives like MIFARE Ultralight, it wins where authenticity verification is mission-critical; where more memory or richer file structures are needed, designers typically step up to NTAG 22x DNA or NTAG X DNA.

As an RF-only NFC Forum Type 4 Tag, NTAG 224 DNA is read with any ISO/IEC 14443-A reader or NFC-enabled smartphone using standard ISO 7816-4 APDUs: SELECT to pick the application/file, then READ BINARY for NDEF or file content. AES-128 mutual AUTHENTICATE sessions unlock CMAC- or encryption-protected files and key management operations; GET_VERSION-style commands are commonly used during provisioning to confirm IC identity and batch data.

Because user memory is only 224 bytes, NDEF message overhead (URI records, SUN payload fields) consumes a meaningful fraction of capacity — plan the NDEF template before locking configuration. SUN/SDM-style dynamic URLs embed counters and a MAC directly in the tag's served URL, so backend verification logic must track counter state per UID to prevent replay. Common integration pitfalls include misconfigured key diversification across the three AES keys, failing to test against real mobile NFC stacks (which vary in APDU timing), and exhausting or mismanaging the tamper/authentication counters during high-frequency tap testing.

NTAG 224 DNA is sourced through NXP's authorized distributor network and the RFID inlay/label converter ecosystem that builds wet inlays, dry inlays, and finished tags around NXP DNA-family silicon. As a brand-protection-focused IC, it's typically bought as a finished or semi-finished label rather than bare die, so lead times and MOQs are usually set by the converter rather than the chip itself.

When evaluating suppliers, ask specifically about AES key injection/provisioning support, SUN/URL template configuration, originality signature verification tooling, and whether they can pre-encode unique counters per unit for brand-protection rollouts. If your application needs more than 224 bytes of memory or a richer multi-application file structure, cross-shop to NTAG 22x DNA or NTAG X DNA; if cryptographic authentication isn't required at all, a simpler MIFARE Ultralight tag may be more cost-effective.