.pro domain names

What .pro is

.pro stands for professional. IANA classifies it distinctively as a restricted generic top-level domain rather than a plain generic gTLD - a legacy of the credentialed-professionals mandate it launched with. It belongs to ICANN's 2000 proof-of-concept round, not the 2012 New gTLD Program. That classification now sits awkwardly against reality: the IANA type is still restricted generic, while the operative eligibility rules have not been restrictive since 2015.

The operator as of 2026 is Identity Digital Limited, per the IANA delegation record, last updated on 10 March 2026. The chain is longer than most: RegistryPro, formed in 2000 and operational from May 2002; then Afilias, which acquired RegistryPro in 2012; then Donuts, which acquired Afilias in 2020; and the combined company rebranded as Identity Digital in 2022.

.pro was delegated on 8 May 2002, but public registration did not open until 23 June 2004 - a gap that reflects how much machinery the original credential-verification model required before anyone could buy a name.

Who can register .pro

Anyone. .pro has been fully unrestricted since 16 November 2015. There is no licence check, no certification requirement, no documentation and no verification step at registration; registrar policy documentation describes it plainly as an unrestricted TLD with no special registration requirements.

The history matters because the assumption it created still lingers. At the 2004 launch, eligibility covered four professions in four countries - accountants, engineers, lawyers and medical professionals, in Canada, Germany, the United Kingdom and the United States - and registrants had to demonstrate licensure. In September 2008 the registry admitted government-certified professionals in all countries and broadened the occupational scope. On 16 November 2015 the requirement was removed entirely.

The consequence runs both ways. A .pro domain no longer certifies anything about its owner, and any assumption that it implies a licensed professional is more than a decade out of date. Equally, anyone avoiding .pro because they expect to be rejected for lacking credentials is avoiding a gate that no longer exists.

What .pro costs to own

.pro is priced above the commodity new gTLDs at the registry level. It is a legacy Identity Digital extension carrying a mid-tier wholesale fee rather than a volume play.

Registry price increases are a live and material issue. One took effect on or around 19 January 2026 - widely reported at that date, though one registrar communication places it a few days earlier - and applied uniformly to new registrations, renewals and transfers, alongside simultaneous increases to .info and .io in the same Identity Digital adjustment. That followed a broader programme touching more than 200 extensions in October 2025. Budget for the cost of holding a .pro to drift upward. Two mechanics partly offset this: six months' notice of an increase, and the right to renew for up to ten years at the pre-increase price before it lands.

First-year discounting is common at registrar level, so the gap between acquisition price and renewal is wide and widening. Premium tiers exist under Identity Digital's premium programme, with premium renewal pricing that recurs annually. Restoring a lapsed .pro during its redemption grace period - the window after deletion in which only the original registrant may recover the name - costs substantially more than renewing on time.

Registration terms, renewals, and transfers

.pro registrations run for a minimum of one year and a maximum of ten, in whole-year increments, with expiry never more than ten years out. The ordinary gTLD lifecycle applies after expiry - an auto-renew grace period, a redemption period during which restoration is possible at substantially higher cost, then pending delete.

Transfers follow standard ICANN policy with no .pro-specific requirements. An EPP authorization code is required, the losing registrar must release it and lift clientTransferProhibited within five days of a valid request, and a transfer adds a year to the term. The three standard sixty-day locks apply - after initial registration, after a prior transfer, and after a Change of Registrant, the last with an opt-out available before the change. The reform approved by the GNSO Council on 12 March 2025 would replace them with 720-hour locks, but no effective date has been published.

The one genuinely .pro-specific point is what is no longer there. Before November 2015, moving a .pro could involve re-establishing the registrant's professional credentials with the registry. That friction is gone.

WHOIS, RDAP, and privacy

.pro is a gTLD, so ICANN's 28 January 2025 WHOIS sunset applies: RDAP is now the definitive source for registration data. Public output is redacted in line with ICANN's Registration Data Policy, in force since 21 August 2025, with contact routed through an anonymised email address or a registrar web form.

