Observed cohorts

Observed cohorts are curated and sometimes overlapping analytical lenses across the fixed .auDO panel. They help readers examine current visible posture and observed change across related sets of domains.

They are not rankings, exhaustive classifications, organisation comparisons or whole-sector assessments.

Curated groupsAggregate context Coverage limits

Observed groups

Cohorts in the current panel

Select a published cohort to view transparent membership, current posture and 30-day and 90-day aggregate signal summaries.

Loading observed cohort cards from the public cohort index...

Composition context

Cohorts are curated panel lenses

Cohorts organise domains already included in the fixed .auDO panel through public-service, industry and public-interest perspectives.

-domains in fixed panel
-published cohort lenses
-domains in more than one published cohort
-longest available cohort window

Loading cohort composition from namespace-panel context...

A domain may appear in more than one analytical cohort. Cohort membership totals therefore do not sum to the fixed panel size.

The suffix mix explains the .auDO panel groups only. It does not measure sector-wide adoption or namespace-wide posture.

How to read cohorts

A way to organise the observed panel

Cohorts group domains already included in the fixed .auDO panel by broad context, such as government, education, media, not-for-profit or commercial relevance.

Logical grouping

Cohorts are a way to organise the curated panel so public domain-layer signals can be described more clearly.

Aggregate context

Cohort views are intended to support aggregate interpretation, not unnecessary domain-by-domain comparison.

Not sector coverage

Cohorts are not complete sector coverage, ordered assessments, risk scores or labels of domain quality.

Use alongside

Browse .auDO State pages, Signals, Reports and Methodology to understand what is being observed and where the limits are.

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.