pul

13 ms·

91.
by pul 5y ago
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.
92.
by pul 5y ago
It's a fair point, and I've thought about this when making the stats public. There are plenty domain enumeration tools out there. DNS data is inherently public, so I don't think one should rely on it for their security model.
93.
by pul 5y ago
I can confirm. I earn about 2-3 BAT (€1.5 - €2) each month for nslookup.io (without serving Brave ads) and whoismyisp.org (with Brave ads) combined. That's ~1M page views across all browsers. Not lucrative at all ;)
94.
by pul 5y ago
I have. In fact, you can check this for any site using nslookup.io ;) (so meta) See the TXT records at https://www.nslookup.io/dns-records/nslookup.io
95.
by pul 5y ago
Thanks for the offer :) I already submitted it a while ago: https://www.saashub.com/nslookup-io-alternatives
96.
by pul 5y ago
Which one? Because I explicitly added support for that and tested it.
97.
by pul 5y ago
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
98.
by pul 5y ago
Thank you :) Even though it's straight to the point, there's so much more to do to help people fix their DNS issues faster. I'll try not to compromise on the simplicity while adding more information.
99.
by pul 5y ago
Thank you! Nice to hear that one of my explicit design goals worked out :) In my opinion, these kinds of tools, which you only need once in a while, need to take as little cognitive load as possible. People have something to get done, don&#
100.
by pul 5y ago
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 :
101.
by pul 5y ago
> I hope that you make more than your salary Not yet by a large margin, but it's going up slowly :) > how did you attract users to website? Currently, mainly through SEO. My stats are open [1], so you can see the percentage that
102.
by pul 5y ago
Someone on Reddit asked how I make a living. Might be interesting for folks here too. Right now, we're living off our savings and my wife's salary. Both sites are already profitable, though. I've recently launched an API for
103.
by pul 5y ago
Hi HN! Ruurtjan here, from NsLookup.io. I've read plenty of these kinds of blog posts, and they've been a big motivator for me to take the jump. So I thought I'd share my story here as well. Thanks everyone, for giving me the
104.
I quit my job to make free web tools(nslookup.io)
317 points by pul 5y ago|104 comments
105.
by pul 5y ago
I've done some search ads for https://www.nslookup.io in the early days, but I don't think it has done much. I don't track users, so I don't know if it got me any returning users. In any case, facebook's
106.
by pul 5y ago
Even if you disregard push vs pull, 'propagation' still implies spread through proximity. That there would be some physical or logical topology through which it spreads. So, I agree with the OP. More details argumentation here: h
107.
Understanding Kafka with Factorio (2019)(ruurtjan.medium.com)
133 points by pul 5y ago|72 comments
108.
by pul 5y ago
Exactly, that's the analogy I used to explain the core concepts of Kafka here: https://ruurtjan.medium.com/understanding-kafka-with-factori...
109.
by pul 5y ago
The article lists these reasons to pick a short or long TTL: - Agility - Latency - Defense against DNS outage - Load balancing through DNS - The type of DNS record Are there any other things to take into consideration?
110.
What is a good TTL for DNS?(nslookup.io)
1 points by pul 5y ago|1 comments
111.
by pul 5y ago
Jep, also from other caches: https://www.nslookup.io/dns-records/facebook.com
112.
by pul 5y ago
Jep, but I’ve started proxying the statistics JavaScript to circumvent ad blockers. So the historic stats are a bit lower than today’s.
113.
by pul 5y ago
Thanks! Fixed once CI is done building and deploying :)
114.
by pul 5y ago
There's no company, it's just me :) I'll probably make a printable cheatsheet at some point, but I'm not yet sure what else to put on there.
115.
by pul 5y ago
It's just a glorified Dig wrapper ;)
116.
by pul 5y ago
Ruurtjan from nslookup.io here. No one is really using the API it yet. Some competitors seem to be doing well, so I guess there's a demand. Maybe because it's simpler to integrate over HTTP than over DNS in terms of network config
117.
A quick and simple DNS explorer(nslookup.io)
1 points by pul 5y ago|0 comments
118.
DNS Propagation Does Not Exist: A Suggested Change in Terminology(hackernoon.com)
3 points by pul 5y ago|1 comments
119.
Smart Constructors(wiki.haskell.org)
2 points by pul 5y ago|0 comments
120.
A poor man’s Alexa ranking dashboard(nslookup.io)
1 points by pul 5y ago|0 comments

More ›