PDF version

EPP Notifications

.uk

This document outlines the notifications that are sent to a registrar when a change takes place which affects domain names or accounts on their tag.

 

 

Abuse notification

This notification is sent when we receive notification of abuse on a domain name on one of our feeds:

These notifications are sent on an opt-in basis only. The service can be subscribed to on our online service.  The notifications use the nom-abuse-feed-1.0 schema.

<epp:resData> element

The <epp:resData> element contains an <abuse-feed:infData> element that contains the following sub-elements:

  • <abuse-feed:key>
  • <abuse-feed:activity>
  • <abuse-feed:source>
  • <abuse-feed:hostname>
  • <abuse-feed:url>
  • <abuse-feed:date>
  • <abuse-feed:ip>
  • <abuse-feed:nameserver>
  • <abuse-feed:dnsAdmin>
  • <abuse-feed:target>
  • <abuse-feed:wholeDomain>

Example abuse feed notification

<?xml version="1.0" encoding="UTF-8" standalone="no"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="http://www.nominet.org.uk/epp/xml/epp-1.0
 epp-1.0.xsd">
  <response>
   <result code="1301">
    <msg>Command completed successfully; ack to dequeue</msg>
     </result>
      <msgQ count="10" id="12345">
       <qDate>2007-09-26T07:31:30</qDate>
        <msg>Domain Activity Notification</msg>
      </msgQ>
      <resData>
       <abuse-feed:infData
        xmlns:abuse-feed="http://www.nominet.org.uk/epp/xml/nom-abuse-feed-1.0"
        xsi:schemaLocation="http://www.nominet.org.uk/epp/xml/nom-abuse-feed-1.0
        nom-abuse-feed-1.0.xsd">
        <abuse-feed:key>phished.co.uk</abuse-feed:key>
        <abuse-feed:activity>phishing</abuse-feed:activity>
        <abuse-feed:source>Netcraft</abuse-feed:source>
        <abuse-feed:hostname>www.youve.been.phished.co.uk</abuse-feed:hostname>
        <abuse-feed:url>http://www.youve.been.phished.co.uk/give/us/your/money.htm</abuse-feed:url>
        <abuse-feed:date>2011-03-01T11:44:01</abuse-feed:date>
        <abuse-feed:ip>213.135.134.24</abuse-feed:ip>
        <abuse-feed:nameserver>ns0.crooked.dealings.net</abuse-feed:nameserver>
        <abuse-feed:dnsAdmin>hostmaster@crooked.dealings.net</abuse-feed:dnsAdmin>
        <abuse-feed:target>paypal</abuse-feed:target>
        <abuse-feed:wholeDomain>Y</abuse-feed:wholeDomain>
      </abuse-feed:infData>
     </resData>
     <trID>
      <clTRID>EPP-12345C-8BF-4CAA-A944-2F0EFCD37D9E</clTRID>
      <svTRID>1254234</svTRID>
     </trID>
    </response>
</epp>

 

Amend Account Details

This notification is generated when an account is modified by the registrant directly with us.

<epp:resData> element

The <resData> element contains a single <contact:infData> element which gives the details of the account after the change had been made.

Example of an Account Change Notification

<?xml version="1.0" encoding="UTF-8"?>
    <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
      epp-1.0.xsd">
      <response>
        <result code="1301">
          <msg>Command completed successfully; ack to dequeue</msg>
        </result>
        <msgQ count="4" id="123456">
          <qDate>2005-10-06T10:29:30Z</qDate>
          <msg>Account Details Change Notification</msg>
        </msgQ>
        <resData>
          <contact:infData
            xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"
            xsi:schemaLocation="urn:ietf:params:xml:ns:contact-1.0
            contact-1.0.xsd">
            <contact:id>CMyContactID</contact:id>
            <contact:roid>548965487-UK</contact:roid>
            <contact:status s="ok"/>
            <contact:postalInfo type="loc">
              <contact:name>Mr Jones</contact:name>
              <contact:org>Company.</contact:org>
              <contact:addr>
                <contact:street>High Street</contact:street>
                <contact:city>Oxford</contact:city>
                <contact:pc>OX1 1AH</contact:pc>
                <contact:cc>GB</contact:cc>
              </contact:addr>
            </contact:postalInfo>
            <contact:voice>+44.1865658754</contact:voice>
            <contact:email>example@epp-example.org.uk</contact:email>
            <contact:clID>EXAMPLE-TAG</contact:clID>
            <contact:crID>n/a</contact:crID>
            <contact:crDate>2007-05-12T12:44:00Z</contact:crDate>
            <contact:upDate>2008-06-12T06:46:00Z</contact:upDate>
          </contact:infData>
        </resData>
        <trID>
          <clTRID>ABC-12345</clTRID>
          <svTRID>123456</svTRID>
        </trID>
      </response>
    </epp>

 

