Schema

The record, field by field.

Every record is stored as a single document in the domain_metadata collection. The table below documents each field's origin, meaning, and how often it's populated in the current snapshot.

field type source description / example present

domain string zone file

Fully-qualified domain, lowercased

example.com

0.0%

tld string zone file

Top-level label extracted from the domain

com

0.0%

rdap_queried bool orchestrator

Whether RDAP was attempted for this record

true

0.0%

rdap_status string RDAP worker

Outcome: ok, not_found, failed, throttled, unsupported

0.0%

rdap_raw object RDAP worker

Full parsed RDAP response (conformance, events, notices, links)

{ objectClassName: 'domain', ... }

0.0%

registrar string RDAP

Sponsoring registrar name

NameCheap, Inc.

0.0%

registrar_iana_id string RDAP

IANA registrar ID

1068

0.0%

creation_date date RDAP

Domain creation timestamp (ISO 8601)

2004-08-15T14:00:00Z

0.0%

expiry_date date RDAP

Next scheduled expiry

2026-08-15T14:00:00Z

0.0%

updated_date date RDAP

Last modification at the registry

2025-02-03T09:12:00Z

0.0%

dnssec bool RDAP

True if the delegation is DNSSEC-signed

true

0.0%

status string[] RDAP

EPP status flags

[clientTransferProhibited]

0.0%

nameservers string[] RDAP

Authoritative nameservers at the registry level

[ns1.example.net, ns2.example.net]

0.0%

registrant_country string RDAP vCard

Raw country / region from the registrant vCard (mixed ISO / state)

US · Arizona · REDACTED

0.0%

ip_queried bool orchestrator

Whether IP lookup was attempted (the resolver does not persist A records yet)

true

0.0%

enriched_at date orchestrator

Timestamp of the lookup pass

2025-11-14T03:10:00Z

0.0%

coverage column is derived from countDocuments({ field: { $exists: true, $ne: null } }) / total at build time. Fields sourced from RDAP sub-entities (registrant_country, registrar_iana_id, updated_date) are sparse because they depend on what the registry chose to publish.