BUY WEBSITES
BUY DOMAINS
LOGIN
SIGNUP
Verifying ICANN Accreditation: How to Confirm a Domain Registrar Is Real Using the Official ICANN and IANA Sources
Verifying ICANN accreditation means confirming that the company holding or transferring a domain is a registrar ICANN authorised, by matching it against ICANN’s official list and the IANA registrar-ID registry. It is a two-minute cross-check, and it is the single fastest way to separate a legitimate registrar from a reseller, a lookalike, or an outright fraud.
This guide does it properly. It names the three official sources of truth, walks through a repeatable verification procedure, and shows how to read the IANA registry status that tells you whether a registrar is accredited, terminated, or a reserved placeholder. It also resolves the confusion that drives half of these searches: the “ICANN verification” email that lands in registrants’ inboxes is a different thing from registrar accreditation, and conflating the two is where people get scammed.
The buyer angle runs through all of it. When a domain changes hands, accreditation is the rail the transfer runs on. SEO Domains operates as an ICANN-accredited marketplace, so every aged or expired domain in the catalogue moves through verified accreditation instead of an unverified middleman, and this page explains the checks that prove it.
What ICANN accreditation actually is
ICANN accreditation is the formal authorisation, granted by the Internet Corporation for Assigned Names and Numbers, that lets a company sell and manage domain registrations in generic top-level domains. An accredited registrar has signed the Registrar Accreditation Agreement, holds a unique IANA ID, and appears on ICANN’s published list. Verifying accreditation means matching a company against that record.
ICANN is the non-profit body that coordinates the domain name system at the policy layer. It does not sell domains. It accredits the registrars that do, and it sets the contractual rules those registrars operate under. A registrar without accreditation has no authority to register a name in a gTLD such as .com, .net, or .org.
The Registrar Accreditation Agreement is the contract behind the badge
Accreditation is not a logo a company adds to its footer. It is a binding contract. The 2013 Registrar Accreditation Agreement, known as the RAA, is the governing contract between ICANN and every accredited registrar, and ICANN applied a 2024 global amendment to existing agreements, effective 5 April 2024. The RAA sets registrant protections, data-handling duties, and compliance enforcement, which is why an accredited registrar is held to a standard a reseller is not.
What accreditation covers, and what it does not
Accreditation has a defined scope. It authorises a registrar to operate in gTLDs, and ICANN updates the descriptions and contact information for accredited registrars on a daily basis. It does not cover country-code top-level domains. A .uk or .de name is governed by Nominet or DENIC, the national registries, under their own rules, so an ICANN check is the wrong tool for a ccTLD-only provider.
Why verifying accreditation matters before you buy or transfer a domain
Verifying accreditation matters because the registrar is the entity that legally controls the registration. When you buy, transfer, or hold a domain, accreditation is what guarantees the registrar can lawfully manage the name, run an ICANN-compliant transfer, and is bound by registrant-protection rules. An unverified provider exposes the transaction to loss of the domain, a stalled transfer, or fraud.
The registrar holds the keys, so its status is the transaction
Whoever the registrar is controls the authorisation code, the transfer lock, and the registration record. If a domain sits with an entity that is not accredited, the transfer it promises is not one ICANN recognises, and the buyer can pay for a name they cannot reliably move or defend. This is the practical reason verification comes before money changes hands, not after.
For aged and expired domains, the rail matters more
The stakes rise with aged and expired domains, where the value is the inherited backlink profile and the registration history. A clean transfer through an accredited registrar keeps that history intact and recorded. An off-the-books transfer through an unverified intermediary risks the name lapsing again, the inheritance being lost, or the ownership record being disputed. Sourcing from an accredited operation removes that risk at the door, which is why the curated catalogue on the SEO Domains marketplace runs every acquisition through ICANN-accredited transfer instead of an unverified handoff.
The three official sources of truth
Three official sources verify accreditation, and only these three are authoritative. ICANN’s List of Accredited Registrars is the master record. The IANA registrar-ID registry assigns and tracks the unique number behind each registrar. The ICANN registration data lookup tool, which queries RDAP, shows which registrar holds a given domain. Cross-checking all three is what closes the verification.
Source one: the ICANN List of Accredited Registrars
ICANN publishes the master list of every accredited registrar, with public contact information, IANA numbers, and website links, updated daily. This is the first and primary source. If a company claims to be a registrar and does not appear here, it is not ICANN-accredited, whatever its website says.
Source two: the IANA registrar-ID registry
IANA, the Internet Assigned Numbers Authority within ICANN, maintains the registry of registrar IDs. Each entry carries four fields: the numeric ID, the registrar name, a status, and an RDAP base URL. The registry records that these IDs are assigned by ICANN, and it is the canonical place to confirm an IANA ID maps to the registrar that claims it.
Source three: the ICANN registration data lookup tool and RDAP
The ICANN registration data lookup tool lets anyone look up the current registration data for a domain name, returning the registrar of record and its IANA ID. It runs on RDAP, the Registration Data Access Protocol, which is the ICANN-standard successor to WHOIS. Using it on a real domain held by the registrar lets you confirm the name resolves to the IANA ID you verified in the registry.
| Official source | What it confirms | What you read from it |
|---|---|---|
| ICANN List of Accredited Registrars | The company is an accredited registrar | Registrar name, IANA number, contact details, website |
| IANA registrar-ID registry | The IANA ID maps to that registrar and its status | ID, registrar name, status, RDAP base URL |
| ICANN registration data lookup (RDAP) | The registrar actually holds a real domain | Registrar of record and IANA ID for a live domain |
How to verify a registrar is ICANN-accredited, step by step
Verification is a six-step cross-check. Find the registrar name, locate it on the ICANN list, read its IANA ID, confirm that ID and its status in the IANA registry, run an RDAP lookup on a real domain to see the same ID, and rule out the reseller and lookalike traps. Each step uses an official source, and the answer is conclusive when the registrar name and IANA ID match across them.
The procedure below works for any registrar, whether the goal is checking a provider before opening an account or confirming the entity behind a domain on offer. Run it top to bottom. A mismatch at any step is the signal to stop.
-
Identify the exact registrar name
Get the registrar’s full legal name, not just a brand. If you are checking the registrar behind a specific domain, run an RDAP or WHOIS lookup first, which returns the registrar of record and its IANA ID. The legal name is what you will match against the official list.
The trap: matching on a trading name or logo. A brand can resell under a parent registrar, so the marketing name can differ from the accredited legal entity. Use the legal name.
-
Find it on the ICANN List of Accredited Registrars
Open ICANN’s List of Accredited Registrars and search the name. The list is the master record, updated daily, and it shows the registrar’s IANA number, contact details, and website. A genuine accredited registrar appears here.
The trap: a company absent from the list but displaying an ICANN logo. The logo is not proof. Presence on the official list is.
-
Read the IANA ID from the listing
Note the IANA number shown against the registrar. This unique numeric ID is the key you will carry into the IANA registry and match against any domain lookup. Record it exactly.
The trap: assuming two similarly named registrars share an ID. Each accredited registrar has its own number, so a near-match on name with a different ID is a different entity.
-
Confirm the ID and status in the IANA registrar-ID registry
Open the IANA registrar-ID registry and find the ID. Confirm the registrar name matches and the status reads as accredited, with an RDAP base URL present. This is the canonical confirmation that the number is live and belongs to the company.
The trap: ignoring a status of terminated. A terminated ID means the registrar no longer operates, so any current claim to hold domains under it is a red flag covered in the next section.
-
Run an RDAP lookup on a real domain
Use the ICANN registration data lookup tool, which runs on RDAP, on a domain the registrar genuinely manages. The result shows the registrar of record and its IANA ID. Confirm that ID is the same number you verified in steps three and four. The chain is now closed end to end.
The trap: stopping at the list without a live lookup. The list proves accreditation; the RDAP lookup proves the registrar is genuinely the one operating a real name under that ID.
-
Rule out the reseller and lookalike traps
If the provider does not appear on the list, check whether it is a reseller operating under an accredited parent. A legitimate reseller will name its accredited registrar, and that parent must pass steps two through five. Only then is the chain of accountability intact.
The trap: a provider that cannot name its accredited registrar at all. With no accredited entity behind it, there is no ICANN accountability, and that is where verification fails for good.
Reading the IANA registrar-ID registry: accredited, terminated, reserved
The IANA registrar-ID registry lists every ID with a status, and the status is the detail a hurried check skips. Accredited means the registrar is live and operating, with an RDAP base URL. Terminated means it no longer operates, and its domains have been or will be bulk-transferred to a gaining registrar. Reserved marks an ID held for internal or historical use, not an active registrar.
The three statuses, and what each tells you
The registry assigns each entry a status, and reading it correctly is the difference between a sound verification and a missed warning. The three values carry distinct meanings for anyone holding or buying a domain under that ID.
Accredited (the live status)
The registrar is currently authorised and operating. Accredited entries carry an active RDAP base URL, which is itself a sign the registrar is running live registration services. This is the status a genuine current registrar shows.
Terminated (the warning)
The registrar no longer operates. Terminated entries typically lack an RDAP base URL. When a registrar is terminated, ICANN arranges a bulk transfer of its domains to a gaining registrar, so a domain still claimed under a terminated ID is a red flag.
Reserved (the placeholder)
The ID is held for internal registry use or a historical allocation, not an operating registrar. A reserved ID will never be the legitimate registrar of a public domain, so it never appears as a domain’s registrar of record.
The RDAP base URL signal
The presence of an RDAP base URL alongside an ID is corroborating evidence. Accredited registrars maintain active RDAP endpoints so their registration data can be queried; the absence of one alongside an otherwise current claim is worth a second look.
What a terminated registrar means for a domain
A terminated registrar does not orphan the domains it held. ICANN runs a bulk transfer that moves them to a gaining registrar, which becomes the new registrar of record. For a buyer, the lesson is to verify against the current registrar of record returned by a live lookup, not against a stale record naming a registrar that has since been terminated.
Accreditation verification versus the “ICANN verification” email
Verifying a registrar’s accreditation is not the same as the “ICANN verification” email registrants receive, and confusing the two is where people get scammed. The accreditation check confirms a registrar is authorised. The verification email is a separate, routine requirement under which a registrar must confirm a registrant’s contact details. Both are real, but they answer different questions, and phishers exploit the overlap in the name.
Two different things that share a word
Search interest splits across two meanings of “verification”. One is the subject of this guide: confirming a registrar holds ICANN accreditation. The other is the contact-data verification a registrar performs on registrants. ICANN’s own material on the verification of contact information describes the second process, where an accredited registrar must verify a registrant’s email or contact details, typically within a short window, or risk the domain being suspended.
Verifying registrar accreditation (this guide)
You check that a company is an ICANN-accredited registrar, using the ICANN list, the IANA ID registry, and an RDAP lookup. The question answered is: can I trust this entity to hold or transfer a domain?
The contact-verification email (a separate process)
Your accredited registrar asks you to confirm your registrant contact details, a routine duty under the RAA. The question answered is: are the registrant’s contact details valid and current?
How to tell a real verification request from a phishing attempt
A genuine contact-verification request comes from your own registrar, references the specific domain, and links to the registrar’s own verified domain or the ICANN process. A phishing version imitates the ICANN name, creates urgency, and routes to an unfamiliar address. The defence is the same verification skill this guide teaches: confirm the sender against the registrar of record returned by an RDAP lookup, and never act on an “ICANN” email whose links do not resolve to your accredited registrar.
Registrar versus reseller, and what accreditation guarantees
A registrar is the ICANN-accredited entity with a direct contract and an IANA ID. A reseller sells domain registrations through an accredited registrar but is not itself accredited and has no IANA ID. Accreditation guarantees an ICANN-compliant relationship, registrant protections under the RAA, and a chain of accountability. It does not guarantee price, service quality, or that any single domain is a good investment.
Where resellers fit, and why the distinction matters
A reseller is any company that offers domain registration through an accredited registrar without holding accreditation itself. A legitimate reseller operates under a named accredited parent. The distinction matters because the accountability runs to the accredited registrar, not the reseller. If a reseller cannot name the accredited registrar behind it, the chain that ICANN can enforce is broken, and a registration record can surface the reseller in the registrant or organisation fields instead of an accredited entity.
What accreditation does and does not promise
Accreditation is a floor, not a rating. It confirms a registrar is contractually bound to ICANN’s rules and registrant protections. It is silent on whether a given registrar is the cheapest, the strongest on support, or the right home for a particular domain. Those are separate judgements, and the related guidance in Choosing a registrar for aged domain parking and Registrar transfer policies compared covers them. Accreditation answers can-I-trust-the-entity. It does not answer is-this-the-best-deal.
The verification and red-flag checklist
The whole verification reduces to a short, repeatable checklist. Each row pairs a check with the red flag it catches and the official source that settles it. Read top to bottom, the right column converges on a single rule: trust the official ICANN and IANA records, and trust nothing a provider only claims about itself.
The table below consolidates every check from the procedure and the status reading into one scannable reference. The left column is the verification step, the centre column is the red flag it surfaces, and the right column is the authoritative source that confirms or refutes it.
| The check | The red flag it catches | The official source |
|---|---|---|
| Registrar appears on the ICANN list | An ICANN logo with no listing behind it | ICANN List of Accredited Registrars (updated daily) |
| Match on the legal name, not the brand | A trading name that hides an unaccredited entity | ICANN list legal-name field |
| IANA ID maps to the registrar | A near-match name with a different ID | IANA registrar-ID registry |
| Status reads as accredited | A terminated or reserved ID still being claimed | IANA registry status field |
| RDAP base URL is present | An active claim with no RDAP endpoint | IANA registry RDAP field |
| Live RDAP lookup shows the same ID | A registrar of record that does not match | ICANN registration data lookup (RDAP) |
| A reseller names its accredited parent | A provider that cannot name an accredited registrar | ICANN list, applied to the named parent |
| An “ICANN verification” email resolves to your registrar | A phishing email imitating ICANN | RDAP registrar of record for your domain |
| The TLD is a gTLD, not a ccTLD | An ICANN check used on a ccTLD-only provider | The relevant national registry, not ICANN |
Verifying ICANN accreditation: frequently asked questions
The questions buyers and domain holders raise when they search for an ICANN accredited registrar list or how to verify accreditation, answered against the official ICANN and IANA records.
Q1How do I check if a registrar is ICANN-accredited?
Search the registrar’s legal name on ICANN’s List of Accredited Registrars, which is the master record updated daily. Read its IANA ID, confirm that ID and an accredited status in the IANA registrar-ID registry, then run an RDAP lookup on a real domain to confirm the same ID is returned as the registrar of record. A match across all three is conclusive.
Q2What is an IANA ID and where do I look it up?
An IANA ID is the unique numeric identifier ICANN assigns to each accredited registrar. You look it up in the IANA registrar-ID registry, which lists every ID with the registrar name, a status, and an RDAP base URL. The same ID also appears in RDAP and WHOIS results for any domain that registrar holds, which lets you cross-check it.
Q3Is the “ICANN verification” email I received a scam?
It depends on where it came from. A legitimate contact-verification request comes from your own accredited registrar, references your specific domain, and is a routine duty under the Registrar Accreditation Agreement. ICANN does not email individual registrants to chase contact details directly. Confirm the sender against the registrar of record returned by an RDAP lookup, and treat any “ICANN” email whose links do not resolve to your registrar as phishing.
Q4Does ICANN accreditation cover all domain extensions?
No. ICANN accreditation covers generic top-level domains such as .com, .net, and .org. Country-code domains like .uk or .de are governed by their national registries, Nominet and DENIC, under separate rules. So an ICANN check is the right verification for a gTLD provider and the wrong tool for a ccTLD-only one.
Q5What is the difference between a registrar and a reseller?
A registrar is the ICANN-accredited entity with a direct contract and an IANA ID. A reseller sells registrations through an accredited registrar without holding accreditation itself, so it has no IANA ID. A legitimate reseller will name its accredited parent, and that parent must pass the verification. A provider that cannot name any accredited registrar behind it has no ICANN accountability.
Acquire from an accredited operation: where verification meets the domain
Verification is the entry test, and it points to one practical conclusion: acquire domains through an accredited operation so the rail is sound before the transfer begins. For aged and expired domains, where the value is an inherited history that a botched transfer can destroy, sourcing through ICANN-accredited rails protects the asset. SEO Domains operates that accredited marketplace.
Why the accredited rail is the point
Every check in this guide answers one question: is the entity controlling the domain accountable to ICANN. When the answer is yes across the official sources, the transfer runs on a rail that ICANN can enforce, the registration record stays clean, and the inherited authority of an aged domain moves intact. When the answer is no, the same transaction carries the risk of a stalled transfer, a disputed record, or a lost name.
What an accredited marketplace removes from the equation
Sourcing an aged or expired domain through an accredited operation removes the verification burden from the buyer at the moment it matters the hardest. The transfer runs through ICANN-accredited rails, the registration record is recorded against an accountable registrar, and the chain of custody on the domain’s history is preserved. That is the practical reason accreditation is not abstract compliance but a direct protection on the value of the name.