Domain Cancelled

A domain cancelled notification is generated to inform you when a domain name is cancelled by us.

<epp:resData> element

The <resData> element contains a single <n:cancData> element with the details of the cancellation. This contains the following sub-elements:

  • A <n:domainName> element.
  • A <n:orig> element giving the originator of the cancellation.

Example of a Domain Cancelled Notification

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
   xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
   epp-1.0.xsd">
   <response>
     <result code="1301">
       <msg>Command completed successfully; ack to dequeue</msg>
     </result>
     <msgQ count="10" id="12345">
       <qDate>2007-09-26T07:31:30</qDate>
       <msg>Domain name Cancellation Notification</msg>
     </msgQ>
     <resData>
       <n:cancData
         xmlns:n="http://www.nominet.org.uk/epp/xml/std-notifications-1.0"
         xsi:schemaLocation=
             "http://www.nominet.org.uk/epp/xml/std-notifications-1.0
         std-notifications-1.0.xsd">
         <n:domainName>epp-example1.co.uk</n:domainName>
         <n:orig>example@nominet</n:orig>
       </n:cancData>
     </resData>
     <trID>
       <clTRID>ABC-12345</clTRID>
       <svTRID>123456</svTRID>
     </trID>  
   </response>
 </epp>

 

Domains Released

This notification on a successful registrar change is generated in the following two cases:

  • When a registrar change is requested via the online services
  • When a registrar change is requested via EPP or WDM and the new tag requires and accepts the handshake.

<epp:resData> element

