A rejection from the .NP registry usually means that something in the application could not be verified or did not comply with the registry policy. The best response is to identify the stated cause, correct the underlying record or document, and submit a consistent request.
The guidance below is based on the official registry’s published common rejection cases.
Domain name and identity do not match
Personal domains should be related to the applicant’s name as shown in an accepted identity document. Company requests need a demonstrable connection to the legal entity, brand, product or service. If that link is not apparent, revise the requested name or provide appropriate documentary evidence. Domains based solely on a surname or caste name may be restricted for personal requests.
Wrong second-level extension
Some extensions are reserved for eligible institutions: for example, .edu.np is for education and .coop.np for cooperatives. Choosing an institutional suffix without meeting its conditions can lead to rejection. Compare the extension rules before applying.
Incorrect or missing nameservers
A nameserver is a domain hostname, not just an IP address. Enter properly configured fully qualified names such as ns1.example.com and ns2.example.com, supplied by your hosting or DNS provider. Do not use the examples literally; replace them with your actual nameservers.
Unreadable or missing documents
Blurred photographs, cropped citizenship scans, missing pages, and incomplete company registration records prevent successful verification. Use clear, complete copies and include every document requested for your specific applicant category. The registry can request additional proof.
Company letterhead, signature or stamp missing
The registry specifically lists missing letterhead, authorized signature, and official company stamp as organization request-letter rejection reasons. A typed draft is not a substitute for formal authorization. Generate the draft using the CodeDeb .NP cover letter tool, print it on the organization’s official letterhead, then complete the required signature and stamp before submission.
Missing applicant details
Double-check your full name, contact email, telephone and other requested information. The registry needs accurate details to verify the application and contact the registrant. Check all fields for consistency with your submitted documents.
A final pre-submission checklist
- The domain name is three or more characters and has a justifiable connection to the applicant.
- The extension matches the type of applicant.
- Nameservers use valid hostnames and are properly configured.
- All identity or organization documents are complete and readable.
- Any required organization letterhead, stamp and authorized signature are present.
- Contact information is complete and accurate.
Submission does not guarantee approval; the registry makes the final eligibility decision. For the full sequence, see how to register a .NP domain.