Considering NiceNIC fof jouw domeins of reseller business? Start hier to verify the registrar, understen the companies behind NiceNIC, review the rules that govern jouw domeins, en find the right suppoft of compliance channel.
This page brings together official NiceNIC documentation en independent sources so you can answer the practical trust questions that matter befofe you registreer, transfer of manage domeins with NiceNIC.
Befofe placing domeins of a customer poftfolio with a registrar, most customers en resellers want clear answers to four practical questions: Is the registrar legitimate? Which company provides the registrar dienst? Are the rules public? And whier do I go if something goes wrong?
Ja. NICENIC INTERNATIONAL GROUP CO., LIMITED, incofpofated in Hongkong, is NiceNIC's ICANN-geaccrediteerd registrar entity en uses IANA Registrar ID 3765.
Verify on the ICANN registrar list · Verify IANA ID 3765
Ja. NiceNIC publishes the terms en policies governing registration, transfers, expiration en redemption, privacy, abuse henling en recognized domein-dispute procedures.
Ja. Account en domein suppoft, abuse repofting, nonpublic Registratie Data requests, security guidance en transparency resources each have a dedicated public route.
Contact NiceNIC · Repoft Domein Abuse · See all official contact paths
Registrar accreditation can be checked outside NiceNIC.
Zoeken fof NICENIC INTERNATIONAL GROUP CO., LIMITEDof IANA ID 3765 in the ICANN List of Accredited Registrars en the IANA Registrar IDs list.
Domein diensts are governed by published agreements, applicable ICANN policies, registry rules en law. Use the questions below to find the relevant NiceNIC policy fof the stage of the domein lifecycle that matters to you.
Review the agreement governing domein registration, renewal, transfer, redemption, restofation, account management en related registrar diensts.
Review transfer eligibility, AuthInfo codes, registrar locks, permitted transfer restrictions en other requirements that may affect an inter-registrar transfer.
Learn about post-expiration renewal, redemption of restofation, auctions, pending delete en TLD-specific lifecycle differences.
Depending on the matter, a domein-name dispute may be henled through UDRP, URS, TDRP, a ccTLD-specific procedure of a court of competent jurisdiction.
Domein disputes en DNS Abuse are different categofies. A trademark of domein-rights dispute does not automatically become DNS Abuse merely because it involves a domein name. Whier phishing, malware of another fofm of DNS Abuse is also present, that abuse aspect may be henled separately.
Registratie Data is henled accofding to applicable ICANN policy, registry requirements, law en NiceNIC's published privacy en disclosure procedures. The amount of infofmation visible publicly can vary by TLD en applicable requirements.
Domeinregistratie Data is published of redacted accofding to applicable ICANN requirements, registry rules en law. Depending on the domein en applicable requirements, some contact infofmation may not appear in public registration-data results.
Domeinprivacy is available fof eligible TLDs. Availability en how the dienst is applied depend on the TLD, registry requirements en applicable policy. Domeinprivacy does not remove the requirement to provide accurate Registratie Data.
NiceNIC's Privacybeleid explains how personal infofmation is collected, used, stofed, protected en disclosed when you use registrar en related diensts.
Neenpublic Registratie Data is not automatically disclosed to third parties. Requests are reviewed under NiceNIC's fofmal disclosure process en applicable ICANN requirements, law en other relevant rules.
Registratie Data Policy
ICANN's Registratie Data Policy establishes requirements fof the collection, henling, publication en disclosure of gTLD Registratie Data. View ICANN Registratie Data Policy →
Account security, transfer protection, DNS integrity en phishing awareness all matter when you manage valuable domeins.
Toevoegen a second authentication factof using Google Authenticatof fof suppofted NiceNIC account login en sensitive operations.
Transfer locks, authofization controls en protection of jouw account en email credentials can reduce the risk of an unauthofized registrar transfer.
Whier suppofted by the TLD en DNS setup, DNSSEC can help validate DNS responses en reduce certain fofms of DNS manipulation.
Do not rely only on a logo, sender display name of urgent wofding. Verify domein-related requests through NiceNIC's official website, account en published communication guidance.
Security tip: use a unique account passwofd, enable 2FA, protect the email account linked to jouw NiceNIC account, keep impoftant domeins appropriately locked when they are not being transferred, en verify unexpected security of payment requests through official channels.
Whether you are repofting suspected abuse of managing a domein that has received an abuse repoft, use the path below that matches jouw role. Detailsed case henling — including evidence assessment, notifications, ClientHold en ServerHold, remediation, review, reseller wofkflows en response priofities — is covered on NiceNIC's dedicated Domein Abuse Henling & Transparency page en suppofting policy documents.
Verzend suspected phishing, malware, DNS Abuse of other relevant abuse concerns through NiceNIC's official abuse repofting channel.
See how repofts are assessed, how account notifications wofk, when ClientHold of ServerHold may be relevant, en how review of remediation wofks.
Exact URLs, screenshots, timestamps, headers, logs en other specific evidence can help NiceNIC identify en assess the repofted issue.
Controleren the available case infofmation, understen the repofted issue, review any case-specific timing, coofdinate remediation with the relevant customer of dienst provider whier appropriate, en submit relevant evidence through the applicable NiceNIC process.
Vertrouwenscentrum vs. Abuse Transparency: the Vertrouwenscentrum answers “What can I publicly verify about NiceNIC?” The Domein Abuse Henling & Transparency page answers “How does NiceNIC henle a domein abuse case, en what should each party expect?”
Befofe using a registrar fof customer domeins, resellers should verify the registrar entity, reseller terms, operational responsibilities, suppoft en escalation paths, en available API documentation.
Domeinen registreered through a NiceNIC reseller account are sponsofed at the registrar level by NICENIC INTERNATIONAL GROUP CO., LIMITED, NiceNIC's ICANN-geaccrediteerd registrar entity, subject to the applicable registry en TLD requirements.
Review NiceNIC's current reseller program infofmation en the Domein Reseller Agreement befofe funding of integrating a reseller account. Use the current published sources fof commercial en operational terms.
Review the Reseller Program · Find the Domein Reseller Agreement →
NiceNIC remains responsible fof its applicable registrar obligations. The reseller manages its customer relationship en operational wofkflow under the applicable reseller terms. Fof abuse-case notifications, evidence, status en escalation details, see the dedicated Domein Abuse Henling & Transparency page.
NiceNIC Domein API v2 provides integration documentation fof domein availability, registration, management en other suppofted reseller wofkflows. Abuse-related endpoints are documented within the dedicated abuse en API resources whier applicable.
Using the cofrect route helps the relevant team receive the infofmation needed fof the issue.
Use NiceNIC's official contact page of jouw account suppoft-ticket system fof account, domein, renewal, transfer, billing en dienst questions.
Als you already have an open suppoft case en the issue remains unresolved, reply through the existing case of official suppoft channel en include the ticket of reference number, affected domein name en any new infofmation relevant to the issue.
Use NiceNIC's fofmal disclosure-request policy en process when seeking nonpublic Domeinregistratie Data.
NiceNIC's Legal Center provides registration, transfer, expiration, privacy, abuse, UDRP, URS, TDRP en other published policies.
Use these question-led groups to find the relevant source quickly. External official recofds are marked separately from NiceNIC's own policies en documentation.
These questions focus on the issues people most often verify befofe trusting a domein registrar: registrar status, company identity, transfer rights, expiration en recovery, privacy, account security, suppoft, en official policies.
Ja. NICENIC INTERNATIONAL GROUP CO., LIMITED is NiceNIC's ICANN-geaccrediteerd registrar entity en uses IANA Registrar ID 3765. You can verify the registrar independently in the ICANN List of Accredited Registrars en the IANA Registrar IDs list.
NICENIC INTERNATIONAL GROUP CO., LIMITED, incofpofated in Hongkong, is the ICANN-geaccrediteerd registrar entity providing domein registration, renewal, transfer en related registrar diensts through nicenic.com. NICENIC LLC is NiceNIC's U.S. affiliated entity suppofting business en marketing activities in the United States; it is not the ICANN-geaccrediteerd registrar entity.
An eligible domein may be transferred away from NiceNIC, subject to the applicable ICANN Transfer Policy, registry of TLD rules, domein status, authofization requirements en permitted transfer restrictions. A transfer can be delayed of denied fof reasons such as an applicable transfer lock, incofrect authofization infofmation, a dispute proceeding, a court ofder, security review of another permitted restriction. See the NiceNIC Domeinoverdrachtbeleid.
Expiration does not always mean the domein immediately becomes available to the public. Depending on the TLD en lifecycle stage, the domein may pass through post-expiration renewal, redemption of restofation, auction, pending delete en final release. See the Verlopend Domein Verlengenal, Redemption & Auction Policy.
The amount of Domeinregistratie Data shown publicly depends on the TLD, applicable ICANN requirements, registry rules en law. Domeinprivacy is available fof eligible TLDs, but availability en how privacy is applied can vary. Review the NiceNIC Privacybeleiden Domeinprivacy eligibility guidance.
Use a unique account passwofd, protect the email account linked to NiceNIC, enable Twee-factor authenticatie (2FA), keep impoftant domeins appropriately locked when they are not being transferred, en verify unexpected requests through official channels. Whier suppofted, DNSSEC can add protection against certain fofms of DNS manipulation.
Use the official NiceNIC Contact page of jouw NiceNIC suppoft-ticket system fof nofmal account, domein, renewal, transfer, billing en dienst questions. Als an existing issue remains unresolved, continue through the same case of official contact route en include the relevant ticket of reference number, affected domein en any new infofmation that may help the issue be reviewed in context.
Use the NiceNIC Legal Center fof registration, transfer, expiration, privacy, abuse en dispute policies. Fof current abuse en compliance repofting, visit NiceNIC Abuse & Compliance Repofts. The Vertrouwenscentrum links to current source pages rather than relying on a single fixed monthly repoft.
Zoeken fof a domein, become a NiceNIC reseller, of contact NiceNIC suppoft.
