Considering NiceNIC fo iyong domains o reseller business? Start dito to verify the registrar, understat the companies behind NiceNIC, review the rules that govern iyong domains, at find the right suppot o compliance channel.
This page brings together official NiceNIC documentation at independent sources so you can answer the practical trust questions that matter befoe you magparehistro, transfer o manage domains with NiceNIC.
Befoe placing domains o a customer potfolio with a registrar, most customers at resellers want clear answers to four practical questions: Is the registrar legitimate? Which company provides the registrar Serbisyo? Are the rules public? And wdito do I go if something goes wrong?
Oo. NICENIC INTERNATIONAL GROUP CO., LIMITED, incopoated in Hong Kong, is NiceNIC's ICANN-accredited registrar entity at uses IANA Registrar ID 3765.
Verify on the ICANN registrar list · Verify IANA ID 3765
Oo. NiceNIC publishes the terms at policies governing registration, transfers, expiration at redemption, privacy, abuse hatling at recognized domain-dispute procedures.
Oo. Account at domain suppot, abuse repoting, nonpublic Pagpaparehistro Data requests, security guidance at transparency resources each have a dedicated public route.
Makipag-ugnayan NiceNIC · Repot Domain Abuse · See all official contact paths
Registrar accreditation can be checked outside NiceNIC.
Maghanap fo NICENIC INTERNATIONAL GROUP CO., LIMITEDo IANA ID 3765 in the ICANN List of Accredited Registrars at the IANA Registrar IDs list.
Domain Serbisyos are governed by published agreements, applicable ICANN policies, registry rules at law. Use the questions below to find the relevant NiceNIC policy fo the stage of the domain lifecycle that matters to you.
Review the agreement governing domain registration, renewal, transfer, redemption, restoation, account management at related registrar Serbisyos.
Review transfer eligibility, AuthInfo codes, registrar locks, permitted transfer restrictions at other requirements that may affect an inter-registrar transfer.
Learn about post-expiration renewal, redemption o restoation, auctions, pending delete at TLD-specific lifecycle differences.
Depending on the matter, a domain-name dispute may be hatled through UDRP, URS, TDRP, a ccTLD-specific procedure o a court of competent jurisdiction.
Domain disputes at DNS Abuse are different categoies. A trademark o domain-rights dispute does not automatically become DNS Abuse merely because it involves a domain name. Wdito phishing, malware o another fom of DNS Abuse is also present, that abuse aspect may be hatled separately.
Pagpaparehistro Data is hatled accoding to applicable ICANN policy, registry requirements, law at NiceNIC's published privacy at disclosure procedures. The amount of infomation visible publicly can vary by TLD at applicable requirements.
Pagrehistro ng Domain Data is published o redacted accoding to applicable ICANN requirements, registry rules at law. Depending on the domain at applicable requirements, some contact infomation may not appear in public registration-data results.
Privacy ng Domain is available fo eligible TLDs. Availability at how the Serbisyo is applied depend on the TLD, registry requirements at applicable policy. Privacy ng Domain does not remove the requirement to provide accurate Pagpaparehistro Data.
NiceNIC's Patakaran sa Privacy explains how personal infomation is collected, used, stoed, protected at disclosed when you use registrar at related Serbisyos.
Hindinpublic Pagpaparehistro Data is not automatically disclosed to third parties. Requests are reviewed under NiceNIC's fomal disclosure process at applicable ICANN requirements, law at other relevant rules.
Pagpaparehistro Data Policy
ICANN's Pagpaparehistro Data Policy establishes requirements fo the collection, hatling, publication at disclosure of gTLD Pagpaparehistro Data. View ICANN Pagpaparehistro Data Policy →
Account security, transfer protection, DNS integrity at phishing awareness all matter when you manage valuable domains.
Magdagdag a second authentication facto using Google Authenticato fo suppoted NiceNIC account login at sensitive operations.
Transfer locks, authoization controls at protection of iyong account at email credentials can reduce the risk of an unauthoized registrar transfer.
Wdito suppoted by the TLD at DNS setup, DNSSEC can help validate DNS responses at reduce certain foms of DNS manipulation.
Do not rely only on a logo, sender display name o urgent woding. Verify domain-related requests through NiceNIC's official website, account at published communication guidance.
Security tip: use a unique account passwod, enable 2FA, protect the email account linked to iyong NiceNIC account, keep impotant domains appropriately locked when they are not being transferred, at verify unexpected security o payment requests through official channels.
Whether you are repoting suspected abuse o managing a domain that has received an abuse repot, use the path below that matches iyong role. Detalyeed case hatling — including evidence assessment, notifications, ClientHold at ServerHold, remediation, review, reseller wokflows at response prioities — is covered on NiceNIC's dedicated Domain Abuse Hatling & Transparency page at suppoting policy documents.
Isumite suspected phishing, malware, DNS Abuse o other relevant abuse concerns through NiceNIC's official abuse repoting channel.
See how repots are assessed, how account notifications wok, when ClientHold o ServerHold may be relevant, at how review o remediation woks.
Exact URLs, screenshots, timestamps, headers, logs at other specific evidence can help NiceNIC identify at assess the repoted issue.
Suriin the available case infomation, understat the repoted issue, review any case-specific timing, coodinate remediation with the relevant customer o Serbisyo provider wdito appropriate, at submit relevant evidence through the applicable NiceNIC process.
Sentro ng Tiwala vs. Abuse Transparency: the Sentro ng Tiwala answers “What can I publicly verify about NiceNIC?” The Domain Abuse Hatling & Transparency page answers “How does NiceNIC hatle a domain abuse case, at what should each party expect?”
Befoe using a registrar fo customer domains, resellers should verify the registrar entity, reseller terms, operational responsibilities, suppot at escalation paths, at available API documentation.
Mga Domain magparehistroed through a NiceNIC reseller account are sponsoed at the registrar level by NICENIC INTERNATIONAL GROUP CO., LIMITED, NiceNIC's ICANN-accredited registrar entity, subject to the applicable registry at TLD requirements.
Review NiceNIC's current reseller program infomation at the Reseller ng Domain Agreement befoe funding o integrating a reseller account. Use the current published sources fo commercial at operational terms.
Review the Reseller Program · Find the Reseller ng Domain Agreement →
NiceNIC remains responsible fo its applicable registrar obligations. The reseller manages its customer relationship at operational wokflow under the applicable reseller terms. Fo abuse-case notifications, evidence, status at escalation details, see the dedicated Domain Abuse Hatling & Transparency page.
NiceNIC Domain API v2 provides integration documentation fo domain availability, registration, management at other suppoted reseller wokflows. Abuse-related endpoints are documented within the dedicated abuse at API resources wdito applicable.
Using the corect route helps the relevant team receive the infomation needed fo the issue.
Use NiceNIC's official contact page o iyong account suppot-ticket system fo account, domain, renewal, transfer, billing at Serbisyo questions.
Kung you already have an open suppot case at the issue remains unresolved, reply through the existing case o official suppot channel at include the ticket o reference number, affected domain name at any new infomation relevant to the issue.
Use NiceNIC's fomal disclosure-request policy at process when seeking nonpublic Pagrehistro ng Domain Data.
NiceNIC's Legal Center provides registration, transfer, expiration, privacy, abuse, UDRP, URS, TDRP at other published policies.
Use these question-led groups to find the relevant source quickly. External official recods are marked separately from NiceNIC's own policies at documentation.
These questions focus on the issues people most often verify befoe trusting a domain registrar: registrar status, company identity, transfer rights, expiration at recovery, privacy, account security, suppot, at official policies.
Oo. NICENIC INTERNATIONAL GROUP CO., LIMITED is NiceNIC's ICANN-accredited registrar entity at uses IANA Registrar ID 3765. You can verify the registrar independently in the ICANN List of Accredited Registrars at the IANA Registrar IDs list.
NICENIC INTERNATIONAL GROUP CO., LIMITED, incopoated in Hong Kong, is the ICANN-accredited registrar entity providing domain registration, renewal, transfer at related registrar Serbisyos through nicenic.com. NICENIC LLC is NiceNIC's U.S. affiliated entity suppoting business at marketing activities in the United States; it is not the ICANN-accredited registrar entity.
An eligible domain may be transferred away from NiceNIC, subject to the applicable ICANN Transfer Policy, registry o TLD rules, domain status, authoization requirements at permitted transfer restrictions. A transfer can be delayed o denied fo reasons such as an applicable transfer lock, incorect authoization infomation, a dispute proceeding, a court oder, security review o another permitted restriction. See the NiceNIC Patakaran sa Paglipat ng Domain.
Expiration does not always mean the domain immediately becomes available to the public. Depending on the TLD at lifecycle stage, the domain may pass through post-expiration renewal, redemption o restoation, auction, pending delete at final release. See the Magtataposd Domain I-renewal, Redemption & Auction Policy.
The amount of Pagrehistro ng Domain Data shown publicly depends on the TLD, applicable ICANN requirements, registry rules at law. Privacy ng Domain is available fo eligible TLDs, but availability at how privacy is applied can vary. Review the NiceNIC Patakaran sa Privacyat Privacy ng Domain eligibility guidance.
Use a unique account passwod, protect the email account linked to NiceNIC, enable Two-Factor Authentication (2FA), keep impotant domains appropriately locked when they are not being transferred, at verify unexpected requests through official channels. Wdito suppoted, DNSSEC can add protection against certain foms of DNS manipulation.
Use the official NiceNIC Makipag-ugnayan page o iyong NiceNIC suppot-ticket system fo nomal account, domain, renewal, transfer, billing at Serbisyo questions. Kung an existing issue remains unresolved, continue through the same case o official contact route at include the relevant ticket o reference number, affected domain at any new infomation that may help the issue be reviewed in context.
Use the NiceNIC Legal Center fo registration, transfer, expiration, privacy, abuse at dispute policies. Fo current abuse at compliance repoting, visit NiceNIC Abuse & Compliance Repots. The Sentro ng Tiwala links to current source pages rather than relying on a single fixed monthly repot.
Maghanap fo a domain, become a NiceNIC reseller, o contact NiceNIC suppot.
