Buy .pw Domain Name

No. The registry's own FAQ settles it in one line: anyone in the world can register a .pw name, with no country restriction and no documents required. A company based in Türkiye, a sole trader and a private individual all apply on the same terms. You are not asked to hold an address in Palau, to name a local contact or to appoint a trustee, and no identity document, company registration or trademark certificate is requested. Registration goes through an accredited registrar, and since 25 March 2013 names have been allocated first come, first served. No published cap limits how many names one holder may take.

From one to ten years, in whole-year steps. The lower bound comes from the registry's launch policy, which sets a minimum registration period of one year. The upper bound was measured directly: a name registered on 1 March 2026 showed an expiry of 1 March 2036 the following day, so a full ten years can be taken in a single transaction. Intermediate lengths were observed too, with records running two, three and three and a half years. Renewals are not capped in number; a name opened in 2015 had been extended to 2032. Expiry is timed at 23:59:59 UTC.

The chain works exactly as in a generic extension, and it was measured live. A name is not deleted on its expiry date: it first enters an auto-renew grace period, which ended 41, 42 and 43 days after expiry across three separate records. The name then moves into recovery, stops resolving and is queued for deletion; at the time of measurement those names were still in that stage 47 to 57 days past expiry. In practice: if you forget, ordinary renewal remains open for roughly six weeks, after which a costlier recovery step is possible for a limited further period.

Yes. The registry states IDN support plainly in its FAQ and lists Chinese, Japanese, Arabic, Hebrew, Spanish, Russian and Turkish among the scripts and languages covered. Measurement confirms it: a .pw name written in Chinese and one written in Arabic have both been registered since 3 December 2012, the opening day of the launch, and both carry a normal status. One caveat: the registry separately blocks lookalike names built to be confused with a Latin-script brand. In measurement a Cyrillic name of that kind was refused as contrary to registry policy, while names in other scripts came back clean the same day.

Not through the ordinary queue. The registry's reserved names policy treats every one and two character name as reserved, including all combinations of letters and digits, and the same policy says such names may be released through means other than first-come, first-served registration. That is what happened: on 9 July 2013 the registry announced an auction for single-character .pw names, and they were distributed that way. Both single-letter and two-character names exist in the zone today, and at least one of them is in active use. If you want a short name, plan around the registry's separate allocation route rather than a normal order.

No, the personal fields are redacted by default. The lookup output carries its own footnote stating that the information has been withheld in line with registration data privacy rules. In measurement no record showed a holder name, address, telephone number or email; what appears is the domain name, the dates, the registrar's details and abuse contact, the status codes and the name servers. On top of that the registry permits a separate privacy service, but on one condition: it must be operated by the domain's own sponsoring registrar. You can inspect your record on the whois search page.

The registry writes no separate procedure of its own; it states that it has adopted ICANN's inter-registrar transfer policy. In practice that means the flow you already know from generic extensions: you request the authorisation code from your current provider, have the transfer lock lifted, and hand the code to the new provider. The lock is genuinely used — most of the records measured carried a status code blocking transfer, so nothing starts until it is released. Disputes arising from a transfer fall under ICANN's transfer dispute procedure. You can start on the domain transfer page.

The registry runs an anti-abuse policy with twelve headings, among them intellectual property infringement, spam, phishing, DNS hijacking, malware distribution, botnet command and control, unauthorised access, financial fraud and illegal pharmaceutical sales. A catch-all heading also covers supplying inaccurate registration data. The policy reserves to the registry the discretionary right to deny, cancel, suspend, lock or transfer any registration it considers necessary. That power is not merely on paper: measurement found names still inside their registration term that the registry had taken out of resolution. Keeping your registration details accurate and current therefore matters.