Domain Expiration & Recovery Policy

The purpose of this Policy is to help Customers understand:

• domain expiration dates.
• renewal reminders.
• automatic renewal.
• manual renewal.
• what happens when a domain expires.
• post-expiration renewal.
• DNS interruption.
• website and email interruption.
• renewal grace periods.
• Redemption Grace Period.
• restoration fees.
• Pending Delete.
• permanent deletion.
• re-registration risk.
• differences between domain extensions; and
• Hostwover's role as a domain-service reseller.

This Policy applies to domain names purchased, renewed, transferred, or otherwise managed through Hostwover.

The precise expiration and recovery process may vary according to:

• the top-level domain ("TLD").
• registry.
• Sponsoring Registrar.
• upstream provider.
• domain status.
• applicable policy.
• applicable law; and
• circumstances affecting the registration.

Hostwover may provide domain-registration services through an upstream registrar or domain-services provider.

Hostwover is not necessarily the ICANN-accredited registrar or registry operator for domains purchased through Hostwover.

Certain expiration, deletion, restoration, and recovery actions are therefore controlled by the Sponsoring Registrar or registry.

The Sponsoring Registrar is the registrar responsible for the domain registration at the applicable registry.

The Sponsoring Registrar may control actions including:

• renewal submission.
• deletion.
• redemption requests.
• restoration.
• registrar-level status changes; and
• certain post-expiration procedures.

Hostwover may submit eligible requests to the Sponsoring Registrar on behalf of the Customer.

A registry operates the database for a particular top-level domain.

Registry rules may determine:

• registration periods.
• expiration behavior.
• redemption availability.
• redemption duration.
• deletion processes.
• restoration requirements; and
• when a deleted domain becomes available for registration again.

The Customer is ultimately responsible for ensuring that a domain it wishes to keep is renewed before expiration.

Hostwover may provide:

• renewal notices.
• dashboard notifications.
• automatic-renewal functionality.
• billing reminders; and
• other assistance.

These tools do not remove the Customer's responsibility to monitor and renew the domain.

A domain registration exists for a limited registration term.

The expiration date represents the end of the current registration period unless the domain is successfully renewed.

Customers should not assume that purchasing hosting, email, VPS, Google Workspace, or another Hostwover Service automatically renews the associated domain.

The registration period available for a domain depends on the applicable TLD and registry.

Some domains may permit multi-year registration, while others may impose different restrictions.

The registration period confirmed in the Customer's order controls the purchased term.

A domain must generally be renewed for an additional registration period if the Customer wishes to retain it beyond its current expiration date.

Renewal becomes effective only after the renewal has been successfully:

• paid.
• accepted.
• submitted; and
• completed by the applicable provider.

Customers are strongly encouraged to renew domains before their expiration date.

Renewing before expiration reduces the risk of:

• website interruption.
• email interruption.
• DNS interruption.
• restoration fees.
• loss of the domain; and
• disruption to services that depend on the domain.

For gTLD registrations subject to ICANN's Expired Registration Recovery Policy ("ERRP"), applicable registrar procedures include expiration reminders approximately:

• one month before expiration; and
• one week before expiration.

If an eligible registration remains unrenewed after expiration, an additional notice may be required within five days after expiration.

ICANN currently treats notices sent between 26–35 days and 4–10 days before expiration as compliant with the respective approximate pre-expiration timing requirements.

Hostwover may send additional renewal notifications beyond those required by applicable policy.

Additional notices are provided as a convenience and may vary by Service, account configuration, or operational process.

Expiration and renewal notices may be sent through one or more channels, including:

• email.
• Hostwover account notifications.
• dashboard alerts.
• support communications.
• automated renewal messages; or
• other reasonable electronic methods.

The primary method will generally be electronic communication using the contact information associated with the Customer or domain.

Customers must keep their contact information accurate and current.

This includes maintaining a valid email address capable of receiving important domain notices.

Customers are strongly encouraged to maintain a Hostwover contact email address that does not depend solely on the domain being renewed.

