Exact-domain workflow
- Copy only the hostname, removing paths and tracking parameters.
- Compare spelling, hyphens and top-level domain with the site you opened.
- Search ACMA’s current blocked-site resource and relevant investigation releases.
- Record exact match, related-brand match or no match; do not merge those outcomes.
- If a mirror appears, repeat the check from the beginning rather than transferring trust.
Interpret the result correctly
| Result | What it supports | What it does not support |
|---|---|---|
| Exact hostname listed | The named domain appears in the dated official record. | That every lookalike domain is identical. |
| Related brand listed | A reason to investigate operator and domain relationships. | An automatic exact-domain match. |
| No result found | No match was located in the checked resource on that date. | Safety, legality, licensing or future status. |
Do not chase mirrors
A new domain supplied after a block can expose a different operator, payee or software package. Do not install a replacement app, send funds to a new alias or hand over documents until the complete identity and safety checks are repeated.
Use the evidence before the action
The live route can change. Recheck identity, terms and account conditions before depositing, installing or uploading documents.
Use the maintained route only after the exact-domain checkQuestions for this exact task
Is a blocked brand the same as a blocked hostname?
Not always. Record the exact hostname and separately investigate brand or operator relationships.
Does no ACMA match mean a site is safe?
No. It only describes the result of one dated search in one official resource.
Should I use a mirror after a block?
Do not transfer trust. Treat every new hostname as a new identity and payment check.