RDAP and registration signals

Visible RDAP availability, status and registration-lifecycle signals across the fixed .auDO panel.

Fixed observation panelLatest run 10 Sep 202630/90-day windows

Latest available data: 10 Sep 2026

What this State view answers

Is public registration information available and stable, which status signals are visible, and where has registration-layer state changed?

Show the availability, visible state and completeness of public registration metadata, together with observed RDAP-status, restrictive-status and registration-lifecycle changes during defined observation windows.

What is visible now

Current posture is rendered from the canonical State contract for the fixed panel, not from compatibility metrics.

99RDAP available
1RDAP unavailable
99Registrar visible
100Active Domains

RDAP Statuses

  • available9999%
  • temporary_collection_unavailability11%

Restrictive Status Visibility

  • no_restrictive_status_visible100100%
  • restrictive_status_visible00%

Observed movement

30-day window

12 Aug 2026 to 10 Sep 2026

19 material trust-posture observations were visible across the fixed panel during the selected 30-day window. No additional supporting observations were recorded.

19Material
0Supporting
0Routine churn
12Affected domains
7Repeated domains

Continuous per-domain coverage cannot be established from the public manifest artefacts alone; counts use available generated event records.

Retained event types

  • RDAP Status Changed19rdap_status_changed

90-day window

13 Jun 2026 to 10 Sep 2026

73 material trust-posture observations were visible across the fixed panel during the selected 90-day window. No additional supporting observations were recorded.

73Material
0Supporting
0Routine churn
44Affected domains
25Repeated domains

Continuous per-domain coverage cannot be established from the public manifest artefacts alone; counts use available generated event records.

Retained event types

  • RDAP Status Changed73rdap_status_changed

Evidence

30-day evidence

90-day evidence

Cohort lenses

Cohort lenses preserve the published cohort order and are descriptive comparisons, not rankings.

Australian government domains

14 domains observed

RDAP available
14
RDAP unavailable
0
Registrar visible
14
30d events
1
30d affected
1
30d repeated
0
90d events
4
90d affected
3
90d repeated
1
View cohort

Australian not-for-profit domains

16 domains observed

RDAP available
16
RDAP unavailable
0
Registrar visible
16
30d events
3
30d affected
2
30d repeated
1
90d events
18
90d affected
9
90d repeated
8
View cohort

Australian higher education domains

10 domains observed

RDAP available
10
RDAP unavailable
0
Registrar visible
10
30d events
6
30d affected
3
30d repeated
3
90d events
8
90d affected
4
90d repeated
4
View cohort

Australian media domains

8 domains observed

RDAP available
8
RDAP unavailable
0
Registrar visible
8
30d events
4
30d affected
2
30d repeated
2
90d events
6
90d affected
3
90d repeated
3
View cohort

Retail and marketplace domains

14 domains observed

RDAP available
14
RDAP unavailable
0
Registrar visible
14
30d events
1
30d affected
1
30d repeated
0
90d events
13
90d affected
9
90d repeated
3
View cohort

Financial services domains

8 domains observed

RDAP available
8
RDAP unavailable
0
Registrar visible
8
30d events
0
30d affected
0
30d repeated
0
90d events
8
90d affected
6
90d repeated
2
View cohort

Public-interest domains

21 domains observed

RDAP available
21
RDAP unavailable
0
Registrar visible
21
30d events
2
30d affected
2
30d repeated
0
90d events
12
90d affected
7
90d repeated
4
View cohort

Australian software platforms

5 domains observed

RDAP available
4
RDAP unavailable
1
Registrar visible
4
30d events
0
30d affected
0
30d repeated
0
90d events
0
90d affected
0
90d repeated
0
View cohort

How to interpret this view

RDAP provides public registration-layer information where available. Status, redaction and lifecycle fields require registry-specific context. Missing optional fields, temporary collection unavailability and fallback-source use do not establish poor governance, non-compliance or a change in the domain itself.

Published limitations

  • Derived from public .auDO observations generated from the canonical observatory dataset.
  • Counts describe the observed .auDO panel, not the whole .au namespace.
  • Missing optional fields are counted as missing rather than inferred.
  • RDAP shows public registration-layer information where available.
  • RDAP redaction or missing fields do not prove non-compliance or poor governance.
  • Public registration signals do not reveal private operational intent.
  • Domain creation and expiry date counts are unavailable when those optional fields are absent from the observatory dataset.

Data quality and availability

  • Required public event scope: observatory.
  • Domain Created Date Known Count is not available in this generated payload.
  • Domain Expiry Date Known Count is not available in this generated payload.
  • RDAP Authoritative Count is not available in this generated payload.
  • RDAP Fallback Count is not available in this generated payload.
  • RDAP Redacted Count is not available in this generated payload.