Launching today
DropVigil Domain Drop
Track expiring domains, get alerted the moment they drop
7 followers
Track expiring domains, get alerted the moment they drop
7 followers
DropVigil watches your domain watchlist and tracks every name through the full drop lifecycle: expired → redemption → pending delete → dropped. It scans daily using official registry RDAP data and sends a browser alert the moment a domain becomes available. Your list never leaves your browser — no account, no server, no tracking. Free for up to 5 domains; a yearly license unlocks unlimited tracking on up to 3 devices. Works in 17 languages.
Being able to see a short history of past drop dates and registrar changes for each domain would help me predict the next drop window more accurately. Maybe a tiny timeline view right next to each name in the list.
@havvat57401 Great suggestion — and it splits into two parts with very different answers, so let me be transparent about both.
The feasible half: DropVigil already scans your list daily, so it can start recording every state transition it observes — expired → redemption → pending delete → dropped, plus registrar changes — from the moment you add a domain. A tiny timeline next to each name showing that observed history is very doable, stays 100% local, and genuinely helps predict drop windows (redemption/pendingDelete durations are fairly consistent per registry). Adding this to the roadmap.
The hard half: history from before you started tracking a domain. RDAP only exposes current state, so pre-tracking history would require paid historical-WHOIS providers — which means sending your watchlist to a third party. That breaks the core promise that your list never leaves your browser, so I'm not doing that by default. If there's real demand I might explore it as an explicit opt-in someday, but local-first stays the default.
Would the observed-history timeline (from the day you add a domain onward) cover most of your use case, or is the pre-tracking history the part you actually need?
Love that everything stays local in the browser, no signups or accounts to manage. Watched it pick up an expired name through the redemption phase in real time, which is honestly more detail than other tools bother to show.
@ezgiprjp Thank you — this made my day! 🙌
Watching a name move through redemption in real time is exactly the moment I built this for, so it's great to hear it delivered.
The lifecycle detail comes straight from querying registry RDAP data directly instead of scraped WHOIS — the registries expose those EPP status codes (redemptionPeriod, pendingDelete…), most tools just don't surface them. Since everything runs in your browser anyway, passing that detail on costs nothing.
If a TLD you care about ever shows as unsupported, tell me — coverage grows as registries roll out RDAP, and user requests decide what I chase first.
Really like that everything stays in the browser, no account needed is a big plus. One thing that would make it even better for me is letting me set custom alert thresholds for specific TLDs or keywords, so I can get pinged for a .io with a 3-letter word but stay quiet on longer .com names. Would save me from tuning my list manually all the time.
@birolkorur3867 Thanks so much — really glad the local-first approach resonates, that was a deliberate choice from day one.
And this is a genuinely good idea. Rule-based alerts (e.g. "ping me for .io names ≤ 3 chars, stay quiet on .com longer than X") fit naturally into how DropVigil already works: since everything runs in your browser, the rules would just live in local storage next to your watchlist — no server needed, consistent with the privacy model.
Adding it to the roadmap as per-TLD / pattern-based notification rules. Can't promise a date since I'm a solo maker shipping carefully, but it's now near the top of the list.
Quick question to make sure I build the right thing: would you want these as global rules that filter alerts across your whole watchlist, or per-domain overrides (mute/prioritize individual names)? Or both? Curious how you'd actually use it day to day.
Honestly this looks really clean, especially the no-account local-only setup. One thing I'd love is the ability to export the domain timeline as a simple CSV or PDF for each name, basically so I can share the drop history with clients when I'm pitching backorder strategies. Would make it way more useful for anyone running this as part of a domain business.
@arasdm02 Thanks! And this lands at a perfect time — another commenter here just asked for a per-domain timeline of observed lifecycle changes (expired → redemption → pending delete → dropped), which is now on the roadmap. Export is the natural next layer on top of it.
The nice part: it fits the local-only model perfectly. Since the history would already live in your browser, generating a CSV is just packaging data you own — no server, no account, nothing leaves your machine unless you choose to share the file. CSV is straightforward and will come first; a clean client-ready PDF is more work but I get why it matters when you're pitching backorder strategies, so I'm noting it as a follow-up.
One question to shape it right: would you want export per domain (one file per name for a specific pitch) or the whole watchlist at once (portfolio overview)? And does CSV alone cover the client-sharing case for now, or is the polished PDF the actual must-have?
Use cases like yours — running this as part of a domain business — are exactly what I want to build for, so keep the ideas coming.