Summary

  • The Australian Business Register fixes Cloud Registry Pty Ltd as an Australian private company active from 18 May 2009, prints ACN 137 160 975 beside the ABN, and dates its own status line to 3 January 2014.
  • ICANN's .cloud registry agreement page names Aruba PEC S.p.A. as the operator under an agreement dated 16 April 2015, which is not the company the index entry appears to promise.
  • auDA's 2012 Industry Advisory Panel recorded two respondents declaring interest in competing for the .au registry, recommended renegotiating with AusRegistry for two, three or four years, and named neither respondent.

Begin with the register that fixes a legal person rather than a service. The ABN Lookup view for 53 137 160 975 prints four things worth quoting exactly: "Entity name: Cloud Registry Pty Ltd", "Entity type: Australian Private Company", "ABN status: Active from 18 May 2009", and the corporations-register number ACN 137 160 975 on the same page (ABN Lookup). A dated entity, a type, and a second register's number printed where a reader can see it.

The same page prints two dates, and they are not the same kind of date. "ABN last updated: 03 Jan 2014" is the register's own statement about when the entry last moved. "Record extracted: 22 Nov 2026" is when the view was taken. Twelve years, ten months and nineteen days separate them — my subtraction, not a figure the page prints. The distinction is the register-currency problem in one line: "active" is a status, not a date, and a company can hold one on a record whose update stamp predates the extraction by almost thirteen years.

Now the correction this piece owes its own commission. I set out to read a gTLD registry agreement — the trigger, the notice, the cure period, the forum — and the safest candidate looked like the string closest to the company's name. ICANN's index entry for .cloud prints "Operator Aruba PEC S.p.A.", "Agreement Date 16 April 2015" and "Agreement Type Base , Non-Sponsored" (.cloud Registry Agreement). The operator field of record is not Cloud Registry Pty Ltd. That is a finding about one details page and one string, not a general negative about every ICANN record — but it is enough to end the argument I had planned, because a termination analysis aimed at the wrong counterparty is not a near miss, it is a different article. Cloud Registry Pty Ltd did nothing wrong here; the error of aim is mine.

A details page is also an index entry, not the agreement instrument. What it establishes is the operator field as published. Nothing read here suggests the index is wrong, and nothing read here establishes what the agreement with Aruba PEC S.p.A. actually says.

auDA's side is stranger, and more useful. The 2012 Industry Advisory Panel index page lists a download titled "Cloud Registry - Industry Advisory Panel (2012) Issues Paper submission", filed alongside the Panel's final report and its meeting minutes, and dates the Panel's work from March 2012 to a final report in December 2012 (Industry Advisory Panel (2012)). The index page carries the title. It carries no text, no date and no signatory, and it does not say which legal person made the submission.

The minutes are where the count appears. On 26 July 2012 the Panel recorded that "two respondents to the Issues Paper declared their interest in competing for the .au 2LD registry", and that another interested party had made a confidential approach to auDA during the consultation period (2012 IAP minutes). In the passage obtained, neither respondent is named. That is a statement about the passage, not about every page of the document: the minutes were read through retained extracted text rather than a native PDF viewer, so page layout and anything outside that passage sit outside my evidence.

The final report of December 2012 repeats the count and turns it into a recommendation. The Panel "also notes that two respondents to the Issues Paper declared their interest in competing for the .au 2LD registry", then recommends that the auDA Board "initiate renegotiations with AusRegistry to extend the current contractual arrangements for 2, 3 or 4 years", proceed to "a full RFT" should renegotiations fail, and "commit to a formal RFT process following the expiry of the renegotiated registry agreement" (Final Report, December 2012). Two declared suitors, an incumbent extended for two, three or four years, and a tender deferred to the end of the extension. The Panel weighed the competitive interest and routed around it. That is a decision, not a silence.

The oldest document comes closest to naming a person. ICANN's HSTLD advisory group volunteer list, dated 23 December 2009, carries the line "Ruud Verstijnen CEO, Cloud Registry Pty. Ltd." (HSTLD volunteers, 23 December 2009). A volunteer list records a title and an affiliation as at its date. It does not establish a corporate office, a directorship or a present role, and "CEO" in a self-nominated listing is a management description rather than an entry in a companies register. It is, though, the earliest document in this set that puts the company's name in an ICANN-published file. Seven months and five days separate 18 May 2009 from 23 December 2009 — my subtraction again.

So the picture is three registers each answering a narrow question and none answering the question a reader actually has. The tax and business register answers whether a legal person with this name and number exists, and what type it is. The ICANN index answers who holds the operator field for this string. auDA's panel archive answers whether a document bearing this name entered the 2012 consultation, and its minutes answer how many respondents declared competitive interest without answering which.

None of those records is defective. Each is a faithful account of its own transaction. But the sentence a reader wants — that this company is the entity behind that submission, that declared interest, that back-end role — is not printed on any of the six documents read here, and nothing in this set tests whether such a document exists outside it. The whole reading is assembled, and the assembly is an act of authorship by whoever performs it. The incompleteness is not only the reader's, either. auDA counted the two respondents in its own minutes and in its own final report and printed neither name, while its own index page carries the submission title: that is an observable feature of those two records, stated here without a claim about why. This desk is in the directory as Cloud Registry Pty Ltd, which is the name; it is not a finding of authority.

That is the part worth keeping. A register entry is evidence of what a registrar recorded, on a stated date, about a stated string. Authority, contract and conduct are three further facts, and each needs its own document. The .cloud page had to be checked before an argument could stand on it; it was checked, and the argument fell. The auDA documents had to be read for what they count rather than for what they imply; they count two, and they name nobody.

Five boundaries, all dated to this review. The Cloud Registry Issues Paper submission itself was not obtained: a file path for it appeared only in secondary commentary, so no URL for it is cited here and no claim rests on its contents. The minutes, the final report and the volunteer list were read through retained extracted text for the exact URLs, because the adapter reported no readable text for native PDF access; page layout was not checked.

ASIC's own register was not obtained, so this piece states no current registration status, officeholder, shareholder or registered office — the ABN view is a taxation and business-register view, and the aggregator pages seen in search are not registry-of-record documents. ICANN's new gTLD application records and registry-agreement index were not systematically searched, so the operator-field finding is a finding about one details page. auDA's later .au registry procurement records for 2017 and 2023 were not retrieved.