For example, if `example.com` expires and the Customer's only contact address is `[email protected]`, expiration may disrupt the very mailbox needed to receive recovery notices.

ICANN's ERRP implementation guidance likewise encourages a secondary contact address that is not dependent on the expiring domain.

Failure to notice, read, or act on a reminder does not extend the domain's registration term.

A Customer remains responsible for renewal even where a message is:

• filtered as spam.
• sent to an outdated address.
• deleted.
• overlooked.
• blocked by the Customer's mail provider; or
• otherwise not read by the Customer.

Nothing in this section limits mandatory notification obligations that apply to the Sponsoring Registrar.

Where available, the Hostwover dashboard may display:

• expiration date.
• renewal status.
• automatic-renewal status.
• renewal price.
• domain status; and
• recovery options.

Customers should periodically review their domain portfolio.

Hostwover may offer automatic renewal for eligible domains.

Where automatic renewal is enabled, Hostwover may attempt to collect the applicable renewal charge using an authorized payment method before or around the renewal deadline.

Automatic renewal is a convenience feature and does not guarantee successful renewal.

Automatic renewal can fail because of:

• expired payment details.
• declined transactions.
• insufficient funds.
• payment-provider restrictions.
• fraud screening.
• account restrictions.
• technical failures.
• registry restrictions.
• registrar restrictions.
• unsupported payment methods; or
• other circumstances.

Even where automatic renewal is enabled, the Customer remains responsible for confirming that the renewal completed successfully.

Customers should not assume that a domain has renewed solely because auto-renew was enabled.

If an automatic-renewal attempt fails, Hostwover may:

• retry payment.
• notify the Customer.
• request an alternative payment method; or
• require manual renewal.

Hostwover does not guarantee any particular number of payment retries.

By enabling automatic renewal and maintaining an authorized payment method, the Customer authorizes Hostwover to attempt to collect the applicable renewal amount according to the applicable billing terms.

A Customer who does not wish to renew a domain should disable automatic renewal before Hostwover begins or completes the applicable renewal process.

Disabling automatic renewal does not necessarily reverse a renewal already submitted or completed.

Renewal pricing may differ from:

• initial registration pricing.
• promotional pricing.
• transfer pricing; or
• a previous renewal price.

The applicable renewal price is the price shown by Hostwover for that renewal transaction.

Domain renewal prices may change because of:

• registry price changes.
• registrar price changes.
• provider costs.
• exchange rates.
• taxes.
• regulatory fees.
• premium-domain classification; or
• Hostwover pricing changes.

For applicable gTLDs, ICANN's ERRP requires renewal, post-expiration renewal, and redemption/restore fees to be made reasonably available, including through reseller websites.

Hostwover may therefore publish current domain pricing through its website, checkout, renewal interface, or applicable domain-pricing page.

Premium domains may have renewal prices significantly different from ordinary domains.

A premium registration may remain subject to premium renewal pricing throughout its life.

Customers should review the displayed renewal price before completing a premium-domain transaction.

A domain is considered expired when its registration term ends without successful renewal.

Expiration does not necessarily mean the domain is immediately available for registration by another person.

A domain may pass through several post-expiration stages first.

Depending on the TLD, an expired domain may move through stages such as:

1. Active Registration
2. Expiration
3. Post-Expiration / Renewal Grace Period
4. Deletion
5. Redemption Grace Period
6. Pending Delete
7. Release / Availability for New Registration

Not every domain extension follows this exact sequence.

Domain life cycles vary significantly between extensions.

Customers must not assume that:

• every TLD has a renewal grace period.
• every TLD has a 30-day redemption period.
• every TLD enters Pending Delete.
• every TLD can be restored; or
• every expired domain follows `.com` lifecycle behavior.

The applicable registry and registrar rules control.

Hostwover does not promise a universal post-expiration renewal grace period for every domain.

Some extensions may:

• provide a grace period.
• provide a shorter period.
• provide a longer period.
• delete the domain immediately.
• use registry-specific recovery procedures; or
• provide no restoration process at all.

