Skip to Main Content

Nominet

Log in to the online service
Skip Primary Navigation
Skip All Secondary and Tertiary Navigation
  
Print this page  | Contact Us
The info command is used to retrieve information associated with an object. You are only able to query objects on your own tag.

Domains



This command returns all the data associated with a domain, including the account, contacts and nameservers.  This data is returned in a <domain:infData> element.

<domain:info> element

To obtain information associated with a domain object, the info command must contain a <domain:info> element that identifies the domain namespace and location of the domain schema. The <domain:info> element must contain the following child elements:
  • A <domain:name> element that contains the fully qualified name of the domain object to be queried.

<domain:infData> element

The <domain:infData> element contains the following child elements:
  • A <domain:name> element.
  • A <domain:account> element that contains an <account:infData> element defining the account object associated with the domain name.
  • A <domain:reg-status> element describing the registration status of the domain name.
  • An optional <domain:ns> element. This has 1 to 10 <ns:infData> elements describing the nameservers for the domain name.
  • An optional <domain:first-bill> element.
  • An optional <domain:recur-bill> element.
  • An optional <domain:auto-bill> or <domain:next-bill> element. Only one of these two elements should be present.
  • An optional <domain:notes> element.
  • A <domain:clID> containing the TAG of the domain name.
  • A <domain:crID> containing the identifier (TAG, email address or identifier of Nominet staff member) of who or what created the domain name. This element is not present for .sch.uk domain names.
  • A <domain:crDate> element.
  • A <domain:exDate> element.
  • A <domain:upID> giving the identifier of who (TAG, email address, contact identifier or identifier of Nominet staff member) or what (automatic process identifier) last updated the domain object fields (not the account fields).This element is not present if the domain has not been modified since registration.
  • A <domain:upDate> giving the date and time of the most recent domain object modification. This element is not present if the domain has not been modified since registration.

Examples

Example of a <domain:info> command

  <?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">
      <command>
        <info>
          <domain:info
           xmlns:domain="http://www.nominet.org.uk/epp/xml/nom-domain-1.0"
           xsi:schemaLocation="http://www.nominet.org.uk/epp/xml/nom-domain-1.0
           nom-domain-1.0.xsd">
            <domain:name>example.co.uk</domain:name>
         </domain:info>
       </info>
       <clTRID>ABC-12345</clTRID>
     </command>
   </epp>

