A domain, hosting package, certificate and cloud licence often support the same business process. Yet four different parties may be responsible, with different contract dates, payments and technical checks. A general reminder to “renew the website” captures only part of this.
A central overview shows which service is needed, who may decide and what could fail when it ends. Deadline management connects commercial information with actual technical operations. The two need to be brought together appropriately.
Record three types of deadline separately
Contract term and cancellation notice period determine when renewal, change or termination must be decided. Payment dates concern billing and the payment method used. Technical validity concerns a certificate or application credential, for example. These events may fall on different dates.
Automatic renewal does not provide general protection against outages: payment details, plan, required scope and the application concerned still need to be correct. Conversely, a technically accessible website does not mean all contractual and organisational matters are settled.
What belongs in the shared overview
For critical business services, first record the actual holder or contracting party and the provider through which the service is managed. A personal account or invoice addressed to an individual should not quietly remain the only link to an important business service.
- Service and purpose: domain, DNS, hosting, certificate, cloud licence, SaaS, external API, payment or, where relevant, consent service; affected website or automation.
- Contract: start, term, agreed renewal, notice period and governing documents.
- Billing: cost and billing period, next payment date, invoice recipient and responsible party; derive comparable annual costs transparently.
- Responsibility: business decision, technical support, deputy and escalation route.
- Operations: reference to protected credential management, dependencies, required lead time, maintenance window and last functional test.
Secrets and complete payment details do not belong in a broadly accessible overview. The inventory instead points to the authorised management system. Knowing who is responsible is different from possessing every credential.
| Service group | Record separately | Technical check |
|---|---|---|
| Domain and DNS | Holder, registrar, contractual route and associated services. | Check resolution and required availability. |
| Hosting and certificate | Package/payment, plus certificate validity and renewal. | Check the service and credential actually delivered. |
| Cloud licence and SaaS | Scope, term, renewal, cancellation and payment. | Check required usage and data access. |
| API and external service | Usage agreement/payment and technical credentials. | Test dependent forms, jobs and integrations. |
Distinguish domains, DNS and hosting
Domain registration, name servers, email and web hosting may be handled by different providers. nic.at explicitly explains this distinction for .at domains. Check all associated services before changing hosting or cancelling a package.
For generic domains, ICANN refers to the agreements with the registrar. .at and other country-code domains may follow different procedures. Take actual deadlines from the governing documents; a general grace or recovery period is not a reliable operating plan. Current holder and contact assignments help important notices reach the right people.
Certificates and licences need their own checks
Automatic certificate renewal is useful, but it must succeed and reach the intended service. Check the certificate actually being served. A newly issued credential in an administration panel alone does not prove the public connection is already using it.
A specific vendor notice: Let’s Encrypt ended its expiry-warning emails on 4 June 2025. Anyone who relied on those messages needs a suitable warning route of their own. The current integration guide covers automatic renewal and ACME Renewal Information. Actual setup and monitoring remain operational responsibilities.
For cloud subscriptions, renewal, access and subsequent states depend on the product and contractual route. Microsoft explicitly describes different lifecycles for business customers. General assumptions about extra usage time after a subscription ends therefore cannot replace a timely decision and verified data transfer.
A warning must lead to a traceable decision
A reminder names the service, impact, action deadline and responsible party. If no answer arrives, involve the deputy or next escalation contact through an agreed process. A shared mailbox without clear ownership does not solve this automatically.
Renewal, provider change or termination must be explicitly decided and documented by the authorised party. A second responsible person is useful for critical actions. Technical implementation follows, with a suitable window and subsequent functional test.
One possible example: a business uses an external consent or integration service. If it becomes unusable or an API payment fails, a website function may be affected, depending on the integration. A dependency overview shows who must make the commercial decision and who must check the function technically. This is hypothetical, not a statement about an existing DAXS customer installation.
Organise deadline management as an agreed operational service
DAXS supports inventory work, technical monitoring and a traceable deadline process. Maintenance and checks can be agreed as a managed operational service. Explicitly record which services are included, who supplies information, what lead times apply and who decides.
A useful starting point is a shared view of the key services and dependencies. The article on API lifetimes and rotation explores technical credentials in more depth. Our cloud and SaaS services and service overview explain the wider scope. You can request an inventory of digital services.
Frequently asked questions
Is enabling automatic renewal enough?
It can handle part of the process. Responsibility, valid payment methods, required scope and actual functionality still need checking.
Does domain expiry also mean hosting ends?
Not necessarily. Registration, DNS, hosting and other services may have separate agreements and responsibilities. Record the actual relationships in the inventory.
Should technical support decide on renewal?
Technical support provides information on impact and effort. The authorised party in the business decides; scope and responsibility are agreed in advance.
Sources: nic.at: domain holders, providers and services (external link) · ICANN: registration and registrar agreement (external link) · Let’s Encrypt: integrating renewal (external link) · Let’s Encrypt: expiry-warning emails ended (external link) · Microsoft: business subscription lifecycle (external link) · OWASP: protected credential management (external link)
The sample overview and procedures are simplified examples. The actual agreements and rules of each service govern; costs, decisions and responsibilities must be checked accordingly.
