What could your domain
portfolio unlock?

Each monthly expired batch = total domains × annual expired rate ÷ 12, rounded to a whole domain. Domains remain in the expired account for up to 30 days and earn the selected expired revenue per domain / month amount ($0.05 by default). For domains selected to transfer to O&O, expired-month revenue also includes the admin-selected percentage (70% at baseline) of the nominated O&O monthly yield per selected domain, on top of the 5-cent baseline; both amounts are subject to monthly variation and revenue share. At the end of each month the selected percentage, rounded to the nearest whole domain, moves to O&O; the remainder is dropped or sold. A new monthly batch replaces it. The expired account does not accumulate prior batches. O&O earnings begin in the following month. All modelled domains are assumed eligible and authorised; revenue share does not change domain counts. O&O revenue is based on $2 per domain-month at the starting point, subject to illustrative monthly variation. There is no overlapping expired and O&O revenue for the same cohort-month.

O&O renewal is interpreted as a registrar cost: charged in the first O&O earning month, then at each annual anniversary for the retained fraction. The first batch is selected in month 1 and incurs its initial cost when O&O earnings begin in month 2. Its first annual renewal cost is charged at the end of month 13. Domains selected in month 12 incur their initial renewal cost in month 13. First renewal retention applies after the first 12 paid O&O months (75% at baseline). Subsequent annual retention applies to the remaining domains at every later anniversary (90% at baseline), with whole-domain rounding at each renewal. The screenshot does not confirm this timing, cost direction, or repeated annual rule; these are explicit prototype assumptions to review.

Starting Default Name Server base = total domains × Default Name Server percentage, rounded to a whole domain. The base increases by the admin-selected net growth rate (1% per month at baseline), with each monthly count rounded to a whole domain. Monthly expired batches, retained cohorts and anniversary renewals are rounded to the nearest whole domain. Released domains are calculated as the expired batch minus the retained count, so the batch reconciles exactly.

Monthly registrar contribution = gross revenue − that month’s ParkLogic share − O&O renewal costs − monthly operating cost. Incremental net additionally subtracts the existing monthly net baseline. The green chart line, Net Monthly Registrar Revenue, shows each individual month’s gross revenue minus O&O renewal costs minus ParkLogic’s share of gross revenue. It does not accumulate across months. The headline registrar-receipts metric remains the total over the selected period. Operating costs and the existing baseline are not subtracted from this chart line; the deductions and yield comparison show incremental net after those additional amounts. Zero baseline and zero operating costs are placeholders, not measured values. Other deductions, tax, payment lag, refunds and traffic-quality adjustments are not modelled. Growth is a scenario assumption, not an uplift claim.

Source assumptions: the two user-supplied spreadsheet screenshots. No workbook or source formulas were supplied, so this is not a formula-for-formula reproduction. Registrar-wide content is informed by the Notion context dated 27/10/2026: Registrar Monetisation — ParkLogic Opportunity, DNS Integration & Technical Adoption. Access to that source follows its existing permissions.

Use current registrar data and ParkLogic engineering/commercial confirmation before making a decision. Historical customer-specific correspondence from the source is excluded. Product descriptions and older DNS documents do not establish current support. Integration guidance is a discovery framework; it is not a DNS change procedure.

A self-contained GenUI-style HTML/CSS/JavaScript prototype, hosted temporarily on R2 and embedded in Fibery. No live AI service, cookies, analytics, external libraries, credentials, domain connections or automatic Fibery writes. Slider changes stay in memory and reset on reload unless a scenario link is used. Copied scenario links include assumptions and pilot ticks in the URL fragment; treat any shared link or exported file according to the information you enter. Do not use confidential customer values on this public demonstration.