Home Entry
Introduces the observatory, latest state, core pathways, learning resources and repeated observation model.
Visual site map
A human-readable map of the public .auDO observatory surface, showing how the main pages, evidence views, learning pages and governance pages relate to each other.
The primary navigation stays deliberately small. This page makes the wider hierarchy visible without turning every public page into a top-level menu item.
Public hierarchyObservation viewsEvidence pathsLearning pagesProject context
4primary nav entries
6major public areas
3evidence pathways
1crawler sitemap XML
Hierarchy
How the public observatory is organised
The map is grouped by reader intent: start, observe, understand, read evidence, and check project context.
Start
The main entry point and the four compact navigation routes used across the site.
Primary navOrientation
Primary navigation Compact
The current top navigation stays focused on the highest-value public entry points.
Observe
Pages that show the fixed panel, grouped cohorts, and current state summaries across visible trust signals.
Observation Panel Panel
The fixed observation panel, panel design, repeated observation rationale and limitations.
State of .au Current state
Current summaries for major public signal families across the observed panel.
Observed cohorts Grouped view
Curated observation groups used to compare visible signals without treating the cohorts as rankings or complete sector coverage.
Supporting observation context Context
Reference paths that help explain why the same domain panel is observed over time.
Understand
Learning pages that explain the signals .auDO observes and how to read them carefully.
Signals Reference
The signal directory for DNS, RDAP, mail, provider, provenance and evidence fields.
Explainers Plain language
Short pages that explain domain-layer concepts for governance, communications and technical readers.
- What is a domain-layer signal?
- What public DNS can and cannot show
- Registry, registrar and registrant
- What is domain delegation?
- What MX records reveal about mail posture
- Why repeated observation matters
- What is DNSSEC?
- Why DMARC matters
- What is RDAP?
- Why name server changes matter
- What registrar changes can mean
- Domain-layer governance
Read evidence
Report and archive routes that preserve dated observations, featured interpretation and periodic summaries.
Reports Evidence
The report entry point for monthly briefs, latest daily evidence records, featured analysis and archive access.
Featured reports Interpretation
Longer public notes anchored to observed signals, defined windows and explicit limitations.
Machine-readable public surfaces Index
Public indexes that support discovery and syndication without replacing the human-readable report pages.
Dated reports Archive
Dated daily reports are exposed through the Reports page and report archive controls rather than listed one by one here.
Project and governance
Pages that explain what .auDO is, how it works, what it does not claim, and how to get in touch.
Project context Governance
Public context for the observatory, methodology, limitations and related work.
Related work External
Related public work that helps position .auDO within the broader digital trust surface.
Reading notes
What else this page should make clear
A visual site map should do more than list URLs. It should explain how the observatory expects people to move through the evidence.
Reader pathways
Group links by intent: start with the panel, view the current state, compare cohorts, read dated evidence, or learn what a signal means.
Evidence boundaries
Keep dated reports, featured interpretation and explanatory pages visually separate so readers can see the difference between observation and explanation.
Public scope
Show public pages only. Gated or private investigation views should not be surfaced as public navigation targets.
Site map scope
This page is the human-readable visual site map. The crawler-facing sitemap remains available at /sitemap.xml.