Domain registration guides

Compare multiple dated domain registration captures

·

A folder of saved records may combine different registries, timestamps and outcomes. Use one entry per response and retain that provenance in the export.

Bulk Domain Registration Reader

Keep the source with each row

Enter two captures with distinct sources and times. If both contain the same domain, keep both entries. The batch preserves input order so that each record can be traced to its original observation.

IETF RFC 9083 — JSON Responses for RDAP

Distinguish registry outcomes from unreadable input

A saved JSON response with errorCode 429 produces a row marked Rate limited. A file with broken JSON produces a row error instead. An otherwise readable domain record can also have absent expiration or registrar fields.

IETF RFC 9083 — JSON Responses for RDAPIETF RFC 9537 — Redacted Fields in RDAP Responses

Keep a failed lookup distinct from an expired domain

Give two captures different labels and include their capture times. If one parses and the other contains a rate-limit response, keep both rows. The rate-limit row is evidence that the source supplied no registration result at that time.

When sorting a spreadsheet by expiry date, filter records with a known expiry first. Treating a missing date as zero or as today can pull unobserved registrations into an urgent renewal list.

Common questions

Does the reader deduplicate domains?

It preserves every supplied row. Separate observations of one domain can have different dates or sources.

Does removing a response delete the original file?

Removing an entry changes the batch on the page. The selected local file remains on the device.

Sources

Put it into practice.

Related guides