We let our own price-setter lapse. Here is what the system did with it.
On 11 October 2026 the registration for weckett.com reached its expiry date, and we let it. No later than two days and nine hours later, the address was serving a parked page.
On 11 October 2026 the registration for weckett.com reached its expiry date, and we let it. Weckett is the part of url.ventures that sets prices for digital assets, so this was not a forgotten invoice. It was the one experiment in this market we could run without risking anyone else's property: what happens, in public and on the record, when an owner stops paying for an asset that matters.
We had a baseline. Our expiry watcher read the record on 5 October at 03:36 UTC and found what an owner would expect to see: the asset pointed at the nameservers we had set with our DNS host, the site answering as Weckett, an expiry date of 11 October 2026, and a transfer lock in place. Nothing about that record suggested what the next eight days would bring.
When we looked again on 13 October at 16:28 UTC, the address no longer led to our work. The asset's nameservers had been switched to a parking service's, and weckett.com now served a 990-byte page: the address as a headline, a line offering information, resources and links about it, and a second line, “This domain may be for sale.” The page also called a script hosted by the parking service; we saved the page but not what that script drew on screen that day, a gap we come back to below. So no later than that afternoon, the address was serving a for-sale line for an asset its owner could still renew, under the registrar's published terms, at the normal price until 30 days after expiry.
The registry's own record told a stranger story. The authoritative .com record already showed an expiry of 11 October 2027, a full year out. The transfer lock seen on 5 October was gone, and the record carried no redemption-period status, so the registration had not been deleted. Yet the registrar's own public record, which the registry's record links to, still gave the expiry as 11 October 2026 when we read it the next morning. ICANN's rules define two separate expiry dates, one kept by the registry and one by the registrar, and here they no longer matched. In our own registrar account the asset was marked expired and parked. To an outside observer reading the registry, the asset looked as if it had been renewed and unlocked; the registrar's public record said it had expired; the page at the address said it may be for sale. Four views of the same asset within a day disagreed with one another, and none of them showed the owner a price.
The next morning the address rendered a banner across the top saying the registration had expired, with a renewal link, above the same parked text. The registrar's own record still gave the expiry as 11 October 2026. The asset was still parked.
Then we renewed. When we read the records again on 16 October at 23:00 UTC, the registrar's record gave an expiry of 11 October 2027, the same date the registry had shown since 13 October, so the two records agreed again. The asset pointed at the nameservers we had set with our DNS host, and the address answered as Weckett.
We cannot say to the hour when the switch happened, because our watcher did not run between 5 and 13 October. We can say it happened no later than two days and nine hours after expiry: the registration expired on 11 October at 07:25 UTC, and our check came on 13 October at 16:28 UTC. The registry logged its most recent change to the record at 15:33 UTC that day, under an hour before our check, but that change could as easily have been the lock coming off as the nameservers moving. The switch itself is a standard step in the registrar's published terms for an expired registration, and ICANN's policy requires the owner's DNS to be interrupted at some point after expiry; neither calls for asking the owner first.
The record, day by day
- Baseline
Our nameservers, the site answering as Weckett, expiry 11 October 2026, transfer lock on.
- Expiry
The registration reaches its expiry date. We let it.
- Parked page
A parking service's nameservers and a 990-byte page saying the domain may be for sale. The registry shows 11 October 2027.
- Still parked
A top banner now says the registration has expired, with a renewal link. The registrar's record still gives 11 October 2026.
- Renewed, back on its own nameservers
Both records give 11 October 2027, and the site answers as Weckett again.
Why the registry says 2027
The explanation is mechanical and, once seen, hard to unsee. When a .com registration passes its expiry date unrenewed, the registry renews it automatically on the first day after expiry and charges the registrar, not the owner. The registrar then has 45 days in which it can delete the registration and get that fee back as a credit; if it does not, the charge stands. A deleted registration stops resolving and enters a 30-day redemption period in which the only step open to a registrar is a restore, then spends five days pending deletion before it is released.
The registry record for weckett.com shows an expiry a year out because, at the wholesale level, a year has been added and charged to the registrar. The record does not say “renewed”; it shows the new date and a single status, active. The registrar's own published terms say that it provisionally renews an expired registration with the registry on the owner's behalf, and that this gives the owner no rights to it. Who benefits from that extra year is settled by the same terms: a 40-day post-expiry period that ends when a renewal payment is accepted, with a restoration fee in its last 10 days; the right to auction the asset if the owner has not renewed within the first 30 days; and the right to transfer it to a new holder if the owner has not renewed by the end of the period. By our arithmetic from those terms, the normal-price window for weckett.com closes around 10 November.
During that window the registrar controls where the address resolves. Its service agreement says an expired registration has its nameservers changed, and that until renewal the owner has no right to access the asset, change its records or earn parking revenue from it. That control has limits, and they are written down.
ICANN's Expired Registration Recovery Policy sets them, in the version updated in February 2024 that every registrar has had to follow since 21 August 2025. Before expiry, the registrar must send the owner at least two reminders, about a month and about a week out, and unless the registration has been renewed or deleted, one more notice with renewal instructions within five days after expiry. The owner at the moment of expiry must be allowed to renew from then through the period in which the registrar interrupts the owner's DNS. The policy fixes no day count for that window; where deletion comes eight or more days after expiry, the interruption, and so the guaranteed renewal window, covers at least the last eight consecutive days in which the owner can renew. Any web page the registrar sends visitors to while the owner can still renew must, in the policy's words, “conspicuously indicate that the domain name registration is expired” and give renewal instructions, and pointing to the right place on the registrar's site is enough. Once the owner renews, the registrar must restore the owner's DNS settings immediately or as soon as is commercially reasonable. If the registration is deleted instead, a 30-day redemption period follows in which the owner can still redeem it.
Set beside that, here is what we recorded. The page we saved on 13 October did not, in its own text, say that the registration had expired or give renewal instructions. It called the parking service's script, and we did not capture what that script showed on 13 October. When we fetched the same script the next morning, for a page byte-for-byte identical to the one we saved, it contained code for a fixed banner across the top of the page saying the registration had expired, with a link to renewal instructions on the registrar's help pages. We record both observations and draw no conclusion from them about anyone's compliance.
What the owner never sees
This is the gap we described in our own raise pack: an owner who lets an asset go gets no published bid, and whoever holds it next keeps the value. Our lapse made that sentence concrete. By 16:28 UTC on 13 October, no more than two days and nine hours after expiry, the address of our own price-setter was serving a parked page whose text said the domain may be for sale. No one had offered the owner a price for the asset, and the system had nowhere to put one.
The structure explains why. The registry's public record shows the extra year, not the lapse; the original expiry sits in the registrar's record. The parties who read that record closely are the registrar holding the asset, which under its own terms may auction it if the owner has not renewed within the first 30 days, before it is ever deleted, and the services built to catch the assets that do drop. Their interest begins where the owner's ends. A floor, a published price that stands before expiry and that a market maker has funded, is the piece that is missing. It would turn the expiry from a quiet transfer of attention into a moment when the owner is shown what the asset is worth and can choose. That is the product we are building, and this week we watched the reason for it from the inside.
We will keep the full record (the parked page as served, its headers, the script it called, the registry and registrar readings and our watcher's log, each with a hash) in our evidence file, and we will update this piece if anything in it changes.