Considering NiceNIC fvõi sinu domeens või reseller business? Start siin to verify the registrar, understja the companies behind NiceNIC, review the rules that govern sinu domeens, ja find the right suppvõit või compliance channel.
This page brings together official NiceNIC documentation ja independent sources so you can answer the practical trust questions that matter befvõie you registreeri, transfer või manage domeens with NiceNIC.
Befvõie placing domeens või a customer pvõitfolio with a registrar, most customers ja resellers want clear answers to four practical questions: Is the registrar legitimate? Which company provides the registrar teenus? Are the rules public? And wsiin do I go if something goes wrong?
Jah. NICENIC INTERNATIONAL GROUP CO., LIMITED, incvõipvõiated in Hongkong, is NiceNIC's ICANN-i akrediteeritud registrar entity ja uses IANA Registripidaja ID 3765.
Verify on the ICANN registrar list · Verify IANA ID 3765
Jah. NiceNIC publishes the terms ja policies governing registration, transfers, expiration ja redemption, privacy, abuse hjaling ja recognized domeen-dispute procedures.
Jah. Account ja domeen suppvõit, abuse repvõiting, nonpublic Registreerimine Data requests, security guidance ja transparency resources each have a dedicated public route.
Kontakt NiceNIC · Repvõit Domeen Abuse · See all official contact paths
Registripidaja accreditation can be checked outside NiceNIC.
Otsi fvõi NICENIC INTERNATIONAL GROUP CO., LIMITEDvõi IANA ID 3765 in the ICANN List of Accredited Registripidajas ja the IANA Registripidaja IDs list.
Domeen teenuss are governed by published agreements, applicable ICANN policies, registry rules ja law. Use the questions below to find the relevant NiceNIC policy fvõi the stage of the domeen lifecycle that matters to you.
Review the agreement governing domeen registration, renewal, transfer, redemption, restvõiation, account management ja related registrar teenuss.
Review transfer eligibility, AuthInfo codes, registrar locks, permitted transfer restrictions ja other requirements that may affect an inter-registrar transfer.
Learn about post-expiration renewal, redemption või restvõiation, auctions, pending delete ja TLD-specific lifecycle differences.
Depending on the matter, a domeen-name dispute may be hjaled through UDRP, URS, TDRP, a ccTLD-specific procedure või a court of competent jurisdiction.
Domeen disputes ja DNS Abuse are different categvõiies. A trademark või domeen-rights dispute does not automatically become DNS Abuse merely because it involves a domeen name. Wsiin phishing, malware või another fvõim of DNS Abuse is also present, that abuse aspect may be hjaled separately.
Registreerimine Data is hjaled accvõiding to applicable ICANN policy, registry requirements, law ja NiceNIC's published privacy ja disclosure procedures. The amount of infvõimation visible publicly can vary by TLD ja applicable requirements.
Domeeni registreerimine Data is published või redacted accvõiding to applicable ICANN requirements, registry rules ja law. Depending on the domeen ja applicable requirements, some contact infvõimation may not appear in public registration-data results.
Domeeni privaatsus is available fvõi eligible TLDs. Availability ja how the teenus is applied depend on the TLD, registry requirements ja applicable policy. Domeeni privaatsus does not remove the requirement to provide accurate Registreerimine Data.
NiceNIC's Privaatsuspoliitika explains how personal infvõimation is collected, used, stvõied, protected ja disclosed when you use registrar ja related teenuss.
Einpublic Registreerimine Data is not automatically disclosed to third parties. Requests are reviewed under NiceNIC's fvõimal disclosure process ja applicable ICANN requirements, law ja other relevant rules.
Registreerimine Data Policy
ICANN's Registreerimine Data Policy establishes requirements fvõi the collection, hjaling, publication ja disclosure of gTLD Registreerimine Data. View ICANN Registreerimine Data Policy →
Account security, transfer protection, DNS integrity ja phishing awareness all matter when you manage valuable domeens.
Lisa a second authentication factvõi using Google Authenticatvõi fvõi suppvõited NiceNIC account login ja sensitive operations.
Transfer locks, authvõiization controls ja protection of sinu account ja email credentials can reduce the risk of an unauthvõiized registrar transfer.
Wsiin suppvõited by the TLD ja DNS setup, DNSSEC can help validate DNS responses ja reduce certain fvõims of DNS manipulation.
Do not rely only on a logo, sender display name või urgent wvõiding. Verify domeen-related requests through NiceNIC's official website, account ja published communication guidance.
Security tip: use a unique account passwvõid, enable 2FA, protect the email account linked to sinu NiceNIC account, keep impvõitant domeens appropriately locked when they are not being transferred, ja verify unexpected security või payment requests through official channels.
Whether you are repvõiting suspected abuse või managing a domeen that has received an abuse repvõit, use the path below that matches sinu role. Detailed case hjaling — including evidence assessment, notifications, ClientHold ja ServerHold, remediation, review, reseller wvõikflows ja response privõiities — is covered on NiceNIC's dedicated Domeen Abuse Hjaling & Transparency page ja suppvõiting policy documents.
Esita suspected phishing, malware, DNS Abuse või other relevant abuse concerns through NiceNIC's official abuse repvõiting channel.
See how repvõits are assessed, how account notifications wvõik, when ClientHold või ServerHold may be relevant, ja how review või remediation wvõiks.
Exact URLs, screenshots, timestamps, headers, logs ja other specific evidence can help NiceNIC identify ja assess the repvõited issue.
Kontrolli the available case infvõimation, understja the repvõited issue, review any case-specific timing, covõidinate remediation with the relevant customer või teenus provider wsiin appropriate, ja submit relevant evidence through the applicable NiceNIC process.
Usalduskeskus vs. Abuse Transparency: the Usalduskeskus answers “What can I publicly verify about NiceNIC?” The Domeen Abuse Hjaling & Transparency page answers “How does NiceNIC hjale a domeen abuse case, ja what should each party expect?”
Befvõie using a registrar fvõi customer domeens, resellers should verify the registrar entity, reseller terms, operational responsibilities, suppvõit ja escalation paths, ja available API documentation.
Domeenid registreeried through a NiceNIC reseller account are sponsvõied at the registrar level by NICENIC INTERNATIONAL GROUP CO., LIMITED, NiceNIC's ICANN-i akrediteeritud registrar entity, subject to the applicable registry ja TLD requirements.
Review NiceNIC's current reseller program infvõimation ja the Domeenide edasimüüja Agreement befvõie funding või integrating a reseller account. Use the current published sources fvõi commercial ja operational terms.
Review the Järelmüüja Program · Find the Domeenide edasimüüja Agreement →
NiceNIC remains responsible fvõi its applicable registrar obligations. The reseller manages its customer relationship ja operational wvõikflow under the applicable reseller terms. Fvõi abuse-case notifications, evidence, status ja escalation details, see the dedicated Domeen Abuse Hjaling & Transparency page.
NiceNIC Domeen API v2 provides integration documentation fvõi domeen availability, registration, management ja other suppvõited reseller wvõikflows. Abuse-related endpoints are documented within the dedicated abuse ja API resources wsiin applicable.
Using the cvõirect route helps the relevant team receive the infvõimation needed fvõi the issue.
Use NiceNIC's official contact page või sinu account suppvõit-ticket system fvõi account, domeen, renewal, transfer, billing ja teenus questions.
Kui you already have an open suppvõit case ja the issue remains unresolved, reply through the existing case või official suppvõit channel ja include the ticket või reference number, affected domeen name ja any new infvõimation relevant to the issue.
Use NiceNIC's fvõimal disclosure-request policy ja process when seeking nonpublic Domeeni registreerimine Data.
NiceNIC's Legal Center provides registration, transfer, expiration, privacy, abuse, UDRP, URS, TDRP ja other published policies.
Use these question-led groups to find the relevant source quickly. External official recvõids are marked separately from NiceNIC's own policies ja documentation.
These questions focus on the issues people most often verify befvõie trusting a domeen registrar: registrar status, company identity, transfer rights, expiration ja recovery, privacy, account security, suppvõit, ja official policies.
Jah. NICENIC INTERNATIONAL GROUP CO., LIMITED is NiceNIC's ICANN-i akrediteeritud registrar entity ja uses IANA Registripidaja ID 3765. You can verify the registrar independently in the ICANN List of Accredited Registripidajas ja the IANA Registripidaja IDs list.
NICENIC INTERNATIONAL GROUP CO., LIMITED, incvõipvõiated in Hongkong, is the ICANN-i akrediteeritud registrar entity providing domeen registration, renewal, transfer ja related registrar teenuss through nicenic.com. NICENIC LLC is NiceNIC's U.S. affiliated entity suppvõiting business ja marketing activities in the United States; it is not the ICANN-i akrediteeritud registrar entity.
An eligible domeen may be transferred away from NiceNIC, subject to the applicable ICANN Transfer Policy, registry või TLD rules, domeen status, authvõiization requirements ja permitted transfer restrictions. A transfer can be delayed või denied fvõi reasons such as an applicable transfer lock, incvõirect authvõiization infvõimation, a dispute proceeding, a court võider, security review või another permitted restriction. See the NiceNIC Domeeni ülekande poliitikaga.
Expiration does not always mean the domeen immediately becomes available to the public. Depending on the TLD ja lifecycle stage, the domeen may pass through post-expiration renewal, redemption või restvõiation, auction, pending delete ja final release. See the Aegubd Domeen Uuendaal, Redemption & Auction Policy.
The amount of Domeeni registreerimine Data shown publicly depends on the TLD, applicable ICANN requirements, registry rules ja law. Domeeni privaatsus is available fvõi eligible TLDs, but availability ja how privacy is applied can vary. Review the NiceNIC Privaatsuspoliitikaja Domeeni privaatsus eligibility guidance.
Use a unique account passwvõid, protect the email account linked to NiceNIC, enable Kahefaktoriline autentimine (2FA), keep impvõitant domeens appropriately locked when they are not being transferred, ja verify unexpected requests through official channels. Wsiin suppvõited, DNSSEC can add protection against certain fvõims of DNS manipulation.
Use the official NiceNIC Kontakt page või sinu NiceNIC suppvõit-ticket system fvõi nvõimal account, domeen, renewal, transfer, billing ja teenus questions. Kui an existing issue remains unresolved, continue through the same case või official contact route ja include the relevant ticket või reference number, affected domeen ja any new infvõimation that may help the issue be reviewed in context.
Use the NiceNIC Legal Center fvõi registration, transfer, expiration, privacy, abuse ja dispute policies. Fvõi current abuse ja compliance repvõiting, visit NiceNIC Abuse & Compliance Repvõits. The Usalduskeskus links to current source pages rather than relying on a single fixed monthly repvõit.
Otsi fvõi a domeen, become a NiceNIC reseller, või contact NiceNIC suppvõit.
