14 / For experts
Under
the hood.
This chapter is for readers who want the raw records: what each field means, where the clocks come from, and the traps we ran into. It changes nothing in the story. It shows how far the records hold, down to the millisecond. Everything here was looked up again on 19 November 2026 between 11:14 and 12:15 UTC.
One operator’s clock, to the millisecond
The .ai registry’s WHOIS gives whole seconds. Its RDAP service, the newer lookup protocol that registries now have to run, gives milliseconds. The .ai registry runs on the systems of Identity Digital, the company once called Donuts: every .ai record ID in the order ends in -DONUTS. The same RDAP server, rdap.identitydigital.services, answers for .services, .info, .ventures, .support, .domains, .life and .email. So thirteen of the thirty-four names, tibbir.ai among them, were stamped by one operator’s clock.
Terminalcurl -sL https://rdap.org/domain/tibbir.ai \ | jq -r '.handle, (.events[] | "\(.eventAction) \(.eventDate)")'
Registration times on that one clock (RDAP, 19 November 2026)18:41:08.660 ribbitcap.ai18:41:08.695 ribbit.services18:41:09.027 ribbitcap.info18:41:09.745 ribbitcapital.ai18:41:09.835 ribbit-cap.ai18:41:12.306 ribbitvc.info18:41:16.785 tibbir.ai ← seven seconds18:41:19.958 ribbit.ventures18:41:20.563 ribbitvc.ai18:41:21.995 ribbit.support18:41:29.239 ribbit.domains18:41:49.322 ribbit.life18:41:56.109 ribbit.email
On this single clock tibbir.ai comes 6.950 seconds after ribbit-cap.ai and 7.040 seconds after ribbitcapital.ai. The two signed .us names are stamped by another registry, in whole seconds only (18:41:09), so measured against them the gap lies between 6.786 and 7.785 seconds. Seven seconds is the honest round number on either reading. The earliest stamp of the whole order is ribbitcap.ai at 18:41:08.660, 35 milliseconds before ribbit.services.
Comparing two registries assumes both keep their clocks on UTC, which registries do as a matter of course. The thirteen names above need no such assumption: one system wrote all thirteen times.
Who runs each ending: read the record IDs
Every registry gives a name an internal ID, and many end it with a tag for the system that holds it. With the RDAP server that answers, the tags tell which operator stamped which name, and how precisely.
| Endings in the order | Operator, as the records show it | Time precision |
|---|
| .ai, .services, .info, .ventures, .support, .domains, .life, .email | Identity Digital (IDs end -DONUTS; RDAP at rdap.identitydigital.services) | milliseconds |
|---|
| .us | GoDaddy Registry (ID ends -GDREG; RDAP at rdap.nic.us) | seconds |
|---|
| .com, .net | Verisign (IDs end _DOMAIN_COM-VRSN, _DOMAIN_NET-VRSN) | seconds |
|---|
| .org | Public Interest Registry | milliseconds |
|---|
| .app | Google Registry (ID ends -APP) | milliseconds |
|---|
| .xyz, .store | CentralNic’s system (IDs end -CNIC; .store answers from Radix’s RDAP) | a trailing .0 or .000 |
|---|
| .biz, .design, .work | each its own RDAP server (rdap.nic.biz, rdap.nic.design, rdap.nic.work) | seconds |
|---|
| .io, .co, .it.com | no answer at the RDAP bootstrap; read from WHOIS | seconds |
|---|
The registrar is the same on every record we could read: GoDaddy.com, LLC, IANA registrar number 146.
The signature RDAP hides
The .us rules do not allow privacy services, which is why two names in the order carry Ribbit’s management company. Yet the .us registry’s RDAP answer leaves the registrant organization out, “Server policy”. The older WHOIS on port 43 still prints it. Someone who checks only RDAP will not see the signature at all.
Terminalcurl -sL https://rdap.nic.us/domain/ribbitcap.us \ | jq '.redacted[] | select(.name.type=="Registrant Organization")' whois -h whois.nic.us ribbitcap.us | grep "^Registrant Organization"
RDAP: "method": "removal", "reason": {"description": "Server policy"}. WHOIS: Registrant Organization: Ribbit Management Company LLC.
Five days to the second
Three records have a “last changed” date exactly five days after they were created: ribbitcap.us (created 18:41:09, changed 4 June 2025 at 18:41:10), ribbits.us (changed 4 June at 18:41:09) and ribbitcap.app (changed 4 June at 18:41:19.038, the same millisecond as its registration). Five days is the add grace period, the window in which a new registration can still be cancelled for a refund. A change on its last second is the system closing that window, not a person editing the names. Our reading
The other dates of 2026 are the registries’ own: Identity Digital changed its .ai, .services, .support and .domains records on 11 August 2026 at 22:18:36 UTC, the same second for all of them, and records of names at other registrars changed that week too.
Bought for different lengths
One order, three terms. The expiry dates show how long each name was paid for:
- Two years, to 30 May 2027: all five .ai names, tibbir.ai among them, and the .info, .services, .xyz, .store, .life and .email names, and ribbitvc.net.
- Three years, to 2028: the .com names, ribbita.com among them, and ribbitcap.net and ribbits.net.
- Five years, to 2030: the two signed .us names, and the .app, .org, .biz, .ventures, .design, .support, .domains and .work names.
The lengths do not follow the signature. They differ even within .net, so they were set name by name or by the shop’s defaults per ending, not by who signed. Our reading
The zone and the parked page
Terminaldig SOA tibbir.ai +noall +answer tibbir.ai. 3600 IN SOA ns45.domaincontrol.com. dns.jomax.net. 2025053000 28800 7200 604800 600
Read left to right: the primary name server; GoDaddy’s hostmaster address (jomax.net is a GoDaddy domain); the serial, 30 May 2025, version 00; then refresh every 8 hours, retry after 2, give up after 7 days, and remember a missing name for 10 minutes. These are GoDaddy’s defaults, and all thirty-four names carry the same serial.
The thirty-four names sit on five of GoDaddy’s name server pairs: ns09/ns10 (twelve names), ns45/ns46 (nine), ns55/ns56 (seven), ns63/ns64 (four) and ns51/ns52 (two). tibbir.ai shares ns45/ns46 with the signed ribbits.us; ribbitcap.us is on ns51/ns52 and ribbita.com on ns55/ns56. GoDaddy serves many customers’ names from each pair, so a shared pair ties nothing together.
Terminalcurl -s http://tibbir.ai/ <!DOCTYPE html><html><head><script>window.onload=function(){window.location.href="/lander"}</script></head></html>
The whole page, 114 bytes: GoDaddy’s parked page sends the browser on to /lander, which answers 301 to its https address, where GoDaddy’s parking content loads.
Certificates cannot date the order
Every certificate appears twice in the public logs: once as the precertificate a certificate authority logs before issuing, and once as the certificate itself. Read past the doubles and the first certificates after the order are days apart: ribbitcap.us on 30 May 2025 at 19:14:18 UTC, ribbita.com at 20:59:47, ribbitcap.ai on 1 June at 03:49:13 and tibbir.ai on 12 June at 19:02:22. All were issued by GoDaddy, by “Go Daddy Secure Certificate Authority - G2” in 2025 and by “GoDaddy TLS Intermediate CA DV - R1v1” in 2026. The 2026 certificates run 198 days, inside the 200-day ceiling that has applied to new certificates since 15 March 2026.
GoDaddy requests these for its parked pages on its own schedule. They show that the names are parked at GoDaddy. Only the registries show when they were bought.
Terminalcurl -s "https://crt.sh/?q=tibbir.ai&output=json" \ | jq -r '.[] | "\(.not_before) \(.name_value) \(.issuer_name)"' | sort -u
The store’s code: where “Ribbit AAC” comes from
ribbita.ai’s store is a single-page app. The copy of its script that the Wayback Machine saved on 15 April 2026 bundles wagmi and RainbowKit, two common libraries for connecting a crypto wallet. Two lines set the name a visitor’s wallet is told about:
www.ribbita.ai/assets/index-DlB4L9Qq.js, archived 15 April 2026 (minified; our notes after //)const {connectors:eSe}=XEe({appName:"Ribbit AAC",projectId:ZEe}) // wallet connectors; project key left outconst tSe=mwe({chains:MQ,transports:kR,connectors:eSe}) // wagmi configuration…H.jsx(gAe,{initialChain:K$,showRecentTransactions:!1,modalSize:"compact", appInfo:{appName:"Ribbit AAC",learnMoreUrl:"https://ribbit-aac.com"}, …}) // RainbowKit provider
appName is the app name the connection hands to the wallet, and learnMoreUrl is the “learn more” link in RainbowKit’s connect window. The same script carries RainbowKit’s own defaults (learnMoreUrl: "https://learn.rainbow.me/…"), which this setting overrides. The script also holds a WalletConnect project key, which we leave out. ribbit-aac.com has never been registered.
Rebuild the timeline yourself
A few lines of Python print every registration time that RDAP serves, sorted. Wait a second or two between lookups; registries limit fast callers. rdap.org refuses Python’s default identity, hence the User-Agent line. The .us, .io, .co and .it.com names need WHOIS instead.
Python 3import json, time, urllib.requestnames = ["ribbitcap.ai", "ribbit.services", "ribbitcap.info", "ribbitcapital.ai", "ribbit-cap.ai", "ribbitvc.com", "tibbir.ai", "ribbita.com", "ribbit.email"]rows = []for n in names: req = urllib.request.Request("https://rdap.org/domain/" + n, headers={"Accept": "application/rdap+json", "User-Agent": "rdap-check/1.0"}) r = json.load(urllib.request.urlopen(req)) reg = next(e["eventDate"] for e in r["events"] if e["eventAction"] == "registration") rows.append((reg, n)); time.sleep(1.5)for reg, n in sorted(rows): print(reg, n)