Current upstream TLD rules illustrate these differences, including extensions with no conventional Redemption Grace Period and others with periods materially different from the standard gTLD lifecycle.

For eligible domains, a Customer may still be able to renew the registration after its expiration date but before deletion.

The availability and duration of post-expiration renewal depend on the applicable domain.

Hostwover may charge:

• the standard renewal fee.
• a different post-expiration renewal fee; or
• another amount disclosed through the applicable renewal process

where permitted by the registrar and registry.

The presence of a domain in the Customer's account after expiration does not guarantee that ordinary renewal remains available.

The actual provider and registry status controls.

An expired domain may stop resolving.

This may occur because:

• DNS service is interrupted.
• nameserver delegation changes.
• the registrar places the domain on hold.
• the registry changes the domain's status; or
• another expiration-related mechanism applies.

For gTLD registrations subject to ERRP, the registrar must interrupt the existing DNS resolution path for the periods specified by that policy before deletion, subject to registry capability.

If expired web traffic is redirected to an expiration page while renewal remains available, that page must indicate that the registration has expired and provide renewal instructions.

When DNS resolution is interrupted, websites using the expired domain may become unavailable.

This may affect:

• primary websites.
• subdomains.
• customer portals.
• ecommerce stores.
• APIs.
• application endpoints; and
• other internet services.

Expiration may also cause email associated with the domain to stop working.

This can affect:

• incoming email.
• outgoing email.
• account-verification messages.
• password-reset emails.
• business communications; and
• services that use addresses on the expired domain.

Domain expiration may disrupt other products that depend on the domain, including:

• web hosting.
• professional email.
• Google Workspace.
• SSL certificates.
• APIs.
• DNS verification.
• third-party SaaS accounts; and
• authentication systems.

Customers must not rely on a domain continuing to resolve after expiration.

Even if it temporarily remains operational, that does not extend the registration or guarantee continued availability.

An expired domain may temporarily display:

• an expiration notice.
• a renewal page.
• a parking page.
• an upstream-provider page; or
• another expiration-related destination.

Displaying such a page does not mean ownership has transferred.

Where an expired registration remains eligible for renewal, successful renewal should allow the applicable DNS path to be restored according to registrar and registry procedures.

Under ERRP, the registrar must restore the registrant's previous DNS resolution path immediately or as soon as commercially reasonable following eligible renewal.

Even after renewal is completed, website or email functionality may not return instantly.

Recovery may be affected by:

• DNS caching.
• resolver behavior.
• registrar processing.
• registry processing.
• nameserver configuration.
• TTL values; and
• external service caches.

Renewing a domain restores the registration but does not necessarily repair unrelated problems such as:

• deleted DNS records.
• expired hosting.
• expired email subscriptions.
• incorrect nameservers.
• expired SSL certificates.
• application errors; or
• third-party service configuration.

If an expired domain is not renewed within the period made available by the applicable registrar or registry, the registrar may delete the registration.

Deletion is a distinct stage from expiration.

The point at which an expired domain is deleted can vary.

Customers should therefore never rely on an assumed number of post-expiration days unless Hostwover expressly confirms that period for the particular domain.

Many generic top-level domains provide a Redemption Grace Period ("RGP") after deletion.

For gTLD registries subject to ICANN's ERRP requirement, the RGP is generally 30 days immediately following deletion, subject to the exceptions provided by the policy. During RGP, the deleted registration may be restored through the registrar that deleted it.

A domain in Redemption Grace Period is no longer in the ordinary post-expiration renewal stage.

Recovering it requires a redemption or restoration process.

This is generally more expensive and operationally different from normal renewal.

Hostwover may charge a redemption or restoration fee in addition to any applicable renewal amount.

The applicable fee will be displayed or communicated before the restoration is submitted where reasonably practicable.

Restoration costs may be substantially higher than normal renewal costs because they involve a registry-level recovery procedure and upstream-provider charges.

