Live data from Hacker News

I quit my job to make free web tools

nslookup.io

71–80 of 105 posts

Re: I quit my job to make free web tools

#71

Earlier quoted context omitted.

There is no privacy issue here, there aren't source IP addresses attached, you can't tell who's looking these up. It's up there with Amazon's (for example) "other people bought" recommendations, you can't tell who did the looking up. They're just domain names which are effectively public records. And even if you thought you registered a super secret domain name (no such thing), maybe the registrar looked it up, or so…

What if someone looks up an internal domain which is actually publicly exposed. Granted they shouldn’t be secret, doesn’t mean you should broadcast them publicly.

Internal domains generally resolve to private IP ranges, so don't do any harm when broadcasted. Besides, many people use Chrome, and who knows what they do by default with browsing history.

Re: I quit my job to make free web tools

#72
post #9

Earlier quoted context omitted.

Hmm, not that I've taken a second look, I noticed that I added a hidden image hosted on their servers when I implemented the ads. It's used for counting the ad impressions, but it looks like it drops a 1-day valid cookie as well :/

It's a little funny to me you added a literal tracking pixel to your website from a VPN company and then came to HN to preach that you don't do any tracking That said, due to third party cookie changes, tracking pixels have very limited usefulness these days and it's unlikely it actually tracks people over a full 1 day period

I guess you're right.. And indeed, browsers fight back: https://blog.mozilla.org/security/2021/01/26/supercookie-pro...

Re: I quit my job to make free web tools

#73
post #16

Earlier quoted context omitted.

Thanks for your kind words :) > long term what is your goal to differentiate? or where do you want to focus? Most other tools have clunky UX, dated design, or are painfully slow. I'm differentiating in ease of use, clarity and speed. Still a lot to be done, but I think I'm already doing okay compared to other sites. > Other TLDs or Other Associated Domains, is this something that you would be able to find? Since GDPR…

> I'm differentiating in ease of use, clarity and speed. FWIW I've worked for a small company for the last ~15 years and this is basically our differentiator. Most of our products weren't the first in their market, and we don't have all the bells and whistles, but we really focus on making an easy to use, non-frustrating user experience.

Thanks for the validation :) Crazy that lack of frustration can be a differentiator.

Re: I quit my job to make free web tools

#74
post #30

> Mobile game that divides the earth in hexagons Interesting that I hear about this twice in the space of a week or so. Neal Stephenson was talking about it on the Lex Fridman podcast too. Apparently it's not possible. You'll always need a certain number of pentagons to complete the tiling.

If you're interested, here's how Uber solved it for their internal tooling:

https://h3geo.org/

https://www.youtube.com/watch?v=PutOhe8HVNU

Re: I quit my job to make free web tools

#76
post #71

Earlier quoted context omitted.

What if someone looks up an internal domain which is actually publicly exposed. Granted they shouldn’t be secret, doesn’t mean you should broadcast them publicly.

Internal domains generally resolve to private IP ranges, so don't do any harm when broadcasted. Besides, many people use Chrome, and who knows what they do by default with browsing history.

You’ve obviously never seen orgs with /16 IP ranges, or developers/ops accidentally screw up, for that matter.

Chrome don’t actively publish nslookups on public sites.

I think you’ve missed the point.

Re: I quit my job to make free web tools

#78
post #71

Earlier quoted context omitted.

What if someone looks up an internal domain which is actually publicly exposed. Granted they shouldn’t be secret, doesn’t mean you should broadcast them publicly.

Internal domains generally resolve to private IP ranges, so don't do any harm when broadcasted. Besides, many people use Chrome, and who knows what they do by default with browsing history.

Information leakage of any kind potentially gives an attacker something they can use. On its own any given piece of info may seem harmless, but when combined with other info it can start to pose a risk.

Leaking internal hostnames could allow an attacker to build a view of an internal network ahead of time, before actual penetration. Once inside a network it's often a race against time, so this can make a difference.

Re: I quit my job to make free web tools

#79
post #42

Earlier quoted context omitted.

Just to compare, https://nodemailer.com had 194k pageviews (42k “active users” as reported by Google Analytics, whatever that means) in January and the BuySellAds payout was $156.45

I've used nodemailer. Thanks for building it. I have similar stats on my personal project and those earnings are discouraging. Any luck with donations? I've used ko-fi with limited success. Thanks for putting some numbers out there.

Github sponsors payout in January was $159 and one-off donations via Paypal $15. That makes the grand total of $330/mo. It was a regular month as well.
Post reply on HN