Registrar Stability Checklist for Domain Acquisitions

Why registrar stability is a first-class signal

Registrar metadata is not administrative trivia — it predicts transfer friction. Buyers who skip registrar review often discover hidden locks, reseller complexity, or recent churn only after escrow opens.

Use RDAP event ordering (creation, last changed, expiration) as your spine. When last changed clusters near negotiation windows without matching DNS maintenance, treat it as a yellow flag until explained.

30-point registrar stability checklist

Score each domain 0–2 per row (0 = risk, 1 = unclear, 2 = clean):

1. Registrar identity matches known accredited brands
2. IANA registrar ID resolves consistently across lookups
3. Creation date aligns with claimed asset history
4. Updated date spikes are explained (DNS migration vs suspicious churn)
5. Expiry date is beyond your intended hold period + buffer
6. Status flags exclude clientTransferProhibited unless documented
7. No rapid registrar hopping in the last 12 months
8. Reseller chains are shallow (avoid opaque reseller-of-reseller stacks)
9. RDAP entity roles show registrar + registrant separation clearly
10. Privacy/redaction is expected for the TLD — not masking broken data

Add DNS and mail checks from linked MX/TXT tools before final scoring.

Operational workflow

1. Pull full WHOIS/RDAP dossier on WhoisLogic
2. Export MX and nameserver segment URLs for the same apex
3. Compare against your last approved baseline if re-buying from portfolio
4. Document findings in broker disclosure template (see related playbook)

Closing

Registrar stability does not guarantee quality, but registrar chaos guarantees negotiation cost. Make this checklist the first gate in every acquisition pipeline.