By submitting any personal data, I agree that any the personal data will be processed in accordance with the ICANN Privacy Policy, and agree to abide by the website Terms of Service.

You are here

WHOIS ARS Contractual Compliance Metrics

ICANN’s Contractual Compliance team supports the WHOIS Accuracy Reporting System (ARS) effort by receiving reports of identified syntax and operational failures and following up with contracted parties to resolve areas of noncompliance. The team relies on several methods to accomplish this, including WHOIS inaccuracy complaints, WHOIS format complaints and targeted outreach to contracted parties. These complaints are processed in addition to community-submitted WHOIS complaints. Below are ICANN Contractual Compliance’s metrics for each phase and cycle of WHOIS ARS complaint processing.

ICANN reviews data gathered from the complaints it processes during each WHOIS ARS cycle to ensure the accuracy of WHOIS ARS data sampling and to improve the processing of WHOIS ARS complaints. Additionally, ICANN is engaged in continuous improvement efforts for processing WHOIS records. These efforts include implementing new WHOIS ARS testing methods and gathering feedback from contracted parties and ICANN’s Contractual Compliance team.

The process of reviewing and reporting WHOIS ARS test results is time consuming such that it takes anywhere from four to five months before ICANN Contractual Compliance can begin processing the WHOIS ARS.  This lag can result in outdated WHOIS ARS test results. However, with each new WHOIS ARS test cycle, the WHOIS ARS and ICANN Contractual Compliance teams are working to reduce this lag time. 

To contact ICANN Contractual Compliance, please email: compliance@icann.org. For more information about WHOIS inaccuracies or to file a WHOIS inaccuracy complaint, please see: https://www.icann.org/resources/pages/inaccuracy-2013-03-22-en.

 

ICANN Contractual Compliance Follow-Up Statistics:

Phase 1

ICANN Contractual Compliance Metrics for WHOIS ARS Phase 1
(Data as of 1 October 2017)

This Phase tested Syntax (the format of a record) only.

NOTE: Ticket count may not add up to total tickets created as a ticket may reach mulitple notice stages. Due to rounding and tickets being closed with multiple closure reasons, percentages may not always appear to add up to 100%.

For more about the ICANN Contractual Compliance Approach & Process, please see https://www.icann.org/resources/pages/approach-processes-2012-02-25-en.

 

Ticket Processing Summary & Breakdown by Process Step

  Total tickets created    3,703
  Total tickets closed    3,703
        Tickets closed before 1st notice    2,309
        Tickets closed after at least one notice    1,394
  Tickets in process as of 1 October 2017    0

 

Closure Reason for Tickets Closed Before 1st Notice

  WHOIS data when ticket processed different from sampled WHOIS data    53.6%
  Domain not registered when ticket processed    24.2%
  Domain suspended when ticket processed    10.4%
  Duplicate pending complaint when ticket processed    8.7%
  Ticket lacked sufficient information to process    2.4%
  Other (each closure reason representing less than 0.5% of cases)    0.8%

 

Closure Reasons for Tickets Closed After at Least One Notice

  Domain suspended    58.7%
  Registrar changed or updated WHOIS data    27.2%
  Registrar corrected WHOIS format    5.8%
  Registrar verified that sampled WHOIS data is correct    4.6%
  Registrar remediated issue    1.5%
  WHOIS data when ticket processed different from sampled WHOIS data    1.4%
  Other (each closure reason representing less than 0.5% of cases)    0.7%

 

Phase 2 Cycle 1

ICANN Contractual Compliance Metrics for WHOIS ARS Phase 2 Cycle 1
(Data as of 1 October 2017)

This Phase tested Syntax (the format of a record) and Operability (functionality of the information in a record).

NOTE: Ticket count may not add up to total tickets created as a ticket may reach mulitple notice stages. Due to rounding and tickets being closed with multiple closure reasons, percentages may not always appear to add up to 100%

Four registrars received a Notice of Breach for tickets created during Phase 2, Cycle 1. Of the four, one registrar was suspended then terminated.

For more about the ICANN Contractual Compliance Approach & Process, please see https://www.icann.org/resources/pages/approach-processes-2012-02-25-en

 

Ticket Processing Summary & Breakdown by Process Step

  Total tickets created    2,688
  Total tickets closed    2,688
        Tickets closed before 1st notice    1,324
        Tickets closed after at least one notice    1,364
  Tickets in process as of 1 October 2017    0 

 

