SkydiveAI coworkers that actually get work done
Promoted
DropVigil Domain Drop
Track expiring domains, get alerted the moment they drop
5 followers
Track expiring domains, get alerted the moment they drop
5 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.
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.
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.