I never saw your signature, but it sounds to me like all it's doing is reporting the information from the client's user-agent header (browser, OS) along with a geolocation lookup. I'm no expert, but I seem to recall that stack fingerprinting requires the scanner to find both an open and a closed TCP port, which usually takes a couple minutes. Beyond that, many internet users have a firewall, in the form of a home-network router, which is going to silently drop just bout anything, and even if it didn't, the scan would only be fingerprinting the router, hardly the aim here. Also, the IP addresses you gave as examples are both private IPs: They're meaningless to anyone not connected to the private network where they originate (RFC 1918). Perhaps gleaned client-side, pre-firewall?
Sorry, I just had to be pedantic.
~ Burgundy ~