Per-‐Registrar Transactions Report. This report shall be compiled in a comma separated-‐value formatted file as specified in RFC 4180. The file shall be named “gTLD-‐transactions-‐yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-‐TLD, the A-‐label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields per registrar: Field # Field name Description 01 registrar-‐name Registrar’s full corporate name as registered with IANA 02 iana-‐id For cases where the registry operator acts as registrar (i.e., without the use of an ICANN accredited registrar) 9999 should be used, otherwise the sponsoring Registrar IANA id should be used as specified in xxxx://xxx.xxxx.xxx/assignments/registrar-‐ids 03 total-‐domains total domain names under sponsorship in any EPP status but pendingCreate that have not been purged 04 total-‐nameservers total name servers (either host objects or name server hosts as domain name attributes) associated with domain names registered for the TLD in any EPP status but pendingCreate that have not been purged 05 net-‐adds-‐1-‐yr number of domains successfully registered (i.e., not in EPP pendingCreate status) with an initial term of one (1) year (and not deleted within the add grace period). A transaction must be reported in the month the add grace period ends.

See All (8)

Per-‐Registrar Transactions Report. This report shall be compiled in a comma separated- value formatted file as specified in RFC 4180. The file shall be named “net-transactions- yyyymm.csv.” The file shall contain the following fields per registrar: Field # Field name Description 01 registrar-name Registrar’s full corporate name as registered with IANA 03 total-domains total domain names under sponsorship in any EPP status but pendingCreate that have not been purged 04 total-nameservers total name servers (either host objects or name server hosts as domain name attributes) associated with domain names registered for the TLD in any EPP status but pendingCreate that have not been purged 05 net-adds-1-yr number of domains successfully registered (i.e., not in EPP pendingCreate status) with an initial term of one (1) year (and not deleted within the add grace period). A transaction must be reported in the month the add grace period ends.

See All (7)

Per-‐Registrar Transactions Report. This report shall be compiled in a comma separated- value formatted file as specified in RFC 4180. The file shall be named “net-transactions- yyyymm.csv.” The file shall contain the following fields per registrar: Field # Field name Description 01 registrar-name Registrar’s full corporate name as registered with IANA 02 iana-id For cases where the registry operator acts as registrar (i.e., without the use of an ICANN accredited registrar) either 9998 or 9999 should be used depending on registration type, otherwise the sponsoring Registrar IANA id should be used as specified in xxxxx://xxx.xxxx.xxx/assignments/registrar-ids 03 total-domains total domain names under sponsorship in any EPP status but pendingCreate that have not been purged 04 total-nameservers total name servers (either host objects or name server hosts as domain name attributes) associated with domain names registered for the TLD in any EPP status but pendingCreate that have not been purged 05 net-adds-1-yr number of domains successfully registered (i.e., not in EPP pendingCreate status) with an initial term of one (1) year (and not deleted within the add grace period). A transaction must be reported in the month the add grace period ends.

See All (6)

Per-‐Registrar Transactions Report. This report shall be compiled in a comma separated-value formatted file as specified in RFC 4180. The file shall be named “gTLD-transactions-yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-TLD, the A-label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields per registrar: Field # Field Name Description 01 registrar-name registrar's full corporate name as registered with IANA 02 iana-id httx://xxx.xxxx.xxx/xxxxxxxxxxx/registrar-ids 03 total-domains total domains under sponsorship 04 total-nameservers total name servers registered for TLD 05 net-adds-1-yr number of domains successfully registered with an initial term of one year (and not deleted within the add grace period) 06 net-adds-2-yr number of domains successfully registered with an initial term of two years (and not deleted within the add grace period) 07 net-adds-3-yr number of domains successfully registered with an initial term of three years (and not deleted within the add grace period) 08 net-adds-4-yr number of domains successfully registered with an initial term of four years (and not deleted within the add grace period) 09 net-adds-5-yr number of domains successfully registered with an initial term of five years (and not deleted within the add grace period) 10 net-adds-6-yr number of domains successfully registered with an initial term of six years (and not deleted within the add grace period) 11 net-adds-7-yr number of domains successfully registered with an initial term of seven years (and not deleted within the add grace period) 12 net-adds-8-yr number of domains successfully registered with an initial term of eight years (and not deleted within the add grace period) 13 net-adds-9-yr number of domains successfully registered with an initial term of nine years (and not deleted within the add grace period) 14 net-adds-10-yr number of domains successfully registered with an initial term of ten years (and not deleted within the add grace period) 15 net-renews-1-yr number of domains successfully renewed either automatically or by command with a new renewal period of one year (and not deleted within the renew grace period) 16 net-renews-2-yr number of domains successfully renewed either automatically or by command with a new renewal period of two years (and not deleted within the renew grace period) 18 net-renews-4-yr number of domains successfully renewed either automatically or by command with a new renewal period of four year...

See All (5)

Per-‐Registrar Transactions Report. This report shall be compiled in a comma separated-value formatted file as specified in RFC 4180. The file shall be named “gTLD-transactions-yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-TLD, the A-label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields per registrar: [Drafting note to community on change from v4: The requirement for an SLA report was removed given ICANN’s plan to build an SLA monitoring system, as described in Specification 6, that would produce those results directly. ICANN plans to periodically publish results from the SLA monitoring system in order to allow the registrants and other interested parties access to this information.] 1. WHOIS Service. Until ICANN specifies a different format and protocol, Registry Operator will operate a registration data publication service available via both port 43 and a website at <whois.nic.TLD> in accordance with RFC 3912 providing free public query-based access to at least the following elements in the following format. ICANN reserves the right to specify alternative formats and protocols, and upon such specification, the Registry Operator will implement such alternative specification as soon as reasonably practicable. 1.1. The format of responses shall follow a semi-free text format outline below, followed by a blank line and a legal disclaimer specifying the rights of Registry Operator, and of the user querying the database. 1.2. Each data object shall be represented as a set of key/value pairs, with lines beginning with keys, followed by a colon and a space as delimiters, followed by the value. 1.3. For fields where more than one value exists, multiple key/value pairs with the same key shall be allowed (for example to list multiple name servers). The first key/value pair after a blank line should be considered the start of a new record, and should be considered as identifying that record, and is used to group data, such as hostnames and IP addresses, or a domain name and registrant information, together.

Per-‐Registrar Transactions Report Sample Clauses

Filter & Search

Related Clauses

Parent Clauses

Sub-Clauses

Per-­‐Registrar Transactions Report Sample Clauses

Per-‐Registrar Transactions Report Sample Clauses