Customers can avoid these charges by renewing before the domain reaches the redemption stage.

A redemption request can only be processed where:

• the applicable TLD supports restoration.
• the domain remains in a recoverable status.
• the restoration deadline has not passed.
• required fees are paid.
• the Customer is authorized to request restoration; and
• no other restriction prevents restoration.

Not every domain extension offers a Redemption Grace Period.

Some extensions may:

• be deleted immediately.
• follow a registry-specific recovery process.
• have a different redemption period.
• prohibit restoration; or
• become available for new registration through another process.

Upstream domain rules currently show substantial TLD-specific variations—for example, some extensions have no redemption stage, while others use recovery periods ranging from a few days to substantially longer periods.

The specific rules applicable to the Customer's TLD always control.

Customers seeking restoration should contact Hostwover or use an available recovery interface immediately.

A restoration request should identify:

• the domain.
• Hostwover account.
• Customer authorization; and
• any other information requested.

A restoration request may not be submitted until all required restoration and renewal charges have been successfully paid.

Payment alone does not guarantee that restoration will succeed.

A domain may change status between:

• invoice creation.
• payment.
• provider submission; and
• registry processing.

If restoration becomes technically impossible before completion, Hostwover will handle any unsuccessful restoration charge according to the applicable billing and refund rules.

Restoration may require action by:

• Hostwover.
• the upstream provider.
• Sponsoring Registrar; and
• registry.

Processing therefore may not be immediate.

Customers should request restoration as early as possible.

A request submitted near the end of the redemption period may fail if there is insufficient time for:

• payment.
• verification.
• registrar submission; or
• registry processing.

Hostwover does not guarantee recovery of a domain merely because a Customer submits or pays for a restoration request shortly before the registry deadline.

Where Hostwover's domain provider supports restoration, Hostwover may submit the redemption request through that provider.

Current upstream procedures require a restoration request and payment while the domain remains in a restorable status, but extension-specific limitations apply.

Depending on the TLD and provider procedure, restoration may include an additional registration year or may require a separate renewal.

The applicable checkout or recovery transaction will determine what is included.

Once a restoration request has been successfully completed at registry level, it may not be possible to reverse that restoration transaction merely because the Customer changes their mind.

A domain in Redemption Grace Period generally does not function normally in DNS.

For applicable gTLDs, ERRP requires the registry to disable DNS resolution during RGP and prohibit ordinary attempted transfers.

A domain in Redemption Grace Period generally cannot be transferred to another registrar through the ordinary transfer process.

For a typical gTLD, the domain must first be successfully restored before an eligible transfer can proceed. ICANN's registrant guidance expressly identifies this distinction.

If a Customer intends to move an expired domain that has already entered Redemption Grace Period, restoration through the current registrar may therefore be required first.

Applicable transfer restrictions may continue after restoration depending on the domain's status and governing rules.

A restoration request may cause the registry status to change to `pendingRestore`.

This generally indicates that the registrar has requested restoration and the registry is awaiting or processing required restoration information.

A restoration may fail because of:

• missed deadlines.
• unsupported TLD.
• provider refusal.
• registry refusal.
• incorrect status.
• payment failure.
• incomplete verification.
• legal restrictions; or
• technical errors.

Hostwover will provide available information where reasonably possible.

If a domain completes its Redemption Grace Period without successful restoration, many gTLDs move into Pending Delete.

At this stage, restoration is generally no longer available.

For a typical gTLD lifecycle, `pendingDelete` follows the 30-day Redemption Grace Period and lasts approximately five calendar days before the domain is purged from the registry.

This timing must not be assumed for every TLD.

Once a domain is in a non-restorable Pending Delete stage, Hostwover may be unable to:

• renew it.
• restore it.
• transfer it.
• prevent deletion; or
• return it to the Customer.

Hostwover may still provide status information, but a support request cannot override a registry's deletion process where restoration is no longer permitted.

After the applicable deletion process is complete, the registration may be purged from the registry.

The previous Customer's registration rights then end.

