Reference · built on requestOperator by FibricIT & reliability

Domain Renewal

Reads expiry dates from your registrars and live DNS use per domain and proposes renew, enable auto-renew, or release, with an owner named.

Request accessPricing ↗

About

Domains expire on dates that sit in three registrar consoles and no calendar. Domain Renewal reads the expiry date and auto-renew flag for every domain in Cloudflare Registrar, Amazon Route 53, and GoDaddy, then reads the DNS zone for each domain to see what still answers: records, mail exchangers, certificates.

A domain with live records and auto-renew off gets a proposed renewal or a proposed auto-renew change. A domain with an empty zone and no recent changes gets a proposed release, with the person who last touched it named as the owner to ask. You approve each proposal. Renewals that carry a charge say so before you approve. The receipt keeps the expiry date, the zone snapshot, and the decision.

This is a reference listing. It documents what Fibric would read from Domain Renewal and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Domains in Cloudflare Registrar through GET /accounts/{account_id}/registrar/domains, with expires_at, auto_renew, locked, and registry_statuses
  • Domains registered through Amazon Route 53 from ListDomains, with DomainName, Expiry, AutoRenew, and TransferLock, filtered by expiry date
  • Domains in a GoDaddy account from the v1 Domains API, with expires and renewAuto per domain
  • DNS records per zone through GET /zones/{zone_id}/dns_records in Cloudflare, and the zone's status
  • Account audit logs in Cloudflare, to name the last person who changed a zone or a registrar setting
  • Open Jira issues that mention the domain, so a release already under discussion is linked

Proposed actions

  • Target capability: propose a renewal through Route 53 RenewDomain with DomainName, CurrentExpiryYear, and DurationInYears, stating that the charge is billed to your AWS account
  • Target capability: propose setting auto_renew true on a Cloudflare Registrar domain, or renewAuto true on a GoDaddy domain, where live DNS records exist
  • Target capability: propose releasing a domain with an empty zone, as a Jira issue assigned to the named owner, with the lapse date
  • Target capability: propose a Slack or Teams notice to the owner when a live domain enters the registrar's renewal window with auto-renew off

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Renew what still serves mail

    Domains whose Cloudflare zone holds MX records and whose Route 53 registration has AutoRenew false get a proposed RenewDomain call with the expiry year and a one-year term. You approve, and the OperationId is kept.

    With Cloudflare, Slack

  • Release the campaign domains nobody kept

    Registrations with an empty zone and no changes in the Cloudflare audit log get a proposed release as a Jira issue to the last editor, with the lapse date. An objection keeps the domain and sets auto-renew.

    With Cloudflare, Jira

  • Turn auto-renew on across three registrars

    Every domain with live records and auto-renew off, in Cloudflare Registrar, Route 53, or GoDaddy, appears in one proposal. Approving it sets the flag through each registrar and notes the change in Teams.

    With Cloudflare, Microsoft Teams

Requirements

  • A Cloudflare API token with Zone Read and DNS Read, plus the registrar permissions for auto-renew changes
  • AWS credentials allowed to call ListDomains, and RenewDomain or the auto-renew setting where renewals are to be proposed, against the route53domains endpoint in us-east-1
  • A GoDaddy API credential with domain read rights, and update rights if renewAuto changes are wanted
  • An owner per domain, or audit log access to work one out, since a release proposal must name a person
Authentication
Reads registrars and DNS with the Cloudflare API token, AWS credentials, and GoDaddy API credential you attach, and writes renewal or auto-renew changes only on approval.

Limits

  • Cloudflare's registrar domain endpoints are marked deprecated, with an end of life on September 27, 2026. The connector follows the replacement Registrar endpoints.
  • Route 53 renews an auto-renew domain 35 days before expiry, and some registries delete domains before that date. A late renewal can take a day.
  • DNS use is judged from records and zone status, not query traffic. Records nobody resolves still count as in use until you say otherwise.
  • It never lets a domain lapse on its own. A release is a Jira issue for the named owner. An unowned domain is escalated.

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Domain Renewal ↗

Questions and answers

What do I approve for each domain?
One of three: renew now, enable auto-renew, or release. The proposal shows the registrar, the expiry date, the zone's records, the last person to change anything, and the charge if there is one. You can change the term, pick a different owner, or dismiss.
What record is left?
A receipt per domain: the expiry read, the zone snapshot, the decision, who approved, the registrar's response such as a Route 53 OperationId, and the Jira issue for a release. Dismissed proposals are kept so the next expiry shows the earlier choice.
Can it delete a zone or let a domain expire by itself?
No. It reads zones and never edits or deletes records. A release is a Jira issue, and the domain lapses only if the named owner lets the registrar's own process run. Nothing in the operator cancels a registration.
Ask about Domain Renewal

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy