Captures public state
Each run preserves visible domain-layer posture before interpretation is applied.
.auDO independently observes and explains public domain-layer trust signals across the .au ecosystem, preserving evidence over time to support transparency, resilience and better governance.
The public trust layer of .au is important but difficult to see. Repeated observation makes change and persistence more visible, explainable and usable.
What it does
.auDO repeatedly observes a fixed panel of .au domains, preserves visible DNS, registration, mail and infrastructure signals, and turns repeated observation into cautious public evidence and explanation.
Each run preserves visible domain-layer posture before interpretation is applied.
Repeated snapshots make drift, movement, gaps and recurring patterns easier to inspect over time.
State pages, cohort views, reports, signals and explainers separate observed evidence from interpretation.
Project context
.auDO observes a fixed panel. auDA registry data is used as external namespace context, not as .auDO observation evidence.
Repeated observation of the same domains so visible public signals can be preserved and compared over time.
External scale context from auDA monthly registry statistics so readers can distinguish panel observations from wider namespace size.
.auDO does not claim whole-namespace coverage, sector representativeness, domain scoring, compliance assessment or organisational risk rating.
How to use .auDO
The public surface supports five flagship outputs: the Continuous Evidence Archive, State of .au, Monthly Observatory Brief, quarterly and featured longitudinal analysis, and public method and guidance.
Derived public summaries showing the current visible posture of the observed panel.
Daily evidence, Monthly Observatory Briefs, quarterly reviews and featured analysis showing what changed, when and with what supporting context.
Canonical human-readable definitions of the public fields and signal tiers .auDO uses.
Plain-language guides to domain-layer signals, infrastructure, governance and the limits of public observation.
Curated and sometimes overlapping analytical lenses used to examine visible posture and observed change across selected panel domains.
The collection, preservation, classification and publication model, supported by signal definitions, explainers and responsible-reading guidance.
Approved descriptions, citation guidance, identity assets and stable project information for people referring to, researching or writing about .auDO.
A short, shareable overview of .auDO’s purpose, scope and reporting posture, including what it observes, what it avoids claiming, and why cautious public-domain observation matters.
Scope and limits
An independent public-interest observatory and evidence resource focused on visible domain-layer trust signals in the .au ecosystem.
It is not a registry authority, regulator, vulnerability scanner, incident feed, audit, assurance service, rating system, compliance certification or real-time whole-namespace monitor.
The Domain Governance Baseline is a separate practical self-assessment published by Bryan Chetcuti. It helps organisations examine whether domain ownership, renewal, DNS, email authentication, monitoring and accountability are clearly understood and governed.
A simple schematic of repeated observation: state is captured across multiple runs, small changes become visible, and patterns only emerge later.
Operation
.auDO is an independent public-interest observatory. External funders, clients, partners, providers and observed organisations do not direct its scope, method, findings, language, publication timing or corrections.
.auDO is owned and editorially controlled by Bryan Chetcuti. Final responsibility for its scope, method, findings, publication timing and corrections rests with him.
The Vigo Group currently provides operational services and bears project costs. Paid advisory work undertaken by Bryan Chetcuti or The Vigo Group is separate and does not purchase influence over .auDO observation or publication.
.auDO uses Supabase, GitHub and Cloudflare infrastructure services for collection, storage, automation, publication and delivery. These providers are acknowledged for transparency and do not sponsor, review or endorse .auDO’s observations.
Questions, feedback or collaboration enquiries about .auDO, observed signals or domain-layer governance can be sent to [email protected].