Skip to main content
Resources

Security Response Waiver Request Metrics

The Security Response Waiver (SRW) service was established for gTLD registries to request a contractual waiver for actions it might take, or has taken, to mitigate or eliminate a present or imminent security incident to a gTLD and/or the DNS. A contractual waiver is an exemption from compliance with a specific provision of the Registry Agreement for the time period necessary to respond to the incident. The SRW has been designed to allow operational security to be maintained around an incident while keeping relevant parties (e.g., ICANN org, other affected providers) informed as appropriate.

In August 2021, ICANN org expanded the Expedited Registry Security Response (ERSR) service to enable registrars to submit waiver requests. As a result, the ERSR service was renamed the Security Response Waiver (SRW) service.

ID

Dataset Name

Dataset File

SRW

Security Response Waiver Request Metrics

srw_M1_M5.csv

Summary Analysis of SRW Requests

This section provides information on the outcomes of requests for Security Response Waivers (SRWs) for registry operators and registrars, including those previously referred to as Expedited Registry Security Requests (ERSRs). ICANN org will update the below data on an annual basis and will include registrar related data from 2021 onward.

ICANN org publishes the below metrics (M) by calendar year.

  • M1: Total number of requests received
  • M2: Number of generic top-level domains (gTLDs) covered by requests
  • M3: Approximate Number of Impacted Domains. *Note: These numbers do not include ongoing actions such as those taken by registry operators, registrars, law enforcement agencies, and closed court orders.
  • M4: Number of requests made in advance of action taken on the domain names vs. after action was taken on the domain names
  • M5: Outcome of the Request – (i) new waiver, (ii) update to an existing waiver, (iii) determination that the request is in scope of an existing waiver, or (iv) determination that a waiver will not be granted

SRW metrics are also available on the ICANN Open Data Platform at opendata.icann.org (registration required).

Domain Name System
Internationalized Domain Name ,IDN,"IDNs are domain names that include characters used in the local representation of languages that are not written with the twenty-six letters of the basic Latin alphabet ""a-z"". An IDN can contain Latin letters with diacritical marks, as required by many European languages, or may consist of characters from non-Latin scripts such as Arabic or Chinese. Many languages also use other types of digits than the European ""0-9"". The basic Latin alphabet together with the European-Arabic digits are, for the purpose of domain names, termed ""ASCII characters"" (ASCII = American Standard Code for Information Interchange). These are also included in the broader range of ""Unicode characters"" that provides the basis for IDNs. The ""hostname rule"" requires that all domain names of the type under consideration here are stored in the DNS using only the ASCII characters listed above, with the one further addition of the hyphen ""-"". The Unicode form of an IDN therefore requires special encoding before it is entered into the DNS. The following terminology is used when distinguishing between these forms: A domain name consists of a series of ""labels"" (separated by ""dots""). The ASCII form of an IDN label is termed an ""A-label"". All operations defined in the DNS protocol use A-labels exclusively. The Unicode form, which a user expects to be displayed, is termed a ""U-label"". The difference may be illustrated with the Hindi word for ""test"" — परीका — appearing here as a U-label would (in the Devanagari script). A special form of ""ASCII compatible encoding"" (abbreviated ACE) is applied to this to produce the corresponding A-label: xn--11b5bs1di. A domain name that only includes ASCII letters, digits, and hyphens is termed an ""LDH label"". Although the definitions of A-labels and LDH-labels overlap, a name consisting exclusively of LDH labels, such as""icann.org"" is not an IDN."