Cloud hosting is someone else’s computers and a login. DNS is how the name points; a plain explanation is enough: what DNS is. If the lander lives in a cloud account your cousin owns, or in credits that expire, you do not fully control what a buyer sees on the day of the transfer.
This URL still compares cloud plans. It stays. I’m Mostapha; I buy and sell names from Morocco. I have had a “free tier” die during a negotiation. Confirm the registrant with InterNIC WHOIS or ICANN Lookup. Score the letters in the Domain Value Checker before you attach a cloud invoice. FAQ.
Sell the name, not the account
A buyer using escrow wants the registration. They do not want your AWS login. Keep the registrar independent of the host — list of ICANN-accredited registrars is the layer that matters. Push the name; let them point DNS. That split is the same as transfer vs website move.
If the only copy of the lander is inside a locked cloud project, a lapsed card takes the shop window down. Static files on a host you can export, or registrar parking, are enough. What to put on the name: parking, a lander, or a VPS. Price: before you sell.
If you are buying
Do not “keep the seller’s cloud up so traffic continues.” You may inherit billing you cannot access. Get the name, verify Lookup, then point DNS yourself. Checker before you buy. Nameserver stillness: DNS is part of the asset.
When cloud is allowed
You operate a real product on a name you will keep, you can export, 2FA is on both registrar and cloud, and the two logins are not the same password. Then cloud is ordinary infrastructure. It still does not reprice the string. A leftover on Kubernetes is still a leftover.
Decision
- Checker: weak name → no cloud project.
- For sale: lander you can export, registrar you control, and no hostage account.
- Operating a company: cloud if you want, never as the story you tell a domain buyer.
Keep the Google row. The hosting tip that belongs here now is: whoever owns the cloud login must not own your ability to push the domain.