5.4.2. Info contact

A contact info command is used to view details of a contact.

A new AuthInfo is generated for the contact by the server after successfully executing the contact info command with the AuthInfo parameter.

The contact info command is an info element in the contact namespace (http://www.nic.cz/xml/epp/contact-1.6).

The command must be contained in the <info> command type.

5.4.2.1. Command element structure

The <contact:info> element must declare the contact namespace and schema and it must contain the following child element:

Note

For successful execution of the contact info command with the AuthInfo parameter it is necessary to use the authorization information corresponding to the one in the registry.

Example
<?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.nic.cz/xml/epp/contact-1.6"
    xsi:schemaLocation="http://www.nic.cz/xml/epp/contact-1.6 contact-1.6.2.xsd">
      <contact:id>CID-MYCONTACT</contact:id>
   </contact:info>
</info>
<clTRID>zmge004#17-05-04at12:20:55</clTRID>
</command>
</epp>
FRED-client equivalent
> info_contact CID-MYCONTACT

5.4.2.2. Response element structure

The response from the FRED EPP server contains the result, response data, and transaction identification.

See also Success or failure of a command.

The response data element (<resData>) contains a single child element <contact:infData> which declares the contact namespace and schema and it contains the following child elements:

  • <contact:id> (1) – the contact handle as fredcom:objIDType,

  • <contact:roid> (1) – the contact repository identifier as eppcom:roidType,

  • <contact:status> (1..n) – the contact object state(s):
    • @s (R) – state name as one of values:
      • ok

      • linked

      • serverTransferProhibited

      • serverDeleteProhibited

      • serverUpdateProhibited

      • serverBlocked

      • deleteCandidate

      • conditionallyIdentifiedContact

      • identifiedContact

      • validatedContact

      • mojeidContact

      • serverContactNameChangeProhibited

      • serverContactOrganizationChangeProhibited

      • serverContactIdentChangeProhibited

      • serverContactPermanentAddressChangeProhibited

    • @lang – language of the state description as a xs:language (default: en),

    • element content: the state description as a xs:normalizedString,

  • <contact:postalInfo> (1) – contact’s postal information:
  • <contact:voice> (0..1) – the phone number as contact:e164StringType,

  • <contact:fax> (0..1) – the fax number as contact:e164StringType,

  • <contact:email> (0..1) – a comma-separated list of email addresses as contact:emailCommaListType,

  • <contact:authInfo> (0..1) – the authorization information as fredcom:authInfoType,

    Note

    AuthInfo is displayed only to the designated registrar.

  • <contact:clID> (1) – the designated registrar’s handle as eppcom:clIDType,

  • <contact:crID> (1) – the handle of the registrar who created this contact as eppcom:clIDType,

  • <contact:crDate> (1) – the timestamp of creation as xs:dateTime,

  • <contact:upID> (0..1) – the handle of the registrar who was the last to update this contact as eppcom:clIDType,

  • <contact:upDate> (0..1) – the timestamp of the last update as xs:dateTime,

  • <contact:trDate> (0..1) – the timestamp of the last transfer as xs:dateTime,

  • <contact:disclose> (0..1) – contact information disclosure settings:
    • @flag (R) – disclose flag as a xs:boolean: 0 – listed items are hidden, 1 – listed items are published,

    • <contact:addr/> (0..1) – the address disclosure setting as an empty element,

    • <contact:voice/> (0..1) – the voice disclosure setting as an empty element,

    • <contact:fax/> (0..1) – the fax disclosure setting as an empty element,

    • <contact:email/> (0..1) – the email disclosure setting as an empty element,

    • <contact:vat/> (0..1) – the VAT number disclosure setting as an empty element,

    • <contact:ident/> (0..1) – the identity document disclosure setting as an empty element,

    • <contact:notifyEmail/> (0..1) – the notification email disclosure setting as an empty element,

    Note

    Omitted items must be interpreted according to the server disclosure policy.

    See Policies & rules of disclosure.

  • <contact:vat> (0..1) – the VAT-payer identifier as a contact:vatT,

  • <contact:ident> (0..1) – identity-document identification:
    • @type (R) – the type of the identity document as one of values: op (identity card number), passport (passport number), mpsv (number from the Ministry of Labour and Social Affairs), ico (company number), birthday (the date of birth),

    • element content: the identification number as a contact:identValueT,

  • <contact:notifyEmail> (0..1) – a comma-separated list of email addresses for notification as contact:emailCommaListType.

Example
<?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="1000">
      <msg>Command completed successfully</msg>
   </result>
   <resData>
   <contact:infData xmlns:contact="http://www.nic.cz/xml/epp/contact-1.6"
    xsi:schemaLocation="http://www.nic.cz/xml/epp/contact-1.6 contact-1.6.2.xsd">
      <contact:id>CID-MYCONTACT</contact:id>
      <contact:roid>C0009746170-CZ</contact:roid>
      <contact:status s="linked">Has relation to other records in the registry</contact:status>
      <contact:postalInfo>
         <contact:name>Name Surname</contact:name>
         <contact:addr>
            <contact:street>Street</contact:street>
            <contact:city>City</contact:city>
            <contact:pc>12345</contact:pc>
            <contact:cc>CZ</contact:cc>
         </contact:addr>
      </contact:postalInfo>
      <contact:email>email@example.com</contact:email>
      <contact:clID>REG-MYREG</contact:clID>
      <contact:crID>REG-MYREG</contact:crID>
      <contact:crDate>2017-05-04T11:30:25+02:00</contact:crDate>
      <contact:authInfo>PfLyxPC4</contact:authInfo>
      <contact:disclose flag="1">
         <contact:addr/>
      </contact:disclose>
   </contact:infData>
   </resData>
   <trID>
      <clTRID>zmge004#17-05-04at12:20:55</clTRID>
      <svTRID>ReqID-0000132810</svTRID>
   </trID>
</response>
</epp>

5.4.2.2.1. Mailing address extension

The <contact:infData> element is used in the same way as described above.

The response extension is used to display the mailing address.

The response’s <extension> element must contain a single <extra-addr:infData> element which declares the extra-addr namespace (http://www.nic.cz/xml/epp/extra-addr-1.0) and schema and contains:

Example
<?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="1000">
         <msg>Command completed successfully</msg>
      </result>
      <resData>
         <contact:infData xmlns:contact="http://www.nic.cz/xml/epp/contact-1.6"
          xsi:schemaLocation="http://www.nic.cz/xml/epp/contact-1.6 contact-1.6.2.xsd">
            <contact:id>CID-EXTRAADDR</contact:id>
            <contact:roid>C0000000009-CZ</contact:roid>
            <contact:status s="ok">Object is without restrictions</contact:status>
            <contact:postalInfo>
               <contact:name>Foo Bar</contact:name>
               <contact:addr>
                  <contact:street>Kratka 42</contact:street>
                  <contact:city>Praha</contact:city>
                  <contact:pc>11150</contact:pc>
                  <contact:cc>CZ</contact:cc>
               </contact:addr>
            </contact:postalInfo>
            <contact:voice>+420.000000001</contact:voice>
            <contact:email>foobar@nic.cz</contact:email>
            <contact:clID>REG-FRED_A</contact:clID>
            <contact:crID>REG-FRED_A</contact:crID>
            <contact:crDate>2015-08-25T17:03:11+02:00</contact:crDate>
            <contact:upID>REG-FRED_A</contact:upID>
            <contact:upDate>2015-08-25T17:37:31+02:00</contact:upDate>
            <contact:authInfo>TzInfeuS</contact:authInfo>
            <contact:disclose flag="1">
               <contact:addr/>
            </contact:disclose>
            <contact:notifyEmail>foobar-notify@nic.cz</contact:notifyEmail>
         </contact:infData>
      </resData>
      <extension>
         <extra-addr:infData
          xmlns:extra-addr="http://www.nic.cz/xml/epp/extra-addr-1.0"
          xsi:schemaLocation="http://www.nic.cz/xml/epp/extra-addr-1.0 extra-addr-1.0.0.xsd">
            <extra-addr:mailing>
               <extra-addr:addr>
                  <extra-addr:street>Dlouha 24</extra-addr:street>
                  <extra-addr:city>Lysa nad Labem</extra-addr:city>
                  <extra-addr:pc>28922</extra-addr:pc>
                  <extra-addr:cc>CZ</extra-addr:cc>
               </extra-addr:addr>
            </extra-addr:mailing>
         </extra-addr:infData>
      </extension>
      <trID>
         <clTRID>pmlb002#15-08-26at13:51:12</clTRID>
         <svTRID>ReqID-0000000113</svTRID>
      </trID>
   </response>
</epp>