After final deletion, the domain may become available for new registration according to the registry's rules.

Availability may occur:

• immediately.
• after a Pending Delete stage.
• through registry release procedures; or
• through another TLD-specific process.

For domains released into ordinary public availability, another person may register the domain before the former Customer does.

Hostwover does not reserve an expired and fully deleted domain for the former Customer.

Hostwover cannot guarantee that it can re-register a deleted domain.

A third party may acquire it immediately after release.

The exact moment at which a deleted domain becomes available may not be predictable to the Customer or Hostwover.

Hostwover does not guarantee a specific drop time.

Expired domains that have commercial, brand, search, traffic, or other value may attract third-party registration attempts.

Customers should therefore renew valuable domains before expiration rather than relying on later recovery.

If another party lawfully registers a domain after it has been released, Hostwover cannot simply take that registration back for the previous Customer.

Any rights dispute would need to be addressed under applicable:

• domain-dispute procedures.
• trademark procedures.
• court processes; or
• other legal mechanisms.

A previous registration does not create a perpetual ownership right in a domain after the registration has expired, been deleted, and been lawfully registered by another party.

Any independent legal rights the former registrant may possess remain subject to applicable law and dispute procedures.

Loss or expiration of a domain does not necessarily terminate separate Hostwover Services.

For example, a hosting plan or VPS may continue to exist even though the domain no longer points to it.

Customers may remain responsible for charges for separate Services even where the associated domain expires.

Domain expiration does not automatically cancel:

• hosting.
• VPS.
• VDS.
• professional email.
• Google Workspace.
• SSL-related products.
• AI services; or
• other subscriptions.

If the domain supporting Professional Email expires, mailbox infrastructure may remain provisioned while the domain itself no longer routes mail correctly.

The Customer remains responsible for renewing both Services where required.

An expired domain can materially affect Google Workspace functionality associated with that domain.

Renewing a Workspace subscription does not renew the domain itself.

A valid SSL certificate does not prevent domain expiration.

Likewise, restoring or renewing a domain does not guarantee that an expired or invalid SSL certificate will automatically become valid.

Upon renewal or restoration, the applicable provider may attempt to restore or preserve previous nameserver configuration where supported.

Customers should nevertheless verify DNS after recovery.

Hostwover does not guarantee indefinite retention of DNS records after a domain:

• expires.
• is deleted.
• is removed from the account; or
• is re-registered by another person.

Customers should maintain independent records of important DNS configuration.

Customers should maintain appropriate backups of:

• websites.
• databases.
• DNS configuration.
• email.
• application data; and
• other important information.

Domain recovery is not a substitute for data backup.

Customers planning to transfer a domain to another registrar should begin the process sufficiently before expiration.

Waiting until expiration increases the risk of:

• interruption.
• additional fees.
• status restrictions.
• redemption; and
• failed transfer.

For applicable gTLDs, expiration alone does not necessarily eliminate the right to transfer a domain.

ICANN guidance states that a registrar may not deny an otherwise eligible transfer merely because the domain expired or was not renewed, subject to applicable exceptions such as unpaid prior registration periods. Once the domain has entered Redemption Grace Period, restoration is required before transfer.

Other transfer restrictions may still prevent transfer, including:

• domain locks.
• UDRP.
• URS.
• court orders.
• registry restrictions.
• applicable transfer-policy restrictions.
• domain status; or
• unresolved disputes.

If a domain approaches expiration while an inter-registrar transfer is pending, the Customer should immediately review the status with Hostwover.

The outcome may depend on the transfer status, registrar, and registry.

A domain involved in:

• UDRP.
• URS.
• litigation.
• ownership disputes.
• transfer disputes; or
• other restrictions

may have special expiration or renewal handling.

The Hostwover Domain Dispute Policy and applicable external procedures also apply.

A dispute does not automatically renew the domain.

Customers should continue to monitor renewal obligations unless instructed otherwise under the applicable dispute procedure.

A domain suspended for abuse may still reach expiration.

