Captures public state
Each run preserves visible domain-layer posture before interpretation is applied.
Why .auDO exists
The .au namespace is part of the public-facing trust layer of Australian organisations.
.auDO observes a fixed panel of domains over time so visible DNS, RDAP, mail, registrar and provider signals can be preserved, compared and explained.
A single lookup shows a moment. Repeated observation shows behaviour.
Public signals
Repeated observation
State summaries
Evidence-led reports
What it does
.auDO observes, preserves and explains visible domain-layer change
.auDO collects public DNS, RDAP, mail, registrar, DNSSEC and provider signals from a curated panel of .au domains. It turns repeated observation into cautious public evidence.
Compares change
Repeated snapshots make drift, movement, gaps and recurring patterns easier to inspect over time.
Publishes cautiously
State pages, reports, signals and explainers separate observed evidence from interpretation.
Project context
A fixed observation panel with external namespace context
.auDO observes a fixed panel. auDA registry data is used as external namespace context, not as .auDO observation evidence.
-fixed panel domains
-wider namespace names
-latest registry reference
-panel scale
What the panel supports
Repeated observation of the same domains so visible public signals can be preserved and compared over time.
What the registry context supports
External scale context from auDA monthly registry statistics so readers can distinguish panel observations from wider namespace size.
What .auDO avoids claiming
.auDO does not claim whole-namespace coverage, sector representativeness, domain scoring, compliance assessment or organisational risk rating.
How to use .auDO
Start with the current state, then inspect the evidence
.auDo is organised around a simple journey: current aggregate posture, dated evidence, signal definitions, plain-language explainers and cohort context.
State of .au
Derived public summaries showing the current visible posture of the observed panel.
Reports
Dated evidence records and curated analysis showing what changed and when.
Signals
Canonical human-readable definitions of the public fields and signal tiers .auDO uses.
Explainers
Plain-language guides for DNSSEC, DMARC, RDAP, registrar change and domain-layer governance.
Observed cohorts
Logical groupings of domains in the curated panel, used to explain public signals in context.
Method
The collection, preservation, classification and publication model behind the observatory.
Download the introduction brief
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
A public-interest observatory, not a rating system
What it is
A small, independent observatory focused on visible domain-layer trust signals in the .au namespace.
What it is not
It is not a registry service, vulnerability scanner, incident feed, audit, rating system, compliance certification or complete view of the .au namespace.
Domain Governance
For organisations wanting to turn domain-layer visibility into an internal governance conversation, Bryan also publishes the Domain Governance Baseline.
Observation over time
method, not results
A simple schematic of repeated observation: state is captured across multiple runs, small changes become visible, and patterns only emerge later.
Operation
Operation and independence
.auDO is an independent public-interest observatory. Its observations are descriptive records, not allegations, endorsements or assessments of observed organisations.
Maintained independently
.auDO is authored and maintained by Bryan Chetcuti as part of broader public work on digital trust, domain governance and observable trust signals.
Infrastructure services
.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.
Contact
Questions, feedback or collaboration enquiries about .auDO, observed signals or domain-layer governance can be sent to Bryan Chetcuti.