Compliance Code: ‐46600 ‐ Notice of EPP Status Codes

Section 2.6.3 of the 2024 ICANN RDAP Response Profile requires servers provide an RDAP notice with a link to the EPP Status Codes:

2.6.3. A domain name RDAP response MUST contain a notices member with a title “Status Codes”, a description containing the string “For more information on domain status codes, please visit https://icann.org/epp” and a links member with the https://icann.org/epp URL in the href, rel:glossary, and a value with the RDAP lookup path that generated the RDAP response.

NOTE: This is section 2.6.3 of the 2019 Profile.

Here is an example of the notice, which is one of the JSON objects inside the "notices" array that MUST only appear at the top-most JSON of the RDAP response:

{
  "title": "Status Codes",
  "description": [
    "“For more information on domain status codes, please visit https://icann.org/epp"
  ],
  "links": [
    {
      "value": "https://some-value.example",
      "rel": "glossary",
      "href": "https://icann.org/epp",
      "type": "text/html"
    }
  ]
}

The "type" attribute is not required to be set, but if set it should match the media type of the value used in "href", which is "text/html" for "https://icann.org/epp". Setting this attribute is good practice.

The "value" attribute

The "value" attribute must be the request URL of the RDAP query. For example, if the RDAP query used "https://rdap.example/domain/foo.example" to query for a domain where this notice is found, then the "value" attribute must be "https://rdap.example/domain/foo.example".

The "rel" attribute

The value of the "rel" attribute must be "glossary". Values of "alternate" or "about" will trigger a compliance issue.

Using www.icann.org

While using the URL of "https://www.icann.org/epp" in either the "href" attribute or the link description will lead user to the right page, the conformance tool strictly checks for the usage of "https://icann.org/epp" (notice the lack of "www.").