Paying a renewal fee does not automatically remove an abuse-related suspension.

A registrar or registry status may prevent normal:

• renewal.
• transfer.
• update; or
• DNS resolution.

Hostwover may need to coordinate with the upstream provider before further action is possible.

If the registry places a domain in a status that prohibits renewal, Hostwover may be unable to renew it until the underlying restriction is resolved.

ICANN's EPP status guidance recognizes both registrar- and registry-level renewal prohibitions that can occur in situations including disputes or deletion processes.

Failure to pay a renewal invoice or otherwise complete required payment may result in expiration.

A pending or unpaid invoice does not extend the registration.

A payment marked:

• pending.
• processing.
• under review; or
• awaiting confirmation

does not necessarily mean that renewal has been completed.

The Customer should confirm that the domain itself shows a successfully renewed registration term.

Customers who pay shortly before expiration accept the risk that payment processing may not complete before the registry or registrar deadline.

Customers should renew sufficiently in advance.

If payment is received after the domain has moved into a different lifecycle stage, the originally expected renewal operation may no longer be available.

Additional restoration procedures or fees may become necessary.

Where domain fees are displayed in a local currency, the amount for renewal or restoration may change due to:

• provider pricing.
• exchange rates.
• taxes.
• fees; or
• changes between the original registration and recovery date.

Renewal and restoration fees may be subject to applicable taxes.

Taxes will be handled according to applicable Hostwover billing rules and law.

Successful domain renewals are generally final once submitted to and completed by the registrar or registry, except where:

• required by law.
• permitted by the applicable registry or registrar; or
• expressly allowed under the Hostwover Refund Policy.

Successful redemption or restoration transactions may likewise be non-refundable because they may generate irreversible upstream registry operations and charges.

If Hostwover collects payment for a restoration that cannot be submitted or completed, Hostwover will determine the applicable refund, credit, or reversal according to:

• provider outcome.
• payment status.
• applicable fees.
• Hostwover Refund Policy; and
• applicable law.

To the maximum extent permitted by law, Hostwover is not responsible for loss resulting from a Customer's failure to:

• renew.
• maintain payment details.
• monitor expiration.
• review notifications.
• maintain contact information; or
• request restoration in time.

Nothing in this Policy excludes responsibility that Hostwover cannot lawfully exclude.

If a Customer believes a properly paid and accepted renewal was not processed due to a Hostwover error, the Customer should contact support immediately.

A renewal or restoration issue may originate from the Sponsoring Registrar, registry, payment provider, or another external provider.

Hostwover may escalate qualifying issues but cannot guarantee an external provider's outcome.

Registry or registrar maintenance may temporarily affect:

• renewal.
• restoration.
• status updates.
• registration lookup; or
• domain-management operations.

Customers should not wait until the final possible day to renew or restore a domain.

Domain operations may be affected by events outside Hostwover's reasonable control, including:

• registry failures.
• registrar outages.
• internet outages.
• payment-network failures.
• governmental action.
• sanctions.
• technical incidents; or
• other external events.

Hostwover may display lifecycle labels such as:

• Active.
• Expiring Soon.
• Expired.
• Grace Period.
• Redemption.
• Pending Delete.
• Suspended; or
• Deleted.

These labels are informational.

The authoritative registry/registrar status may control where there is a discrepancy.

Applicable gTLDs may expose EPP status codes describing domain lifecycle or restrictions.

Examples relevant to recovery may include:

• `redemptionPeriod`.
• `pendingRestore`.
• `pendingDelete`.
• `clientHold`.
• `serverHold`; and
• renewal or transfer prohibitions.

ICANN maintains explanations of these status codes and their effects.

If a Customer discovers that a domain has expired, the Customer should contact Hostwover or use the available renewal interface immediately.

Delay can materially reduce the available recovery options.

When an expired domain is reviewed, Hostwover may determine:

• current domain status.
• whether ordinary renewal is available.
• whether restoration is required.
• applicable fees.
• available time.
• registrar restrictions; and
• registry restrictions.

