Generic Top-Level Domain (gTLD) Registry Agreements
.name Registry Agreement Appendix 4
Registry Operator's Monthly Reports
(1 December 2012)
Registry Operator shall provide monthly reports as described below. Reports shall be submitted via email to <registry-reports@icann.org>. ICANN may request in the future that the reports be delivered by other means. ICANN shall use reasonable commercial efforts to preserve the confidentiality of the information reported until three months after the end of the month to which the report relates.
(A) Monthly Report. File shall be in Portable Document Format (PDF). Report shall contain the following information.
- Accredited Registrar Status. State the number of registrars in each of the following three categories: (1) operational, (2) ramp-up (registrars that have received a password for access to OT&E), and (3) pre-ramp-up (registrars that have requested access, but have not yet entered the ramp-up period).
- TLD Zone File Access Activity. State the total number of zone file access passwords at end of the reporting month.
- Completed System Software Releases. Describe significant releases during the reporting month, including release name, features, and completion date.
- Whois Service Activity. State the number of Whois queries during the reporting month.
- Total Number of Transactions by Subcategory by Month. State the total number of transactions during the reporting month, in the following subcategories: adds, deletes, modifies, checks, renews, transfers, restores.
- Daily Transaction Range. Tabulate the number of total daily transactions. The range of transaction volume should be shown for each month, along with the average daily transaction volume.
(B) Per-Registrar Activity Report for Second-Level and Traditional Third-Level Transactions. File shall be named "name-transactions-YYYYMM.csv", where "YYYYMM" is the year and month being reported. Registry Operator shall provide this report monthly. This report shall be in comma separated-value format as specified in RFC 4180, using the following fields per registrar:
Field # | Field Name | Notes |
---|---|---|
01 | registrar-name | registrar's full corporate name as registered with IANA |
02 | iana-id | http://www.iana.org/assignments/registrar-ids |
03 | total-domains | total domains under sponsorship |
04 | total-nameservers | total name servers registered |
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) |
17 | net-renews-3-yr | number of domains successfully renewed either automatically or by command with a new renewal period of three 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 years (and not deleted within the renew grace period) |
19 | net-renews-5-yr | number of domains successfully renewed either automatically or by command with a new renewal period of five years (and not deleted within the renew grace period) |
20 | net-renews-6-yr | number of domains successfully renewed either automatically or by command with a new renewal period of six years (and not deleted within the renew grace period) |
21 | net-renews-7-yr | number of domains successfully renewed either automatically or by command with a new renewal period of seven years (and not deleted within the renew grace period) |
22 | net-renews-8-yr | number of domains successfully renewed either automatically or by command with a new renewal period of eight years (and not deleted within the renew grace period) |
23 | net-renews-9-yr | number of domains successfully renewed either automatically or by command with a new renewal period of nine years (and not deleted within the renew grace period) |
24 | net-renews-10-yr | number of domains successfully renewed either automatically or by command with a new renewal period of ten years (and not deleted within the renew grace period) |
25 | transfer-gaining-successful | transfers initiated by this registrar that were ack'd by the other registrar – either by command or automatically |
26 | transfer-gaining-nacked | transfers initiated by this registrar that were n'acked by the other registrar |
27 | transfer-losing-successful | transfers initiated by another registrar that this registrar ack'd – either by command or automatically |
28 | transfer-losing-nacked | transfers initiated by another registrar that this registrar n'acked |
29 | transfer-disputed-won | Number of transfer disputes in which this registrar prevailed |
30 | transfer-disputed-lost | number of transfer disputes this registrar lost |
31 | transfer-disputed-nodecision | number of transfer disputes involving this registrar with a split or no decision |
32 | deleted-domains-grace | domains deleted within the add grace period |
33 | deleted-domains-nograce | domains deleted outside the add grace period |
34 | restored-domains | domains restored from redemption period |
35 | restored-noreport | total number of restored names for which the registrar failed to submit a restore report |
36 | agp-exemption-requests | total number of AGP (add grace period) exemption requests |
37 | agp-exemptions-granted | total number of AGP (add grace period) exemption requests granted |
38 | agp-exempted-domains | total number of names affected by granted AGP (add grace period) exemption requests |
39 | attempted-adds | Number of attempted (successful and failed) domain name create commands |
The first line shall include the field names exactly as they appear in the table above as a "header line" as described in section 2 of RFC 4180. The last line of each report should include totals for each column across all registrars. The first field of this line shall read "Totals" while the second field shall be left empty in that line. Registry Operator shall include field #39 "attempted-adds" in each report within eighteen (18) months of the Effective Date of the Agreement. No other lines besides the ones described above shall be included. Line breaks shall be "CRLF" (<U+000D, U+000A>) as described in RFC 4180.
(C) Per-Registrar Activity Report for Bulk Third-level Transactions. File shall be named "name-bulk-transactions-YYYYMM.csv"; where "YYYYMM" is the year and month being reported . Registry Operator shall provide this report only for those months during which bulk third-level transactions were processed. This report shall be in comma separated-value format, as specified in RFC 4180 using the following fields per registrar:
Field # | Field Name | Notes |
---|---|---|
01 | registrar-name | registrar's full corporate name as registered with IANA |
02 | iana-id | http://www.iana.org/assignments/registrar-ids |
03 | total-domains | total domains under sponsorship |
04 | total-nameservers | total nameservers registered |
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) |
17 | net-renews-3-yr | number of domains successfully renewed either automatically or by command with a new renewal period of three 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 years (and not deleted within the renew grace period) |
19 | net-renews-5-yr | number of domains successfully renewed either automatically or by command with a new renewal period of five years (and not deleted within the renew grace period) |
20 | net-renews-6-yr | number of domains successfully renewed either automatically or by command with a new renewal period of six years (and not deleted within the renew grace period) |
21 | net-renews-7-yr | number of domains successfully renewed either automatically or by command with a new renewal period of seven years (and not deleted within the renew grace period) |
22 | net-renews-8-yr | number of domains successfully renewed either automatically or by command with a new renewal period of eight years (and not deleted within the renew grace period) |
23 | net-renews-9-yr | number of domains successfully renewed either automatically or by command with a new renewal period of nine years (and not deleted within the renew grace period) |
24 | net-renews-10-yr | number of domains successfully renewed either automatically or by command with a new renewal period of ten years (and not deleted within the renew grace period) |
25 | transfer-gaining-successful | transfers initiated by this registrar that were ack'd by the other registrar – either by command or automatically |
26 | transfer-gaining-nacked | transfers initiated by this registrar that were n'acked by the other registrar |
27 | transfer-losing-successful | transfers initiated by another registrar that this registrar ack'd – either by command or automatically |
28 | transfer-losing-nacked | transfers initiated by another registrar that this registrar n'acked |
29 | transfer-disputed-won | Number of transfer disputes in which this registrar prevailed |
30 | transfer-disputed-lost | number of transfer disputes this registrar lost |
31 | transfer-disputed-nodecision | number of transfer disputes involving this registrar with a split or no decision |
32 | deleted-domains-grace | domains deleted within the add grace period |
33 | deleted-domains-nograce | domains deleted outside the add grace period |
34 | restored-domains | domains restored from redemption period |
35 | restored-noreport | total number of restored names for which the registrar failed to submit a restore report |
36 | agp-exemption-requests | total number of AGP (add grace period) exemption requests |
37 | agp-exemptions-granted | total number of AGP (add grace period) exemption requests granted |
38 | agp-exempted-domains | total number of names affected by granted AGP (add grace period) exemption requests |
39 | attempted-adds | Number of attempted (successful and failed) domain name create commands |
The first line shall include the field names exactly as they appear in the table above as a "header line" as described in section 2 of RFC 4180. The last line of each report should include totals for each column across all registrars. The first field of this line shall read "Totals" while the second field shall be left empty in that line. Registry Operator shall include field #39 "attempted-adds" in each report within eighteen (18) months of the Effective Date of the Agreement. No other lines besides the ones described above shall be included. Line breaks shall be "CRLF" (<U+000D, U+000A>) as described in RFC 4180.
(D) Registry Functions Activity Report. Within eighteen (18) months of the Effective Date of the Agreement, Registry Operator shall provide a Registry Functions Activity Report. This report shall be compiled in a comma separated-value formatted file as specified in RFC 4180. The file shall be named "gTLD-activity-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:
Field # | Field Name | Description |
---|---|---|
01 | operational-registrars | number of operational registrars at the end of the reporting period |
02 | ramp-up-registrars | number of registrars that have received a password for access to OT&E at the end of the reporting period |
03 | pre-ramp-up-registrars | number of registrars that have requested access, but have not yet entered the ramp-up period at the end of the reporting period |
04 | zfa-passwords | number of active zone file access passwords at the end of the reporting period |
05 | whois-43-queries | number of WHOIS (port-43) queries responded during the reporting period |
06 | web-whois-queries | number of Web-based Whois queries responded during the reporting period, not including searchable Whois |
07 | searchable-whois-queries | number of searchable Whois queries responded during the reporting period, if offered |
08 | dns-udp-queries-received | number of DNS queries received over UDP transport during the reporting period |
09 | dns-udp-queries-responded | number of DNS queries received over UDP transport that were responded during the reporting period |
10 | dns-tcp-queries-received | number of DNS queries received over TCP transport during the reporting period |
11 | dns-tcp-queries-responded | number of DNS queries received over TCP transport that were responded during the reporting period |
12 | srs-dom-check | number of SRS (EPP and any other interface) domain name "check" requests responded during the reporting period |
13 | srs-dom-create | number of SRS (EPP and any other interface) domain name "create" requests responded during the reporting period |
14 | srs-dom-delete | number of SRS (EPP and any other interface) domain name "delete" requests responded during the reporting period |
15 | srs-dom-info | number of SRS (EPP and any other interface) domain name "info" requests responded during the reporting period |
16 | srs-dom-renew | number of SRS (EPP and any other interface) domain name "renew" requests responded during the reporting period |
17 | srs-dom-rgp-restore-request | number of SRS (EPP and any other interface) domain name RGP "restore" requests responded during the reporting period |
18 | srs-dom-rgp-restore-report | number of SRS (EPP and any other interface) domain name RGP "restore" requests delivering a restore report responded during the reporting period |
19 | srs-dom-transfer-approve | number of SRS (EPP and any other interface) domain name "transfer" requests to approve transfers responded during the reporting period |
20 | srs-dom-transfer-cancel | number of SRS (EPP and any other interface) domain name "transfer" requests to cancel transfers responded during the reporting period |
21 | srs-dom-transfer-query | number of SRS (EPP and any other interface) domain name "transfer" requests to query about a transfer responded during the reporting period |
22 | srs-dom-transfer-reject | number of SRS (EPP and any other interface) domain name "transfer" requests to reject transfers responded during the reporting period |
23 | srs-dom-transfer-request | number of SRS (EPP and any other interface) domain name "transfer" requests to request transfers responded during the reporting period |
24 | srs-dom-update | number of SRS (EPP and any other interface) domain name "update" requests (not including RGP restore requests) responded during the reporting period |
25 | srs-host-check | number of SRS (EPP and any other interface) host "check" requests responded during the reporting period |
26 | srs-host-create | number of SRS (EPP and any other interface) host "create" requests responded during the reporting period |
27 | srs-host-delete | number of SRS (EPP and any other interface) host "delete" requests responded during the reporting period |
28 | srs-host-info | number of SRS (EPP and any other interface) host "info" requests responded during the reporting period |
29 | srs-host-update | number of SRS (EPP and any other interface) host "update" requests responded during the reporting period |
30 | srs-cont-check | number of SRS (EPP and any other interface) contact "check" requests responded during the reporting period |
31 | srs-cont-create | number of SRS (EPP and any other interface) contact "create" requests responded during the reporting period |
32 | srs-cont-delete | number of SRS (EPP and any other interface) contact "delete" requests responded during the reporting period |
33 | srs-cont-info | number of SRS (EPP and any other interface) contact "info" requests responded during the reporting period |
34 | srs-cont-transfer-approve | number of SRS (EPP and any other interface) contact "transfer" requests to approve transfers responded during the reporting period |
35 | srs-cont-transfer-cancel | number of SRS (EPP and any other interface) contact "transfer" requests to cancel transfers responded during the reporting period |
36 | srs-cont-transfer-query | number of SRS (EPP and any other interface) contact "transfer" requests to query about a transfer responded during the reporting period |
37 | srs-cont-transfer-reject | number of SRS (EPP and any other interface) contact "transfer" requests to reject transfers responded during the reporting period |
38 | srs-cont-transfer- request | number of SRS (EPP and any other interface) contact "transfer" requests to request transfers responded during the reporting period |
39 | srs-cont-update | number of SRS (EPP and any other interface) contact "update" requests responded during the reporting period |
The first line shall include the field names exactly as described in the table above as a "header line" as described in section 2 of RFC 4180. No other lines besides the ones described above shall be included. Line breaks shall be <U+000D, U+000A> as described in RFC 4180.