Data source
Data from IANA, delivered clean.
2 datasets pulled from IANA's releases, checked field by field and shipped the way you want them — daily, weekly, or hourly, your call.
- 2 datasets
- 2 industrys
- Real rows on request
Interactive Media & Services
1IANA Root Zone Database
Internet Services & Infrastructure
1Public Suffix List Data
Pick a catch, see the rows.
Name any IANA dataset and we send real rows from it — not a screenshot of rows. 1,744 datasets. Pick your catch.
Get a sampleAPI, files, or your warehouse. Daily, weekly, or hourly.
Straight answers about IANA data
What does Datadory deliver from the IANA source?
One interactive-media dataset: the authoritative root zone delegation table, shipped as six named deliverables covering the full TLD universe, its six-value type enum, the registry-operator roster, all 316 country-code delegations, internationalized strings, and a domain join key that connects to anything else you hold keyed by domain.
How many TLDs does the IANA dataset cover?
Roughly 1,595 as of August 2026: 1,250 generic, 316 country-code, 14 sponsored, 3 generic-restricted, 11 test and 1 infrastructure. Counts move only when delegations change, so a single pull captures the entire space every website address lives above - completeness is structural, not statistical.
Can I slice the data by TLD type?
Directly. Type ships as a six-value enum column rather than prose, so all sponsored TLDs is one predicate and all country-code managers another. Most commercial analyses filter test and infrastructure values out, and the same one-line filter keeps them excluded from every downstream count.
Does the IANA dataset include historical delegation records?
Not natively - the registry keeps current state only, so when a string changes hands the prior arrangement is gone from the next pull. Scheduled deliveries turn cadence into history: each snapshot pins a dated state, and the re-delegations and additions between snapshots accumulate into a change log without extra work.