Generic Top-Level Domain (gTLD) Registry Agreements

gTLD Registry Agreements establish the rights, duties, liabilities, and obligations ICANN requires of registry operators to run gTLDs.

.PRO Agreement Appendix 4 | Registry Operator's Monthly Report

.PRO Agreement Appendix 4 | Registry Operator's Monthly Report
ICANN Logo .PRO Agreement Appendix 4
Registry Operator's Monthly Report

(22 April 2010)

(A) Monthly Report. Registry Operator shall provide a monthly report per TLD to registry-reports@icann.org with the following content. ICANN may request in the future that the report be delivered by other means. The file shall be named “pro-yyyymm.pdf”; where “yyyymm” is the year and month being reported. File shall be in Portable Document Format (PDF). ICANN will 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.

1. 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).

2. Service Level Agreement Performance. Compare Service Level Requirements as listed in Section 6(A)4.2 — Service Definition and Service Level Requirement of Appendix 7, with actual performance measures for the reporting month.

3. TLD Zone File Access Activity. State the total number of zone file access passwords at end of the reporting month.

4. Completed System Software Releases. Describe significant releases during the reporting month, including release name, features, and completion date.

5. Whois Service Activity. State the number of Whois queries during the reporting month.

6. 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.

7. 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 Transactions monthly Report. This report shall be transmitted to ICANN electronically to registry-reports@icann.org in a comma separated-value (CSV) formatted file as specified in RFC 4180. ICANN may request in the future that the report be delivered by other means. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three months after the end of the month to which the reports relate.

The file shall be named “pro-transactions-yyyymm.csv”; where “yyyymm” is the year and month being reported. The file shall contain 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 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 etc.
09 net-adds-5-yr " "
10 net-adds-6-yr " "
11 net-adds-7-yr " "
12 net-adds-8-yr " "
13 net-adds-9-yr " "
14 net-adds-10-yr " "
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 etc.
19 net-renews-5-yr " "
20 net-renews-6-yr " "
21 net-renews-7-yr " "
22 net-renews-8-yr " "
23 net-renews-9-yr " "
24 net-renews-10-yr " "
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 domain names 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-names total number of names affected by granted AGP (add grace period) exemption requests

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. No other lines besides the ones described above shall be included. Line breaks shall be “CRLF” as described in RFC 4180.