Privacy and proxy services are supported, and many registrars bundle them; there is no registry-level prohibition and no residue of the old credential model requiring a registrant to be publicly identifiable. Both the UDRP and the URS - a faster, narrower remedy for clear-cut trademark abuse - apply as ICANN consensus policies.

DNSSEC is supported: the zone is signed and registrants can publish DS records through any mainstream registrar. Internationalised domain names are a different matter - registrar documentation states that IDNs are not supported for this TLD. Identity Digital publishes a general IDN policy covering parts of its portfolio, so verify with the registry before committing if you need a non-ASCII label.

Who .pro suits, and who should avoid it

The value of .pro today is semantic rather than evidentiary. It reads professional; it does not prove professional. Within that limit it suits consultants, freelancers, agencies, coaches and service professionals who want a short, semantically loaded extension; the original credentialed professions of law, medicine, accountancy and engineering, where the word still carries weight; personal professional branding on the pattern of name.pro, where availability is far better than on .com; and businesses where pro carries product rather than occupational meaning - pro tiers, pro tools, professional-grade equipment.

Avoid it if:

• You want the extension itself to signal verified credentials. It has not done so since 2015, and implying otherwise to clients is misleading at best.
• You are cost-sensitive over a long horizon. The registry pricing trend is upward, increases apply to renewals, and the extension is not cheap to begin with.
• You need internationalised domain names, which registrar documentation indicates are not supported.
• Your market treats .com as a hard expectation for professional services - still substantially true in the US legal and medical markets.

Common mistakes with .pro

Implying to clients that .pro certifies professional status. It has not since 16 November 2015. Marketing a .pro address as evidence of licensure is misleading at best, and in regulated professions it is the kind of claim a professional body will take an interest in. The mirror-image error is just as common: registrants who never consider .pro because they assume they would be turned away.

Ignoring the registry price trajectory. .pro took an increase in January 2026 that applied to renewals and transfers as well as new registrations, following an Identity Digital programme across more than 200 extensions in October 2025. Registering a portfolio on the assumption of a flat renewal is a mistake; extending several years ahead of an announced increase is the standard hedge.

Confusing the legacy third-level namespaces with ordinary registrations. Whether law.pro, cpa.pro, med.pro and eng.pro are still openly purchasable is unclear from current registrar documentation, and at least one registrar states that .pro registrations are at the second level only.

What a credential-gated namespace was trying to solve

.pro was an attempt to make a domain name carry a verifiable claim about its holder. In 2002, when it was delegated, there was no practical way for someone reading a web address to know whether the person behind it was actually the lawyer or doctor they claimed to be. The proposition was that the address itself could do the work: if the registry only issued names to people who had proved their licensure, the extension became a credential visible in the address bar.

The original implementation was serious about it. Eligibility at the 2004 launch covered four professions - accountants, engineers, lawyers and medical practitioners - in four countries: Canada, Germany, the United Kingdom and the United States. That is one of the narrowest eligibility windows in the history of top-level domains, and it was narrow for a reason: verification only works if someone can actually check, and checking licensure means understanding the registration body, the register format and the legal meaning of the credential in each jurisdiction.

The namespace design went further, and this part was ahead of its time. .pro was built with profession-specific third-level namespaces - law.pro, cpa.pro, med.pro, eng.pro - under which credentialed practitioners registered names in the form firm.law.pro, creating verified professional sub-namespaces years before anyone was seriously building verified-identity TLDs.

It did not work commercially, and the reasons are instructive rather than embarrassing. Verification is expensive, and the cost falls on the registry at exactly the moment it is trying to build volume; a gate a registrar cannot automate becomes a gate the registrar would rather not sell through. The addressable market was tiny by construction, and the early geography shows the awkwardness: by April 2010 the United States held roughly 42% of registrations and France about 24%, an outsized share for a namespace launched with an Anglo-American professional framing.

The liberalisation followed the logic of those numbers - broader in 2008, unrestricted in 2015. .pro is one of the clearest examples of a restricted TLD abandoning its restriction to chase volume, and IANA still classifies it as restricted. The problem it was built to solve never went away; it was solved elsewhere, by certificate authorities, platform verification and professional directories, none of which live in the domain name.