Domain Info Database: One Enriched Record for Every Domain

Frequently Asked Questions

What is Domain Info Database?

Domain Info Database is an enhanced WHOIS record database. It has three main advantages over traditional WHOIS:

• It has a WHOIS record for any domain, whether it’s active, expired, or deleted.
• It allows users to see through WHOIS redaction by replacing values in redacted fields with historical values from before the redaction (if there ever were any) and merging together records collected via WHOIS and RDAP to offer the most detailed record possible.
• It doesn’t override WHOIS with RDAP if RDAP records are empty, keeping the most informative domain registration records.

Every field is parsed, normalized, and timestamped. Since every domain has only one record, the Domain Info Database easily integrates directly into your pipeline without additional processing.

What fields does the Domain Info Database contain?

The database includes all standard WHOIS registration fields:

• Registrant name, organization, email, and contact details
• Registrar information
• Creation, expiration, and updated dates
• Name servers
• Domain status codes

Every field carries a timestamp showing when it was last confirmed or updated.

What is the difference between Domain Info Database and WHOIS Database?

WHOIS Database contains WHOIS records as collected from registrars, which means expired or deleted domains return no data at all. Domain Info Database has a record for every domain, active or expired, built by merging WHOIS and RDAP data and backfilling redacted or missing fields with the most recent historical values.

What is the difference between Domain Info Database and WHOIS History Database?

WHOIS History Database is a full chronological archive of every WHOIS snapshot captured for a domain. Domain Info Database is not an archive. It provides one consolidated record per domain that reflects the most complete and current registration data available, using history only to fill in gaps. It is also significantly smaller in size than WHOIS History Database.

When should I use Domain Info Database instead of WHOIS History Database?

Domain Info is a more lightweight option with just one record per domain. This may be beneficial when your goals are to ensure that there is a WHOIS or RDAP record for every domain and that all those records have meaningful information (if it was ever available). EASM/CTEM platform builders prefer Domain Info Database because it allows them to reliably pivot from WHOIS while keeping this process relatively simple and straightforward. However, when you need the entire domain ownership history or as many data points per domain as possible, the WHOIS History Database should be the preferred option. For example, WHOIS History is the better option for threat intelligence enrichment, as its historical depth allows users to get more pivoting options and uncover more associated infrastructure.

Does Domain Info Database provide real-time registration data?

Domain Info Database is updated weekly and provides one enriched registration record per domain by combining available WHOIS, RDAP, and historical data. If your workflow requires real-time visibility into newly registered domains, you can use Real-time Domain Registration Streaming alongside Domain Info Database. Together, they provide both enriched domain records and timely registration updates.

What happens if there is zero history to pull from for a redacted field?

If a field has been redacted from the start, it remains that way in the Domain Info Database because the enrichment process relies on past WHOIS data.

What kind of hidden or missing information can the database actually recover?

The database can recover domain registration details that existed in historical records before privacy regulations caused them to be redacted. This includes the registrant name, organization, email, phone, and address. Recovery is possible only when older WHOIS records captured the field before it was removed.

Does my team need to parse or clean the files after downloading them?

No. Records are pre-parsed, normalized, and ready to load. Every field follows a consistent schema with its own timestamp. Your team can move from download to query without writing any post-processing logic.

How often is the database updated, and what is the typical file size?

You get a fresh weekly update, with each full dump approximately 2–5 TB in size.