The top-level domain (TLD) you mentioned, XN—NGBRX, appears to be in Punycode, which represents Unicode within the limited character subset of ASCII, often utilized for internationalized domain names (IDNs) that contain non-ASCII characters, as per the Internet Engineering Task Force Standards (RFC 3492).
However, after a check with the Internet Assigned Numbers Authority (IANA) which is responsible for the global coordination of the DNS Root, IP addressing, and other Internet protocol resources, it appears that XN—NGBRX is not a recognized TLD.
Punycode TLDs always begin with “xn—” but are followed by a string that represents the Unicode characters of the actual TLD in a specific encoding. An example of this is the Arabic TLD “موقع.“which is coded as “xn—wgbh1c” in Punycode. These domain names allow internet users across the world to access the web in their native scripts and specific linguistic needs.
Internationalized domain names are registered and maintained by several domain and web hosting companies across the world after delegated or approved by the Internet Corporation for Assigned Names and Numbers (ICANN), under its IDN ccTLD Fast Track Process, launched in 2009.
As of 2021, there are 154 delegated IDN ccTLDs in the IANA Root Zone Database. These include Punycode TLDs such as “xn—fiqs8s” (China), “xn—io0a7i” (Network), “xn—11b5bs3a9aj6g” (India), etc.
It’s important to note that each Punycode encoding corresponds to a specific Unicode string. Therefore, the decoded Unicode string MUST be exactly the same as the original. A significant check could be achieved using several online Punycode to Unicode converters available.
For TLDs, the entire code string after “xn—” must map to a Unicode string that represents an approved TLD string. If it does not, like in the case of “xn—ngbrx,” the TLD is not considered valid. For this specific TLD, using a Punycode Convertor, it was seen to not correspond to a known TLD upon conversion, reflecting that it’s currently not in use or doesn’t represent a valid domain extension in Unicode.
Sources:
1. IANA Root Zone Database (https://data.iana.org/TLD/tlds-alpha-by-domain.txt)
2. ICANN (https://www.icann.org/resources/pages/tlds-2012-02-25-en)
3. RFC 3492 – Punycode: A Bootstring encoding of Unicode for Internationalized Domain Names in Applications (IDNA) (https://datatracker.ietf.org/doc/html/rfc3492)
4. Punycode Converter (https://www.punycoder.com/)