The resData element contains an <n:relData> element containing the following sub-elements:

  • An <n:accountId> giving the identifier of the account that the domain names are on. This has an attribute here of "moved" which can be "Y" if the account has been moved with the domain name or "N" if the account remains on the tag.
  • An <n:from> giving the tag that the account and domain names have been moved from. (This is the same as the tag that has been used to log into EPP.
  • An <n:registrarTag> giving the tag that the account and domain names have been moved to.
  • An <n:domainListData> element showing the domain names that have been moved from the tag. This element has a "no-domains" element giving the number of domain names moved.

Example of a domains released notification

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
  epp-1.0.xsd">
  <response>
    <result code="1301">
      <msg>Command completed successfully; ack to dequeue</msg>
    </result>
    <msgQ count="10" id="12345">
      <qDate>2007-09-26T07:31:30</qDate>
      <msg>Domains Released Notification</msg>
    </msgQ>
    <resData>
      <n:relData
        xmlns:n="http://www.nominet.org.uk/epp/xml/std-notifications-1.0"
        xsi:schemaLocation="http://www.nominet.org.uk/epp/xml/std-notifications-1.0
        std-notifications-1.0.xsd">
        <n:accountId moved="Y">12345</n:accountId>
        <n:from>EXAMPLE1-TAG</n:from>
        <n:registrarTag>EXAMPLE2-TAG</n:registrarTag>
        <n:domainListData noDomains="6">
          <n:domainName>epp-example1.co.uk</n:domainName>
          <n:domainName>epp-example2.co.uk</n:domainName>
          <n:domainName>epp-example3.co.uk</n:domainName>
          <n:domainName>epp-example4.co.uk</n:domainName>
          <n:domainName>epp-example5.co.uk</n:domainName>
          <n:domainName>epp-example6.co.uk</n:domainName>
        </n:domainListData>
      </n:relData>
    </resData>
    <trID>
      <clTRID>ABC-12345</clTRID>
      <svTRID>123456</svTRID>
    </trID>
  </response>
</epp>

 

Handshake Rejected

This notification is generated when a registrar requests a registrar change, the new tag requires a handshake and they decline it.

<epp:resData> element

The resData element contains a single <n:relData> element which contains the  following sub-elements:

  • An <n:accountId> giving the account that the domain names are on.
  • An <n:from> element giving the tag that requested the registrar change. This is the tag that has been used to log into EPP
  • An <n:registrarTag> element giving the tag that has rejected the handshake.
  • An <n:domainListData> element giving the list of domain names involved. This element has an attribute "noDomains" giving the number of domain names.

Example of a Handshake Rejected Notification

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
   xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
   epp-1.0.xsd">
   <response>
     <result code="1301">
       <msg>Command completed successfully; ack to dequeue</msg>
     </result>
     <msgQ count="10" id="12345">
       <qDate>2007-09-26T07:31:30</qDate>
       <msg>Registrar Change Handshake Rejected Notification</msg>
     </msgQ>
     <resData>
       <n:relData
         xmlns:n="http://www.nominet.org.uk/epp/xml/std-notifications-1.0"
         xsi:schemaLocation="http://www.nominet.org.uk/epp/xml/std-notifications-1.0
         std-notifications-1.0.xsd">
         <n:accountId>1243654</n:accountId>
         <n:from>EXAMPLE1-TAG</n:from>
         <n:registrarTag>EXAMPLE2-TAG</n:registrarTag>
         <n:domainListData noDomains="6">
           <n:domainName>epp-example1.co.uk</n:domainName>
           <n:domainName>epp-example2.co.uk</n:domainName>
           <n:domainName>epp-example3.co.uk</n:domainName>
           <n:domainName>epp-example4.co.uk</n:domainName>
           <n:domainName>epp-example5.co.uk</n:domainName>
           <n:domainName>epp-example6.co.uk</n:domainName>
         </n:domainListData>
       </n:relData>
     </resData>
     <trID>
       <clTRID>ABC-12345</clTRID>
       <svTRID>123456</svTRID>
     </trID>
   </response>
 </epp>

 

Handshake Request

If you have opted to receive registrar change handshake requests then a notification will be generated when a request is received for a domain name to be moved onto your tag. A notification will also be generated when a request is received for a registrant transfer to a domain name on your tag.

<epp:resData> element

The resData element will contain an <n:rcData> element that contains the following sub-elements:

  • An <n:orig> giving the originator of the registrar change or registrant transfer request.
  • An <n:registrarTag> giving the tag that the domain names are to be moved to.
  • An <n:caseId> element giving the case identifier.
  • An <n:domainListdata> element. This has an "noDomains" attribute giving the number of domains to be moved and a list of standard <domain:infData> elements giving the details of the domain names to be moved.
  • A standard <contact:infData> element giving the details of the account for the domain names.

Example Handshake request

  <?xml version="1.0" encoding="UTF-8"?>
 <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
   xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
   epp-1.0.xsd">
   <response>
     <result code="1301">
       <msg>Command completed successfully; ack to dequeue</msg>
     </result>
     <msgQ count="10" id="12345">
       <qDate>2007-09-26T07:31:30</qDate>
       <msg>Registrar Change Authorisation Request</msg>
     </msgQ>
     <resData>
       <n:rcData
         xmlns:n="http://www.nominet.org.uk/epp/xml/std-notifications-1.0"
         xsi:schemaLocation="http://www.nominet.org.uk/epp/xml/std-notifications-1.0
         std-notifications-1.0.xsd">
         <n:orig>p@epp-example.org.uk</n:orig>
         <n:registrarTag>EXAMPLE</n:registrarTag>
         <n:caseId>3560</n:caseId>
         <n:domainListData noDomains="2"
           xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
           xsi:schemaLocation="urn:ietf:params:xml:ns:domain-1.0 domain-1.0.xsd">
           <domain:infData>
             <domain:name>epp-example1.co.uk</domain:name>
             <domain:roid>57486578-UK</domain:roid>
             <domain:registrant>1245435</domain:registrant>
             <domain:ns>
               <domain:hostObj>ns0.epp-example.co.uk</domain:hostObj>
             </domain:ns>
             <domain:host>ns0.epp-example1.co.uk</domain:host>
             <domain:clID>EPP-EXAMPLE2</domain:clID>
           </domain:infData>
           <domain:infData>
             <domain:name>epp-example2.co.uk</domain:name>
             <domain:roid>57486578-UK</domain:roid>
             <domain:registrant>1245435</domain:registrant>
             <domain:ns>
               <domain:hostObj>ns0.epp-example.co.uk</domain:hostObj>
             </domain:ns>
             <domain:clID>EPP-EXAMPLE2</domain:clID>
           </domain:infData>
         </n:domainListData>
         <contact:infData
           xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"
           xsi:schemaLocation="urn:ietf:params:xml:ns:contact-1.0
           contact-1.0.xsd">
          <contact:id>CMyContactID</contact:id>
          <contact:roid>548965487-UK</contact:roid>
          <contact:status s="ok"/>
          <contact:postalInfo type="loc">
           <contact:name>Mr Jones</contact:name>
           <contact:org>Company.</contact:org>
           <contact:addr>
             <contact:street>High Street</contact:street>
             <contact:city>Oxford</contact:city>
             <contact:pc>OX1 1AH</contact:pc>
             <contact:cc>GB</contact:cc>
           </contact:addr>
          </contact:postalInfo>
          <contact:voice>+44.1865658754</contact:voice>
          <contact:email>example@epp-example.org.uk</contact:email>
          <contact:clID>EXAMPLE-TAG</contact:clID>
          <contact:crID>n/a</contact:crID>
          <contact:crDate>2007-05-12T12:44:00Z</contact:crDate>
          <contact:upDate>2008-06-12T06:46:00Z</contact:upDate>
         </contact:infData>
       </n:rcData>
     </resData>
     <trID>
       <clTRID>ABC-12345</clTRID>
       <svTRID>123456</svTRID>
     </trID>  
   </response>
 </epp> 

 

Hosts Cancelled

A host cancellation notification is generated to inform you when hosts, that are linked to domains that you sponsor, are cancelled by us. Such cancellations will occur when a superordinate domain name associated with a host is cancelled.

<epp:resData> element

The <resData> element contains a <n:hostCancData> element. This contains a <n:hostListData> element listing the hosts that were cancelled and a <n:domainListData> which lists the domains that were previously linked to one or more of the cancelled hosts.

Example of a Host Cancelled Notification

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://www.nominet.org.uk/epp/xml/epp-1.0 
  epp-1.0.xsd">
  <response>
    <result code="1301">
      <msg>Command completed successfully; ack to dequeue</msg>
    </result>
    <msgQ count="2" id="1">
      <qDate>2008-04-30T13:39:13Z</qDate>
      <msg>Host cancellation notification</msg>
    </msgQ>
    <resData>
      <n:hostCancData
        xmlns:n="http://www.nominet.org.uk/epp/xml/std-notifications-1.1"
        xsi:schemaLocation="http://www.nominet.org.uk/epp/xml/std-notifications-1.1 
        std-notifications-1.1.xsd">
        <n:hostListData noHosts="2">
          <n:hostObj>ns0.example.co.uk.</n:hostObj>
          <n:hostObj>ns1.example.co.uk.</n:hostObj>
        </n:hostListData>
        <n:domainListData noDomains="2">
          <n:domainName>example-a.co.uk</n:domainName>
          <n:domainName>example-b.co.uk</n:domainName>
        </n:domainListData>
      </n:hostCancData>
    </resData>
    <trID>
      <clTRID>EPP-ABC-12345</clTRID>
      <svTRID>203355</svTRID>
    </trID>
  </response>
</epp>

 

Data quality notification

When a domain name registrant’s name or address cannot be validated our data quality process notifies both the registrar and registrant.

If the details are not updated and we are unable to validate the data, the domain name will be suspended 30 days later.  A ‘Domains Suspended Notification’ will be sent.

The <n:processData> element has the following sub-elements:

  • A standard <contact:infData> element giving the account details concerned.
  • An <n:processType> element indicating the process type is either:
    • "Data Quality workflow - Registrant Name"
    • "Data Quality workflow - Registrant Address"
    • "Data Quality workflow - Registrant Name and Address"
  • An <n:suspendDate> giving the date that the account will be suspended if the incorrect details are not updated.
  • An <n:domainList> element giving a list of the domain names affected. This element has a "noDomains" element giving the number of domains in the list.

Accredited Channel Partners

Data quality notifications differ for Accredited Channel Partners as the process and suspension is managed by the registrar.

The <n:processData> element differs for Accredited Channel Partner tags as follows:

  • A <n:processType> element indicates the process type is either:
    • “Data Quality - Registrant Name”
    • “Data Quality - Registrant Address”
    • “Data Quality - Registrant Name and Address”
    • “Data Quality - Invalid Foreign Registration”
  • A <n:suspendDate> sub-element will not be provided

Example of a data quality workflow process notification

    <msgQ count="4" id="123456">
       <qDate>2007-10-06T10:29:30Z</qDate>
       <msg>Data Quality - {{Workflow type}} process commenced notification</msg>
     </msgQ>
     <resData>
       <n:processData stage="initial"
         xmlns:n="http://www.nominet.org.uk/epp/xml/std-notifications-1.1"
         xsi:schemaLocation="http://www.nominet.org.uk/epp/xml/std-notifications-1.1
         std-notifications-1.1.xsd">
         <contact:infData
           xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"
           xsi:schemaLocation="urn:ietf:params:xml:ns:contact-1.0 contact-1.0.xsd">
           <contact:id>E2CD4B4D83DB0857</contact:id>
           <contact:roid>589695</contact:roid>
           <contact:status s="ok"/>
           <contact:postalInfo type="loc">
             <contact:name>E. Example</contact:name>
             <contact:org>Example Org</contact:org>
             <contact:addr>
               <contact:street>n/a</contact:street>
               <contact:city>n/a</contact:city>
               <contact:sp>n/a</contact:sp>
               <contact:pc>N1 1NA</contact:pc>
               <contact:cc>GB</contact:cc>
             </contact:addr>
           </contact:postalInfo>
           <contact:email>email@epp-example.co.uk</contact:email>
           <contact:clID>TEST</contact:clID>
           <contact:crID>test@epp-example.co.uk</contact:crID>
           <contact:crDate>2009-04-16T11:02:49</contact:crDate>
         </contact:infData>
         <n:processType>{{Workflow type}}</n:processType>
         <n:suspendDate>2010-10-26T00:00:00</n:suspend-date>
         <n:domainListData noDomains="2">
           <n:domainName>epp-example1.co.uk</n:domainName>
           <n:domainName>epp-example2.co.uk</n:domainName>
         </n:domainListData>
       </n:processData>
     </resData>   

Example of notification when Nominet validates a record that was previously unvalidated

     <msgQ count="4" id="123456">
       <qDate>2007-10-06T10:29:30Z</qDate>
       <msg>DQ Workflow process lifted notification</msg>
     </msgQ>
     <resData>
       <n:processData stage="updated"
         xmlns:n="http://www.nominet.org.uk/epp/xml/std-notifications-1.1"
         xsi:schemaLocation="http://www.nominet.org.uk/epp/xml/std-notifications-1.1
         std-notifications-1.1.xsd">
         <n:processType>{{Workflow type}}</n:processType>
         <contact:infData
           xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"
           xsi:schemaLocation="urn:ietf:params:xml:ns:contact-1.0 contact-1.0.xsd">
           <contact:id>E2CD4B4D83DB0857</contact:id>
           <contact:roid>589695</contact:roid>
           <contact:status s="ok"/>
           <contact:postalInfo type="loc">
             <contact:name>E. Example</contact:name>
             <contact:org>Example Org</contact:org>
             <contact:addr>
               <contact:street>n/a</contact:street>
               <contact:city>n/a</contact:city>
               <contact:sp>n/a</contact:sp>
               <contact:pc>N1 1NA</contact:pc>
               <contact:cc>GB</contact:cc>
             </contact:addr>
           </contact:postalInfo>
           <contact:email>email@epp-example.co.uk</contact:email>
           <contact:clID>TEST</contact:clID>
           <contact:crID>test@epp-example.co.uk</contact:crID>
           <contact:crDate>2009-04-16T11:02:49</contact:crDate>
         </contact:infData>
         <n:processType>DQ Workflow</n:ProcessType>
         <n:domainListData noDomains="2"
           <n:domainName>epp-example1.co.uk</n:domainName>
           <n:domainName>epp-example2.co.uk</n:domainName>
         </n:domainListData>
       </n:processData>
     </resData>

 

Domains suspended

This notification is generated upon domain suspension, not including the cases of renewal and phishing.

<epp:resData> element

The resData element contains a <n:suspData> element which contains the following sub-elements:

  • A <n:reason> giving the reason for the suspension of domain names.
  • An optional <n:cancelDate> giving a cancellation date for the domains if they have been scheduled for cancellation.
  • A <n:domainListData> element showing the domain names that have been suspended.

Example of a domains suspended notification

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.nominet.org.uk/epp/xml/epp-1.0 epp-1.0.xsd">
    <response>
        <result code="1301">
            <msg>Command completed successfully; ack to dequeue</msg>
        </result>
        <msgQ count="2" id="1">
            <qDate>2008-04-30T13:39:13Z</qDate>
            <msg>Domains Suspended Notification</msg>
        </msgQ>
        <resData>
            <n:suspData
             xmlns:n="http://www.nominet.org.uk/epp/xml/std-notifications-1.1"
             xsi:schemaLocation="http://www.nominet.org.uk/epp/xml/std-notifications-1.1 
		std-notifications-1.1.xsd">
                <n:reason>Data Quality</n:reason>
                <n:cancelDate>2009-12-12T00:00:13Z</n:cancelDate>
                <n:domainListData noDomains="2">
                    <n:domainName>epp-example1.co.uk</n:domainName>
                    <n:domainName>epp-example2.co.uk</n:domainName>
                </n:domainListData>
            </n:suspData>
        </resData>
        <trID>
            <clTRID>EPP-ABC-12345</clTRID>
            <svTRID>203355</svTRID>
        </trID>
    </response>
</epp>

 

Referral Accept

This notification is generated when a registrar requests a .ltd.uk, .plc.uk or .net.uk domain name and it is accepted.

<epp:resData> element

The <resData> element contains a single <domain:creData> element which contains the details of the domain name that has been registered. This element is returned by a successful create command.

Example of a referral accepted notification

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
   xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
   epp-1.0.xsd">
   <response>
     <result code="1301">
       <msg>Command completed successfully; ack to dequeue</msg>
     </result>
     <msgQ count="10" id="12345">
       <qDate>2007-09-26T07:31:30</qDate>
       <msg>Referral Accepted Notification</msg>
     </msgQ>
     <resData>
       <domain:creData
         xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
         xsi:schemaLocation="urn:ietf:params:xml:ns:domain-1.0
         domain-1.0.xsd">
         <domain:name>epp-example1.ltd.uk</domain:name>
         <domain:crDate>2007-09-25T11:30:45</domain:crDate>
         <domain:exDate>2009-09-25T11:30:45</domain:exDate>
       </domain:creData>
     </resData>
     <trID>
       <clTRID>ABC-12345</clTRID>
       <svTRID>123456</svTRID>
     </trID>
   </response>
 </epp>

 

Referral Reject

This notification is generated when a registrar requests a .ltd.uk, .plc.uk or .net.uk domain name, which is then referred for manual checking, and the request is then rejected.

<epp:resData> element

The <resData> element contains an  <n:domainFailData> element that gives the domain name and the reason why the registration request has been rejected. This contains the following sub-elements:

  • An <n:domainName> element giving the domain name concerned.
  • An <n:reason> giving the reason for rejecting the request.


Example of a Referral Rejection Notification

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
   xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
   epp-1.0.xsd">
   <response>
     <result code="1301">
       <msg>Command completed successfully; ack to dequeue</msg>
     </result>
     <msgQ count="10" id="12345">
       <qDate>2007-09-26T07:31:30</qDate>
       <msg>Referral Rejected Notification</msg>
     </msgQ>
     <resData>
       <n:domainFailData
         xmlns:n="http://www.nominet.org.uk/epp/xml/std-notifications-1.0"
         xsi:schemaLocation="http://www.nominet.org.uk/epp/xml/std-notifications-1.0
         std-notifications-1.0.xsd">
         <n:domainName>epp-example2.ltd.uk</n:domainName>
         <n:reason>V205 Registrant does not match domain name</n:reason>
       </n:domainFailData>
     </resData>
     <trID>
       <clTRID>ABC-12345</clTRID>
       <svTRID>123456</svTRID>
     </trID>
   </response>
 </epp>

 

Registrant Transfer

This notification is generated when a domain name has been transferred or merged from one registrant contact to another.

<epp:resData> element

The <resData> element contains an <n:trnData> which contains the following sub-elements:

  • An <n:accountId> element giving the registrant contact identifier after the transfer
  • An <n:oldAccountId> element giving the registrant contact identifier before the transfer
  • An <n:domainListData> element giving a list of the domain names involved in the registrant transfer. This element has a noDomains attribute giving the number of domain names in the list and one or more <n:domainName> elements giving details of the domain names being transferred.
  • A standard <contact:infData> element giving the details of the registrant contact after the transfer

Example of a registrant transfer notification

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
  epp-1.0.xsd">
  <response>
    <result code="1301">
      <msg>Command completed successfully; ack to dequeue</msg>
    </result>
    <msgQ count="4" id="123456">
      <qDate>2007-10-06T10:29:30Z</qDate>
      <msg>Registrant Transfer Notification</msg>
    </msgQ>
    <resData>
      <n:trnData
        xmlns:n="http://www.nominet.org.uk/epp/xml/std-notifications-1.0"
        xsi:schemaLocation="http://www.nominet.org.uk/epp/xml/std-notifications-1.0
        std-notifications-1.0.xsd">
        <n:orig>p@automaton-example.org.uk</n:orig>
        <n:accountId>58658458</n:accountId>
        <n:oldAccountId>596859</n:oldAccountId>  
        <n:domainListData noDomains="2"
          xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
          xsi:schemaLocation="urn:ietf:params:xml:ns:domain-1.0
          domain-1.0.xsd">
          <n:domainName>epp-example1.co.uk</n:domainName>
          <n:domainName>epp-example2.co.uk</n:domainName>
        </n:domainListData>
        <contact:infData
          xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"
          xsi:schemaLocation="urn:ietf:params:xml:ns:contact-1.0
          contact-1.0.xsd">
          <contact:id>ST68956589R4</contact:id>
          <contact:roid>123456-UK</contact:roid>
          <contact:status s="ok"/>
          <contact:postalInfo type="loc">
           <contact:name>Mr R. Strant</contact:name>
           <contact:addr>  
            <contact:street>2102 High Street</contact:street>
            <contact:city>Oxford</contact:city>
            <contact:sp>Oxon</contact:sp>
            <contact:pc>OX1 1QQ</contact:pc>
            <contact:cc>GB</contact:cc>
           </contact:addr>
          </contact:postalInfo>
          <contact:email>example@epp-example1.co.uk</contact:email>
          <contact:clID>TEST</contact:clID>
          <contact:crID>TEST</contact:crID>
          <contact:crDate>1999-04-03T22:00:00.0Z</contact:crDate>
          <contact:upID>domains@isp.com</contact:upID>
          <contact:upDate>1999-12-03T09:00:00.0Z</contact:upDate>
        </contact:infData>
      </n:trnData>
    </resData>
    <trID>
      <clTRID>ABC-12345</clTRID>
      <svTRID>123456</svTRID>
    </trID>
  </response>
</epp>

 

Registrar Change

A registrar change notification notifies you when an account and it's domain names have been moved on to your tag.

<epp:resData> element

The <epp:resData> element contains an <n:rcData> element that contains the following sub-elements

  • An <n:orig> giving the originator of the registrar change request.
  • An <n:registrarTag> giving the tag that the domain names are to be moved to.
  • A <n:domainListData element. This element has a noDomains attribute which gives the number of domains in the list and contains a list of standard <domain:infData> elements that contain the details of the domain names that are being moved to the tag.
  • A standard <contact:infData> element giving the details of the account being moved to the tag.

Example of a registrar change notification message

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
   xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0
   epp-1.0.xsd">
   <response>
     <result code="1301">
       <msg>Command completed successfully; ack to dequeue</msg>
     </result>
     <msgQ count="4" id="123456">
       <qDate>2005-10-06T10:29:30Z</qDate>
       <msg>Registrar Change Notification</msg>
     </msgQ>
     <resData>
       <n:rcData
         xmlns:n="http://www.nominet.org.uk/epp/xml/std-notifications-1.0"
         xsi:schemaLocation="http://www.nominet.org.uk/epp/xml/std-notifications-1.0
         std-notifications-1.0.xsd">
         <n:orig>p@automaton-example.org.uk</n:orig>
         <n:registrarTag>EXAMPLE</n:registrarTag>
         <n:domainListData noDomains="2"
          xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
          xsi:schemaLocation="urn:ietf:params:xml:ns:domain-1.0
          domain-1.0.xsd">
           <domain:infData>
             <domain:name>auto-example1.co.uk</domain:name>
             <domain:roid>65876854-UK</domain:roid>
             <domain:ns>
               <domain:hostObj>ns0.epp-example.co.uk</domain:hostObj>
               <domain:hostObj>ns1.epp-example.co.uk</domain:hostObj>
             </domain:ns> 
             <domain:clID>EXAMPLE-TAG</domain:clID>
             <domain:crID>example@epp-exam</domain:crID> 
             <domain:crDate>2005-06-03T12:00:00</domain:crDate>
             <domain:exDate>2007-06-03T12:00:00</domain:exDate>
           </domain:infData>
           <domain:infData>
             <domain:name>epp-example2.co.uk</domain:name>
             <domain:roid>568957896-UK</domain:roid>
             <domain:clID>EXAMPLE-TAG</domain:clID>
             <domain:crID>example@epp-exa</domain:crID> 
             <domain:crDate>2005-06-03T12:00:00</domain:crDate>
             <domain:exDate>2007-06-03T12:00:00</domain:exDate>
           </domain:infData>
         </n:domainListData>
         <contact:infData
          xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"
          xsi:schemaLocation="urn:ietf:params:xml:ns:contact-1.0
          contact-1.0.xsd"> 
           <contact:id>ST96503FG</contact:id>
           <contact:roid>5876578-UK</contact:roid>
           <contact:status s="ok"/>
           <contact:postalInfo type="loc">
             <contact:name>Mr R Strant</contact:name>
             <contact:org>reg company</contact:org>
             <contact:addr>
               <contact:street>2102 High Street</contact:street>
               <contact:city>Oxford</contact:city>
               <contact:sp>Oxon</contact:sp>
               <contact:pc>OX1 1QQ</contact:pc>
               <contact:cc>GB</contact:cc>
             </contact:addr>
           </contact:postalInfo>
           <contact:voice>+44.1865123456</contact:voice>
           <contact:email>r.strant@epp-example.co.uk</contact:email>
           <contact:clID>TEST</contact:clID>
           <contact:crID>domains@epp-exam</contact:crID>
           <contact:crDate>1999-04-03T22:00:00.0Z</contact:crDate>
           <contact:upID>domains@isp.com</contact:upID>
           <contact:upDate>1999-12-03T09:00:00.0Z</contact:upDate>
         </contact:infData>
       </n:rcData>
     </resData>
     <trID>
       <clTRID>ABC-12345</clTRID>
       <svTRID>123456</svTRID>
     </trID>
   </response>
 </epp>

Contact Deleted

This notification is sent when a domain contact has been deleted.

<epp:resData> element

The resData element contains a single <n:contactDelData> element containing details of the contact which has been deleted. This contains the following sub-elements:

  • A <n:contactId> element containing the EPP-Standard Id of the deleted contact
  • A <n:roid> element containing the contact identifier of the deleted contact

Example of a Contact Deleted Notification

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xsi:schemaLocation="http://www.nominet.org.uk/epp/xml/epp-1.0 epp-1.0.xsd">
   <response>
     <result code="1301">
       <msg>Command completed successfully; ack to dequeue</msg>
     </result>
     <msgQ count="2" id="25034106">
       <qDate>2015-03-12T14:54:27Z</qDate>
       <msg>Contact deleted notification</msg>
     </msgQ>
     <resData>
       <n:contactDelData
         xmlns:n="http://www.nominet.org.uk/epp/xml/std-notifications-1.2"
         xsi:schemaLocation="http://www.nominet.org.uk/epp/xml/std-notifications-1.2 std-notifications-1.2.xsd">
         <n:contactId> EPP-ABC-12345</n:contactId>
         <n:roid>1002703-UK </n:roid>
       </n:contactDelData>
     </resData>
     <trID>
       <clTRID>1426172282-1s6Lclamc</clTRID>
       <svTRID>4453949562</svTRID>
     </trID>
   </response>
</epp>