Company Domain & Server Costs: Ownership, Renewals, Handover

In short, a company's own domain typically costs about 1,000 to 5,000 yen a year, and rental server hosting typically costs roughly a few hundred to a few thousand yen a month as of 2026. Those numbers look small on their own, but this contract underpins your company's public face and your email inbox — get the ownership or the renewal management wrong, and your website or email can suddenly stop working. This article walks through typical cost ranges for domains and hosting, then focuses on three pitfalls that non-technical managers and business owners most often trip over: contract ownership, missed renewals, and handover between staff or vendors.

First, it helps to understand that a "domain" and a "rental server" are two separate contracts. A domain, such as "example.co.jp," is your company's address on the internet — essentially a nameplate. A rental server, on the other hand, is the physical storage location — the land and building — where your website data and email actually live. Neither one alone makes your website appear online; both need to be contracted and configured correctly for your site and email to function. Understanding this basic structure makes the ownership and renewal issues discussed below much easier to follow. For a broader look at what website production typically costs, see our guide on typical website production costs.

Domain and hosting costs vary considerably by type. The figures below are general ranges as of 2026 and will vary depending on the specific provider and any ongoing promotions.

One of the most commonly overlooked issues is contract ownership. When a company outsources website production to an outside vendor, it is common for the domain and hosting contracts to be registered under the vendor's own name and email address rather than the client's. This usually causes no visible problem while the vendor is operating normally. But if the vendor goes out of business, the responsible staff member leaves, or the client wants to switch to a different vendor, the client can find itself locked out of its own admin panel — effectively unable to reclaim its own domain or website. If you have lost contact with the company that built your site, our guide on what to do when you can't reach the company that built your site covers concrete next steps, and it's worth checking now if this situation sounds familiar. To avoid this risk, make sure three things sit in your own company's name and your own managed email address: the domain's registrant information, the login credentials for the domain and server admin panels, and the payment card or billing address used for renewals. Take a moment to check your contracts and admin panels to confirm none of these are still resting with your vendor.

Most domain and hosting contracts run on annual terms, either auto-renewing or requiring manual renewal. If the renewal payment fails to go through, your website can suddenly stop displaying, or your company's email can stop sending and receiving without warning. A particularly common trap: even with auto-renewal enabled, if the credit card on file has expired, the payment fails silently and the contract lapses anyway. Once a domain lapses, a third party can register it, and in the worst case you may lose access to that domain name permanently. Build a habit of checking expiration dates at least once a year against a calendar or an internal record, and route renewal notification emails to a shared address that multiple people can see, not just one individual's inbox. For ongoing costs after launch, our guide on typical website maintenance costs is also useful reference.

Rental hosting broadly falls into three types: shared hosting, VPS, and cloud. Three factors typically drive the choice. First is traffic volume — a general corporate site or blog with modest monthly visitors is usually well served by shared hosting. Second is whether you have special requirements, such as running custom systems or wanting configuration isolated from other tenants, in which case VPS or cloud tends to fit better. Third is whether you have someone in-house who can operate it — VPS and cloud offer more flexibility, but that flexibility comes with the responsibility of handling initial server setup and security management yourself, so choosing VPS or cloud without a dedicated staff member or outside maintenance partner can leave the system under-managed. When in doubt, starting with shared hosting and migrating to VPS or cloud as traffic and requirements grow is a safer, staged approach.

Whenever staff responsible for the website change roles or leave, or when you switch vendors or maintenance providers, confirm and record the following items. Missing any of these is a common root cause of the "the site disappeared" or "email stopped arriving" problems described above.

- The domain registrar's name, along with its login ID and password
- Where the AuthCode (the authorization code required to transfer a domain to another registrar) is stored
- A record of the current DNS settings (which server your site and email are pointed to)
- The hosting provider, plan details, and payment method on file
- Where the SSL certificate (which enables encrypted connections to your site) is contracted, and its expiration date
- Email configuration details, including the full list of addresses and mail client connection settings
- Final confirmation that the registrant name and payment card on every contract belong to your company, not a vendor

The money involved in a domain and hosting contract is modest — a few thousand yen a year, a few thousand yen a month at most. But this small contract underpins two things your company depends on every day: your website and your email. Keeping registration in your own company's name, tracking expiration dates with more than one person, and following a checklist whenever staff or vendors change are usually enough to prevent most of the trouble described above. If you're at all unsure about your current setup, start simply: check whether you can log into the admin panel right now, and confirm whose name is actually on the registration.