Seriously, create a small report based on the logs that tracks visits, popular calls etc. It will do you good every morning to check it (charts and comparisons are great) and it will be an asset when promotion time comes around and you have define your "contribution" to the company :)

I absolutely love the visualisation on bookdepository [0] where you can see what people are buying...

[0] http://www.bookdepository.com/live

Huh, the books it's showing are really interesting too!

PS, it's a periodic XHR to http://map.bookdepository.com/browse/map.json, which gives back one thing. Just in case you were interested...

Though I know that your intentions were harmless, I'd like to add that it's not a good idea to do such a lookup without a sound reason. At some places where I worked, I could have been fired for doing that unless I was looking to fix a bug and this particular bit of data was essential.

I'm going to assume that those companies u worked at had good intentions as well, but this seems like an unfounded fear.

Unless u are working on a heavily confidential project that has a certain legal anonymity requirement (in which case the user's IP should be scrambled anyway), I don't see how doing a whois query could create any damage.

- It diminishes privacy

- It shows by example that this behaviour is okay thus others are less reluctant to run queries of smilar nature

In itself each of them is not so big but all these behaviours add up to the 'culture' of either respecting the user's privacy or taking it not very seriously.

You should generally have a reason to do anything in production regardless of the confidentiality.