Register a domain privately and point it at your VPS

When you register a name, your details go into at least two places: the registrar you bought it from, and the registry that operates the TLD. A privacy service changes what the public lookup returns. It changes nothing about those two copies.

There are two structurally different products sold under the same word, and the difference matters more than the price:

• A privacy or proxy service. You remain the legal registrant; the registrar publishes a forwarding contact instead of your details and relays mail to you. Fast, cheap, usually a checkbox. The registrar can withdraw it — on a complaint, on a subpoena, or because its terms allow it.
• A proxy registrant. A third party is recorded as the holder of the name and you hold a contract giving you control of it. Nothing of yours reaches the registry at all. The trade is real: you are not the registrant, so if that company folds, changes policy or decides you are a liability, your claim is a contract dispute rather than a registration you control.

It is also worth knowing what you already have for free. Since 2018, data-protection rules pushed the industry to redact registrant contact details for generic TLDs by default, so a public lookup on a .com held by an individual usually returns “REDACTED FOR PRIVACY” whether or not you paid for anything. The protocol changed too: since January 2025 registrars and registries of generic TLDs are no longer required to answer on the old port-43 WHOIS protocol, and RDAP is the lookup that is actually guaranteed to work. Country-code TLDs set their own rules and some of them publish everything.

So be precise about what you are buying. Registration privacy reliably defeats scrapers, bulk data brokers, spam, and the first search anybody curious runs. It does not defeat the registrar, the registry, a subpoena, or a snapshot someone took of the record before you switched it on.

Think about a domain the way you would think about any dependency: not “is it good” but “who can switch it off, and what do they need in order to do it”. There are three answers.

• The registrar. The fastest by a wide margin. It can apply clientHold, which removes the name from the zone — the domain still exists, still shows as registered, and simply stops resolving anywhere in the world. No court is involved. An acceptable-use clause and a complaint are enough, and some registrars act on the complaint alone.
• The registry. Slower, rarer, heavier. A registry can apply serverHold or block transfers, and there is no registrar you can move to that escapes it, because the registry is the TLD. Every registry sits under a national jurisdiction: the operator of .com and .net answers to the United States, and every country-code TLD answers to its own government or delegate.
• A court, on either side. Ordinary orders, plus the domain-specific route: a trademark dispute filed under the UDRP ends in a decision the registrar is contractually obliged to execute, with no judge and no appeal to a national court unless you start one yourself.

Which reframes the question you should be asking a registrar. Not “do you offer privacy” — almost all of them do. Instead: what do you do when you receive a complaint, and whose law do you have to obey when you do? A registrar that suspends first and asks later has quietly become the weakest link in an otherwise careful setup.

We have our own version of this. This site ran on vpscrypto.io from launch until 29 July 2026, when it became vpscrypto.com — same company, same servers, same accounts, same paths, documented in our about page and in the facts index. The lesson we took from doing it is the one worth passing on: the registrar layer is the part of the stack you control least, and having the move already planned is worth more than any assurance anyone gives you beforehand.

The registry writes the rules. The registrar implements them. A permissive registrar sitting under a strict registry buys you nothing at all, which is why choosing the extension deserves more thought than it usually gets and a great deal more than the first-year price justifies.

Before you fall in love with a name, answer four questions about the extension it ends in:

• Who operates the registry, and where is that company incorporated? This is a public fact and takes one command to check.
• Does the registry publish registrant data, or permit privacy services? Some do not. The .us extension, for example, requires registrant details to be published and does not allow proxy registrations — no registrar can work around that.
• Is there a presence or nexus requirement? .eu needs an EU or EEA connection, .ca needs a Canadian presence, and several European country-codes require a local contact of record if the holder lives elsewhere. These are the opposite of private: they force you to attach a verifiable real-world identity to the name.
• Does the extension carry political risk? Country-code TLDs are tied to territories, and territories change. In 2024 the United Kingdom agreed to transfer sovereignty of the territory behind .io to Mauritius, which put a question mark over an extension tens of thousands of technology companies build on. Retirement of a country-code TLD is a process measured in years rather than weeks, so this is not an emergency — it is a clean illustration of a category of risk that generic TLDs simply do not carry.

Then read the price properly. The number that matters is the renewal, not the first year; a name at $0.99 that renews at $45 is a $45 domain with a discount attached. Check whether privacy is included or billed separately, whether the registrar charges to release a name you want to move, and whether the domain is flagged as premium, because premium names often renew at the premium rate forever.

For most people the honest answer is dull: a legacy generic TLD from a registrar you chose carefully will outlast a clever country-code chosen for the pun.

People fix the registration record and leave the other three wide open. A domain exposes you through four independent channels, and the weakest one sets the level for all of them:

• The registration record — solved by a privacy service or a proxy registrant, as above.
• The payment — a card in your legal name creates a record at the registrar, at the processor, and at your bank, none of which you can redact later.
• The mailbox — the address on the account receives renewal notices, transfer confirmations and password resets. It is both an identifier and the key to the whole thing.
• The access pattern — the address you log in from, and whether that address has ever logged in to anything else of yours.