Example of a successful <domain:info> response

   <?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="1000">
        <msg>Command completed successfully</msg>
       </result>
       <resData>
        <domain:infData
         xmlns:domain="http://www.nominet.org.uk/epp/xml/nom-domain-1.0"
         xsi:schemaLocation="http://www.nominet.org.uk/epp/xml/nom-domain-1.0
         nom-domain-1.0.xsd">
         <domain:name>example.co.uk</domain:name>
         <domain:reg-status>Registration request being processed.</domain:reg-status>
         <domain:account>
          <account:infData
           xmlns:account="http://www.nominet.org.uk/epp/xml/nom-account-1.0"
           xmlns:contact="http://www.nominet.org.uk/epp/xml/nom-contact-1.0">
           <account:roid>S123456</account:roid>
           <account:name>Mr R. Strant</account:name>
           <account:trad-name>R. S. Industries</account:trad-name>
           <account:type>STRA</account:type>
           <account:co-no>NI123456</account:co-no>
           <account:opt-out>N</account:opt-out>
           <account:addr type="admin">
            <account:street>2102 High Street</account:street>
            <account:locality>Carfax</account:locality>
            <account:city>Oxford</account:city>
            <account:county>Oxfordshire</account:county>
            <account:postcode>OX1 1DF</account:postcode>
            <account:country>GB</account:country>
           </account:addr>
           <account:contact type="admin" order="1">
            <contact:infData>
             <contact:roid>C12345</contact:roid>
             <contact:name>Mr R.Strant</contact:name>
             <contact:phone>01865 123456</contact:phone>
             <contact:fax>01865 123456</contact:fax>
             <contact:email>r.strant@strant.co.uk</contact:email>
             <contact:clID>TEST</contact:clID>
             <contact:crID>domains@isp.com</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>
           </account:contact>
           <account:contact type="admin" order="2">
            <contact:infData>
             <contact:roid>C23456</contact:roid>
             <contact:name>Ms S. Strant</contact:name>
             <contact:phone>01865 123457</contact:phone>
             <contact:fax>01865 123456</contact:fax>
             <contact:email>s.strant@strant.co.uk</contact:email>
             <contact:clID>TEST</contact:clID>
             <contact:crID>domains@isp.com</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>
           </account:contact>
           <account:contact type="billing" order="1">
            <contact:infData>
            <contact:roid>C12347</contact:roid>
            <contact:name>A. Ccountant</contact:name>
            <contact:phone>01865 657893</contact:phone>
            <contact:email>acc@billing.co.uk</contact:email>
            <contact:clID>TEST</contact:clID>
            <contact:crID>domains@isp.com</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>
          </account:contact>
          <account:clID>TEST</account:clID>
          <account:crID>TEST</account:crID>
          <account:crDate>1999-04-03T22:00:00.0Z</account:crDate>
          <account:upID>domains@isp.com</account:upID>
          <account:upDate>1999-12-03T09:00:00.0Z</account:upDate>
         </account:infData>
        </domain:account>
        <domain:ns
         xmlns:ns="http://www.nominet.org.uk/epp/xml/nom-ns-1.0">
          <ns:infData>
            <ns:roid>NS12345</ns:roid>
            <ns:name>ns1.example.co.uk</ns:name>
            <ns:addr ip="v4">10.10.10.10</ns:addr>
            <ns:clID>TEST</ns:clID>
            <ns:crID>domains@isp.com</ns:crID>
            <ns:crDate>1999-04-03T22:00:00.0Z</ns:crDate>
            <ns:upID>domains@isp.com</ns:upID>
            <ns:upDate>1999-12-03T09:00:00.0Z</ns:upDate>
          </ns:infData>
          <ns:infData>
            <ns:roid>NS12346</ns:roid>
            <ns:name>ns1.example.com</ns:name>
            <ns:clID>TEST</ns:clID>
            <ns:crID>domains@isp.com</ns:crID>
            <ns:crDate>1999-04-03T22:00:00.0Z</ns:crDate>
            <ns:upID>domains@isp.com</ns:upID>
            <ns:upDate>1999-12-03T09:00:00.0Z</ns:upDate>
          </ns:infData>
        </domain:ns>
        <domain:clID>TEST</domain:clID>
        <domain:crID>TEST</domain:crID>
        <domain:crDate>1999-04-03T22:00:00.0Z</domain:crDate>
        <domain:upID>domains@isp.com</domain:upID>
        <domain:upDate>1999-12-03T09:00:00.0Z</domain:upDate>
        <domain:exDate>2007-12-03T09:00:00.0Z</domain:exDate>
       </domain:infData>
      </resData>
      <trID>
        <clTRID>ABC-12345</clTRID>
        <svTRID>54322-XYZ</svTRID>
      </trID>
     </response>
    </epp>

Accounts



You can obtain the details of an account object directly, by an <account:info> command that specifies the account you want information on.

<account:info> element

The account:info element must contain the following child elements:
  • An <account:roid> element that contains the identifier of the account object to be queried.

<account:infData> element

The <account:infData> in the response above contains the following child elements:
  • An <account:roid> element that contains the identifier of the account object.
  • An <account:name> element.
  • An optional <account:trad-name> element.
  • An optional <account:type> element.
  • An optional <account:co-no> element.
  • An <account:opt-out> element.
  • One or two <account:addr> elements giving the administrative and (optional) billing addresses for the account. This element has the following sub-elements:
    • <account:street>
    • <account:locality>
    • <account:city>
    • <account:county>
    • <account:postcode>
    • <account:country>
  • 1-6 <account:contact> elements giving the administrative and billing contacts for the account. This element has two attributes - the first is type which may be "admin" or "billing". The second is order which may be "1", "2" or "3" and identifies the contact specifically. The account:contact element has a single contact:infData element which is defined below.
  • An <account:clID> element giving the sponsoring TAG for the account object.
  • An <account:crID> element giving the identifier of who (TAG id, email address or identifier of Nominet staff member) or what (automatic process identifier) created the account object if this information is available (it may not be for data that precedes the data migration process).
  • An <account:crDate> element giving the date the account was created.
  • An <account:upID> element giving the tag or other identifier of who (TAG id, email address, contact identifier or identifier of Nominet staff member) or what (automatic process identifier) last updated the account object. This element is not present if the account has not been modified since it was created.
  • An <account:upDate> giving the date at which the account object was last modified. This element is not present if the account has not been modified since it was created.

