Observation Panel
A current view of the observed panel, latest signal mix, provider concentration, and repeated patterns over time.
Loading panel context...
Panel composition and current state
Stable composition context plus the latest observatory snapshot metrics.
Fixed panel scale
100 domains are observed repeatedly. This is a fixed observation panel, not a statistical sample.
Wider namespace context
The latest external registry reference covers - names under management for -.
Panel per million
The .auDO panel is deliberately small and curated for repeated observation. auDA registry statistics provide wider namespace scale only.
Scale label: -.
Panel composition
The active panel tracks a fixed set of .au domains for repeated, longitudinal observation rather than namespace-wide coverage.
Panel composition describes the .auDO observation panel only. It is not a proxy for registry-wide .au composition.
| Dimension | Current framing |
|---|---|
| Total domains | Fixed panel domains |
| Namespace mix | Derived from the panel composition artefact when available |
| Cohort model | Curated and sometimes overlapping analytical lenses |
| Selection approach | Curated for public relevance and signal diversity, not random sampling |
| Geographic scope | Australian .au namespace only |
Current visible posture
Canonical State topics summarise current public posture without replacing daily evidence metrics.
Loading current State topics...
Latest signal profile
Loading latest manifest-backed profile...
A concise orientation to the latest dated evidence record. Detailed findings remain in Reports.
Visible infrastructure providers
Loading visible provider concentration...
DNS providers
Registrars
Provider summaries show up to three visible providers in each published category. They are orientation only and do not indicate endorsement, service quality, or internal arrangements.
What has changed over time Longitudinal summary windows
No longitudinal summary artefact was published for this report run.
Each window summarises the retained observations currently available for that period. Counts are evidence summaries, not risk scores.
Signal tiers
Signal tiers help separate different kinds of observed change while preserving all raw observed events. The canonical definitions live in the Signals library.
| Tier | Meaning | Example event types |
|---|---|---|
| High-signal trust posture change (Tier 1) | Changes that may affect visible domain control, mail posture, DNSSEC posture, registration status, or other public trust signals | nameservers_changed, rdap_status_changed, registrar_changed, dnssec_changed, dmarc_present_changed, spf_present_changed |
| Meaningful infrastructure movement (Tier 2) | Changes that suggest visible infrastructure or provider movement | dns_provider_changed, email_provider_changed, mx_changed, sustained_a_changed, sustained_aaaa_changed |
| Routine or low-confidence churn (Tier 3) | Changes that are common, expected, low confidence, or not meaningful without additional context | a_changed, a_record_changed, aaaa_changed, aaaa_record_changed, txt_changed |
| Unclassified | Observed event types not yet explicitly mapped. These are retained as evidence and treated conservatively until classified. | Unmapped event types retained for later classification |
Signal tiers are interpretive metadata, not risk scores. They do not prove impact and do not imply compromise. Daily reports remain factual and transactional; stronger interpretation belongs in featured or periodic reports where repeated observations support it.
Reading guide
How to Read a .auDO Observation
Use the Observation Guide to move from visible panel change to careful public wording without turning observations into scores, findings or domain-level conclusions.