A RegisterMySite catch story
autoregister.org was caught by Site-Sniper
This page lives on a .org that expired, passed through redemption and pending delete, and dropped while a Cloudflare Worker was watching it. The first attempt failed because of a bug. The fix shipped, the watch re-armed, and Site-Sniper registered the name about two minutes later.
Registered ·
The catch
A dropped .org, a false alarm, then a two-minute retry
This is a build-in-public story, not a perfect first shot. Site-Sniper was already watching autoregister.org when the Public Interest Registry released it. The Worker should have bought it immediately. A display bug and a stuck state got in the way — until version 1.4.1 landed.
autoregister.org is a .org name, so its drop clock comes from PIR, not from Verisign’s daily .com/.net batch. After the registration expired it went through the usual redemption and pending-delete phases. Site-Sniper kept the watch in place and, once the name was free, tried to register it through the RegisterMySite account Worker and Cloudflare Registrar.
On the evening of November 21, 2026, that first attempt was reported as “Insufficient balance.” The prepaid Sniper wallet already held $15.00. The watch listed $13.99 as required, and the actual charge was $8.50. The wallet was never the problem. A hardcoded banner made the attempt look underfunded, and the watch was left in a terminal needs_manual state, so it stopped retrying on its own.
Site-Sniper 1.4.1 was deployed around 11:50 PM Pacific Standard Time on November 21, 2026. The watch re-armed, saw that autoregister.org was still available, confirmed the wallet covered the cost, and registered the name at 07:52:08 UTC on November 22, 2026 — 11:52 PM PST on November 21, about two minutes after the deploy. The registrar of record is Cloudflare, Inc. The name is paid through 07:52:08 UTC on November 22, 2027. A WHOIS lookup shortly after the catch showed status addPeriod and nameservers alaric.ns.cloudflare.com and elsa.ns.cloudflare.com.
-
Before the dropPIR registry
The name left the registry
autoregister.org expired, spent time in redemption and pending delete, and then became available again at PIR. Site-Sniper already had a watch on it, with Auto-Purchase on and a wallet large enough to cover the registration.
-
Evening PSTNov 21, 2026
The first snipe was misreported
The UI said the wallet did not have enough funds. That was a hardcoded banner, not a real balance check. The watch was also stuck in a terminal needs_manual state, so it did not keep trying.
-
11:50 PM PSTNov 21, 2026
Site-Sniper 1.4.1 shipped
The false insufficient-balance banner and the stuck needs_manual path were fixed and deployed to sitesniper.registermysite.com.
-
11:52 PM PSTNov 21, 2026
The retry registered the name
The watch re-armed, the account Worker took the $8.50 charge from the prepaid Sniper wallet, and Cloudflare Registrar created the registration. The account dashboard then showed “Caught by Site-Sniper.”
The dashboards
What the product showed after the catch
These are HTML recreations of the Site-Sniper watch row and the RegisterMySite account screens, with a conflicting leftover availability status removed from the watch row. The name is registered. Dates below match each screen: the watch row uses the registry calendar date in UTC; the account app shows Pacific Time.
Exp: Nov 22, 2027 Paid: $8.50
Registrar: Cloudflare Registrar · rdap:registered
Overview
- Registrar
- Cloudflare Registrar
- Registered
- Nov 21, 2026
- Expires
- Nov 21, 2027
- Hosting
- attached
Caught by Site-Sniper · Nov 21, 2027
How it works
Add a watch. Fund the wallet. Let the alarm loop work.
Site-Sniper is a product on RegisterMySite. It does not scrape WHOIS on a guess, and it does not ask you to sit on a checkout page at drop time. You set the watch once. The Worker does the waiting in UTC.
-
01
Add a watch
Enter the domain you care about. Site-Sniper stores the watch and starts reading registry RDAP for that name.
-
02
Fund the Sniper wallet
The account Worker will only register a name if your prepaid Sniper wallet covers the cost. For autoregister.org the actual charge was $8.50, leaving $6.50 in the wallet.
-
03
Turn on Auto-Purchase
When the toggle is on, a successful availability check can go straight to a registration attempt. You do not have to be online.
-
04
Predict the drop from RDAP
For .org, PIR’s last-changed timestamp plus five days is the drop, to the minute, in UTC. For .com and .net, Verisign uses a daily batch around 12:00 UTC.
-
05
Tighten the checks
Far from expiry, Site-Sniper checks about once a day. In the hour before the window, it checks every minute. Inside the window it checks every 15 seconds.
-
06
Register, then confirm
When the name is free, the Worker calls the RegisterMySite account Worker over a Cloudflare service binding. If the wallet clears, Cloudflare Registrar registers the name at cost, the dashboard shows “Caught by Site-Sniper,” and email and X DM alerts can go out.
Be honest about the limits. This is retail-API sniping. Services that speak to the registry in milliseconds will usually win a contested drop. Site-Sniper is for names nobody else is chasing — which is how autoregister.org was caught after it had already been sitting unregistered.
Architecture
A Worker, a Durable Object, and a service binding
The moving parts are all on Cloudflare. Registry time stays in UTC. The only hop from Site-Sniper to checkout is a Worker-to-Worker binding into the RegisterMySite account service, not a public browser request.
The Worker is named site-sniper. Each watch is driven by a Durable Object alarm, so the cadence can change as a name gets closer to its predicted drop without a central cron having to poll every domain every few seconds. A periodic cron is still there as a safety net if an alarm chain ever stops.
Availability comes from registry RDAP — PIR RDAP for .org names. When a check says the name is free, Site-Sniper does not charge a card itself. It calls the account Worker, which checks the prepaid Sniper wallet and, if the balance covers the price, submits the registration to Cloudflare Registrar. The account Worker then writes the result back so the dashboard, email, and X DM can all say the same thing.
RDAP
PIR RDAP for .org. Last changed plus five days, to the minute, in UTC. Verisign .com/.net drops in a daily batch around 12:00 UTC.
Worker + Durable Object
Alarm loop checks daily when far out, every minute the hour before the window, and every 15 seconds inside it.
Account Worker
Reached over a Cloudflare service binding. Confirms the prepaid Sniper wallet can cover the name, then places the order.
Cloudflare Registrar
Registers the domain at cost. For this catch: Cloudflare, Inc., created 07:52:08 UTC on Nov 22, 2026.
Dashboard and alerts
The account app shows “Caught by Site-Sniper.” Email and X DM alerts can follow the same confirmation.
About one RDAP check per day while the name is still active or well before the predicted window.
Checks every minute once the predicted drop is less than an hour away.
Checks every 15 seconds, then calls the account Worker as soon as RDAP says the name is free.
FAQ
Questions about this catch
Short answers, limited to what we actually know from this registration and from how Site-Sniper is built.
What is Site-Sniper?
Site-Sniper is a RegisterMySite tool that runs as a Cloudflare Worker named site-sniper. You add a domain watch, fund a prepaid Sniper wallet, and toggle Auto-Purchase. A Durable Object alarm loop checks registry RDAP, and when the name becomes available the Worker calls the RegisterMySite account Worker over a Cloudflare service binding, which registers the name through Cloudflare Registrar at cost and writes the result back to your dashboard.
When was autoregister.org registered?
WHOIS and the registry record the registration at 07:52:08 UTC on November 22, 2026, which is 11:52 PM PST on November 21, 2026. The name is registered with Cloudflare, Inc. (Cloudflare Registrar) and is paid through 07:52:08 UTC on November 22, 2027. The RegisterMySite dashboard shows those instants as November 21, 2026 and November 21, 2027 because it displays Pacific Time.
Why did the first snipe attempt fail?
On the evening of November 21, 2026, Site-Sniper tried to buy autoregister.org and the interface reported Insufficient balance. That was wrong. The prepaid Sniper wallet already held $15.00, which covered the $13.99 the watch listed as required (the actual charge turned out to be $8.50). The false banner was hardcoded, and the watch was left in a terminal needs_manual state so it stopped retrying. Site-Sniper 1.4.1, deployed around 11:50 PM PST, fixed both issues. The watch re-armed on its own and registered the name about two minutes later.
How does Site-Sniper predict when a domain will drop?
It reads registry RDAP rather than guessing from a countdown clock. For .org names at the Public Interest Registry, the predicted drop is the RDAP last-changed timestamp plus five days, to the minute, in UTC. For .com and .net, Verisign deletes in a daily batch around 12:00 UTC. Site-Sniper compares those UTC instants internally; local time is only for display.
Can Site-Sniper beat dedicated drop-catching services?
No, and we do not claim that it can. Site-Sniper purchases through a retail registrar API. Services that connect directly to the registry can fire in milliseconds and will usually win a contested drop. Site-Sniper is built for names nobody else is chasing: it watches the window, checks often enough to catch the drop, and registers the name if your wallet covers the cost.
How do I watch a name with Site-Sniper?
Open Site-Sniper, add the domain as a watch, fund the prepaid Sniper wallet so it covers the registration cost, and turn on Auto-Purchase. Site-Sniper will check RDAP on its alarm cadence and, if the name becomes available, attempt the registration through your RegisterMySite account. You will see “Caught by Site-Sniper” on the dashboard, and you can receive email and X DM alerts.
Watch the next name before it drops
Site-Sniper is part of RegisterMySite. Add a watch, fund the Sniper wallet, and leave Auto-Purchase on. This domain is the proof that the loop can recover from a bad first attempt and still catch the name.