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.
Request parameters
Standard request parameters
- action = get_registrant_verification_status
- object = domain
Request attributes
| Parameter | Obligation | Definition/Value |
|---|---|---|
| domain | Required | The 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:
| Parameter | Obligation | Definition/Value |
|---|---|---|
| registrant_verification_status | Always returned | The 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. not_verified — The registrant has failed verification but the domain has not yet been suspended. 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_deadline | Returned for unverified domains | The date by which the domain will be suspended. |
| days_to_suspend | Returned for unverified domains | The 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_bounced | Returned for unverified domains | Returns 1, if the verification email was triggered because the WDRP or the renewal notice bounced. |
| notes_count | Optional | The count of notes, if any. Use the "get_notes" command to retrieve them. |
Note for .de domains (DENIC NIS2 verification)
.de domains are subject to DENIC's NIS2 risk-assessment process in addition to standard OpenSRS verification. DENIC may flag a registrant for re-verification of identity claims (name, address, etc.) and, if the deadlines pass, transition the domain to serverHold and ultimately delete it.
When DENIC verification data is available, the response attributes includes next fields:
| Parameter | Obligation | Definition/Value |
|---|---|---|
| denic_status | .de domains only | Reflects DENIC's own risk-assessment outcome. |
| denic_contact_handle | .de domains only | DENIC-issued contact handle of the registrant under verification (e.g. DENIC-20226-17155606). |
| denic_verification_claims | .de domains only | Semicolon-separated list of fields DENIC requires the registrant to verify (e.g. name;address;). |
| denic_deadline_dedelegation | .de domains only | Deadline before DENIC will set the domain to serverHold (de-delegate) if the registrant has not completed verification. Empty when domain is already in serverHold. |
| denic_deadline_deletion | .de domains only | Deadline before DENIC will delete the domain if the registrant has not completed verification. |
Examples
<?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.de</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">verifying</item>
<item key="email_bounced">0</item>
<item key="denic_status">verifying</item>
<item key="denic_contact_handle">DENIC-20226-17155606</item>
<item key="denic_verification_claims">name;address;</item>
<item key="denic_deadline_dedelegation">2026-06-10T14:51:30+02:00</item>
<item key="denic_deadline_deletion">2026-06-17T14:51:30+02:00</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">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><?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.id.au</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">2025-09-01 00:00:00</item>
<item key="email_bounced">0</item>
<item key="days_to_suspend">0</item>
<item key="notes_count">1</item>
</dt_assoc>
</item>
</dt_assoc>
</data_block>
</body>
</OPS_envelope>Updated 17 days ago