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.
Appears in 2082 contracts
Samples: Registry Agreement, Registry Agreement, Registry Agreement
Per-‐Registrar Transactions Report. This report shall be compiled in a comma separated-‐value separated-value formatted file as specified in RFC 4180. The file shall be named “gTLD-‐transactions-‐yyyymm.csvgTLD-transactions-yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-‐TLDIDN-TLD, the A-‐label 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-name Registrar’s full corporate name as registered with IANA 02 iana-‐id 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 xxxx://xxx.xxxx.xxx/assignments/registrar-ids 03 total-‐domains total-domains total domain names under sponsorship in any EPP status but pendingCreate that have not been purged 04 total-‐nameservers 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 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.
Appears in 50 contracts
Samples: Registry Agreement, Registry Agreement, Registry Agreement
Per-‐Registrar Transactions Report. This report shall be compiled in a comma separated-‐value separated-value formatted file as specified in RFC 4180. The file shall be named “gTLD-‐transactions-‐yyyymm.csvgTLD-transactions-yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-‐TLDIDN-TLD, the A-‐label 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-name Registrar’s full corporate name as registered with IANA 02 iana-‐id 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 usedused depending on registration type (as described in Specification 5), otherwise the sponsoring Registrar IANA id should be used as specified in xxxx://xxx.xxxx.xxx/assignments/registrar-‐ids xxxx://xxx.xxxx.xxx/assignments/registrar-ids 03 total-‐domains total-domains total domain names under sponsorship in any EPP status but pendingCreate that have not been purged 04 total-‐nameservers 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 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.
Appears in 19 contracts
Samples: Registry Agreement, Registry Agreement, Registry Agreement
Per-‐Registrar Transactions Report. This report shall be compiled in a comma separated-‐value separated‐value formatted file as specified in RFC 4180. The file shall be named “gTLD-‐transactions-‐yyyymm.csvgTLD‐transactions‐yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-‐TLDIDN‐TLD, the A-‐label 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‐name Registrar’s full corporate name as registered with IANA 02 iana-‐id 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 usedused depending on registration type (as described in Specification 5), otherwise the sponsoring Registrar IANA id should be used as specified in xxxx://xxx.xxxx.xxx/assignments/registrar-‐ids xxxx://xxx.xxxx.xxx/assignments/registrar‐ids 03 total-‐domains total‐domains total domain names under sponsorship in any EPP status but pendingCreate that have not been purged 04 total-‐nameservers 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 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.
Appears in 12 contracts
Samples: Registry Agreement, Registry Agreement, Registry Agreement
Per-‐Registrar Transactions Report. This report shall be compiled in a comma separated-‐value separated‐value formatted file as specified in RFC 4180. The file shall be named “gTLD-‐transactions-‐yyyymm.csvgTLD‐transactions‐yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-‐TLDIDN‐TLD, the A-‐label 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‐name Registrar’s full corporate name as registered with IANA 02 iana-‐id 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 xxxx://xxx.xxxx.xxx/assignments/registrar‐ids 03 total-‐domains total‐domains total domain names under sponsorship in any EPP status but pendingCreate that have not been purged 04 total-‐nameservers 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 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.
Appears in 5 contracts
Samples: Registry Agreement, Registry Agreement, Registry Agreement
Per-‐Registrar Transactions Report. This report shall be compiled in a comma separated-‐value separated-value formatted file as specified in RFC 4180. The file shall be named “gTLD-‐transactions-‐yyyymm.csvgTLD- transactions-yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-‐TLDIDN-TLD, the A-‐label 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-name Registrar’s full corporate name as registered with IANA 02 iana-‐id 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 usedused depending on registration type (as described in Specification 5), otherwise the sponsoring Registrar IANA id should be used as specified in xxxx://xxx.xxxx.xxx/assignments/registrar-‐ids xxxx://xxx.xxxx.xxx/assignments/registrar-ids 03 total-‐domains total-domains total domain names under sponsorship in any EPP status but pendingCreate that have not been purged 04 total-‐nameservers 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 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.
Appears in 5 contracts
Samples: Aero TLD Sponsorship Registry Agreement, Coop Sponsored TLD Registry Agreement, Museum Registry Agreement
Per-‐Registrar Transactions Report. This report shall be compiled in a comma separated-‐value separated-value formatted file as specified in RFC 4180. The file shall be named “gTLD-‐transactions-‐yyyymm.csvgTLD-transactions-yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-‐TLDIDN-TLD, the A-‐label 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-name Registrar’s full corporate name as registered with IANA 02 iana-‐id 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 usedused depending on registration type (as described in Specification 5), otherwise the sponsoring Registrar IANA id should be used as specified in xxxx://xxx.xxxx.xxx/assignments/registrar-‐ids xxxxx://xxx.xxxx.xxx/assignments/registrar-ids 03 total-‐domains total-domains total domain names under sponsorship in any EPP status but pendingCreate that have not been purged 04 total-‐nameservers 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 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.
Appears in 4 contracts
Samples: Registry Agreement, Registry Agreement, Registry Agreement
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.
Appears in 3 contracts
Samples: Registry Agreement, Registry Agreement, Registry Agreement
Per-‐Registrar Transactions Report. This report shall be compiled in a comma separated-‐value separated- value formatted file as specified in RFC 4180. The file shall be named “gTLD-‐transactions-‐yyyymm.csv”, where “gTLDnet-transactions- yyyymm.csv.” 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-name Registrar’s full corporate name as registered with IANA 02 iana-‐id 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 usedused depending on registration type, otherwise the sponsoring Registrar IANA id should be used as specified in xxxx://xxx.xxxx.xxx/assignments/registrar-‐ids xxxx://xxx.xxxx.xxx/assignments/registrar-ids 03 total-‐domains total-domains total domain names under sponsorship in any EPP status but pendingCreate that have not been purged 04 total-‐nameservers 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 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.
Appears in 2 contracts
Samples: Com Registry Agreement, Com Registry Agreement
Per-‐Registrar Transactions Report. This report shall be compiled in a comma separated-‐value separated- value formatted file as specified in RFC 4180. The file shall be named “gTLD-‐transactions-‐yyyymm.csv”, where “gTLDnet-transactions- yyyymm.csv.” 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-name Registrar’s full corporate name as registered with IANA 02 iana-‐id 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 usedused depending on registration type, otherwise the sponsoring Registrar IANA id should be used as specified in xxxx://xxx.xxxx.xxx/assignments/registrar-‐ids xxxxx://xxx.xxxx.xxx/assignments/registrar-ids 03 total-‐domains total-domains total domain names under sponsorship in any EPP status but pendingCreate that have not been purged 04 total-‐nameservers 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 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.
Appears in 2 contracts
Samples: Registry Agreement, Registry Agreement
Per-‐Registrar Transactions Report. This report shall be compiled in a comma separated-‐value separated-value formatted file as specified in RFC 4180. The file shall be named “gTLD-‐transactions-‐yyyymm.csvgTLD-transactions-yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-‐TLDIDN-TLD, the A-‐label A-label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields per registrar: Field Fiel d # Field name Description 01 registrar-‐name registrar-name Registrar’s full corporate name as registered with IANA 02 iana-‐id 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 xxxx://xxx.xxxx.xxx/assignments/registrar-i ds 03 total-‐domains total-domains total domain names under sponsorship in any EPP status but pendingCreate that have not been purged 04 total-‐nameservers 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 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.
Appears in 2 contracts
Samples: Registry Agreement, Registry Agreement
Per-‐Registrar Transactions Report. This report shall be compiled in a comma separated-‐value separated- value formatted file as specified in RFC 4180. The file shall be named “gTLD-‐transactions-‐yyyymm.csvgTLD-transactions- yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-‐TLDIDN-TLD, the A-‐label 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-name Registrar’s full corporate name as registered with IANA 02 iana-‐id 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 xxxx://xxx.xxxx.xxx/assignments/registrar-ids 03 total-‐domains total-domains total domain names under sponsorship in any EPP status but pendingCreate that have not been purged 04 total-‐nameservers 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 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.
Appears in 2 contracts
Samples: Registry Agreement, Registry Agreement
Per-‐Registrar Transactions Report. This report shall be compiled in a comma separated-‐value separated-value formatted file as specified in RFC 4180. The file shall be named “gTLD-‐transactions-‐yyyymm.csvgTLD-transactions-yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-‐TLDIDN-TLD, the A-‐label 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-name Registrar’s full corporate name as registered with IANA 02 iana-‐id iana-id For cases where the registry operator XxXXX acts as registrar (i.e., without the use of an ICANN cxDA 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 xxxx://xxx.xxxx.xxx/assignments/registrar-ids 03 total-‐domains total-domains total domain names under sponsorship in any EPP status but pendingCreate that have not been purged 04 total-‐nameservers 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 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.
Appears in 2 contracts
Samples: Registry Agreement, Registry Agreement
Per-‐Registrar Transactions Report. This report shall be compiled in a comma separated-‐value separated- value formatted file as specified in RFC 4180. The file shall be named “gTLD-‐transactions-‐yyyymm.csvgTLD-transactions- yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-‐TLDIDN-TLD, the A-‐label 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-name Registrar’s full corporate name as registered with IANA 02 iana-‐id 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 usedused depending on registration type (as described in Specification 5), otherwise the sponsoring Registrar IANA id should be used as specified in xxxx://xxx.xxxx.xxx/assignments/registrar-‐ids xxxx://xxx.xxxx.xxx/assignments/registrar-ids 03 total-‐domains total-domains total domain names under sponsorship in any EPP status but pendingCreate that have not been purged 04 total-‐nameservers 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 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.
Appears in 1 contract
Per-‐Registrar Transactions Report. This report shall be compiled in a comma separated-‐value separated-value formatted file as specified in RFC 4180. The file shall be named “gTLD-‐transactions-‐yyyymm.csvgTLD-transactions-yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-‐TLDIDN-TLD, the A-‐label 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-name Registrar’s full corporate name as registered with IANA 02 iana-‐id 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 xxxx://xxx.xxxx.xxx/assignments/regis trar-ids 03 total-‐domains total-domains total domain names under sponsorship in any EPP status but pendingCreate that have not been purged 04 total-‐nameservers 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 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.
Appears in 1 contract
Samples: Registry Agreement
Per-‐Registrar Transactions Report. This report shall be compiled in a comma separated-‐value separated-value formatted file as specified in RFC 4180. The file shall be named “gTLD-‐transactions-‐yyyymm.csvgTLD-transactions-yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-‐TLDIDN-TLD, the A-‐label A-label shall be used; “yyyymm” is the year and month being reportedbeingreported. The file shall contain the following fields per registrar: Field # Field name Description 01 registrar-‐name registrar-name Registrar’s full corporate name as registered with registeredwith IANA 02 iana-‐id 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 xxxx://xxx.xxxx.xxx/assignments/registrar-ids 03 total-‐domains total-domains total domain names under sponsorship in any EPP status but pendingCreate that have not been purged 04 total-‐nameservers 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 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.
Appears in 1 contract
Samples: Registry Agreement
