How to check whether an email domain has been reused
An expired domain can return to the market, be registered by a new owner and begin sending email with a reputation shaped by someone else. That matters when an old supplier, customer or executive contact suddenly appears to be using the same domain again. A familiar address may look legitimate while the underlying organisation has changed completely.
Trusted Sender Score helps investigate this risk by checking a sender’s domain reputation, authentication records and indicators associated with email trust. The platform cannot make a historical ownership decision from one signal, but it can show whether the current domain setup is consistent with the identity you expect.
This is particularly useful for Australian organisations dealing with invoices, payroll changes and supplier banking requests. A domain that has been sitting unused after a lease expired may be snapped up and used for phishing before anyone notices the change.
The process is straightforward: collect the exact domain from the message, run a trust check, inspect technical records, compare the results with known contacts and preserve evidence. Treat the result as a risk assessment rather than a simple yes-or-no verdict.
Start with the exact sender domain
Read the address carefully and isolate the domain after the “@” symbol. Ignore the display name, which can be changed easily, and watch for lookalike spellings, unusual subdomains and substitutions such as “.co” instead of “.com.au”. A message that appears to come from a Melbourne business may actually use a newly registered variant.
Run the root domain through Trusted Sender Score rather than relying on a forwarded message or a shortened link. Check both the visible sender and any reply-to address, because attackers often make those values different. Save the result, timestamp and original email headers so the investigation can be repeated.
Read the trust result as a set of signals
A trust score provides a quick view of reputation and risk, but its value comes from the details behind it. The platform’s trust score guide explains how reputation indicators can support fraud detection without replacing human verification.
Pay attention to warnings about poor reputation, suspicious configuration or authentication failures. A domain with a clean score can still be newly controlled, while a low score may reflect historical abuse by a previous registrant. The combination of current DNS records, email behaviour and business context is more useful than a single rating.
Compare the domain’s current identity
Inspect DKIM and DMARC results to see whether the domain is authorised to send and whether its messages align with the claimed identity. SPF can also show which mail systems are permitted. A missing policy, a very permissive record or a sudden change in signing infrastructure deserves attention.
For Australian organisations, compare these results with the domain’s known website, phone number and ABN records. A “dodgy” invoice that uses a once-familiar domain but now points to unrelated hosting is a stronger warning than an authentication change alone. For .com.au names, the business relationship and eligibility details should also make sense.
Look for signs of a lapsed domain
A reused domain often shows a break in continuity. The website may have disappeared, MX records may have been removed and later recreated, or DKIM selectors may be completely different from those used by the former organisation. These changes do not prove an expired lease, but they indicate that the domain’s operational history may have changed.
Compare the current results with archived supplier records, old email headers and previous DNS snapshots where available. A domain that was inactive for months and then begins sending from a new provider warrants a fresh verification call. Do not use the phone number in the suspicious message; retrieve contact details independently.
Check for spoofing as well as takeover
A reused domain and a spoofed domain require different responses. With spoofing, the sender may be forging an address without controlling the domain. With reuse, the sender may genuinely control the domain but have no connection to the former owner.
Use the platform’s anti-spoofing resources to understand how authentication and domain alignment help separate these cases. DMARC enforcement can reduce unauthorised impersonation, but it cannot tell you whether a legitimate current registrant is the same company that used the domain previously.
Investigate several domains together
Scammers may register a group of related domains after an expired name becomes available. Check the sender’s root domain, links in the email, reply-to domain and any domain used for payment or document hosting. Bulk checking can make this practical for security teams reviewing a campaign or a large supplier list.
This approach suits Australian firms with distributed operations across Sydney, Brisbane and Perth, where procurement and finance teams may receive messages at different times. Keep a record of common nameservers, mail providers, registration patterns and authentication settings. Repeated infrastructure across several domains can reveal a coordinated campaign.
Use verification controls before acting
A suspicious result should trigger a controlled verification process, especially for requests to change bank details, release customer data or reset access. Confirm the request through a previously trusted channel and involve finance or the security team before payment. Australian businesses often face fast-moving invoice fraud, so a short delay is safer than accepting an apparently urgent instruction.
If your organisation owns the domain or needs to correct its profile, review the requirements for becoming a domain admin. Record the domain, message headers, score, DNS findings and verification outcome in the incident file. This creates an audit trail and helps distinguish a genuinely reused domain from an ordinary mail configuration change.
Turn the check into a repeatable workflow
For occasional checks, analysts can run the domain manually and attach the findings to the email security ticket. Larger teams can use bulk checks or developer integrations to screen supplier domains, monitor changes and route higher-risk results for review. Set sensible thresholds rather than blocking every domain with an imperfect score.
Recheck domains after ownership changes, long periods of inactivity or unexpected authentication updates. A sender’s domain can remain technically valid while its business identity changes, making continuity checks essential. Used alongside independent contact verification and payment controls, Trusted Sender Score gives Australian organisations a practical way to spot the risks associated with expired and reused domains.