Received a Domain Registration Compliance Email? Here’s How to Check If It’s Legitimate
If a “domain registration compliance” email has recently landed in your inbox warning that your domain is non-compliant or at risk of suspension, you’re not alone, and you’re right to pause before acting on it.
A wave of these notices is going out across Australia at the moment. Some are genuine and worth acting on. Others are vague, automated, and confusing, and a few reference domains the recipient doesn’t even own or that are not even with the registrar sending the notice. This guide explains what .au domain compliance actually is, why you might be hearing about it now, how to tell a clear notice from a poor one, and exactly what you can check yourself before you do anything.
What “domain registration compliance” actually means
Every .au domain is issued under rules set by auDA, the body that administers Australia’s domain space. For the most common business extensions, .com.au and .net.au, you must be an Australian commercial entity and hold an active ABN, ACN, or an Australian trademark that matches the domain. Other namespaces have their own rules. For example, .org.au is for not-for-profit entities, and .id.au is for Australian individuals.
Compliance simply means the registration details on your domain still satisfy those eligibility rules. If the ABN used to register a .com.au is cancelled, or the registrant details no longer match the eligibility criteria, the domain is no longer compliant, and that can put your renewal at risk.
Registrars (the companies you register and renew domains through) are obligated to check eligibility at three points: when a domain is registered, when it is transferred, and when it is renewed. If something doesn’t meet the rules at one of those points, your registrar should contact you to clarify or correct it.
Why you might be receiving these emails now
The modernised and consolidated .au licensing rules came into effect in 2021, however enforcement has been uneven. While all registrars have been performing validation at registration since then, many larger registrars are only now beginning to actively check and act on eligibility at renewal. That’s why a domain you’ve held without issue for years can suddenly trigger a compliance notice. Nothing about your domain has necessarily changed; the registrar your domain is with has simply started enforcing rules that were always there, and that they’re obligated to enforce under their agreement with auDA.
So if a notice has caught you by surprise, that timing is the likely explanation. It doesn’t automatically mean the notice is wrong, but it does mean it’s worth checking carefully rather than acting under pressure.
What a clear, legitimate compliance notice looks like
A good notice should leave you in no doubt about what the problem is and what to do. It will:
- Name the exact domain affected, one you recognise and actually hold.
- State specifically what is non-compliant. For example, the precise ABN used for eligibility and the date it was cancelled.
- Explain your options clearly, including any costs involved.
- Reference the relevant auDA rules so you can verify the requirement yourself.
- Give you a reasonable, honest timeframe rather than an artificial countdown.
As an illustration, a clear notice reads something like this:
Dear Client,
Your domain [insert domain] is due for renewal on [date].
A validation check on the current WHOIS information shows that the ABN [lists ABN] used as eligibility to register this domain was cancelled on [date], which means you are no longer eligible to hold the domain under auDA rules, and the upcoming renewal will fail.
You have two options to maintain your domain registration: you can reactivate the ABN, or update the registrant details (to an eligible entity) by completing a Change of Registrant (which may require a supporting chain of title) before expiry.
A Change of Registrant costs [amount].
For the full eligibility requirements, see the auDA licensing rules.
Notice what that does: it tells you the specific problem, the specific cause, your specific options, and the cost, and it points you to the source. You can act on it with confidence because nothing is hidden.
Warning signs that a notice may not be accurate
Not every compliance email is this clear. Be cautious if a notice does any of the following:
- It’s vague about the actual problem. A notice that quotes a raw system error code (something like “identifier type not permitted”) without plain-English explanation isn’t telling you what’s genuinely wrong or how to fix it.
- It refers to a domain you don’t recognise. A legitimate notice will always concern a domain you actually hold. If you receive a notice about a domain you don’t own, no longer own, or that doesn’t appear in your account, that can indicate an automated, poorly targeted mailout rather than a genuine, verified issue.
- It’s unclear who actually sent it. You should be able to tell immediately which registrar the notice is from and confirm it matches the registrar your domain is actually with.
A notice showing one or two of these signs isn’t necessarily a scam, but it does mean you should verify before paying anything or sharing details.
What you can check yourself
Before you respond to any compliance notice, you can confirm your own situation in a few minutes:
- Confirm it’s your domain. Check the domain named in the email is one you actually hold and that it appears in your account with your current registrar.
- Check your ABN or ACN is current. If your eligibility was based on an ABN, look it up on the ABN Lookup register to confirm it’s still active. A cancelled or lapsed ABN is the most common genuine cause of a .com.au compliance issue.
- Check the registrant details on the domain. You can look up the public registration details of any .au domain through the official auDA WHOIS tool . This shows you what’s currently on record and helps you see whether the details still meet the eligibility rules.
- Contact your registrar directly. Use the contact details from your own account or the registrar’s official website, not a link or phone number from a suspicious email, to confirm whether the notice is genuine.
If everything checks out and the issue is real, the fix is usually either reactivating a lapsed ABN or completing a Change of Registrant.
A quick word on Change of Registrant
One thing that catches people out: correcting eligibility is often not a simple “update my details” edit in a portal. If the registrant entity itself needs to change (a different ABN, ACN, trademark or incorporated body), that’s a formal Change of Registrant, which is a paid, documented process rather than a quick field update. A clear notice will tell you this upfront, including the cost, so there are no surprises.
How we approach it at Domain Central
We think compliance notices should make your life easier, not harder. Rather than waiting for a renewal to fail, we proactively scan upcoming renewals, identify any domains that would fail eligibility, and contact the registrant ahead of time, spelling out exactly which detail is non-compliant and what the options are. No error codes, no countdowns, no guesswork.
If you’ve received a compliance notice from your current registrar and you’re left guessing what it actually means, that’s worth reflecting on. You’re entitled to a registrar that tells you precisely where you stand and helps you fix it. If that’s not the experience you’re having, you’re always free to transfer your domain to us and bring it somewhere that communicates clearly.
In the meantime, the most important thing is this: don’t act on any compliance notice under pressure. Check the domain is yours, check your ABN is current, look up the details on the auDA WHOIS, and confirm directly with your registrar. A genuine issue will still be there after you’ve taken ten minutes to verify it, and a misleading one will be a lot easier to spot.
Domain Central is an accredited auDA and ICANN registrar. For the full .au eligibility and allocation rules, see the auDA licensing policy.