Examples

Example of an <account:info> command

    <?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">
        <command>
          <info>
            <account:info
            xmlns:account="http://www.nominet.org.uk/epp/xml/nom-account-1.0" 
            xsi:schemaLocation="http://www.nominet.org.uk/epp/xml/nom-account-1.0
            nom-account-1.0.xsd">
             <account:roid>S1001</account:roid>
           </account:info>
         </info>
         <clTRID>ABC-12345</clTRID>
       </command>
    </epp>

Example of a successful <account:info> response

    <?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="1000">
            <msg>Command completed successfully</msg>
          </result>
          <resData>
           <account:infData
            xmlns:account="http://www.nominet.org.uk/epp/xml/nom-account-1.0"
            xmlns:contact="http://www.nominet.org.uk/epp/xml/nom-contact-1.0"
            xsi:schemaLocation="http://www.nominet.org.uk/epp/xml/nom-account-1.0
            nom-account-1.0.xsd">
            <account:roid>S123456</account:roid>
            <account:name>Mr R. Strant</account:name>
            <account:trad-name>R. S. Industries</account:trad-name>
            <account:type>STRA</account:type>
            <account:co-no>NI123456</account:co-no>
            <account:opt-out>N</account:opt-out>
            <account:addr>
             <account:street>2102 High Street</account:street>
             <account:locality>Carfax</account:locality>
             <account:city>Oxford</account:city>
             <account:county>Oxfordshire</account:county>
             <account:postcode>OX1 1DF</account:postcode>
             <account:country>GB</account:country>
            </account:addr>
            <account:contact type="admin" order="1">
             <contact:infData>
              <contact:roid>C12345</contact:roid>
              <contact:name>Mr R.Strant</contact:name>
              <contact:phone>01865 123456</contact:phone>
              <contact:fax>01865 123456</contact:fax>
              <contact:email>r.strant@strant.co.uk</contact:email>
              <contact:clID>TEST</contact:clID>
              <contact:crID>domains@isp.com</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>
            </account:contact>
            <account:contact type="admin" order="2">
             <contact:infData>
             <contact:roid>C23456</contact:roid>
             <contact:name>Ms S. Strant</contact:name>
             <contact:phone>01865 123457</contact:phone>
             <contact:fax>01865 123456</contact:fax>
             <contact:email>s.strant@strant.co.uk</contact:email>
             <contact:clID>TEST</contact:clID>
             <contact:crID>domains@isp.com</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>
           </account:contact>
           <account:contact type="billing" order="1">
            <contact:infData>
             <contact:roid>C12347</contact:roid>
             <contact:name>A. Ccountant</contact:name>
             <contact:phone>01865 657893</contact:phone>
             <contact:email>acc@billing.co.uk</contact:email>
             <contact:clID>TEST</contact:clID>
             <contact:crID>domains@isp.com</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>
           </account:contact>
           <account:clID>TEST</account:clID>
           <account:crID>TEST</account:crID>
           <account:crDate>1999-04-03T22:00:00.0Z</account:crDate>
           <account:upID>domains@isp.com</account:upID>
           <account:upDate>1999-12-03T09:00:00.0Z</account:upDate>
          </account:infData>
         </resData>
         <trID>
          <clTRID>ABC-12345</clTRID>
          <svTRID>54322-XYZ</svTRID>
        </trID>
      </response>
    </epp>

Contacts

You can find information on a contact object directly by using the <contact:info> command and specifying the ID of the contact to query.

<contact:info> element

The <contact:info> element must contain the following child elements:
  • A <contact:roid> element that contains the identifier of the contact object to be queried.

<contact:infData> element

The <contact:infData> in the response contains the following child elements:
  • A <contact:roid> element.
  • A <contact:name> element.
  • An optional <contact:phone> element.
  • An optional <contact:fax> element.
  • A <contact:email> element.
  • A <contact:clID> element giving the sponsoring tag for the contact object.
  • A <contact:crID> element giving the identifier of who (tag, email address, contact identifier or identifier of Nominet staff member) or what (identifier of automatic process) created the contact if this information is available (may not be for data that preceded the data migration process).
  • A <contact:crDate> element giving the date the contact was created.
  • A <contact:upID> element giving the identifier of who (tag, email address, contact identifier or identifier of Nominet staff member) or what (identifier of automatic process) modified the contact object. This element is not present if the contact has not been modified since it was created.
  • A <contact:upDate> giving the date at which the contact object was last modified. This element is not present if the contact has not been modified since it was created.

