Re: [eppext] Suggestion for check domain extension

"Linlin Zhou" <> Thu, 08 October 2015 07:52 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 4C5FD1A0BE8 for <>; Thu, 8 Oct 2015 00:52:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.611
X-Spam-Status: No, score=-2.611 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 6D-PfnIsOX_E for <>; Thu, 8 Oct 2015 00:52:29 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id EA4281A06FD for <>; Thu, 8 Oct 2015 00:52:27 -0700 (PDT)
Received: from zll (unknown []) by (Coremail) with SMTP id AQAAf0CJkDi0IBZWKWR+Ag--.5877S2; Thu, 08 Oct 2015 15:52:20 +0800 (CST)
Date: Thu, 8 Oct 2015 15:52:49 +0800
From: "Linlin Zhou" <>
To: =?UTF-8?B?SG9sbGVuYmVjaywgU2NvdHQ=?= <>, "Michael Hansen" <>, "" <>
References: <>, <>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7, 2, 5, 136[cn]
Mime-Version: 1.0
Message-ID: <>
Content-Type: multipart/alternative; boundary="----=_001_NextPart353573685156_=----"
X-Coremail-Antispam: 1UD129KBjvJXoWxCFWUuw1rGF4rurykJF47urg_yoW5Jw45pF sFyrWYgF4kZr1xJrW8uw45uryjk34Y939rGrnYqF12vFWUWa4kX3ZYyr1j9Fy0yr4rJr4v va9rtr17Zw48ZFJanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUUdIb7Iv0xC_Cr1lb4IE77IF4wAFF20E14v26r1j6r4UM7CY07I2 0VC2zVCF04k26cxKx2IYs7xG6rWj6s0DM7CIcVAFz4kK6r1j6r18M28lY4IEw2IIxxk0rw A2F7IY1VAKz4vEj48ve4kI8wA2z4x0Y4vE2Ix0cI8IcVAFwI0_Ar0_tr1l84ACjcxK6xII jxv20xvEc7CjxVAFwI0_Cr0_Gr1UM28EF7xvwVC2z280aVAFwI0_GcCE3s1l84ACjcxK6I 8E87Iv6xkF7I0E14v26rxl6s0DM2AIxVAIcxkEcVAq07x20xvEncxIr21l5I8CrVAYj202 j2C_Gr0_Xr1l5I8CrVAqjxCE14ACF2xKxwAqx4xG64kEw2xG04xIwI0_Jr0_Gr1l5I8CrV CF0I0E4I0vr24l5I8CrVC2j2CEjI02ccxYII8I67AEr4CY67k08wAv7VC0I7IYx2IY67AK xVWUJVWUGwAv7VC2z280aVAFwI0_Jr0_Gr1lOx8S6xCaFVCjc4AY6r1j6r4UM4x0Y48Icx kI7VAKI48JM4xvF2IEb7IF0Fy264kE64k0F24lFcxC0VAYjxAxZF0Ex2IqxwCY02Avz4vE 14v_GF4l42xK82IYc2Ij64vIr41l4I8I3I0E4IkC6x0Yz7v_Jr0_Gr1lx2IqxVAqx4xG67 AKxVWUGVWUWwC20s026x8GjcxK67AKxVWUGVWUWwC2zVAF1VAY17CE14v26r1Y6r17MIIY rxkI7VAKI48JMIIF0xvE2Ix0cI8IcVAFwI0_Jr0_JF4lIxAIcVC0I7IYx2IY6xkF7I0E14 v26r1j6r4UMIIF0xvE42xK8VAvwI8IcIk0rVWrZr1j6s0DMIIF0xvEx4A2jsIE14v26r1j 6r4UMIIF0xvEx4A2jsIEc7CjxVAFwI0_Jr0_Gr1l6VACY4xI67k04243AbIYCTnIWIevJa 73UjIFyTuYvjxU2l4iDUUUU
X-CM-SenderInfo: p2kr3zplqox0w6fq0xffof0/
Archived-At: <>
Subject: Re: [eppext] Suggestion for check domain extension
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: EPPEXT <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 08 Oct 2015 07:52:36 -0000

We also have the same requirement. Moreover, some users want to know whether a domain is allocated/blocked/reserved in different language scripts, such as Chinese, Japanese and Korean. Because of different label generation rules, even the same domain may have different status. I'd like to help write an initial draft to specify this extension.


Linlin Zhou
From: Hollenbeck, Scott
Date: 2015-10-02 18:58
To: Michael Hansen;
Subject: Re: [eppext] Suggestion for check domain extension
Have you considered writing a draft describing such an extension?
It would be nice if the AFNIC extension was registered:
From: EppExt [] On Behalf Of Michael Hansen
Sent: Friday, October 02, 2015 5:11 AM
Subject: [eppext] Suggestion for check domain extension
As a registrar I would like to see a standard way in check domain to get information about if a domain is blocked or reserved, like in the AFNIC extension (

AFNIC <check> response extensions details
<complexType name="resChkDataType">
    <element name="domain" type="frnic:resChkDomDataType"/>

<complexType name="resChkDomDataType">
    <element name="cd" type="frnic:domCheckType" maxOccurs="unbounded"/>

<complexType name="domCheckType">
    <element name="name" type="frnic:domCheckNameType"/>
    <element name="rsvReason" type="eppcom:reasonType" minOccurs="0"/>
    <element name="fbdReason" type="eppcom:reasonType" minOccurs="0"/>

<complexType name="domCheckNameType">
    <extension base="eppcom:labelType">
      <attribute name="reserved" type="boolean" use="required"/>
      <attribute name="forbidden" type="boolean" use="required"/>

Using the current check domain it is not possible to identify blocked/reserved domains unless the reason can be parsed, as most just return unavailable for blocked domains, and available for reserved domains.

It might also be extended with some kind of identifier for who the domain is reserved to (i.e. domain name for .uk domains, or VAT number for .rio domains).


Michael Hansen
Senior Developer A/S