4,537 records

Is my domain registrar still accredited by ICANN?

4,537 records covering 4,535 registrars, one fact each. Every value is transcribed from the source that states it and carries the sentence it was taken from: 2 sources across 2 sites, last checked 2026-09-14, due for re-check by 2026-09-28. Every record has a page of its own, quoting the line that states it.

Recent changes

• 2026-09-14303 records added or updated
• 2026-09-07155 records added or updated
• 2026-08-314 records added or updated

Full change history · Atom feed

About this data

Whether a domain name registrar is still ICANN-accredited, and what enforcement action ICANN has taken against it. Each record is one registrar identified by its IANA registrar ID, carrying the accreditation status IANA publishes ('Accredited', 'Terminated', 'Reserved') and, where one exists, the dated ICANN Contractual Compliance notice ('Notice of Breach', 'Notice of Suspension', 'Notice of Termination', 'Notice of Non-Renewal') with the date and the notice PDF. Answers 'is my domain registrar still ICANN accredited', 'which registrars lost their accreditation in 2026', 'is IANA ID 3221 accredited', 'what happens to my domain if my registrar is terminated', and 'has this registrar been issued a breach notice'. The two authorities publish complementary halves and neither publishes the other's: IANA states a registrar is Terminated but never says when or why, and ICANN dates every enforcement action but never states current status. A registrar termination triggers a bulk transfer of every domain under it, so the answer is consequential and it changes several times a year.

The data

Showing the first 400 of 4,537 records. Every record has its own page, with its source and the quoted line that states it; these list the rest.

• Records 1–400Reserved … NamePal.com #8024, LLC
• Records 401–800NamePal.com #8025, LLC … Betterthanaveragedomains.com LLC
• Records 801–1,200Biglizarddomains.com LLC … NameSector LLC
• Records 1,201–1,600NameSay LLC … DropCatch.com 497 LLC
• Records 1,601–2,000DropCatch.com 498 LLC … Pheenix 2, LLC
• Records 2,001–2,400Pheenix 3, LLC … DropCatch.com 1019 LLC
• Records 2,401–2,800DropCatch.com 1020 LLC … Nimzo 62, LLC
• Records 2,801–3,200Nimzo 63, LLC … DropCatch.com 1372 LLC
• Records 3,201–3,600DropCatch.com 1373 LLC … Gname 019 Inc
• Records 3,601–4,000Gname 020 Inc … Gname 346 Inc
• Records 4,001–4,400Gname 347 Inc … DropCatch.com 1745 LLC · 4789
• Records 4,401–4,537DropCatch.com 1746 LLC · 4790 … Webagentur.at Internet Services GmbH d/b/a domainname.at

Where this came from

Every record above links the page it was taken from and quotes the sentence that states it. These are the 2 sources this dataset was assembled from.

• icann.orghttps://www.icann.org/compliance/notices
• iana.orghttps://www.iana.org/assignments/registrar-ids/registrar-ids-1.csv

Machine-readable

• data.jsonThe whole dataset — every record with its source URL and source quote.
• Open Knowledge Format bundleOne JSON object per line — every record's frontmatter and quoted span exactly as it is held here, in one fetch.
• data.csvThe same records as one flat table, for a spreadsheet or a dataframe. The last four columns are the source URL, the quoted sentence it was read from, the date we last checked it, and which columns are our reading rather than the page's words.
• changes.xmlAtom feed of what changed and when — poll this instead of re-fetching the dataset. Also as changes.json.
• What changedThe same change history as a readable page — each date, what moved, and the records' current state.
• How this is made and checkedWhat "verified against source" does and does not mean.

From your own code

Same records, same quotes, without scraping the page: refsource is on PyPI and npm. Each value comes back carrying the URL it was read from and the sentence on that page that states it — .source and .quote sit on the value itself rather than in a side channel, so the checking step is available instead of skipped.

pip install refsource
refsource lookup icann-registrar-accreditation-status registrar_name=Reserved

npx -y refsource lookup icann-registrar-accreditation-status registrar_name=Reserved

Set your AI assistant up to use this

Two files and no account. Put this in .mcp.json at the root of your project — Claude Code, Cursor, Windsurf, VS Code and Codex all read that file — and your assistant can look this register up instead of recalling it. The server is remote, keyless and read-only.

{
  "mcpServers": {
    "referencesource-registrars": {
      "type": "http",
      "url": "https://referencesource.org/mcp/registrars"
    }
  }
}

Add to Cursor · or, on the command line: claude mcp add --transport http referencesource-registrars https://referencesource.org/mcp/registrars --scope project

Then one line in the project's CLAUDE.md or AGENTS.md, so the assistant knows when to reach for it:

When a question needs "Domain registrar accreditation status and ICANN enforcement history, by IANA ID", call the referencesource-registrars MCP server at https://referencesource.org/mcp/registrars (tool `resolve_registrar`, dataset_slug `icann-registrar-accreditation-status`) instead of answering from memory — every record it returns carries its source URL and a verbatim quote from that page.

What each tool does, and the servers built over single registers: Connect your AI assistant.

4,537 records. last verified against source 2026-09-14. due for re-check by 2026-09-28.

Licence. Facts extracted from two freely published registries: IANA's Registrar IDs assignment registry and ICANN's Contractual Compliance notices page. Registrar names, IANA IDs, accreditation statuses and notice dates are facts and not copyrightable. Each record links back to the page it was read from. Notice PDFs are linked, never mirrored.