The field of registrars accepting crypto is much smaller than the field of hosts accepting it, and thinner still for Monero. If you find one, apply the same discipline you would apply to a server: send from a wallet that is not your exchange withdrawal address, and prefer a coin that does not publish a permanent public graph of where the funds came from. Our Monero payment walkthrough covers the mechanics, and buying without a card covers getting there from zero.

If no crypto-accepting registrar fits your requirements, that is a real decision rather than a failure: a card in your name at a registrar with a good policy record may genuinely be the better trade compared with a crypto-friendly registrar that suspends names on the first email it receives. Decide it consciously instead of defaulting into it.

Registration privacy closes one channel. These are the ones that stay open, roughly in order of how often they are the thing that actually connects a name to a person:

• Certificate Transparency. Every publicly trusted TLS certificate is written to public, append-only logs that anyone can search. Issue a certificate for staging.example.com and you have published the existence of that host to the world, permanently. A wildcard certificate avoids enumerating subdomains, but the apex is published either way. If the existence of the domain is the secret, TLS will not keep it.
• Historical registration data. Commercial databases have been archiving lookups for decades. If the name was ever registered with real details — even for an hour, even before you bought it from someone else — that snapshot exists and enabling privacy afterwards does not retract it.
• Shared infrastructure. The same nameservers, the same server IP, the same analytics identifier, the same distinctive favicon across two projects will link them far more reliably than a registration record ever could. Whole-internet scanners index this continuously and it is trivially searchable.
• The registrar’s own correspondence. Renewal notices, invoices and support tickets all land in a mailbox, all name the domain, and all sit on somebody else’s mail server.

The rule that follows is simple and almost impossible to retrofit: one project, one mailbox, one registrar account, one server. Separation is nearly free on the day you start and cannot be bought back afterwards.

Bundling the domain with the hosting is convenient and it merges two failure domains into one. The complaint that reaches your host does not touch the name; the complaint that reaches your registrar does not touch the server — unless both are the same company, in which case one email reaches everything and one compromised password loses everything.

Separation also gives you somewhere to stand during a problem. If the host goes away, the name still resolves and you repoint it at a new server in minutes, which is exactly the drill in our migration guide. If the registrar goes away, the server keeps running and serving on its IP while you sort the name out. Bundled, neither of those recoveries is available.

This is also why we do not sell domains. We are VPS-first: our accounts are no-KYC, need nothing but an address to deliver credentials to, and are paid on chain — and the right shape is for your registrar to be a different company, in a different country, with a different complaint queue. The private hosting walkthrough sets out how the layers fit together.

The cost is honest: two accounts, two renewal dates, two sets of credentials, two places to keep recovery codes. That is the price, and it is a good one.

Not seizure. Not a complaint. A date that passed. For generic TLDs the lifecycle after expiry is fixed and unforgiving:

• Expiry to roughly day 45 — an auto-renew grace period, length at the registrar’s discretion. The name usually stops resolving early in this window even though you can still renew at the normal price.
• Then 30 days of redemption — recoverable, but only by paying a redemption fee that is routinely many times the price of the domain.
• Then 5 days pending delete — nothing can be done at all.
• Then it drops — and if the name has any traffic or inbound links, a drop-catching service will very likely register it in the same second it becomes available.

Anyone paying in crypto is unusually exposed here, because the mechanism that quietly saves everybody else is a card on file. You gave that up deliberately, so replace it deliberately: register for several years at once, keep a balance at the registrar if it supports one, and put the expiry date in a calendar with reminders at 90, 30 and 7 days. Then verify it from outside rather than trusting the panel:

#!/bin/sh
# warn when a domain is within 45 days of expiry
D=example.com
EXP=$(curl -s https://rdap.org/domain/$D | jq -r '.events[] | select(.eventAction=="expiration") | .eventDate')
LEFT=$(( ( $(date -d "$EXP" +%s) - $(date +%s) ) / 86400 ))
[ "$LEFT" -lt 45 ] && echo "$D expires in $LEFT days ($EXP)"

Run it from cron on a machine that is not the one the domain points at. A weekly check costs nothing and removes the single most common way people lose a name they cared about.

Private is not anonymous, and the distinction is not pedantry. Registration privacy raises the cost of casual identification enormously and raises the cost of determined, funded identification barely at all. If what you publish attracts an adversary with subpoena power and patience, the registration record is not the thing that decides how it ends — the payment trail, the mailbox, the access pattern and the content itself all matter more.

It is also worth being clear that a domain is a lease inside somebody else’s namespace, and no registrar choice changes that. The only namespaces with no registrar are the ones with no registry: a Tor onion address is derived from a keypair you generate yourself, so there is nobody to serve an order on and nothing to suspend. The trade is that nobody can type it from memory and an ordinary browser will not open it. Running both is a common and sensible answer — the domain for reach, the onion address for continuity — and our Tor guide and Tor use-case cover that side.

On our own side, so you can calibrate: we run no-KYC servers, we do not action US-style takedown emails as a matter of operational policy rather than legal immunity, we answer court orders in the jurisdictions we operate in, and we keep a hard abuse floor. We do not register domains and we cannot shield one. Anyone telling you a registration is untouchable is selling something.