Examples

Example <contact:info> command

    <?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">
        <command>
          <info>
            <contact:info
             xmlns:contact="http://www.nominet.org.uk/epp/xml/nom-contact-1.0"
             xsi:schemaLocation="http://www.nominet.org.uk/epp/xml/nom-contact-1.0
             nom-contact-1.0.xsd">
              <contact:roid>C12345</contact:roid>
            </contact:info>
          </info>
          <clTRID>ABC-12345</clTRID>
        </command>
      </epp>

Example successful <contact:info> response

    <?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="1000">
            <msg>Command completed successfully</msg>
          </result>
          <resData>
            <contact:infData
             xmlns:contact="http://www.nominet.org.uk/epp/xml/nom-contact-1.0"
             xsi:schemaLocation="http://www.nominet.org.uk/epp/xml/nom-contact-1.0
             nom-contact-1.0.xsd">
              <contact:roid>R12345</contact:roid>
              <contact:name>Mr Contact</contact:name>
              <contact:phone>01865 123456</contact:phone>
              <contact:fax>01865 123456</contact:fax>
              <contact:email>r.strant@strant.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>TEST</contact:upID>
              <contact:upDate>1999-12-03T09:00:00.0Z</contact:upDate>
            </contact:infData>
          </resData>
          <trID>
            <clTRID>ABC-12345</clTRID>
            <svTRID>54322-XYZ</svTRID>
          </trID>
        </response>
      </epp>

Nameservers

You can query for information on a nameserver directly by specifying the nameserver ID.

<ns:info> element

The <ns:info> element must contain the following child elements:
  • A <ns:roid> element that contains the identifier of the nameserver object to be queried.

<ns:infData> element

The <ns:infData> contains the following child elements:
  • A <ns:roid> giving the identifier of the host object.
  • A <ns:name> giving the name of the nameserver.
  • One optional <ns:addr> element with an ip attribute of "v4" giving the IPV4 address of the nameserver.
  • One optional <ns:addr> element with an ip attribute of "v6" giving the IPV6 address of the nameserver.
  • A <ns:clID> element giving the sponsoring tag of the nameserver object.
  • A <ns:crID> element giving the TAG or other identifier of who created the nameserver if this information is available.
  • A <ns:crDate> element giving the date the nameserver was created.
  • A <ns:upID> element giving the TAG or other identifier of who or what last modified the nameserver object.
  • A <ns:upDate> giving the date the nameserver was last modified.

Examples

Example of a <ns:info> command

    <?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">
        <command>
          <info>
            <ns:info
             xmlns:ns="http://www.nominet.org.uk/epp/xml/nom-ns-1.0"
             xsi:schemaLocation="http://www.nominet.org.uk/epp/xml/nom-ns-1.0
             nom-ns-1.0.xsd">
              <ns:roid>NS12345</ns:roid>
            </ns:info>
          </info>
          <clTRID>ABC-12345</clTRID>
        </command>
      </epp>

Example of a successful <ns:info> response

    <?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="1000">
            <msg>Command completed successfully</msg>
          </result>
          <resData>
            <ns:infData
             xmlns:ns="http://www.nominet.org.uk/epp/xml/nom-ns-1.0"
             xsi:schemaLocation="http://www.nominet.org.uk/epp/xml/nom-ns-1.0
             nom-ns-1.0.xsd">
              <ns:roid>NS12346</ns:roid>
              <ns:name>ns1.example.co.uk</ns:name>
              <ns:addr ip="v4">10.10.10.10</ns:addr>
              <ns:clID>TEST</ns:clID>
              <ns:crID>TEST</ns:crID>
              <ns:crDate>1999-04-03T22:00:00.0Z</ns:crDate>
              <ns:upID>TEST</ns:upID>
              <ns:upDate>1999-12-03T09:00:00.0Z</ns:upDate>
            </ns:infData>
          </resData>
          <trID>
            <clTRID>ABC-12345</clTRID>
            <svTRID>54322-XYZ</svTRID>
          </trID>
        </response>
      </epp>
 
More pages
Related contacts
Contact Registrar Systems Support Telephone: 01865 332233 Email: support@nominet.org.uk Technical Blog Web: blog.nominet.org.uk/tech  
 
 
© Nominet UK 1996-2008  |  Accessibility  |  Site Map  |  Feeds