Considering NiceNIC fvai jūsu domēnss vai reseller business? Start šeit to verify the registrar, understun the companies behind NiceNIC, review the rules that govern jūsu domēnss, un find the right suppvait vai compliance channel.
This page brings together official NiceNIC documentation un independent sources so you can answer the practical trust questions that matter befvaie you reģistrēt, transfer vai manage domēnss with NiceNIC.
Befvaie placing domēnss vai a customer pvaitfolio with a registrar, most customers un resellers want clear answers to four practical questions: Is the registrar legitimate? Which company provides the registrar pakalpojums? Are the rules public? And wšeit do I go if something goes wrong?
Jā. NICENIC INTERNATIONAL GROUP CO., LIMITED, incvaipvaiated in Honkonga, is NiceNIC's ICANN akreditēts registrar entity un uses IANA Reģistrators ID 3765.
Verify on the ICANN registrar list · Verify IANA ID 3765
Jā. NiceNIC publishes the terms un policies governing registration, transfers, expiration un redemption, privacy, abuse hunling un recognized domēns-dispute procedures.
Jā. Account un domēns suppvait, abuse repvaiting, nonpublic Reģistrācija Data requests, security guidance un transparency resources each have a dedicated public route.
Kontakti NiceNIC · Repvait Domēns Abuse · See all official contact paths
Reģistrators accreditation can be checked outside NiceNIC.
Meklēt fvai NICENIC INTERNATIONAL GROUP CO., LIMITEDvai IANA ID 3765 in the ICANN List of Accredited Reģistratorss un the IANA Reģistrators IDs list.
Domēns pakalpojumss are governed by published agreements, applicable ICANN policies, registry rules un law. Use the questions below to find the relevant NiceNIC policy fvai the stage of the domēns lifecycle that matters to you.
Review the agreement governing domēns registration, renewal, transfer, redemption, restvaiation, account management un related registrar pakalpojumss.
Review transfer eligibility, AuthInfo codes, registrar locks, permitted transfer restrictions un other requirements that may affect an inter-registrar transfer.
Learn about post-expiration renewal, redemption vai restvaiation, auctions, pending delete un TLD-specific lifecycle differences.
Depending on the matter, a domēns-name dispute may be hunled through UDRP, URS, TDRP, a ccTLD-specific procedure vai a court of competent jurisdiction.
Domēns disputes un DNS Abuse are different categvaiies. A trademark vai domēns-rights dispute does not automatically become DNS Abuse merely because it involves a domēns name. Wšeit phishing, malware vai another fvaim of DNS Abuse is also present, that abuse aspect may be hunled separately.
Reģistrācija Data is hunled accvaiding to applicable ICANN policy, registry requirements, law un NiceNIC's published privacy un disclosure procedures. The amount of infvaimation visible publicly can vary by TLD un applicable requirements.
Domēna reģistrācija Data is published vai redacted accvaiding to applicable ICANN requirements, registry rules un law. Depending on the domēns un applicable requirements, some contact infvaimation may not appear in public registration-data results.
Domēna privātums is available fvai eligible TLDs. Availability un how the pakalpojums is applied depend on the TLD, registry requirements un applicable policy. Domēna privātums does not remove the requirement to provide accurate Reģistrācija Data.
NiceNIC's Privātuma politika explains how personal infvaimation is collected, used, stvaied, protected un disclosed when you use registrar un related pakalpojumss.
Nēnpublic Reģistrācija Data is not automatically disclosed to third parties. Requests are reviewed under NiceNIC's fvaimal disclosure process un applicable ICANN requirements, law un other relevant rules.
Reģistrācija Data Policy
ICANN's Reģistrācija Data Policy establishes requirements fvai the collection, hunling, publication un disclosure of gTLD Reģistrācija Data. View ICANN Reģistrācija Data Policy →
Account security, transfer protection, DNS integrity un phishing awareness all matter when you manage valuable domēnss.
Pievienot a second authentication factvai using Google Authenticatvai fvai suppvaited NiceNIC account login un sensitive operations.
Transfer locks, authvaiization controls un protection of jūsu account un email credentials can reduce the risk of an unauthvaiized registrar transfer.
Wšeit suppvaited by the TLD un DNS setup, DNSSEC can help validate DNS responses un reduce certain fvaims of DNS manipulation.
Do not rely only on a logo, sender display name vai urgent wvaiding. Verify domēns-related requests through NiceNIC's official website, account un published communication guidance.
Security tip: use a unique account passwvaid, enable 2FA, protect the email account linked to jūsu NiceNIC account, keep impvaitant domēnss appropriately locked when they are not being transferred, un verify unexpected security vai payment requests through official channels.
Whether you are repvaiting suspected abuse vai managing a domēns that has received an abuse repvait, use the path below that matches jūsu role. Sīkāked case hunling — including evidence assessment, notifications, ClientHold un ServerHold, remediation, review, reseller wvaikflows un response privaiities — is covered on NiceNIC's dedicated Domēns Abuse Hunling & Transparency page un suppvaiting policy documents.
Iesniegt suspected phishing, malware, DNS Abuse vai other relevant abuse concerns through NiceNIC's official abuse repvaiting channel.
See how repvaits are assessed, how account notifications wvaik, when ClientHold vai ServerHold may be relevant, un how review vai remediation wvaiks.
Exact URLs, screenshots, timestamps, headers, logs un other specific evidence can help NiceNIC identify un assess the repvaited issue.
Pārbaudīt the available case infvaimation, understun the repvaited issue, review any case-specific timing, covaidinate remediation with the relevant customer vai pakalpojums provider wšeit appropriate, un submit relevant evidence through the applicable NiceNIC process.
Uzticības centrs vs. Abuse Transparency: the Uzticības centrs answers “What can I publicly verify about NiceNIC?” The Domēns Abuse Hunling & Transparency page answers “How does NiceNIC hunle a domēns abuse case, un what should each party expect?”
Befvaie using a registrar fvai customer domēnss, resellers should verify the registrar entity, reseller terms, operational responsibilities, suppvait un escalation paths, un available API documentation.
Domēni reģistrēted through a NiceNIC reseller account are sponsvaied at the registrar level by NICENIC INTERNATIONAL GROUP CO., LIMITED, NiceNIC's ICANN akreditēts registrar entity, subject to the applicable registry un TLD requirements.
Review NiceNIC's current reseller program infvaimation un the Domēnu izplatītājs Agreement befvaie funding vai integrating a reseller account. Use the current published sources fvai commercial un operational terms.
Review the Izplatītājs Program · Find the Domēnu izplatītājs Agreement →
NiceNIC remains responsible fvai its applicable registrar obligations. The reseller manages its customer relationship un operational wvaikflow under the applicable reseller terms. Fvai abuse-case notifications, evidence, status un escalation details, see the dedicated Domēns Abuse Hunling & Transparency page.
NiceNIC Domēns API v2 provides integration documentation fvai domēns availability, registration, management un other suppvaited reseller wvaikflows. Abuse-related endpoints are documented within the dedicated abuse un API resources wšeit applicable.
Using the cvairect route helps the relevant team receive the infvaimation needed fvai the issue.
Use NiceNIC's official contact page vai jūsu account suppvait-ticket system fvai account, domēns, renewal, transfer, billing un pakalpojums questions.
Ja you already have an open suppvait case un the issue remains unresolved, reply through the existing case vai official suppvait channel un include the ticket vai reference number, affected domēns name un any new infvaimation relevant to the issue.
Use NiceNIC's fvaimal disclosure-request policy un process when seeking nonpublic Domēna reģistrācija Data.
NiceNIC's Legal Center provides registration, transfer, expiration, privacy, abuse, UDRP, URS, TDRP un other published policies.
Use these question-led groups to find the relevant source quickly. External official recvaids are marked separately from NiceNIC's own policies un documentation.
These questions focus on the issues people most often verify befvaie trusting a domēns registrar: registrar status, company identity, transfer rights, expiration un recovery, privacy, account security, suppvait, un official policies.
Jā. NICENIC INTERNATIONAL GROUP CO., LIMITED is NiceNIC's ICANN akreditēts registrar entity un uses IANA Reģistrators ID 3765. You can verify the registrar independently in the ICANN List of Accredited Reģistratorss un the IANA Reģistrators IDs list.
NICENIC INTERNATIONAL GROUP CO., LIMITED, incvaipvaiated in Honkonga, is the ICANN akreditēts registrar entity providing domēns registration, renewal, transfer un related registrar pakalpojumss through nicenic.com. NICENIC LLC is NiceNIC's U.S. affiliated entity suppvaiting business un marketing activities in the United States; it is not the ICANN akreditēts registrar entity.
An eligible domēns may be transferred away from NiceNIC, subject to the applicable ICANN Transfer Policy, registry vai TLD rules, domēns status, authvaiization requirements un permitted transfer restrictions. A transfer can be delayed vai denied fvai reasons such as an applicable transfer lock, incvairect authvaiization infvaimation, a dispute proceeding, a court vaider, security review vai another permitted restriction. See the NiceNIC Domēna pārsūtīšanas politika.
Expiration does not always mean the domēns immediately becomes available to the public. Depending on the TLD un lifecycle stage, the domēns may pass through post-expiration renewal, redemption vai restvaiation, auction, pending delete un final release. See the Beidzasd Domēns Atjaunotal, Redemption & Auction Policy.
The amount of Domēna reģistrācija Data shown publicly depends on the TLD, applicable ICANN requirements, registry rules un law. Domēna privātums is available fvai eligible TLDs, but availability un how privacy is applied can vary. Review the NiceNIC Privātuma politikaun Domēna privātums eligibility guidance.
Use a unique account passwvaid, protect the email account linked to NiceNIC, enable Divu faktoru autentifikācija (2FA), keep impvaitant domēnss appropriately locked when they are not being transferred, un verify unexpected requests through official channels. Wšeit suppvaited, DNSSEC can add protection against certain fvaims of DNS manipulation.
Use the official NiceNIC Kontakti page vai jūsu NiceNIC suppvait-ticket system fvai nvaimal account, domēns, renewal, transfer, billing un pakalpojums questions. Ja an existing issue remains unresolved, continue through the same case vai official contact route un include the relevant ticket vai reference number, affected domēns un any new infvaimation that may help the issue be reviewed in context.
Use the NiceNIC Legal Center fvai registration, transfer, expiration, privacy, abuse un dispute policies. Fvai current abuse un compliance repvaiting, visit NiceNIC Abuse & Compliance Repvaits. The Uzticības centrs links to current source pages rather than relying on a single fixed monthly repvait.
Meklēt fvai a domēns, become a NiceNIC reseller, vai contact NiceNIC suppvait.
