This sounds like a boring administrative question until the day it isn't, usually the day you try to change providers and discover you don't actually control the accounts your business depends on.
The three questions that reveal your real risk
- Whose name is the domain actually registered under, and can you log into that registrar account yourself, right now?
- Who receives the renewal reminder emails, and would anyone notice if a payment failed?
- If your current developer or agency disappeared tomorrow, could you (or anyone) get back in?
If any answer is "I'm not sure," that's the actual problem, not a hypothetical one.
Why this specific thing goes wrong so often
It's genuinely convenient, in the moment, to let a developer register everything under their own account "to make setup easier." It almost always is more convenient, right up until the relationship ends and convenience becomes leverage. This is the single most recurring website horror story across every rescue-guide and forum thread on the topic, for a reason.
What proper ownership looks like
Your domain, registered in your name, in an account you can access directly. Your hosting, in your account, with your billing details. Whoever's helping you, whether that's an agency or a freelancer, works within accounts you own and control, not the reverse.
The uncomfortable audit worth doing today
If you're not certain of the answers above, it costs nothing to check, and it's far easier to fix while the relationship is fine than to discover the problem mid-dispute. This is exactly what "nothing held hostage" should mean in practice, not just as a line in a proposal.
See how domain, hosting and account ownership work under Care →