Skip to Main Content

Nominet

Log in to the online service
Log in to Online Services
Skip Primary Navigation
Skip All Secondary and Tertiary Navigation
  
Print this page  | Contact Us
The EPP <info> command is used to retrieve information associated with an object.

Domains

The <domain:info> command will retrieve information associated with a domain and is described in RFC 5731.

Example of a <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="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-example.co.uk</domain:name>
         <domain:roid>7854785487-UK</domain:roid>
         <domain:registrant>S70T1</domain:registrant>
         <domain:ns>
           <domain:hostObj>ns0.epp-example2.co.uk</domain:hostObj> 
           <domain:hostObj>ns1.epp-example2.co.uk</domain:hostObj>
         </domain:ns>
         <domain:host>ns0.epp-example.co.uk</domain:host>
         <domain:host>ns1.epp-example.co.uk</domain:host>
         <domain:clID>EXAMPLE_TAG</domain:clID>
         <domain:crID>epp@epp-example.</domain:crID>
         <domain:crDate>2008-01-01T13:34:20.0Z</domain:crDate>
         <domain:upID>epp@epp-example.</domain:upID>
         <domain:upDate>2009-04-02T13:56:03.0Z</domain:upDate>
         <domain:exDate>2010-01-01T13:34:20.0Z</domain:exDate>
       </domain:infData> 
    </resData>
    <extension>
      <domain-ext:infData 
       xmlns:domain-ext="http://www.nominet.org.uk/epp/xml/domain-nom-ext-1.1"
       xsi:schemaLocation="http://www.nominet.org.uk/epp/xml/domain-nom-ext-1.1 domain-nom-ext-1.1.xsd">
        <domain-ext:first-bill>bc</domain-ext:first-bill>
        <domain-ext:recur-bill>bc</domain-ext:recur-bill>
        <domain-ext:auto-bill>123</domain-ext:auto-bill>
        <domain-ext>
      </domain-ext:infData>
    </extension>
    <trID>
      <clTRID>ABC-12345</clTRID>
      <svTRID>54322-XYZ</svTRID>
    </trID>
  </response>
</epp>

Notes

:
  • There will be no <domain:status> element within the standard object.
  • The <domain:crID> field in the standard object will be truncated to 16 characters. The full field will be provided in a warning extension object.
  • The <domain:upID> field in the standard object will be truncated to 16 characters. The full field will be provided in a warning extension object.
  • There will be no <domain:trDate> element within the standard object.
  • There will be no <domain:authInfo> element within the standard object.

Registrant contacts

The standard <contact:info> will retrieve information associated with a registrant contact and is described in RFC 5733.

Example of a <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="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:crDate>2007-05-12T12:44:00Z</contact:crDate>
        <contact:upDate>2008-06-12T06:46:00Z</contact:upDate>
      </contact:infData>
    </resData>
    <extension>
      <contact-ext:infData
        xmlns:contact-ext="http://www.nominet.org.uk/epp/xml/contact-nom-ext-1.0"
        xsi:schemaLocation="http://www.nominet.org.uk/epp/xml/contact-nom-ext-1.0
        contact-nom-ext-1.0.xsd">
        <contact-ext:trad-name>Big enterprises</contact-ext:trad-name>
        <contact-ext:type>LTD</contact-ext:type>
        <contact-ext:co-no>5489549</contact-ext:co-no>
        <contact-ext:opt-out>N</contact-ext:opt-out>
      </contact-ext:infData>
    </extension>    
    <trID>
      <clTRID>ABC-12345</clTRID>
      <svTRID>54322-XYZ</svTRID>
    </trID>
  </response>
</epp>

Notes

:
  • The <contact:crID> and <contact:upID> elements in the standard object will be truncated to 16 characters. The full field will be given in a warning extension object.
  • There will be no <contact:authInfo> element.
  • There will be no <contact:trDate> element.
  • The <contact:city> and <contact:cc> fields are mandatory in the standard schema but may not be present in the database for some domain names. In this circumstance, the <contact:city> field will be '.' and the <contact:cc> field '..'.

Hosts

The <host:info> command will retrieve information associated with a nameserver object and is described in RFC 5732.

Example of a <host: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="http://www.nominet.org.uk/epp/xml/epp-1.0 epp-1.0.xsd">
  <response>
    <result code="1000">
      <msg>Command completed successfully</msg>
    </result>
    <resData>
      <host:infData
        xmlns:host="urn:ietf:params:xml:ns:host-1.0"
        xsi:schemaLocation="urn:ietf:params:xml:ns:host-1.0 host-1.0.xsd">
        <host:name>ns0.epp-example.co.uk.</host:name>
        <host:roid>548965487-UK</host:roid>
        <host:status s="ok"/>
        <host:addr ip="v4">123.123.123.123</host:addr>
        <host:addr ip="v6">1080:0:0:0:8:800:200C:417B</host:addr>
        <host:clID>EXAMPLE_TAG</host:clID>
        <host:crID>epp-user</host:crID>
        <host:crDate>2008-06-12T06:46:00Z</host:crDate>
      </host:infData>
    </resData>
    <trID>
      <clTRID>EPP-ABC-12345</clTRID>
      <svTRID>116890</svTRID>
    </trID>
  </response>
</epp>

Notes

:
  • The <host:crID> and <host:upID> elements in the standard object will be truncated to 16 characters. The full field will be given in a warning extension object.
  • There will be no <contact:trDate> element.
 
More pages
Related contacts
For questions from our members and registrars Telephone: 01865 332233 Email: support@nominet.org.uk To make a payment Telephone: 01865 332348 Email: payments@nominet.org.uk Emergency out of hours support for registrars Telephone: 01606 866663 
If you need any more advice, request a call back and discuss your query with one of our advisors. Request call back ›
 
 
© Nominet UK 1996-2012  |  Accessibility  |  Site Map  |  Feeds  |  Glossary  |  Privacy Policy  |  Terms of Use  |  Cookies  |  Contact Us