How to Read a .auDO Observation

.auDO observations are public signals, not findings. This guide helps you move from visible change to cautious interpretation without treating observations as scores, allegations or proof of risk.

Public signals Cautious interpretation Australian .au context Not a score

Before you start

Observations are descriptive records

A visible change is not automatically a risk. Public data cannot prove internal intent, approval, compromise, compliance or governance quality.

Visible, not complete

.auDO reads public DNS, RDAP, mail, DNSSEC and provider signals. Public evidence is useful, but it is not the whole operating picture.

Change needs context

One observation rarely tells the whole story. Repeated patterns can support stronger interpretation, but they still need cautious wording.

Counts are summaries

Panel counts and provider summaries help readers compare context. They are not ratings, rankings, findings or organisation comparisons.

Observation Guide

Read the observation in context

Work through four simple prompts to understand what a visible .auDO observation may suggest, what it cannot show, and what to compare next. This guide does not look up domains or make assessments.

Step 1 of 4

Loading static reading guide content.

Your reading note

Complete the four prompts to see how this observation can be read, where its limits sit, and what to compare next.

Where to go next

Keep reading across .auDO

Use this guide alongside the public surfaces that preserve evidence, define signals and explain collection limits.