Summary

  • A string in a script not integrated into the applicable RZ-LGR cannot be submitted.
  • The pre-submission DNS Stability Review challenge can address an incorrectly applied or miscoded validation, but it expressly excludes unsupported scripts.

An applied-for IDN is validated against the applicable version of the Root Zone Label Generation Rules. For the 2026 Round, the Guidebook identifies RZ-LGR version 6 and lists the scripts and writing systems integrated into it.

The Guidebook states that an applicant cannot submit a string in a script that is not integrated into the applicable RZ-LGR.

The prescribed path starts with the script community. A potential applicant should work with that community to integrate the script under the RZ-LGR Procedure. ICANN says it will actively support the process and can be contacted at any time. If integration is completed and made available in an applicable version, the applicant may be able to apply in a subsequent application period; the Guidebook does not promise acceptance.

The pre-submission DNS Stability Review challenge has a narrower role. It lets an applicant contest an automated validation that appears to have been incorrectly applied or miscoded. The Guidebook expressly says that this challenge does not apply to scripts unsupported by the RZ-LGR. Its scope is the contested validation, not integration of a missing script.

That distinction changes sequencing. Teams should verify script integration before investing in a round-specific string, evidence package or filing timetable. A red validation caused by an implementation error and a red validation caused by absent script support require different responses.

BTW recommends a script-readiness checkpoint recording the applicable RZ-LGR version, script integration status, the exact validation output and the application-period consequence. This is editorial guidance, not an ICANN requirement.

Sources