> For the complete documentation index, see [llms.txt](https://cyberpassion.gitbook.io/internal-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cyberpassion.gitbook.io/internal-docs/ernet-documentation/introduction.md).

# Introduction

#### **Letter of Undertaking**

A Letter of Undertaking (LoU) must be submitted on the official letterhead of the organization. This document serves as a declaration that all information provided for domain registration is true and authentic.

#### Purpose:

• Declaration of authenticity of information\
• Acceptance of domain registration terms and conditions\
• Confirmation of authorized usage of the domain name

#### **Application Letter** 

An Application Letter must be submitted on the official organization letterhead and signed by the competent authority.

#### Purpose:

• Formal request for domain registration\
• Identification of the applicant organization\
• Authorization for domain ownership

#### **Availability During Office Hours**

* Every employee must remain properly available during office timing (9 AM to 5 PM).
* Employees should respond to calls, office groups, chats, and work-related messages on time.
* Long unavailability without information will not be accepted.

#### **Important Note:**

The application letter should be uploaded only on the official letterhead of the organization. Applications submitted without letterhead may not be approved.

#### **Letter of Appointment of Administrator**

This document authorizes a designated administrator who will be responsible for managing the domain, DNS records, and technical communication.

#### Information Required:

• Name of Administrator\
• Designation\
• Email Address\
• Mobile Number\
• Official Authorization

A valid registration certificate proving the legal existence of the organization must be submitted.

#### Examples:

• Society Registration Certificate\
• Trust Registration Certificate\
• Company Incorporation Certificate\
• Government Establishment Order\
• Institution Registration Certificate

#### Purpose:

• Verification of legal identity\
• Ownership validation of the domain name

#### **Affiliation Letter**

Educational institutions must submit a valid affiliation or recognition letter issued by the competent authority.

#### Purpose:

• Verification of institutional status\
• Eligibility confirmation for educational domain registration

#### Examples:

• University Affiliation Letter\
• AICTE Approval Letter\
• UGC Recognition Letter\
• NMC Approval Letter\
• Board Affiliation Certificate

#### **Address Proof**

A valid address proof of the organization is required to verify the official location of the institution.

#### Acceptable Documents:

• Electricity Bill\
• Telephone Bill\
• Government Address Certificate\
• Rent Agreement\
• Property Tax Receipt\
• Official Government Correspondence

#### Purpose:

• Verification of physical address\
• Organizational authenticity confirmation

####


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cyberpassion.gitbook.io/internal-docs/ernet-documentation/introduction.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.