A recovery option shown in a dashboard or communicated by support is not guaranteed until the relevant registrar or registry operation successfully completes.

Domain statuses can change over time.

Where automated restoration is unavailable, Hostwover may attempt to coordinate recovery manually with its upstream provider.

Manual assistance does not guarantee successful recovery.

Hostwover may require account or identity verification before performing sensitive recovery actions.

This may be particularly necessary where:

• account access is disputed.
• domain ownership is disputed.
• the Customer cannot access the registered email.
• fraud is suspected; or
• another high-risk circumstance exists.

Hostwover will not knowingly restore or transfer control of a domain to an unauthorized third party.

Security and ownership verification may therefore delay recovery where the requester cannot establish proper authority.

Recovery involving:

• a deceased registrant.
• dissolved company.
• corporate restructuring.
• former employee.
• ownership dispute; or
• inaccessible registrant account

may require additional documentation under the Domain Dispute Policy and upstream-provider rules.

Because Hostwover may operate as a reseller, certain notices or lifecycle changes may originate directly from:

• the Sponsoring Registrar.
• registry.
• upstream provider; or
• ICANN-related systems.

Customers should not disregard a legitimate domain-expiration communication merely because it was not sent from a Hostwover-branded address.

Domain owners may also receive fraudulent renewal notices or misleading solicitations.

Customers should verify any unexpected domain-payment request through their Hostwover account or Hostwover Support before submitting payment or credentials.

Customers should never send:

• Hostwover passwords.
• payment-card security codes.
• SSH private keys; or
• unrelated authentication secrets

merely to renew a domain.

Hostwover encourages Customers to:

1. maintain accurate contact information.
2. use a secondary email address independent of the registered domain.
3. enable automatic renewal for important domains where available.
4. maintain a valid payment method.
5. monitor expiration dates.
6. renew important domains early.
7. review renewal pricing in advance.
8. keep domain ownership information accurate; and
9. contact Hostwover immediately when an unexpected expiration occurs.

Customers using a domain for important business operations should treat domain renewal as a critical operational responsibility.

A domain can affect:

• websites.
• email.
• customer trust.
• authentication.
• API access.
• search visibility.
• payment systems.
• advertising.
• business applications; and
• company identity.

Organizations may wish to:

• maintain multiple domain administrators.
• document renewal dates.
• use monitored billing contacts.
• enable auto-renew.
• maintain backup payment methods where supported.
• document DNS configuration; and
• periodically audit their domain portfolio.

Registering a domain provides rights to use the registration for the applicable registration period subject to governing terms.

It does not create perpetual ownership independent of renewal requirements.

Post-expiration grace periods are intended as recovery mechanisms, not substitutes for timely renewal.

Customers must not intentionally rely on a grace or redemption period as their normal renewal process.

Registries may change:

• renewal periods.
• restoration rules.
• eligibility rules.
• fees.
• technical procedures; or
• lifecycle policies.

Hostwover may update its procedures accordingly.

ICANN may update applicable consensus policies governing generic top-level domains.

Mandatory updated policies will apply where required even if this Hostwover Policy has not yet been updated.

Country-code top-level domains ("ccTLDs") are generally governed by their respective registries and local policies rather than a single universal ICANN gTLD lifecycle.

Customers should review extension-specific requirements where available.

Certain sponsored, restricted, geographic, country-code, or specialized extensions may impose recovery rules substantially different from ordinary gTLDs.

Those rules take precedence where applicable.

If this Policy conflicts with a mandatory registry rule governing a particular TLD, the registry rule controls for that domain.

If a mandatory Sponsoring Registrar requirement applies to a particular expiration or recovery action, the registrar requirement controls to the extent necessary.

For applicable gTLDs, mandatory ICANN consensus policies control where they conflict with this Policy.

The Domain Renewal & Expiration Agreement establishes the Customer's contractual obligations relating to domain renewal, expiration, billing, and related matters.

This Domain Expiration & Recovery Policy primarily explains the operational domain lifecycle and recovery procedures.

