https://zonewatcher.com
After having multiple clients change their DNS settings without warning and then email us when shit hits the fan I knew I needed some type of warning system.
This checks every X minutes and saves each version so you can see the revision history for all your DNS zones across many providers.
I make ~$50 a month right now with it, which is enough to cover the hosting. I haven't really marketed it much beyond my twitter circle of friends but hopefully others will find it useful.
It took about 3 weekends worth of work to complete and is based on Laravel Spark.
Signed up to paid plan, thanks. This is something I had looked for previously.
Some suggestions (only because I really want you to succeed!):
- Please consider the use case where I want to protect against a domain having its nameservers changed at the registrar. I don't think you currently handle that case, as e.g. pulling the NS records from Route53 will always show Route53 as the authoritative NS, which may not match what the registrar says. This is actually the main feature I want.
- I couldn't find docs or advice regarding how alerting or notifications work. I don't even know if I will receive alerts.
- Please support "plain" DNS-based checks. As in, ability to add a zone and add a number of records (e.g. MX) that I want checked and it is done via DNS protocol query to the authoritative NS.
- Fix the "flash of not-yet-parsed-by-Angular content" that appears on the signup page, it's pretty jarring on a medium latency connection
- For the credit card form, I had some misgivings about putting my details in until I dove into the HTML of the page to check that you weren't sending the card details to your own server. Maybe add a "powered by Stripe" icon or something.
I would potentially consider per-domain pricing. $5 dollar/month/domain for under 100 domains, $2.5 dollar/month/domain for under 1000 domains, and if people want to use more than 1000 domains they should contact you and work out a deal specific to them.
Price tranches are good because they make expenses easily predictable while still providing some operational flexibility. That's especially good for enterprise customers with finance teams.
They can also make good money if you set the boundaries right. If a lot of your customers have ~30 domains, a boundary at 25 might make you more money than per-domain pricing.
I would also look to see if you can add failover as a feature. With the recent DDOS attacks against DNS providers, a lot of companies are considering failover planning for DNS who previously ignored that. To really hit big bucks with this, you will need to integrate with bigger DNS providers like Dyn, UltraDNS, etc.
I agree that you're not charging enough. Keep the free level but then I would charge at least a dollar per domain.
I make ~$50 a month right now with it, which is enough to cover the hosting. I haven't really marketed it much beyond my twitter circle of friends but hopefully others will find it useful.
It took about 3 weekends worth of work to complete and is based on Laravel Spark.