In the 2009 RAA and 2013 RAA, presence of a Registrant, Admin and a Tech postal address is required.
1. Is there presence of a postal address?
(i.e., field is not blank)
a. Registrant, b. Tech, and c. Admin postal address
Yes - Pass
No – Fail
2. Is there presence of a country?
a. Registrant, b. Tech, and c. Admin postal address
Yes – Pass
No – Fail
3. Is the country identifiable?
(i.e., full country name or an ISO 3166-1 abbreviation)
a. Registrant, b. Tech, and c. Admin postal address
Yes – Pass
No – Fail
4. Is the country provided in the Country field?
a. Registrant, b. Tech, and c. Admin postal address
Yes – Pass
No – Fail: 2013 RAA || Pass: 2009 RAA
5. Is the country syntactically valid?
(i.e., meets ISO 3166-1: Alpha 2-code format)
a. Registrant, b. Tech, and c. Admin postal address
Yes – Pass
No – Fail: 2013 RAA || Pass: 2009 RAA
IDENTIFIER – Does the country use a postal code system?
a. Registrant, b. Tech, and c. Admin postal address
Yes – Proceed to additional postal code validation
No – Appropriately left blank, move to next field (i.e., Test 9)
6. Is there presence of a postal code?
a. Registrant, b. Tech, and c. Admin postal address
Yes – Pass
No – Fail
7. Is the postal code in the Postal Code field?
a. Registrant, b. Tech, and c. Admin postal address
Yes – Pass
No – Fail: 2013 RAA || Pass: 2009 RAA
8. Is the Postal Code syntactically valid based on the country?
(i.e., format of postal code meets length, alpha/numeric formats of country)
a. Registrant, b. Tech, and c. Admin postal address
Yes – Pass
No – Fail
IDENTIFIER – Does the country require states/provinces in its addressing system?
a. Registrant, b. Tech, and c. Admin postal address
Yes – Proceed to additional State/Provide validation
No – Appropriately left blank, move to next field (i.e., Test 13)
9. Is there presence of a state/province?
a. Registrant, b. Tech, and c. Admin postal address
Yes – Pass
No – Fail
10. Is the state/province in the State/Province field?
a. Registrant, b. Tech, and c. Admin postal address
Yes – Pass
No – Fail: 2013 RAA || Pass: 2009 RAA
11. Is the State/Province syntactically valid?
(i.e., full name or abbreviation depending on country addressing system)
a. Registrant, b. Tech, and c. Admin postal address
Yes – Pass
No – Fail: 2013 RAA || Pass: 2009 RAA
12. Is there presence of a city?
a. Registrant, b. Tech, and c. Admin postal address
Yes – Pass
No – Fail
13. Is the city in the City field?
a. Registrant, b. Tech, and c. Admin postal address
Yes – Pass
No – Fail: 2013 RAA || Pass: 2009 RAA
14. Is there presence of a street?
a. Registrant, b. Tech, and c. Admin postal address
Yes – Pass
No – Fail
15. Is the street in the Street field?
a. Registrant, b. Tech, and c. Admin postal address
Yes – Pass
No – Fail: 2013 RAA || Pass: 2009 RAA
All postal addresses will be subjected to both syntax and operability testing. Operability testing is mostly automated through the use of a tool employed by ICANN’s postal address validation vendor. No mail will be sent as part of the testing.
Note: There is no difference between 2009 and 2013 RAA verification requirements. All records will be given the same tests.
The validation vendor attempts to verify the deliverability of the address automatically via the tool.
A “Yes” for Stage One will be considered a “Pass” for Operability (i.e., deliverable). A “No” for Stage One will trigger either a “Fail” or a follow-on testing scenario.
1. Is the tool able to automatically verify deliverability?
The Operability Test in Manual Stage (A) is performed on all contact fields that attained a "Possible Fail (A)" from the Automated Stage above. Here the validation vendor conducts manual testing of the given address using its own complementary data on the given country to determine if the address is likely to be deliverable.
A “Yes” response for Manual Stage (A) will be considered a “Pass” for Operability (i.e., deliverable). A “No” for Manual Stage (A) will be considered “Indeterminate” for Operability (i.e., unable to verify automatically or manually the address deliverabilityB
1. Based on the validation vendor’s manual check of the address, is the address likely deliverable?
The Operability Test in Manual Stage (B) is performed on all contact fields that attained a "Possible Fail (B)" from the Automated Stage above. Here the validation vendor checks the available reference data for the given address components to determine if the address is likely to be deliverable. Two components state/province (if applicable) and city, are essential to the validation vendor’s ability to complete this test; in the absence of these two components, an address will not be considered deliverable.
A “Yes” response to all three criteria for Manual Stage (B) will be considered a “Pass” for Operability (i.e., deliverable). A “No” response to at least one will be considered a “Fail” for Operability (i.e., not deliverable).
1. Is there presence of a city in the given address?
(i.e., field is not blank)
2. If Postal Address Syntax Identifier Test for State/Province = yes, is there presence of a state/province in the given address?
(i.e., field is not blank)
3. Based on the validation vendor’s manual check of the given address components, is the address likely to be deliverable?
To provide comments on WHOIS ARS or suggestions to improve WHOIS ARS reports and validation criteria, please email: globalsupport@icann.org.