The Domain Registration Agreement governs the original registration relationship and continuing obligations relating to the domain.

This Policy supplements that agreement for expiration and recovery matters.

The Domain Transfer Agreement governs transfers to or from Hostwover's domain supply channel.

Expired domains may additionally be subject to the restrictions described in this Policy.

If an expired domain is also involved in an ownership, trademark, UDRP, URS, transfer, or court dispute, the Hostwover Domain Dispute Policy may also apply.

Expiration does not remove or override:

• abuse suspensions.
• legal holds.
• DNS-abuse mitigation.
• fraud restrictions; or
• other enforcement actions.

An informal estimate from a support representative regarding the remaining recovery time does not override the actual registry deadline.

Customers should act immediately rather than relying on an estimated final day.

Registry deadlines may operate according to different technical or geographic time standards.

Hostwover does not guarantee that a recovery opportunity remains available until the end of the Customer's local calendar day.

For purposes of registrar and registry processing, the provider's recorded expiration and status timestamps may control.

Customers should not assume that an expiration, redemption, or deletion deadline will be extended because it falls on:

• a weekend.
• public holiday; or
• non-business day.

Registry processes may operate automatically.

By registering, transferring, renewing, or managing a domain through Hostwover, the Customer acknowledges that:

1. domain registrations exist for limited terms.
2. the Customer is responsible for timely renewal.
3. auto-renew may fail.
4. renewal pricing may differ from registration pricing.
5. expiration may interrupt websites, DNS, and email.
6. post-expiration renewal availability varies by TLD.
7. not all TLDs have the same grace period.
8. deletion is different from expiration.
9. redemption may require substantially higher fees.
10. not all domains can be restored.
11. redemption periods are limited.
12. Pending Delete may make recovery impossible.
13. released domains can be registered by another person.
14. Hostwover cannot guarantee re-registration after deletion.
15. separate hosting and email subscriptions do not automatically renew a domain.
16. Hostwover may rely on an upstream registrar and registry.
17. registrar and registry rules may control the domain lifecycle.
18. important domains should be renewed well before expiry; and
19. recovery is not guaranteed until the registrar or registry confirms successful completion.

For purposes of this Policy:

• "Customer" means the person or entity purchasing, managing, controlling, or using a domain Service through Hostwover.
• "Expiration" means the end of the domain's current registration term without completed renewal.
• "Post-Expiration Renewal" means renewal after the expiration date but before the domain reaches a stage requiring redemption or preventing ordinary renewal.
• "Renewal Grace Period" means any post-expiration period during which the applicable registrar or registry permits ordinary or special renewal before deletion.
• "Redemption Grace Period" or "RGP" means a registry recovery period following deletion during which an eligible domain may be restored through the deleting registrar.
• "Redemption" or "Restoration" means the process of recovering an eligible deleted domain from a recoverable registry status.
• "Pending Delete" means a late deletion stage in which the domain may no longer be restorable and is moving toward final release, where applicable.
• "Registry" means the entity responsible for operating the applicable top-level domain registry.
• "Sponsoring Registrar" means the registrar responsible for the registration at the registry.
• "TLD" means the top-level domain or domain extension, such as `.com`, `.net`, or another applicable extension.

Questions regarding domain expiration, renewal, redemption, or recovery may be directed to:

Hostwover Support

Email: [email protected]

Website: hostwover.com

When contacting Hostwover regarding an expired domain, provide:

• the domain name.
• your Hostwover account information.
• relevant order or invoice information; and
• a description of the issue.

If the domain has already expired, contact Hostwover immediately. Recovery options can decrease as the domain progresses through its lifecycle.

Do not send passwords, Auth/EPP codes, full payment-card numbers, private keys, or unnecessary authentication secrets by email.

This Domain Expiration & Recovery Policy becomes effective on the date stated above and applies to domain-related Hostwover Services that reference or incorporate this Policy.

END OF DOMAIN EXPIRATION & RECOVERY POLICY