Launching a static site starts with securing the right domain name. This guide walks beginners through key steps to compare registrars: creating an account, searching for availability, and ensuring your contact details meet registry rules. You will learn what to check before committing to a provider.
Assuming you are ready to pick a domain name for your new static site
Suppose you are a beginner with a folder of plain HTML files and a short list of name ideas, ready to compare registrars. One workable checklist row would read “Registration period and renewal term,” with columns for what happens after the first year. A second row could read “DNS records provided,” asking whether you can add an A record for the host and a CNAME for the www subdomain without paying extra. A third row could read “Transfer lock and authorization code,” which matters once the site is live and you want the option to move.
Take the candidate names you jotted down: harborlightnotes.site, quietmapjournal.site, and fieldgardenlog.site. These are names an author might assemble for a small writing project, and their spelling is simply how that author recorded them; nothing here says a registrar’s search will return the same results. An example choice: pick quietmapjournal.site over fieldgardenlog.site because the shorter middle word reduces the chance of typos when readers retype the address from a printed card. Write the reason in the row so the decision is traceable later.
A form for each candidate could use these fields: Candidate name; Intended use (one line); Registrar account needed (yes or no); Price shown for year one; Price shown for renewal; DNS editing included; Transfer lock and code availability; Registrar support channel. Two fictional entries show how the form is filled. Entry one: Candidate name quietmapjournal.site; Intended use a photo journal; Registrar account needed yes; Price shown for year one ten credits; Price shown for renewal twenty credits; DNS editing included yes; Transfer lock and code availability yes; Registrar support channel email. Entry two: Candidate name fieldgardenlog.site; Intended use a seasonal planting log; Registrar account needed yes; Price shown for year one eight credits; Price shown for renewal eighteen credits; DNS editing included no, sold separately; Transfer lock and code availability yes; Registrar support channel web form. The two entries differ in DNS inclusion, which is exactly the kind of gap the checklist row is meant to expose.
On links, fix where each one goes before you paste anything into a note: the “terms” link goes to the registrar’s published terms page, the “renewal price” link goes to the registrar’s pricing page, and the “DNS help” link goes to that registrar’s documentation index. Set the channel for each link as the registrar’s own site rather than an aggregator, and do not write a recipient address until you have confirmed one. These examples are only the author’s own working notes for this assumed situation.
Creating your account and providing valid contact information
At Porkbun , step one of registering a domain is creating a Porkbun account. The source states that you will be required to provide valid contact information for your account. This contact information can be masked using Porkbun 's free WHOIS Privacy service, which the source says is enabled by default for any domain that supports it.1
The same source adds a condition: the majority of TLDs allow for WHOIS Privacy, but a few do not, naming .us domains as an example. It advises paying close attention to any warnings displayed during checkout. For a static site, this account step comes before searching for the domain name.1
Before you open any registrar’s sign-up form, you can make a small contact-record sheet for yourself: one row per candidate name, with columns for the contact email you would use, the postal address you are willing to supply, and the name and phone number you would enter as the account holder. Keep the same details consistent across every row, so that later you compare your options on price and features rather than on mismatched information.
You might also draft a short working note for each candidate, such as “FieldGardenLog — admin email: my main inbox; contact address: home address; phone: mobile; keep a copy of every confirmation.” That note is not evidence of anything; it is simply a reminder of what you intend to fill in, so that a form does not become the place where you first decide these details.
Consider keeping the contact email separate from any public-facing address you may later mention on the site. If you plan to publish a contact page, you can choose an address you are comfortable putting online, while keeping the account email private to your registrar record. Both choices are yours; the checklist only asks you to decide before you begin.
When you look at a sign-up form, you can read each field slowly and ask: is this required, optional, or something I should verify from the registrar’s own help pages? Jot the answer beside the field name in your note. If a field asks for information you would rather not supply at sign-up, note that too, and check the registrar’s published policy rather than guessing. Your sheet then holds your decisions, not promises from anyone else, and you can carry the same rows forward when you compare prices or renewal terms.
Searching for your desired domain name using bulk or single options
Porkbun ’s documented flow places search on its Domains page after account sign-up. Under the heading “SEARCH FOR YOUR NEW DOMAIN NAME,” a single name goes into the search bar; for several names, the bulk search option to the right of the bar accepts multiple entries. According to the same page, bulk search supports up to 100 domains and can automatically add all available ones to the cart. After entering the name or names, you select the magnifying glass icon and wait while availability is checked. The resulting search page shows whether the domain is available and recommends other extensions that might fit.1
With your shortlist typed into one plain-text note, you can move from collecting names to querying them in a registrar’s search box. Start with a single candidate instead of the whole list, and copy the exact result string back into your note beside that name. For example, if you search for harborlightnotes.site, note whether the display shows the full name as available, taken, or priced for the first year; then search the next name separately so you can compare each result on its own terms.
If a registrar offers a bulk search, you can paste several candidates at once, one per line, and treat the returned table as a first pass rather than a verdict. Keep your rows in the same order as your note so a “taken” mark on one line does not get attached to the wrong candidate. A worked layout might read: harborlightnotes.site — shown available — first-year price visible; quietmapjournal.site — shown taken — no price; fieldgardenlog.site — shown available — price only in cart. Those are example entries you can replace with what you actually see.
You might also set a rule before searching: if a name returns as taken, you can write it down and move on, or you can check whether a different suffix for the same words still appears open. Decide which of these you prefer, then apply it consistently so your shortlist does not quietly grow during one sitting.
When comparing a single search with a bulk result, consider whether the page states a first-year price separately from a renewal price. If only one number appears, mark that field as unclear in your note rather than assuming it covers later years. That small habit keeps your later registrar comparison anchored to what you observed, not to what you hoped the search would show.
Reviewing included free features like DNS and SSL certificates
Once the search result has told you which names are open, the next question is what a registration actually includes beyond the name itself. That is the moment to compare the free features bundled with each option, because the answer shapes how much extra setup your static site will need later.
| Aspect | NamesLink | Porkbun | Cloudflare |
|---|---|---|---|
| Free DNS and SSL features included with registration | The guide's domain management console covers viewing expiry, renewal or redemption, transfer-out, and editing DNS records; it does not mention free SSL certificates as an included registration feature. | Every registration includes free DNS management powered by Cloudflare , free email forwarding up to 20 addresses per domain, free SSL certificates that automatically renew, free WHOIS privacy on any TLD that allows it, and free URL forwarding. | The guide states that all domains acquired through the registrar use its nameservers automatically and that another DNS provider's nameservers cannot be used while there; the excerpt does not mention free SSL certificates as an included registration feature. |
| Whether free WHOIS privacy is enabled by default at registration | The guide states that domain privacy protection is automatically enabled and can hide registrant information from WHOIS. | The guide states that the free WHOIS Privacy service is enabled by default for any domain that supports it, with warnings shown during checkout for TLDs that do not allow it. | The guide states that personal information is redacted when permitted by the registry and refers readers to its WHOIS redaction page for details. |
Updating contact data to comply with ASCII character requirements
Cloudflare Registrar states that only ASCII characters can be used for contact data at this time. If the default contact has non-ASCII characters, you will need to update the domain contact details before proceeding, and Cloudflare recommends that you update your default contact information to include ASCII characters only. When filling the form, the First Name and Last Name fields each require a minimum of two letters, Email must be a properly formatted email address, and Phone number requires a valid country code selected from the drop-down options, with only numbers accepted in the phone number field. The Ext field accepts only numbers. Address 1 is required and may not be all numeric, while Address 2 is optional. City, State, Country, and Postal Code are required; Country must be selected from the drop-down options, and Postal Code must be properly formatted. Organization is optional for most TLDs. The details entered create all required contacts — Registrant, Admin, Technical, and Billing — and may be updated after registration is completed.3
For each candidate on your shortlist, you can prepare a draft contact line before typing anything into a form: role label, email, and a short note on why that address was chosen. For example, “Admin contact — quietmapjournal@example inbox — used only for account notices” or “Technical contact — fieldgardenlog@example inbox — same person as admin for now.” These are your own working notes, not registrar requirements, and you can revise them once you see what a sign-up form actually asks for.
You might draft both versions of a single value and compare them. As a plain-text note: “Registrant: 陈静, 上海市徐汇区某路 12 号.” As an ASCII-only version you could enter if a field rejects non-ASCII characters: “Registrant: Chen Jing, 12 Some Road, Xuhui District, Shanghai.” The second is a transliteration choice, not a legally certified rendering, so you might keep both lines in your sheet and note which one you expect to use where.
Consider treating accent marks the same way. “Café Notes” can stay as the display name you publish, while the account record might read “Cafe Notes.” You can decide per candidate whether the difference matters to you or whether you would rather pick names that need no adjustment at all.
When a form rejects part of your entry, you can note the exact field, the text you tried, and the ASCII alternative you would accept. That record helps you compare registrars later without retyping guesses, and it keeps your original spelling decisions visible rather than silently overwritten.
Checking WHOIS privacy availability for your chosen TLD
Porkbun 's registration guide states that every domain registration there includes free WHOIS Privacy on any TLD that allows for it. It adds that the service is enabled by default for any domain that supports it, so you can mask the valid contact information required for your account.1
The same source warns that while the majority of TLDs allow WHOIS Privacy, a few do not, giving .us domains as an example. It advises paying close attention to any warnings displayed during checkout.1
You can start a privacy comparison by listing the exact suffix you chose for each candidate, because availability and naming of privacy options often differ from one TLD to the next. In your existing candidate table, add a column headed “Privacy option shown,” and beside harborlightnotes.site write the wording you saw, if any. Do not assume that a privacy line offered for a .com applies to a .site simply because both appear on the same registrar page.
You might then open the registrar’s help or policy text and look for the word “privacy” in the context of registration data, rather than only on the search result screen. Note whether the text names the specific suffix you are considering. Consider a second column, “Where the wording appears,” with values such as search result, checkout step, or help article. If the search result says nothing for quietmapjournal.site but the help article lists that suffix, you can record that gap and decide whether to keep the name on your shortlist for now.
For a candidate such as fieldgardenlog.site, compare how a registrar presents the privacy option at the moment you would register: is it included, offered as a separate line, or only mentioned as something to request later? Write your observation in plain words, for example, “separate line at checkout; no mention in help page.” You can mark each cell as seen, not seen, or unclear. You can also leave the field blank when you have not yet reached that screen.
Keep the table as a personal record for choosing your next step, not as a verdict on any registrar. You can return to it after comparing another suffix or registrar and decide which open questions you want to resolve before picking a name.
Frequently asked questions
What should I do with the names I jotted down before searching at a registrar?
Take the candidate names you jotted down: harborlightnotes.site, quietmapjournal.site, and fieldgardenlog.site. These are names an author might assemble for a small writing project, and their spelling is simply how that author recorded them; nothing here says a registrar’s search will return the same results.
How can I keep a note from a single search from being mistaken for a bulk result?
If a registrar offers a bulk search, you can paste several candidates at once, one per line, and treat the returned table as a first pass rather than a verdict. Keep your rows in the same order as your note so a “taken” mark on one line does not get attached to the wrong candidate.
What can I prepare for each shortlisted candidate before typing contact details into a form?
For each candidate on your shortlist, you can prepare a draft contact line before typing anything into a form: role label, email, and a short note on why that address was chosen. For example, “Admin contact — quietmapjournal@example inbox — used only for account notices” or “Technical contact — fieldgardenlog@example inbox — same person as admin for now.”
How to register a domain at Porkbun - Porkbun Knowledge Base . Retrieved 2026-11-19. ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎
域名注册入门指南 | NamesLink . Retrieved 2026-11-19. ↩︎
Register a new domain · Cloudflare Registrar docs . Retrieved 2026-11-19. ↩︎ ↩︎