Suche in diesem Bereich
Table of contents
Here the notifications are described that may occur in connection with an outgoing domain transfer.
n the case of an outgoing transfer, two scenarios can occur.
The transfer takes place without the involvement of the registrar, in which case it is processed and completed immediately.
In the second scenario, when the registrar is involved, the transfer is initiated immediately with corresponding real-time notifications.
During processing, after being processed by the registry, notifications are then made available for retrieval with a delay.
transfer_start
Description
The notification is sent at the start of an outgoing domain transfer.
Notification trigger
Another AutoDNS user or an external registrar starts an outgoing transfer for the domain.
Recipient of the notification
The recipient of the notification is the AutoDNS user, who currently holds the domain and to the person who wants to have the domain.
POLLING notification examples
JSON
{
"stid": "20220119-app3-dev-5016",
"status": {
"code": "S0905",
"text": "The notification was polled successfully.",
"type": "SUCCESS"
},
"object": {
"type": "Message",
"value": "1012054052",
"summary": 1
},
"data": [
{
"id": 1012054052,
"notify": {
"type": "transfer_start",
"object": {
"type": "Transfer",
"data": {
"gainingRegistrar": "greg",
"loosingRegistrar": "lreg",
"start": "2022-01-19T10:54:42.000+0100",
"reminder": "2022-01-22T10:54:42.000+0100",
"end": "2022-01-24T10:54:42.000+0100"
}
}
},
"object": {
"type": "Domain",
"value": "example.org",
"data": {
"name": "example.org"
}
}
}
]
}
XML
<response>
<result>
<data>
<summary>1</summary>
<message>
<id>1005360835</id>
<owner />
<notify>
<domain>
<name>example.com</name>
</domain>
<transfer>
<gaining_registrar>greg</gaining_registrar>
<loosing_registrar>lreg</loosing_registrar>
<start>2021-05-03 11:05:56</start>
<reminder>2021-05-06 11:05:56</reminder>
<autonack>2021-05-08 05:05:56</autonack>
<end>2021-05-08 11:05:56</end>
<owner>
<user>customer</user>
<context>4</context>
</owner>
<updater>
<user>customer</user>
<context>4</context>
</updater>
<id>83076</id>
<created>2021-05-03 11:05:56</created>
<updated>2021-05-03 11:05:56</updated>
</transfer>
<type>transfer_start</type>
<status>
<code>S1403</code>
<type>success</type>
</status>
<created>2021-05-03 11:06:14</created>
</notify>
<created>2021-05-03 11:06:14</created>
</message>
</data>
<status>
<code>S0905</code>
<text>The notification was polled successfully.</text>
<type>success</type>
<object>
<type>message</type>
<value>1005360835</value>
</object>
</status>
</result>
<stid>20210503-app3-dev-6872</stid>
</response>
PUSH notification examples
JSON
{
"id": 1012054076,
"notify": {
"type": "transfer_start",
"object": {
"type": "Transfer",
"data": {
"gainingRegistrar": "greg",
"loosingRegistrar": "lreg",
"start": "2022-01-19T11:42:56.000+0100",
"reminder": "2022-01-22T11:42:56.000+0100",
"end": "2022-01-24T11:42:56.000+0100"
}
}
},
"object": {
"type": "Domain",
"value": "example.com",
"data": {
"name": "example.com"
}
}
}
XML
<message>
<transfer>
<status>start</status>
</transfer>
<domain>
<name>example.com</name>
<domain_created>2016-11-21 10:36:58</domain_created>
<payable>2021-11-21 10:36:58</payable>
<ownerc>23202049</ownerc>
<adminc>23202049</adminc>
<techc>23202049</techc>
<zonec>23202049</zonec>
<nic_member_label>nml</nic_member_label>
<registry_status>ACTIVE</registry_status>
<nserver>
<name>ns1.example.com</name>
</nserver>
<nserver>
<name>ns2.example.com</name>
</nserver>
<period>1</period>
<action>TRANSFER_INTERN</action>
<use_privacy>false</use_privacy>
<authinfo>dQGP7ZVt5+kDc2BF</authinfo>
<autorenew>true</autorenew>
<extension />
<confirm_owner_consent>1</confirm_owner_consent>
<registrar_status>ACTIVE</registrar_status>
<use_privacy_plus>false</use_privacy_plus>
<rdds_opt_in>NOT_SET</rdds_opt_in>
<owner />
<updater />
<created>2019-11-21 10:36:58</created>
</domain>
<job>
<id>4309872175</id>
<object><![CDATA[example.com]]></object>
<status>RUNNING</status>
<execution>2021-05-03 12:48:05</execution>
<type>
<type>domain</type>
<sub_type>test</sub_type>
<action>transfer</action>
</type>
<created>2021-05-03 12:46:37</created>
<updated>2021-05-03 12:48:06</updated>
</job>
<status>
<code>S0104</code>
<type>notify</type>
<object>
<type>domain</type>
<value>example.com</value>
</object>
</status>
<id>1005360905</id>
<stid>20210503-app2-dev-16478</stid>
</message>
transfer_reminder
Description
This notification reminds the domain owner of an running outgoing transfer. It is sent automatically 3 days after the transfer start.
The reminder can be sent only once.
Notification trigger
Trigger 1: Internal transfer
The domain is transferred from the current AutoDNS user to another AutoDNS user. The transfer must have the status pending_notify.
Trigger 2: Transfer to another registrar
The domain is transferred from the current AutoDNS user to another registrar and thus leaves the InterNetX inventory.
The transfer must have the status pending_notify.
Recipient of the notification
The recipient of the notification is the AutoDNS user who currently holds the domain.
POLLING notification examples
JSON
{
"stid": "20211001-app3-dev-5562",
"status": {
"code": "S0905",
"text": "The notification was polled successfully.",
"type": "SUCCESS"
},
"object": {
"type": "Message",
"value": "1006189949",
"summary": 9
},
"data": [
{
"id": 1006189949,
"notify": {
"type": "transfer_reminder",
"object": {
"type": "Transfer",
"data": {
"gainingRegistrar": "greg",
"loosingRegistrar": "lreg",
"start": "2021-09-28T10:02:26.000+0200",
"reminder": "2021-10-01T10:02:26.000+0200",
"end": "2021-10-03T10:02:26.000+0200"
}
}
},
"object": {
"type": "Domain",
"value": "example.com",
"data": {
"name": "example.com"
}
}
}
]
}
XML
<response>
<result>
<data>
<summary>1</summary>
<message>
<id>1005362828</id>
<owner />
<notify>
<domain>
<name>example.com</name>
</domain>
<transfer>
<gaining_registrar>greg</gaining_registrar>
<loosing_registrar>lreg</loosing_registrar>
<start>2021-05-01 09:12:01</start>
<reminder>2021-05-04 10:00:22</reminder>
<autonack>2021-05-09 03:12:01</autonack>
<end>2021-05-09 09:12:01</end>
<owner>
<user>customer</user>
<context>4</context>
</owner>
<updater>
<user>customer</user>
<context>4</context>
</updater>
<id>83115</id>
<created>2021-05-03 09:12:01</created>
<updated>2021-05-04 10:11:26</updated>
</transfer>
<type>transfer_reminder</type>
<status>
<code>S1403006</code>
<type>success</type>
</status>
<created>2021-05-04 10:11:33</created>
</notify>
<created>2021-05-04 10:11:33</created>
</message>
</data>
<status>
<code>S0905</code>
<text>The notification was polled successfully.</text>
<type>success</type>
<object>
<type>message</type>
<value>1005362828</value>
</object>
</status>
</result>
<stid>20210504-app3-dev-7649</stid>
</response>
PUSH notification examples
JSON
{
"id": 1006190050,
"notify": {
"type": "transfer_reminder",
"object": {
"type": "Transfer",
"data": {
"gainingRegistrar": "greg",
"loosingRegistrar": "lregT",
"start": "2021-10-01T13:33:18.000+0200",
"reminder": "2021-10-01T14:08:00.000+0200",
"end": "2021-10-06T13:33:18.000+0200"
}
}
},
"object": {
"type": "Domain",
"value": "example.com",
"data": {
"name": "example.com"
}
}
}
XML
<message>
<domain>
<name>example.com</name>
<extension />
</domain>
<transfer>
<gaining_registrar>greg</gaining_registrar>
<loosing_registrar>lreg</loosing_registrar>
<start>2021-05-01 10:59:04</start>
<reminder>2021-05-04 11:08:30</reminder>
<autonack>2021-05-09 04:59:04</autonack>
<end>2021-05-09 10:59:04</end>
<owner>
<user>customerr</user>
<context>4</context>
</owner>
<updater>
<user>customer</user>
<context>4</context>
</updater>
<id>83116</id>
<created>2021-05-04 10:59:04</created>
<updated>2021-05-04 11:07:12</updated>
</transfer>
<type>transfer_reminder</type>
<status>
<code>S1403006</code>
<type>success</type>
</status>
<id>1005362832</id>
<created>2021-05-04 11:08:49</created>
</message>
transfer_autoack
Description
This notification automatically confirms an outgoing domain transfer (AutoAck).
Notification trigger
Trigger 1: Internal transfer of .de domains
The transfer of .de domains between two AutoDNS users (= internal transfer) triggers the notification.
Process
- The current domain holder enters a cancellation with PREACK. (PREACK = Pre-Acknowledgement, automatic approval of a future outgoing transfer).
- The new owner initiates the incoming transfer,
- The transfer_autoack notification is triggered
Trigger 2: Transfer of gTLD domains
The outbound transfer of .gTLD domains triggers the notification.
Process
- An outgoing transfer of a gTLD domain is successfully initiated. The AuthInfo must be valid and the domain must not be locked ("LOCK", "HOLD-LOCK").
- The current owner does not send an acknowledgement ("ACK").
- After 5 days an automatic acknowledgement is done and the system generates the transfer_autoack message
Recipient of the notification
In both cases, the recipient of the notification is the previous domain owner (AutoDNS user).
POLLING notification examples
JSON
{
"stid": "20220124-app2-test-6788",
"status": {
"code": "S0905",
"text": "The notification was polled successfully.",
"type": "SUCCESS"
},
"object": {
"type": "Message",
"value": "5406726",
"summary": 1
},
"data": [
{
"id": 5406726,
"notify": {
"type": "domain_away",
"object": {
"type": "Transfer",
"data": {
"gainingRegistrar": "greg",
"loosingRegistrar": "lreg",
"start": "2022-01-24T14:10:24.000+0100",
"reminder": "2022-01-24T14:10:24.000+0100",
"end": "2022-01-24T14:10:24.000+0100"
}
}
},
"object": {
"type": "Domain",
"value": "example.com",
"data": {
"name": "example.com"
}
}
}
]
}
XML
<response>
<result>
<data>
<summary>1</summary>
<message>
<id>5406716</id>
<owner />
<notify>
<domain>
<name>example.com</name>
</domain>
<transfer>
<status>ack</status>
<gaining_registrar>greg</gaining_registrar>
<loosing_registrar>lreg</loosing_registrar>
<start>2022-01-24 13:44:22</start>
<reminder>2022-01-24 13:44:22</reminder>
<autonack>2022-01-24 13:44:22</autonack>
<end>2022-01-24 13:44:22</end>
<owner>
<user>1351100001</user>
<context>4</context>
</owner>
<updater>
<user>root</user>
<context>1</context>
</updater>
<id>107749</id>
<created>2022-01-24 13:44:22</created>
<updated>2022-01-24 13:44:22</updated>
</transfer>
<answer>AUTOACK</answer>
<type>domain_away</type>
<msg>
<code>MSG010409</code>
<type>notice</type>
</msg>
<status>
<code>S0106</code>
<type>success</type>
</status>
<created>2022-01-24 13:44:53</created>
</notify>
<created>2022-01-24 13:44:53</created>
</message>
</data>
<status>
<code>S0905</code>
<text>The notification was polled successfully.</text>
<type>success</type>
<object>
<type>message</type>
<value>5406716</value>
</object>
</status>
</result>
<stid>20220124-app2-test-6555</stid>
</response>
PUSH notification examples
PUSH JSON Message
{
"id": 1005502016,
"job": {
"created": "2021-05-17T14:04:33.000+0200",
"updated": "2021-05-17T14:04:38.000+0200",
"status": "SUCCESS",
"execution": "2021-05-17T14:04:37.000+0200",
"action": "transfer_out_ack",
"subType": "VGRS-TEST_com",
"id": 4309936105
},
"ctid": "1621252989072",
"object": {
"type": "Transfer",
"value": "example.com",
"data": {
"owner": {
"context": 4,
"user": "normal_user"
},
"updater": {
"context": 4,
"user": "normal_user"
},
"autoAnswer": true,
"status": "ACK"
}
}
}
XML
<message>
<transfer>
<domain>example.com</domain>
<status>ack</status>
<gaining_registrar>greg</gaining_registrar>
<loosing_registrar>lreg</loosing_registrar>
<start>2021-05-17 14:24:43</start>
<end>2021-05-16 14:24:43</end>
<autoanswer>1</autoanswer>
</transfer>
<domain>
<name>example.com</name>
<domain_created>2021-01-10 09:15:37</domain_created>
<expire>2022-01-10 09:15:37</expire>
<payable>2022-01-10 09:15:37</payable>
<ownerc>23252437</ownerc>
<adminc>23252437</adminc>
<techc>23252437</techc>
<zonec>23252437</zonec>
<nic_member_label>greg</nic_member_label>
<registry_status>ACTIVE</registry_status>
<nserver>
<name>ns1.example.com</name>
</nserver>
<nserver>
<name>ns2.example.com</name>
</nserver>
<ip>1.2.3.4</ip>
<period>1</period>
<action>UPDATE</action>
<use_trustee>false</use_trustee>
<use_privacy>false</use_privacy>
<domainsafe>false</domainsafe>
<autorenew>true</autorenew>
<extension />
<registrar_status>ACTIVE</registrar_status>
<rdds_opt_in>NOT_SET</rdds_opt_in>
<owner>
<user>normal_user</user>
<context>4</context>
</owner>
<updater>
<user>normal_user</user>
<context>4</context>
</updater>
<created>2021-01-10 09:15:37</created>
<updated>2021-05-17 14:19:43</updated>
</domain>
<answer>ACK</answer>
<job>
<id>4309936108</id>
<object><![CDATA[example.com]]></object>
<status>SUCCESS</status>
<execution>2021-05-17 14:27:15</execution>
<type>
<type>domain</type>
<sub_type>greg</sub_type>
<action>transfer_out_ack</action>
</type>
<created>2021-05-17 14:27:12</created>
<updated>2021-05-17 14:27:18</updated>
</job>
<status>
<code>S0106</code>
<type>success</type>
<object>
<type>domain</type>
<value>example.com</value>
</object>
</status>
<id>1005502027</id>
<ctid>1621254283065</ctid>
</message>
transfer_autonack
Description
This notification is sent automatically when an outgoing domain transfer is rejected (AutoNack). The time of sending is after the transfer start notification and - if this was sent - the transfer reminder, but before the domain_away notification.
AutoNACK is not supported by all TLDs, e.g. not by gTLDs.
Notification trigger
The transfer was not approved within the consent period.
Recipient of the notification
The recipient of the notification is the AutoDNS user who has the domain in his inventory.
POLLING notification examples
JSON
{
"stid": "20210511-app3-dev-9624",
"status": {
"code": "S0905",
"text": "The notification was polled successfully.",
"type": "SUCCESS"
},
"object": {
"type": "Message",
"value": "1005456045",
"summary": 4
},
"data": [
{
"id": 1005456045,
"job": {
"created": "2021-05-11T14:14:21.000+0200",
"updated": "2021-05-11T14:14:27.000+0200",
"status": "SUCCESS",
"execution": "2021-05-11T14:14:25.000+0200",
"subType": "ME-TEST_me",
"action": "transfer_out_nack",
"id": 4309913877
},
"ctid": "1620734856068",
"object": {
"type": "Transfer",
"value": "exampledomain.me",
"data": {
"status": "NACK"
}
}
}
]
}
XML
<response>
<result>
<data>
<summary>1</summary>
<message>
<id>1005456045</id>
<owner>
<user>normal_user</user>
<context>4</context>
</owner>
<job>
<transfer>
<domain>example.me</domain>
<status>nack</status>
<gaining_registrar>greg</gaining_registrar>
<loosing_registrar>lreg</loosing_registrar>
<start>2021-05-11 14:11:00</start>
<end>2021-05-11 14:13:00</end>
<autoanswer>1</autoanswer>
</transfer>
<domain>
<name>example.me</name>
<domain_created>2021-05-04 12:37:04</domain_created>
<expire>2022-05-04 12:37:04</expire>
<payable>2022-05-04 12:35:02</payable>
<ownerc>23252437</ownerc>
<adminc>23252437</adminc>
<techc>23252437</techc>
<zonec>23252437</zonec>
<nic_member_label>greg</nic_member_label>
<registry_status>ACTIVE</registry_status>
<nserver>
<name>ns1.example.com</name>
</nserver>
<nserver>
<name>ns2.example.com</name>
</nserver>
<ip>1.2.3.4</ip>
<period>1</period>
<use_trustee>false</use_trustee>
<use_privacy>false</use_privacy>
<domainsafe>false</domainsafe>
<autorenew>true</autorenew>
<registrar_status>ACTIVE</registrar_status>
<rdds_opt_in>NOT_SET</rdds_opt_in>
<owner>
<user>customer</user>
<context>4</context>
</owner>
<updater>
<user>customer</user>
<context>4</context>
</updater>
<created>2021-02-04 12:37:04</created>
<updated>2021-05-04 13:00:08</updated>
</domain>
<answer>NACK</answer>
<status>
<code>S0106</code>
<type>success</type>
<object>
<type>domain</type>
<value>example.me</value>
</object>
</status>
<id>4309913877</id>
<ctid>1620734856068</ctid>
</job>
<created>2021-05-11 14:14:27</created>
</message>
</data>
<status>
<code>S0905</code>
<text>The notification was polled successfully.</text>
<type>success</type>
<object>
<type>message</type>
<value>1005456045</value>
</object>
</status>
</result>
<stid>20210511-app2-dev-19375</stid>
</response>
PUSH notification examples
JSON
{
"id": 1005456996,
"job": {
"created": "2021-05-11T14:55:42.000+0200",
"updated": "2021-05-11T14:55:49.000+0200",
"status": "SUCCESS",
"execution": "2021-05-11T14:55:48.000+0200",
"subType": "ME-TEST_me",
"action": "transfer_out_nack",
"id": 4309914348
},
"ctid": "1620737585082",
"object": {
"type": "Transfer",
"value": "exampledomain.me",
"data": {
"status": "NACK"
}
}
}
XML
<message>
<transfer>
<domain>example.me</domain>
<status>nack</status>
<gaining_registrar>greg</gaining_registrar>
<loosing_registrar>lreg</loosing_registrar>
<start>2021-05-11 14:27:00</start>
<end>2021-05-11 14:30:00</end>
<autoanswer>1</autoanswer>
</transfer>
<domain>
<name>example.me</name>
<domain_created>2021-05-04 12:37:04</domain_created>
<expire>2022-05-04 12:37:04</expire>
<payable>2022-05-04 12:35:03</payable>
<ownerc>23252437</ownerc>
<adminc>23252437</adminc>
<techc>23252437</techc>
<zonec>23252437</zonec>
<nic_member_label>nml</nic_member_label>
<registry_status>ACTIVE</registry_status>
<nserver>
<name>ns1.example.com</name>
</nserver>
<nserver>
<name>ns2.example.com</name>
</nserver>
<ip>1.2.3.4</ip>
<period>1</period>
<action>UPDATE</action>
<use_trustee>false</use_trustee>
<use_privacy>false</use_privacy>
<domainsafe>false</domainsafe>
<autorenew>true</autorenew>
<extension />
<registrar_status>ACTIVE</registrar_status>
<rdds_opt_in>NOT_SET</rdds_opt_in>
<owner>
<user>normal_user</user>
<context>4</context>
</owner>
<updater>
<user>normal_user</user>
<context>4</context>
</updater>
<created>2021-02-04 12:37:04</created>
<updated>2021-05-04 13:00:08</updated>
</domain>
<answer>NACK</answer>
<job>
<id>4309914039</id>
<object><![CDATA[exampledomain.me]]></object>
<status>SUCCESS</status>
<execution>2021-05-11 14:29:35</execution>
<type>
<type>domain</type>
<sub_type>ME-TEST_me</sub_type>
<action>transfer_out_nack</action>
</type>
<created>2021-05-11 14:29:28</created>
<updated>2021-05-11 14:29:39</updated>
</job>
<status>
<code>S0106</code>
<type>success</type>
<object>
<type>domain</type>
<value>example.me</value>
</object>
</status>
<id>1005456375</id>
<ctid>1620735861402</ctid>
</message>
domain_away
Description
This notification is sent in some cases when a domain is removed from the inventory, e.g. in case of a domain transfer without the registrar's involvement.
Notification trigger
An outgoing transfer away from the current registrar (R1) to another registrar (R2)
Process
- the outgoing transfer is initiated with valid AuthInfo by another registrar (R2)
- the automatic transfer acknowledgement is done (auto_ack)
- the domain_away notification is sent to the AutoDNS user who held the domain.
This case does not occur with an internal transfer because the registar does not change.
Recipient of the notification
The recipient of the notification is the AutoDNS user who held the domain.
POLLING notification examples
JSON
{
"stid": "20211001-app2-dev-113619",
"status": {
"code": "S0905",
"text": "The notification was polled successfully.",
"type": "SUCCESS"
},
"object": {
"type": "Message",
"value": "1006190079",
"summary": 1
},
"data": [
{
"id": 1006190079,
"notify": {
"type": "domain_away",
"object": {
"type": "Transfer",
"data": {
"gainingRegistrar": "greg",
"loosingRegistrar": "lregT",
"start": "2021-10-01T15:08:49.000+0200",
"end": "2021-10-01T15:08:49.000+0200"
}
}
},
"object": {
"type": "Domain",
"value": "example.com",
"data": {
"name": "example.com"
}
}
}
]
}
XML
<response>
<result>
<data>
<summary>1</summary>
<message>
<id>1005363286</id>
<owner />
<notify>
<domain>
<name>example.com</name>
</domain>
<transfer>
<status>ack</status>
<gaining_registrar>greg</gaining_registrar>
<loosing_registrar>lreg</loosing_registrar>
<start>2021-05-04 16:27:36</start>
<end>2021-05-04 16:27:36</end>
<owner>
<user>customer</user>
<context>4</context>
</owner>
<updater>
<user>customer</user>
<context>4</context>
</updater>
<id>83120</id>
<created>2021-05-04 16:27:36</created>
<updated>2021-05-04 16:27:36</updated>
</transfer>
<answer>AUTOACK</answer>
<type>domain_away</type>
<msg>
<code>MSG010409</code>
<type>notice</type>
</msg>
<status>
<code>S0106</code>
<type>success</type>
</status>
<created>2021-05-04 16:27:38</created>
</notify>
<created>2021-05-04 16:27:38</created>
</message>
</data>
<status>
<code>S0905</code>
<text>The notification was polled successfully.</text>
<type>success</type>
<object>
<type>message</type>
<value>1005363286</value>
</object>
</status>
</result>
<stid>20210504-app3-dev-11243</stid>
</response>
PUSH notification examples
JSON
{
"id": 1006190069,
"notify": {
"type": "domain_away",
"object": {
"type": "Transfer",
"data": {
"gainingRegistrar": "greg",
"loosingRegistrar": "lreg",
"start": "2021-10-01T15:02:42.000+0200",
"end": "2021-10-01T15:02:42.000+0200"
}
}
},
"object": {
"type": "Domain",
"value": "example.com",
"data": {
"name": "example.com"
}
}
}
XML
<message>
<domain>
<name>example.com</name>
<extension />
</domain>
<transfer>
<status>ack</status>
<gaining_registrar>greg</gaining_registrar>
<loosing_registrar>lreg</loosing_registrar>
<start>2021-05-04 16:34:55</start>
<end>2021-05-04 16:34:55</end>
<owner>
<user>customer</user>
<context>4</context>
</owner>
<updater>
<user>customer</user>
<context>4</context>
</updater>
<id>83122</id>
<created>2021-05-04 16:34:55</created>
<updated>2021-05-04 16:34:55</updated>
</transfer>
<answer>AUTOACK</answer>
<type>domain_away</type>
<msg>
<code>MSG010409</code>
<type>notice</type>
</msg>
<status>
<code>S0106</code>
<type>success</type>
</status>
<id>1005363304</id>
<created>2021-05-04 16:34:57</created>
</message>
Overview
Content Tools