Guides

get_registrant_verification_status

When a domain is registered or transferred, or when the registrant contact information is changed, the registrant must reply to an email requesting them to confirm that the submitted contact information is correct. This command returns the current state of the verification request.

Suggest Edits

Request parameters

Standard request parameters

  • action = get_registrant_verification_status
  • object = domain

Request attributes

ParameterObligationDefinition/Value
domainRequiredThe domain name to retrieve the registrant verification status for.

Response parameters

Standard response parameters

  • action = reply
  • object = domain
  • is_success = Boolean indicating success or failure of the request.
  • response_code = Response code indicating outcome of the request.
  • response_text = Message describing the outcome of the request.

Response attributes

Parameters within the attributes associative array are described below:

ParameterObligationDefinition/Value
registrant_verification_statusAlways returnedThe current status of the verification.

Allowed values are:

admin_reviewing—The registrant data has been submitted and is being validated manually by the Tucows Compliance team.
pending—The verification process has been initiated, and the verification email will be sent.
suspended—The registrant has failed verification and the domain has been suspended.
verified—The registrant has been validated.
verifying—The verification process has been initiated and is waiting for registrant response.
unverified—The verification process has not been initiated.
verification_deadlineReturned for unverified domainsThe date by which the domain will be suspended.
days_to_suspendReturned for unverified domainsThe number of days remaining until the domain is suspended if the registrant information is not validated. If the domain has already been suspended, this value will be a negative number.
email_bouncedReturned for unverified domainsReturns 1, if the verification email was triggered because the WDRP or the renewal notice bounced.

Example

<?xml version='1.0' encoding='UTF-8' standalone='no'?>
<!DOCTYPE OPS_envelope SYSTEM 'ops.dtd'>
<OPS_envelope>
    <header>
        <version>0.9</version>
    </header>
    <body>
        <data_block>
            <dt_assoc>
                <item key="protocol">XCP</item>
                <item key="action">get_registrant_verification_status</item>
                <item key="object">domain</item>
                <item key="attributes">
                    <dt_assoc>
                        <item key="domain">example.com</item>
                    </dt_assoc>
                </item>
            </dt_assoc>
        </data_block>
    </body>
</OPS_envelope>

<?xml version='1.0' encoding="UTF-8" standalone="no"?>
<!DOCTYPE OPS_envelope SYSTEM "ops.dtd">
<OPS_envelope>
    <header>
        <version>0.9</version>
    </header>
    <body>
        <data_block>
            <dt_assoc>
                <item key="protocol">XCP</item>
                <item key="action">REPLY</item>
                <item key="object">DOMAIN</item>
                <item key="response_code">200</item>
                <item key="is_success">1</item>
                <item key="response_text">Command Successful</item>
                <item key="attributes">
                    <dt_assoc>
                        <item key="registrant_verification_status">suspended</item>
                        <item key="verification_deadline">2013-11-02
                            00:00:00</item>
                        <item key="email_bounced">1</item>
                        <item key="days_to_suspend">2</item>
                    </dt_assoc>
                </item>
            </dt_assoc>
        </data_block>
    </body>
</OPS_envelope>

Updated 3 months ago