Member
Correct, but the JSON schema is standardized unlike whois text. My parser is 30 lines not 300. The registry servers still vary in rate limits but at least IETF gave us a spec.
RDAP doesn't cover all the legacy TLDs I still have. .cc and .ws registries I use have no RDAP endpoint at all, whois only. Had to keep both code paths.
Built something similar to YuriDavid's bot but for Slack. Used Namecheap API for domains there, Gandi API for .fr and .eu, manual whois fallback for the rest. The real pain was normalizing date formats across registrars. ISO 8601 is apparently optional.
In Brazil we have .br domains with REGISTRO.BR whois that blocks most international IPs entirely. Had to rent a tiny VPS in São Paulo just to poll it. Regional TLDs are the real monitoring nightmare.
Member
Same with .tr and some Middle East registries. I use proxy through local server, very cheap. You want I find you good price?
Following this thread because I just realized I have domains across 6 registrars and no unified view. The CSV export from each is different enough that I can't even merge them in LibreOffice without hand-editing.
This. Gandi gives you ISO dates, Namecheap gives you MM/DD/YYYY, Cloudflare (https://www.cloudflare.com) gives you Unix timestamp in the API but human-readable in the web CSV. I gave up and wrote a Python normalizer.
I just pay for Domain Name Sanity, $12/year, they email me. Not self-hosted but I've got enough infrastructure to babysit.
Did not know this existed. Do they handle registrar APIs or just whois polling? Their site is vague on methodology.
They claim "direct registrar partnerships" but I suspect it's mostly whois with better rate limiting. Works for my 40 domains, wouldn't scale to hundreds.