Closure Reason for Tickets Closed Before 1st Notice

  WHOIS data when ticket processed different from sampled WHOIS data    40.9%
  Domain not registered when ticket processed    30.4%
  Domain suspended when ticket processed    16.4%
  WHOIS format issue identified for 2013 Grandfathered Domain    5.6%
  Registrar verified that sampled WHOIS data is correct    5.1%
  Registrar changed or updated WHOIS data    1.0%
  Known Privacy/Proxy service    0.5%
  Other (each closure reason representing less than 0.5% of cases)    0.1%

 

Closure Reasons for Tickets Closed After at Least One Notice

  Domain suspended    60.1%
  Registrar changed or updated WHOIS data    28.2%
  Registrar verified that sampled WHOIS data is correct    6.6%
  WHOIS data when ticket processed different from sampled WHOIS data    2.1%
  Registrar corrected WHOIS format    1.7%
  Domain not registered when ticket processed    0.7%
  Other (each closure reason representing less than 0.5% of cases)    0.6%

Phase 2 Cycle 2

ICANN Contractual Compliance Metrics for WHOIS ARS Phase 2 Cycle 2
(Data as of 1 October 2017)

This Phase tested Syntax (the format of a record) and Operability (functionality of the information in a record).

NOTE: Ticket count may not add up to total tickets created as a ticket may reach mulitple notice stages. Due to rounding and tickets being closed with multiple closure reasons, percentages may not always appear to add up to 100%.

For more about the ICANN Contractual Compliance Approach & Process, please see https://www.icann.org/resources/pages/approach-processes-2012-02-25-en

 

Ticket Processing Summary & Breakdown by Process Step

  Total tickets created    4,001
  Total tickets closed    4,001
        Tickets closed before 1st notice    2,481
        Tickets closed after at least one notice    1,520
  Tickets in process as of 1 October 2017    0

 

Closure Reason for Tickets Closed Before 1st Notice

  WHOIS data when ticket processed different from sampled WHOIS data    59.7%
  Domain suspended when ticket processed    13.6%
  Domain not registered when ticket processed    12.5%
  WHOIS format issue identified for 2013 Grandfathered Domain    9.9%
  Known Privacy/Proxy service    3.1%
  Registrar previously verified/corrected WHOIS inaccuracy    0.9%
  Ticket lacked sufficient information to process    0.6%
  Other (each closure reason representing less than 0.5% of cases)    0.6%

 

Closure Reasons for Tickets Closed After at Least One Notice

  Domain suspended    60.6%
  WHOIS data changed or updated    25.4%
  Registrar corrected WHOIS format    6.1%
  Registrar verified that sampled WHOIS data is correct    4.9%
  WHOIS data when ticket processed different from sampled WHOIS data    1.2%
  Other (each closure reason representing less than 0.5% of cases)    1.8%

Phase 2 Cycle 3

ICANN Contractual Compliance Metrics for WHOIS ARS Phase 2 Cycle 3
(Data as of 1 October 2017)

This Phase tested Syntax (the format of a record) and Operability (functionality of the information in a record).

NOTE: Ticket count may not add up to total tickets created as a ticket may reach mulitple notice stages. Due to rounding and tickets being closed with multiple closure reasons, percentages may not always appear to add up to 100%.

For more about the ICANN Contractual Compliance Approach & Process, please see https://www.icann.org/resources/pages/approach-processes-2012-02-25-en

 

Ticket Processing Summary & Breakdown by Process Step

  Total tickets created    4,552
  Total tickets closed    4,552
        Tickets closed before 1st notice     2,662
        Tickets closed after at least one notice     1,890
  Tickets in process as of 1 October 2017    0

 

Closure Reason for Tickets Closed Before 1st Notice

  WHOIS data when ticket processed different from sampled WHOIS data    60.1%
  WHOIS format issue identified for 2013 Grandfathered Domain    14.3%
  Domain suspended when ticket processed    7.9%
  Domain not registered when ticket processed    7.7%
  Known Privacy/Proxy service    6.3%
  Duplicate WHOIS compliant already pending     3.8%
  Other (each closure reason representing less than 0.5% of cases)    0.4%

 

Closure Reasons for Tickets Closed After at Least One Notice

  Domain suspended     65.0%
  WHOIS data changed or updated    21.5%
  Registrar corrected WHOIS format    7.2%
  Registrar verified that sampled WHOIS data is correct    3.9%
  WHOIS data when ticket processed different from sampled WHOIS data    0.9%
  Registrar demonstrated compliance with RAA    0.7%
  Registry or Registrar remediated issue    0.5%
  Other (each closure reason representing less than 0.5% of cases)    0.6%

Phase 2 Cycle 4

