.au Domain Observatory

Explainers

Plain-language explainers for governance, communications and technical readers who need to understand how public domain-layer signals are observed, what they may suggest, and what they cannot prove.

Plain languagePublic signalsGovernance context

What these explainers are for

.auDO observes public domain-layer signals across a fixed panel of .au domains. These explainers describe the concepts behind those observations in plain language.

They are designed for readers who need to interpret DNS, registration, mail posture and provider signals without turning visible change into unsupported conclusions.

Public signals can help make domain-layer change easier to notice, explain and govern. They do not, by themselves, prove risk, intent, operational concern or poor governance.

Core domain-layer concepts

What is a domain-layer signal?

The keystone concept behind .auDO: visible public evidence from DNS, registration, mail posture or infrastructure.

Read explainerSignals

What public DNS can and cannot show

How public DNS records support observation, and why visible records must be interpreted with clear limits.

Read explainerMethodology

Registry, registrar and registrant

A plain-language guide to the roles behind domain registration and administration.

Read explainerState view

What is domain delegation?

How a registered domain points to authoritative name servers, and why delegation is a meaningful control-plane signal.

Read explainerState view

Why repeated observation matters

Why dated, repeated observation is more useful than isolated snapshots when interpreting public domain-layer change.

Read explainerObservation panel

Domain-layer governance

A non-specialist guide to treating domains, DNS, registration and mail posture as managed organisational assets.

Read explainerState of .au

Observable signal explainers

What is RDAP?

How public registration data can show registrar, status, date and related metadata signals for observed domains.

Read explainerState view

What registrar changes can mean

How visible registrar movement can reflect administration, supplier change, consolidation or portfolio management.

Read explainerState view

Why nameserver changes matter

How nameserver movement can indicate visible DNS control-plane change without implying concern by default.

Read explainerState view

What MX records reveal about mail posture

How public mail routing records can show visible email provider and mail posture context.

Read explainerState view

Why DMARC matters

What DMARC can tell observers about visible mail posture, and where public DMARC evidence has clear limits.

Read explainerState view

What is DNSSEC?

How DNSSEC-related evidence appears in public observations, and what visible presence or absence can and cannot show.

Read explainerState view

How to use these pages

Use these explainers as a companion to the .auDO Signals library, State of .au pages and dated reports.

Signals explain the field-level evidence .auDO records. State pages summarise the current observed panel. Reports preserve dated evidence. Cohorts provide grouped context where a reader wants to compare public signals across a defined set of domains.

None of these views should be read as a rating, ranking, compliance finding or security assessment.

Use Signals for field-level meaning, State pages for aggregate posture, Reports for dated evidence, Cohorts for grouped context and Methodology for collection limits.

Observation GuideSignalsState of .auReportsObserved cohortsMethodology

Introducing .auDO

A short, shareable brief explaining what .auDO is, why it exists, and how it makes public .au domain-layer trust signals more visible, consistent and explainable.

Download the .auDO introduction PDF