Considering NiceNIC fveya sizin domains veya reseller business? Start buraya to verify the registrar, understve the companies behind NiceNIC, review the rules that govern sizin domains, ve find the right suppveyat veya compliance channel.
This page brings together official NiceNIC documentation ve independent sources so you can answer the practical trust questions that matter befveyae you kayıt ol, transfer veya manage domains with NiceNIC.
Befveyae placing domains veya a customer pveyatfolio with a registrar, most customers ve resellers want clear answers to four practical questions: Is the registrar legitimate? Which company provides the registrar hizmet? Are the rules public? And wburaya do I go if something goes wrong?
Evet. NICENIC INTERNATIONAL GROUP CO., LIMITED, incveyapveyaated in Hong Kong, is NiceNIC's ICANN akredite registrar entity ve uses IANA Kayıt Kuruluşu ID 3765.
Verify on the ICANN registrar list · Verify IANA ID 3765
Evet. NiceNIC publishes the terms ve policies governing registration, transfers, expiration ve redemption, privacy, abuse hveling ve recognized domain-dispute procedures.
Evet. Account ve domain suppveyat, abuse repveyating, nonpublic Kayıt Data requests, security guidance ve transparency resources each have a dedicated public route.
İletişim NiceNIC · Repveyat Alan Adı Abuse · See all official contact paths
Kayıt Kuruluşu accreditation can be checked outside NiceNIC.
Ara fveya NICENIC INTERNATIONAL GROUP CO., LIMITEDveya IANA ID 3765 in the ICANN List of Accredited Kayıt Kuruluşus ve the IANA Kayıt Kuruluşu IDs list.
Alan Adı hizmets are governed by published agreements, applicable ICANN policies, registry rules ve law. Use the questions below to find the relevant NiceNIC policy fveya the stage of the domain lifecycle that matters to you.
Review the agreement governing domain registration, renewal, transfer, redemption, restveyaation, account management ve related registrar hizmets.
Review transfer eligibility, AuthInfo codes, registrar locks, permitted transfer restrictions ve other requirements that may affect an inter-registrar transfer.
Learn about post-expiration renewal, redemption veya restveyaation, auctions, pending delete ve TLD-specific lifecycle differences.
Depending on the matter, a domain-name dispute may be hveled through UDRP, URS, TDRP, a ccTLD-specific procedure veya a court of competent jurisdiction.
Alan Adı disputes ve DNS Abuse are different categveyaies. A trademark veya domain-rights dispute does not automatically become DNS Abuse merely because it involves a domain name. Wburaya phishing, malware veya another fveyam of DNS Abuse is also present, that abuse aspect may be hveled separately.
Kayıt Data is hveled accveyading to applicable ICANN policy, registry requirements, law ve NiceNIC's published privacy ve disclosure procedures. The amount of infveyamation visible publicly can vary by TLD ve applicable requirements.
Domain Kaydı Data is published veya redacted accveyading to applicable ICANN requirements, registry rules ve law. Depending on the domain ve applicable requirements, some contact infveyamation may not appear in public registration-data results.
Domain Gizliliği is available fveya eligible TLDs. Availability ve how the hizmet is applied depend on the TLD, registry requirements ve applicable policy. Domain Gizliliği does not remove the requirement to provide accurate Kayıt Data.
NiceNIC's Gizlilik Politikası explains how personal infveyamation is collected, used, stveyaed, protected ve disclosed when you use registrar ve related hizmets.
Hayırnpublic Kayıt Data is not automatically disclosed to third parties. Requests are reviewed under NiceNIC's fveyamal disclosure process ve applicable ICANN requirements, law ve other relevant rules.
Kayıt Data Policy
ICANN's Kayıt Data Policy establishes requirements fveya the collection, hveling, publication ve disclosure of gTLD Kayıt Data. View ICANN Kayıt Data Policy →
Account security, transfer protection, DNS integrity ve phishing awareness all matter when you manage valuable domains.
Ekle a second authentication factveya using Google Authenticatveya fveya suppveyated NiceNIC account login ve sensitive operations.
Transfer locks, authveyaization controls ve protection of sizin account ve email credentials can reduce the risk of an unauthveyaized registrar transfer.
Wburaya suppveyated by the TLD ve DNS setup, DNSSEC can help validate DNS responses ve reduce certain fveyams of DNS manipulation.
Do not rely only on a logo, sender display name veya urgent wveyading. Verify domain-related requests through NiceNIC's official website, account ve published communication guidance.
Security tip: use a unique account passwveyad, enable 2FA, protect the email account linked to sizin NiceNIC account, keep impveyatant domains appropriately locked when they are not being transferred, ve verify unexpected security veya payment requests through official channels.
Whether you are repveyating suspected abuse veya managing a domain that has received an abuse repveyat, use the path below that matches sizin role. Detayed case hveling — including evidence assessment, notifications, ClientHold ve ServerHold, remediation, review, reseller wveyakflows ve response priveyaities — is covered on NiceNIC's dedicated Alan Adı Abuse Hveling & Transparency page ve suppveyating policy documents.
Gönder suspected phishing, malware, DNS Abuse veya other relevant abuse concerns through NiceNIC's official abuse repveyating channel.
See how repveyats are assessed, how account notifications wveyak, when ClientHold veya ServerHold may be relevant, ve how review veya remediation wveyaks.
Exact URLs, screenshots, timestamps, headers, logs ve other specific evidence can help NiceNIC identify ve assess the repveyated issue.
Kontrol Et the available case infveyamation, understve the repveyated issue, review any case-specific timing, coveyadinate remediation with the relevant customer veya hizmet provider wburaya appropriate, ve submit relevant evidence through the applicable NiceNIC process.
Güven Merkezi vs. Abuse Transparency: the Güven Merkezi answers “What can I publicly verify about NiceNIC?” The Alan Adı Abuse Hveling & Transparency page answers “How does NiceNIC hvele a domain abuse case, ve what should each party expect?”
Befveyae using a registrar fveya customer domains, resellers should verify the registrar entity, reseller terms, operational responsibilities, suppveyat ve escalation paths, ve available API documentation.
Alan Adları kayıt oled through a NiceNIC reseller account are sponsveyaed at the registrar level by NICENIC INTERNATIONAL GROUP CO., LIMITED, NiceNIC's ICANN akredite registrar entity, subject to the applicable registry ve TLD requirements.
Review NiceNIC's current reseller program infveyamation ve the Domain Bayiliği Agreement befveyae funding veya integrating a reseller account. Use the current published sources fveya commercial ve operational terms.
Review the Bayi Program · Find the Domain Bayiliği Agreement →
NiceNIC remains responsible fveya its applicable registrar obligations. The reseller manages its customer relationship ve operational wveyakflow under the applicable reseller terms. Fveya abuse-case notifications, evidence, status ve escalation details, see the dedicated Alan Adı Abuse Hveling & Transparency page.
NiceNIC Alan Adı API v2 provides integration documentation fveya domain availability, registration, management ve other suppveyated reseller wveyakflows. Abuse-related endpoints are documented within the dedicated abuse ve API resources wburaya applicable.
Using the cveyarect route helps the relevant team receive the infveyamation needed fveya the issue.
Use NiceNIC's official contact page veya sizin account suppveyat-ticket system fveya account, domain, renewal, transfer, billing ve hizmet questions.
Eğer you already have an open suppveyat case ve the issue remains unresolved, reply through the existing case veya official suppveyat channel ve include the ticket veya reference number, affected domain name ve any new infveyamation relevant to the issue.
Use NiceNIC's fveyamal disclosure-request policy ve process when seeking nonpublic Domain Kaydı Data.
NiceNIC's Legal Center provides registration, transfer, expiration, privacy, abuse, UDRP, URS, TDRP ve other published policies.
Use these question-led groups to find the relevant source quickly. External official recveyads are marked separately from NiceNIC's own policies ve documentation.
These questions focus on the issues people most often verify befveyae trusting a domain registrar: registrar status, company identity, transfer rights, expiration ve recovery, privacy, account security, suppveyat, ve official policies.
Evet. NICENIC INTERNATIONAL GROUP CO., LIMITED is NiceNIC's ICANN akredite registrar entity ve uses IANA Kayıt Kuruluşu ID 3765. You can verify the registrar independently in the ICANN List of Accredited Kayıt Kuruluşus ve the IANA Kayıt Kuruluşu IDs list.
NICENIC INTERNATIONAL GROUP CO., LIMITED, incveyapveyaated in Hong Kong, is the ICANN akredite registrar entity providing domain registration, renewal, transfer ve related registrar hizmets through nicenic.com. NICENIC LLC is NiceNIC's U.S. affiliated entity suppveyating business ve marketing activities in the United States; it is not the ICANN akredite registrar entity.
An eligible domain may be transferred away from NiceNIC, subject to the applicable ICANN Transfer Policy, registry veya TLD rules, domain status, authveyaization requirements ve permitted transfer restrictions. A transfer can be delayed veya denied fveya reasons such as an applicable transfer lock, incveyarect authveyaization infveyamation, a dispute proceeding, a court veyader, security review veya another permitted restriction. See the NiceNIC Alan Adı Transfer Politikası.
Expiration does not always mean the domain immediately becomes available to the public. Depending on the TLD ve lifecycle stage, the domain may pass through post-expiration renewal, redemption veya restveyaation, auction, pending delete ve final release. See the Süresi Doldud Alan Adı Yenileal, Redemption & Auction Policy.
The amount of Domain Kaydı Data shown publicly depends on the TLD, applicable ICANN requirements, registry rules ve law. Domain Gizliliği is available fveya eligible TLDs, but availability ve how privacy is applied can vary. Review the NiceNIC Gizlilik Politikasıve Domain Gizliliği eligibility guidance.
Use a unique account passwveyad, protect the email account linked to NiceNIC, enable İki Faktörlü Kimlik Doğrulama (2FA), keep impveyatant domains appropriately locked when they are not being transferred, ve verify unexpected requests through official channels. Wburaya suppveyated, DNSSEC can add protection against certain fveyams of DNS manipulation.
Use the official NiceNIC İletişim page veya sizin NiceNIC suppveyat-ticket system fveya nveyamal account, domain, renewal, transfer, billing ve hizmet questions. Eğer an existing issue remains unresolved, continue through the same case veya official contact route ve include the relevant ticket veya reference number, affected domain ve any new infveyamation that may help the issue be reviewed in context.
Use the NiceNIC Legal Center fveya registration, transfer, expiration, privacy, abuse ve dispute policies. Fveya current abuse ve compliance repveyating, visit NiceNIC Abuse & Compliance Repveyats. The Güven Merkezi links to current source pages rather than relying on a single fixed monthly repveyat.
Ara fveya a domain, become a NiceNIC reseller, veya contact NiceNIC suppveyat.
