ICANN retired its Open Data Platform and API on September 1. Audit endpoints, move supported datasets to CSV sources, and keep provenance visible.
ICANN's Open Data Platform and its API are no longer available as of September 1, 2026. If a domain-research script, dashboard, spreadsheet job, or scheduled report still calls the old service, the right response is not to hide the error or paste a new URL into the same parser. It is time to audit the data contract. ICANN has moved the public datasets it currently provides to its Open Data Initiative page .
The files can be downloaded as CSV without a login. That keeps public access open, but it changes how automated workflows retrieve, validate, store, and cite the data. This guide explains what changed, what did not change, and how domain researchers can migrate without turning a visible API failure into silent stale data.
What changed on September 1 ICANN announced on August 27 that the Open Data Platform would no longer be available after August 31. Beginning September 1, the platform and its API would stop operating, and the former URL would redirect to the Open Data Initiative page. The replacement page provides data as downloadable CSV files. ICANN says the format is widely supported and does not require an API or a user login.
At the time of this draft, the page lists two data families: Domain Name Marketplace Indicators: public datasets related to marketplace indicators. Security Response Waiver Requests: public datasets related to waiver requests. ICANN also says more datasets will be added as they become available. That statement matters operationally.
A migration should discover and validate the current published files instead of assuming that today's page structure, filenames, or column set will never change. What did not change The retirement applies to ICANN's Open Data Platform and its associated API. It does not mean every ICANN data service disappeared, and it does not turn one CSV page into a universal source for every domain question.
ICANN describes the Registration Data Access Protocol , or RDAP, as a separate protocol for accessing current registration data. RDAP can help answer domain-specific registration questions through standardized responses. The Open Data Initiative publishes broader public datasets for analysis. Use each source for the question it is designed to answer. A marketplace-indicator CSV is not a live registration record.
An RDAP response is not a replacement for a historical aggregate dataset. A Catches expiring-domain row is an acquisition workflow record, not an ICANN policy dataset. Seven steps to migrate a domain-data workflow 1.
Inventory every ODP dependency Search scheduled jobs, notebooks, dashboards, spreadsheet connectors, scripts, environment files, monitoring checks, and documentation for the old ODP host, endpoint paths, dataset identifiers, and authentication assumptions.