.donor
Is .donor a real TLD? Who’s applying to run it?
Nobody has applied for .donor in its own right, as of 7 October 2026. Public Interest Registry named .donor as the replacement string of its .donate application.
A niche giving-themed address for donor pages and registries; nonprofits will keep their main identity on .org.
nonprofits and fundraising platforms wanting a donor-facing campaign or portal address, plus blood, organ and donor-registry organisations
No applications recorded for this TLD yet.
The 2012 applications making the most similar bet. Chosen by AI from every string in that round, without being told what happened to any of them.
Same bet: a plain English word for the philanthropic transaction that no single community owns, sold to the same nonprofit and fundraising-platform buyers who already hold their .org, and dependent on campaign and supporter-facing names rather than anyone moving their primary identity.
Same bet from the other grammatical side — a giving-relationship word whose only natural use is brand.gives sitting beside an organisation's real identity, which is exactly how a supporter-facing string like the target gets used.
Same sector and same buyer pool, but it names the organisation doing the asking rather than the counterparty being asked, so the registrant is the thing described and the identity claim is a degree stronger.
What a .donor domain is
.donor is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under Culture. Nobody has applied for .donor in its own right. It is named on ICANN’s list as part of an application for another string.
Is the .donor domain extension real yet?
.donor is not yet a domain extension you can register: nothing resolves under it, and no registrar sells names in it. Nobody has applied for it on the public record; the ICANN 2026 new gTLD round is the process that would decide whether it becomes one.
When can you buy a .donor domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .donor name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .donor was .giving, delegated on 6 August 2015.
Is .donor a real TLD?
Not yet. .donor is not in the DNS root, so nothing resolves under it. It’s here because ICANN’s list names .donor as part of an application for another string. Every entry on this page links to its source.
- Public Interest Registry · first recordedICANN
“PIR2624T-T89953 · Public Interest Registry · replacement string of .donate”ICANN
- Band chosen: 10-29 (vanity/narrow). The string names a role (the person who gives), not the organisation or the act, so it reads as a secondary, campaign-style address (give.donor, blood.donor, become.donor) rather than a primary identity. By analogy (flagged as analogy), giving-themed strings such as .charity, .foundation, .gives and .giving have found modest, sustained but thin use, and .ngo did not displace .org among nonprofits despite shared operator backing; .donor is narrower than all of those, which keeps it below the 30-49 band — there is no obvious volume or price-driven registration path because 'donor' is not a business category people build companies under. It sits above 1-9 because real demand exists in bounded pockets: donor-registry organisations, donor-advised fund providers, donor-management software vendors and fundraising microsites could plausibly use it as a clear, memorable secondary address. The record shows the applicant (Public Interest Registry) filed it as a replacement string for .donate with no contention; that operator's existing nonprofit relationships raise adoption likelihood somewhat but do not change the string's ceiling. Main market uncertainty: whether nonprofits will adopt a separate donor-facing domain at all, or keep donation flows on their .org site and on hosted fundraising platforms, which would leave .donor with event-driven campaign registrations and a negligible aftermarket. Registration volumes, pricing and comparable-TLD counts are unknown.