Yes, the first draft Applicant GuideBook is here. This is not the final version.
ICANN also did two webinars explaining the high points. Last time, they changed it more than six times before the process began, and they changed it during and after. Here are the things I noticed…
The first thing I noticed is that there is an entire process for changing things. They are calling this the Predictability Framework. They changed things last time, but there wasn’t a clear process for doing so. This tells me that there will be more versions of the Applicant Guidebook, but we’ll have a better idea of how it’s done this time. 🙂
Another significant change has been discussed and implemented now for at least a year; Registry Service Providers (RSPs) will be evaluated only once before the Applicant Window opens. This looks like a nice improvement. Last time, RSPs were evaluated over and over with each applicant. That was wasted time.
In contrast with the last Applicant Guidebook (AGB), this guidebook has a very well-organized Table of Contents. I really like the Applicant Journey section. It’s a clear depiction of what applicants can expect as part of this process.
On my first read, I was concerned that 2012 applicants would get their singulars and plurals for free under 2.3.1.1.2 (Four Variant Strings free for existing gTLDs). I asked about that on the webinar, and they seemed to confirm that this is not the case. We’ll see how this is treated as time goes by.
Refunds: This time, there are only three distinct refund windows: 65% within ten days of String Confirmation Day, 35% until the start of the Application and Applicant Evaluation, and 20% up to the point at which an applicant would enter into a registry agreement with ICANN. It’s simpler, but it also adds more risk for applicants.
They also offer refunds if there are material changes as described above in the Predictability Framework. I love ICANN, but this feels more like an unpredictability framework. :-). At least there is a way out if a big change materially affects your application. 2.3.3.2 discusses an Application Volume Refund that will be important to think of when you apply. It has something to do with what will happen if ICANN ends up getting less than 1,000 submissions (and revenue). We have to watch this.
Another new feature is the Replacement Period. This means that if you think your original string is going to be part of a difficult contention set, you’ll be able to substitute a replacement string that you listed with your application. After the Reveal Day, there will be a 14-day Replacement Period to notify ICANN that you wish to replace your original applied-for string with the replacement identified your your application. I’ll reserve judgment here.
There will still be a Prioritization Draw that determines the order of delegation, with IDNs being prioritized above others.
The processes for contention resolution seem onerous; they give ICANN several options to enforce, including legal action. OMG. But after reading through Module 3: Community Input. Objections and Appeals, I was encouraged… There is a lot of material about how to resolve contention. A lot of this new guidebook deals with situations you may never find yourself in, depending on the string(s) you choose. I get the feeling that ICANN is really looking for applicants who want to run their strings in good faith, and that’s not a bad thing. Look for more here over the coming weeks and months. Please get my book on how to get your own top-level domain to learn more.
ICANN’s draft version is published here: https://itp.cdn.icann.org/en/files/policy-development/new-gtld-program-next-round-draft-applicant-guidebook-for-public-comment-30-05-2025-en.pdf
