To review recurring homepage costs, build a service register instead of reading only last month's invoice. Include every dependency that keeps the page reachable, editable, secure, and useful: domain registration, DNS, hosting or platform plans, usage charges, certificates if separately billed, forms, email, analytics, plugins, monitoring, backups, maintenance labor, and support. For each item, record the owner, billing unit, renewal date, current evidence, cancellation effect, and export or transfer path.

Separate the domain from the website platform

A domain and a hosted homepage are different assets even when one vendor sells both. ICANN's registration overview says registration terms, fees, transfers, and renewals are governed by the agreement between the registrant and registrar. Record the legal registrant, registrar, expiration date, renewal price source, account owner, recovery contact, and nameservers.

Do not budget from an introductory price alone. ICANN's expired-registration guidance says registrars must make renewal, post-expiration renewal, and redemption or restore fees reasonably available and send required renewal notices. Verify where those notices go and whether the contact is still controlled by the business.

Identify fixed, usage-based, and optional charges

Mark each service as fixed monthly, fixed annual, usage-based, or one-time. A platform plan may be fixed while bandwidth, requests, storage, form submissions, or email volume varies. Add-ons may be billed separately. Do not mix a free allowance with a guarantee that future use will remain free.

Cloudflare's billing overview is one vendor-specific example: it describes monthly or annual plan cycles, separately billed add-ons, and some usage-based products. Its charge-accrual guidance explains that a request can touch several products with different billing dimensions. Use the equivalent current documentation for each provider in the homepage's actual stack.

Include labor and operational dependencies

Recurring cost is not limited to vendor invoices. Record scheduled content updates, accessibility checks, security updates, form testing, link checks, analytics review, backups, restore drills, and incident response. Estimate internal labor separately from cash expense so a supposedly free tool does not hide a fragile manual process. Identify work that is genuinely optional and work required to keep a customer-facing page accurate or secure.

For subscriptions and plugins, record which page function depends on each one. Ask what happens if it is downgraded or cancelled: Does the form stop, does branding appear, does data become inaccessible, or does only a convenience feature disappear? Keep evidence from the current plan page or invoice rather than relying on memory.

Review ownership and exit cost

For every dependency, confirm a business-controlled account, a recovery method, and a second authorized person or documented continuity plan. Check whether content, form data, analytics, and configuration can be exported in a usable format. Record transfer fees, notice periods, minimum terms, and the time needed to move. Do not cancel a service as part of the review.

Produce a decision-ready cost register

Use one row per service with: purpose, owner, vendor, account identifier without secrets, billing cadence, unit, current charge, variable driver, renewal date, notice period, cancellation effect, export path, evidence date, and next action. Total fixed costs separately from variable scenarios and labor. The result should show what keeps the homepage operating, which costs can change with use, and which dependencies create the largest continuity risk.

Sources

  1. The Domain Name Registration Process — Internet Corporation for Assigned Names and Numbers
  2. 5 Things Every Domain Name Registrant Should Know About ICANN's Expired Registration Recovery Policy — Internet Corporation for Assigned Names and Numbers, Dec. 7, 2018
  3. Expired Registration Recovery Policy — Internet Corporation for Assigned Names and Numbers
  4. Cloudflare Billing Overview — Cloudflare
  5. How Charges Accrue — Cloudflare