Reading Your Numpad Test Results
The numeric keypad is a separate 17-key block with its own key codes. Numpad4 is a completely different key from Digit4on the number row, even though both type a 4. That distinction is why a general keyboard test can show a "working" keyboard while your numpad does nothing — it was checking the wrong keys.
The first thing to read on this page is the Num Lock state at the top. When Num Lock is off, the numpad switches to its secondary functions: 8 becomes Up, 4 becomes Left, 7 becomes Home, and so on. The keys are working perfectly — they are simply doing their other job. If the readout says Num Lock is off and your numbers are not appearing, press Num Lock once and try again. That single toggle resolves most numpad complaints.
Below that, each key you press turns green and stays green. Work around the whole block including the operators — divide, multiply, minus, plus, Enter and the decimal point — because those fail just as often as the digits and are easy to skip. A key that never turns green is not sending anything to the browser.
One honest limitation: web pages cannot read the Num Lock LEDdirectly. What we read is the browser's reported modifier state during a key event, which is why the readout shows "unknown" until you press something. Safari and some Linux configurations report this less reliably than Chrome or Edge. If the state looks wrong but your numbers type correctly, trust the numbers.
If keys register but produce doubled digits, the problem is switch bounce rather than the numpad itself — the double typing test measures that. For the rest of the keyboard, the full keyboard test covers every key at once, and the Windows layout test shows the numpad in position on a full 104-key board.