GEARCHECK LABCheck the separate numeric keypad rather than the top row of numbers. The grid highlights keypad key codes observed by the browser and shows the key value produced with your current Num Lock state.
Start capture, then press keys here.
Escape stops. Tab leaves this area.
No events recorded yet.
Seen keys remain highlighted for the session, while held keys use a separate active state. The observed count covers the 17 listed codes and does not require every keyboard to have all of them. Num Lock is read from the modifier state reported with a key event; the page cannot directly inspect the keyboard LED. Key location and physical code help distinguish keypad Enter and digits from their main-keyboard equivalents.
Compact keyboards, embedded laptop keypads, accessibility remapping and operating-system shortcuts may expose different events. Some browsers or systems intercept Num Lock itself. A missing code is not a universal hardware failure, and the browser state may differ from a device-specific LED or firmware mode. Compare the same key in another application and on another computer before replacing hardware. Capture stops when focus moves away to avoid stuck held-key indicators.
They have different physical key codes. This focused test expects Numpad codes from the separate keypad or a device that exposes equivalent codes.
Diagnostic data is processed locally in this tab and is not intentionally sent to analytics. Network tools send only their test probes and temporary payloads to GearCheck Lab’s speed-test server. Media and device access starts only after your explicit action and any required browser permission. Downloaded results stay on your device.
Read the privacy policy and testing methodology. If something fails, report the tool URL and visible message.