Registrar and registry changes

Renames, terminations, platform migrations, changes of registry operator and backend transitions — the visible traces of mergers, acquisitions and reassignments in the new-gTLD industry.

These are observations, not announcements. ICANN publishes no machine-readable record of mergers or registry assignments, so each row below is simply a case where what ICANN or IANA publishes today differs from what it published before. A rename usually follows a corporate change but can also be a rebrand; a registrar's RDAP platform moving to another company's infrastructure is strong evidence of an acquisition, but it is still evidence rather than confirmation.

No changes detected yet Detection compares each day's published values against the previous run, so entries appear from the first change onward rather than being backfilled. Nothing has moved since collection began.

Why history is not lost when this happens

Every time series on this site is keyed on an identifier that survives a corporate change: registrar figures on the ICANN-assigned IANA number, TLD figures on the string itself. Neither is reissued when a company is acquired or renamed, so a rename moves the label without disturbing a single historical row.

What a rename would otherwise destroy is the knowledge that it happened, and the previous value. That is what this page is for. Where an accreditation's domains are genuinely moved to a different accreditation, the volume legitimately leaves one row and appears in another — the combined registrar view is the way to read that as one company rather than two unrelated movements.

Data currency. Domain counts on this page are from zone files dated 12 August 2026 and refresh daily. Registrar figures are from ICANN's monthly registry reports for April 2026, which ICANN publishes about three months in arrears; zone files contain no registrar information, so no fresher source exists. Full detail on methodology and live pipeline status.