SW1/SW2 status word lookup
Type a status word (e.g. 9000, 6A82, 63CX) or a phrase (e.g. "file not found", "security status"). Returns matching entries from ISO/IEC 7816-4, GlobalPlatform, EMV, and common FIDO conventions.
How to use this tool
What it does
Looks up smart-card status words (SW1 SW2) by hex code or by phrase across ISO/IEC 7816-4, GlobalPlatform, EMV and FIDO conventions.
When to use it
Reach for it while debugging an APDU exchange when a card returns two trailing status bytes and you need to know what they mean without paging through four specifications.
Worked example
Type 6A82 and you get “File or application not found”; search the phrase security status to surface 6982 (security status not satisfied).
Search
About status words
A smart card ends every response APDU with two bytes — SW1 SW2 — that say what happened. 9000 is the universal “OK”. The 6XYY range covers warnings (62/63), state errors (64/65), wrong-length (67), command-not-allowed (69), wrong-parameters (6A), and proprietary (6F). The full table lives in ISO/IEC 7816-4, with extensions in GlobalPlatform and per-application standards.
Spec
ISO/IEC 7816-4 §5.1.4.
Frequently asked questions
What is a status word?
The two trailing bytes of every APDU response, SW1 and SW2. 9000 means success; everything else is a warning or an error whose meaning depends on the specification in force.
What do 61xx and 6Cxx mean?
Neither is an error. 61xx says XX more bytes are available and you should issue GET RESPONSE; 6Cxx says your Le was wrong and XX is the correct value to re-send.
Why do the same bytes mean different things on different cards?
Because ISO 7816-4 defines a common set and then leaves ranges to the application. GlobalPlatform, EMV and FIDO each define their own, so the context decides the meaning.
What is the difference between 6A82 and 6A83?
6A82 is file or application not found — usually a SELECT against a missing AID. 6A83 is record not found, meaning the file exists but the record index does not.
Does anything I paste leave my browser?
Nothing. The tool is entirely client-side: the page ships a static script, does no network calls, and never transmits what you paste. You can confirm it by opening the network tab, or by loading the page and then going offline.