Re: [eppext] Suggestion for check domain extension

"Hollenbeck, Scott" <> Fri, 02 October 2015 10:58 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id EAABD1B29F3 for <>; Fri, 2 Oct 2015 03:58:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id YFUcVtyr34Cj for <>; Fri, 2 Oct 2015 03:58:20 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E7A5F1B29F2 for <>; Fri, 2 Oct 2015 03:58:19 -0700 (PDT)
Received: by oixx17 with SMTP id x17so6373941oix.2 for <>; Fri, 02 Oct 2015 03:58:19 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20130820; h=x-gm-message-state:from:to:subject:thread-topic:thread-index:date :message-id:references:in-reply-to:accept-language:content-language :content-type:mime-version; bh=/4rIEI78xaHijpCmhttO1q2ReayrjIYwuiXlaufYp1A=; b=NbNWnON5w/eEWLJQg2Sm8OvygnzhKiric48mJIQMUeXMImmbxgGADz8vqUeZxeGIvX i3uvtJIafhKbsInI63gL+zmWP4yyK/XlKVI9wQ3uARFNmnMvES85InKyqAov9XLPXRh0 0sObV9/oFi5NyGtJ6v2w2bwDs9uf6LgeOAwRI7DWn0vLm8l+7IdXl61y7tB2+egIKKAm dgAHukKD8wLR0/aX+PljRQjpRMPXe0pvkJv1vog/XQLUxfshm30/8RDlFSPqlu7Hav8+ 0i5p4hwm8YZRpxmB5rR3DQZZMmgOBWvmKD5TDPrqj3Jz8geoveEer251C+uFCIIJ/Lru XnnA==
X-Gm-Message-State: ALoCoQk44iL5c4UmIPGkl4tfxVFw2IqOAbRVo4+iXVUX0eZ65vgIatEY0Mvoowy/9JITUlHXTMVnO004WTf0SKkKeYbweaxBZQ==
X-Received: by with SMTP id b63mr19462478qkb.4.1443783499111; Fri, 02 Oct 2015 03:58:19 -0700 (PDT)
Received: from ( []) by with ESMTPS id b67sm1055332qka.7.2015. (version=TLSv1 cipher=RC4-SHA bits=128/128); Fri, 02 Oct 2015 03:58:19 -0700 (PDT)
Received: from (brn1wnexcas02 []) by (8.13.8/8.13.8) with ESMTP id t92AwI3d026693 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 2 Oct 2015 06:58:18 -0400
Received: from ([::1]) by ([::1]) with mapi id 14.03.0174.001; Fri, 2 Oct 2015 06:58:18 -0400
From: "Hollenbeck, Scott" <>
To: Michael Hansen <>, "" <>
Thread-Topic: [eppext] Suggestion for check domain extension
Thread-Index: AQHQ/PJC+ib3+WviIEaFNe/wevGWnJ5YCBAA
Date: Fri, 2 Oct 2015 10:58:17 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_831693C2CDA2E849A7D7A712B24E257F4A0A6CD3BRN1WNEXMBX02vc_"
MIME-Version: 1.0
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: Fri, 02 Oct 2015 10:58:22 -0000

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