ICANN Contractual Compliance Metrics for WHOIS ARS Phase 2 Cycle 4
(Data as of 1 April 2018)

This Phase tested Syntax (the format of a record) and Operability (functionality of the information in a record).

NOTE: Ticket count may not add up to total tickets created as a ticket may reach mulitple notice stages. Due to rounding and tickets being closed with multiple closure reasons, percentages may not always appear to add up to 100%.

For more about the ICANN Contractual Compliance Approach & Process, please see https://www.icann.org/resources/pages/approach-processes-2012-02-25-en

 

Ticket Processing Summary & Breakdown by Process Step

  Total tickets created    4,681
  Total tickets closed    4681
        Tickets closed before 1st notice    2,669
        Tickets closed after at least one notice    2,012
  Tickets in process as of 1 April 2018    0

 

Closure Reason for Tickets Closed Before 1st Notice

  WHOIS data when ticket processed different from sampled WHOIS data    49.7%
  Domain not registered when ticket processed    18.2%
  WHOIS format issue identified for 2013 Grandfathered Domain    13.3%
  Domain suspended when ticket processed    11.8%
  Known Privacy/Proxy service     7.0%
  Other (each closure reason representing less than 0.5% of cases)     0.3%

 

Closure Reasons for Tickets Closed After at Least One Notice

  Domain suspended    69.5%
  WHOIS data changed or updated    16.3%
  Registrar corrected WHOIS format     6.0%
  Registrar verified that sampled WHOIS data is correct     5.9%
  Registrar demonstrated compliance with RAA     0.9%
  Other (each closure reason representing less than 0.5% of cases)     1.3%

Phase 2 Cycle 5

ICANN Contractual Compliance Metrics for WHOIS ARS Phase 2 Cycle 5
(Data as of 1 October 2018)

This Phase tested Syntax (the format of a record) and Operability (functionality of the information in a record).

NOTE: Ticket count may not add up to total tickets created as a ticket may reach mulitple notice stages. Due to rounding and tickets being closed with multiple closure reasons, percentages may not always appear to add up to 100%.

For more about the ICANN Contractual Compliance Approach & Process, please see https://www.icann.org/resources/pages/approach-processes-2012-02-25-en

 

Ticket Processing Summary & Breakdown by Process Step

  Total tickets created    4,639
  Total tickets closed    3,088
        Tickets closed before 1st notice    2,150
        Tickets closed after at least one notice    938
  Tickets in process as of 1 October 2018    1,550

 

Closure Reason for Tickets Closed Before 1st Notice

  WHOIS data when ticket processed different from sampled WHOIS data    56.9%
  Domain not registered when ticket processed    24.4%
  Domain suspended when ticket processed    10.2%
  Known Privacy/Proxy service     7.2%
  WHOIS format issue identified for 2013 Grandfathered Domain     1.2%
  Other (each closure reason representing less than 0.5% of cases)     0.2%

 

Closure Reasons for Tickets Closed After at Least One Notice

  Domain suspended    79.7%
  WHOIS data changed / updated    12.2%
  Registrar verified that sampled WHOIS data is correct     5.5%
  Registrar corrected WHOIS format     1.5%
  Other (each closure reason representing less than 0.5% of cases)     1.1%

Phase 2 Cycle 6

ICANN Contractual Compliance Metrics for WHOIS ARS Phase 2 Cycle 6
(Data as of 1 October 2018)

This Phase tested Syntax (the format of a record) and Operability (functionality of the information in a record).

NOTE: Ticket count may not add up to total tickets created as a ticket may reach mulitple notice stages. Due to rounding and tickets being closed with multiple closure reasons, percentages may not always appear to add up to 100%.

For more about the ICANN Contractual Compliance Approach & Process, please see https://www.icann.org/resources/pages/approach-processes-2012-02-25-en

 

Ticket Processing Summary & Breakdown by Process Step

  Total tickets created    5,600
  Total tickets closed    1,169
        Tickets closed before 1st notice    1,151
        Tickets closed after at least one notice    18
  Tickets in process as of 1 October 2018    4,431

 

Closure Reason for Tickets Closed Before 1st Notice

  Domain not registered when ticket processed    72.1%
  WHOIS data when ticket processed different from sampled WHOIS data    14.8%
  Domain suspended when ticket processed    12.9%
  Other (each closure reason representing less than 0.5% of cases)     0.3%

 

Closure Reasons for Tickets Closed After at Least One Notice

  Domain suspended    83.3%
  WHOIS data changed / updated    11.1%
  Registrar verified that sampled WHOIS data is correct     5.6%