Why a Recently Changed DNS TXT Record Needs Immediate Review
A domain can have a valid DKIM signature and still present a serious security concern when its DNS TXT records have changed recently. DKIM confirms that an authorised key signed a message, but it does not prove that the key, the domain account, or the mail system remains under legitimate control.
A sudden TXT update may reflect routine key rotation, a new email provider, or a marketing platform migration. It can also indicate compromised registrar credentials, unauthorised DNS access, a malicious DKIM selector, or changes designed to support phishing campaigns. Timing, ownership and configuration history matter as much as the cryptographic result.
This issue is especially relevant to Australian organisations managing customer data, invoices and supplier communications across Sydney, Melbourne, Brisbane and Perth. A suspicious DNS change during end-of-financial-year activity, a property settlement or a major retail promotion can create an attractive opening for business email compromise.
What A Valid DKIM Result Actually Proves
DKIM verifies that a message carries a valid digital signature associated with a public key published in DNS. If the selector and public key match, the receiving server can confirm that the message was signed by a system with access to the corresponding private key.
That result has limits. It does not establish that the sending company requested the change, that the domain registrar account is secure, or that the content is safe. A criminal who gains control of a mail platform or DNS account may be able to produce technically valid messages.
Why A Recent TXT Change Raises Risk
DNS TXT records can contain DKIM public keys, SPF policies, DMARC instructions and verification tokens for third-party services. A change made shortly before suspicious emails appear should be treated as a significant event, particularly when the new value uses an unfamiliar selector, provider or hosting network.
Review the exact before-and-after values, record TTL, change timestamp and registrar audit trail. Check whether the organisation recently moved from an Australian provider to an overseas SaaS platform, launched a new .au domain, or changed its transactional email service. A legitimate explanation should be documented and independently verified.
| Signal | Likely Explanation | Immediate Review |
|---|---|---|
| New DKIM selector from a known provider | Planned key rotation or platform migration | Confirm the change with the provider and domain owner |
| Multiple selectors added suddenly | Several services enabled, or unauthorised access | Identify every selector and remove unused entries |
| TXT value changed during a phishing incident | Possible DNS or registrar compromise | Preserve logs and investigate access immediately |
| DKIM passes but DMARC alignment fails | Unapproved or misconfigured sender | Check the visible From domain and organisational alignment |
| SPF, DKIM and DMARC changed together | Mail infrastructure redesign or account takeover | Validate each policy against approved sending services |
Check The Selector And Sending Infrastructure
The selector in a DKIM header identifies the public key used for verification. Review it against known services such as Microsoft 365, Google Workspace, Mailchimp or an approved Australian email provider. An unexpected selector deserves scrutiny even when the signature passes.
Inspect the sending IP, reverse DNS, envelope-from domain and message headers. A valid DKIM result paired with a newly registered infrastructure host, unusual geography or a shared service with poor reputation may indicate abuse. Organisations can also check shared IP reputation when a legitimate provider appears alongside suspicious delivery patterns.
Validate DMARC Alignment And Message Intent
DMARC evaluates whether the authenticated DKIM or SPF domain aligns with the visible From domain. A message may pass DKIM while failing alignment if a third-party sender signs with a different domain. This weakens protection against impersonation and can create confusing policy results.
Content still requires human and technical review. A signed email asking a Brisbane accounts team to change bank details, or requesting a Sydney customer to open an unexpected attachment, may be malicious. Review DMARC spoofing guidance before treating authentication as proof of safety.
Distinguish Routine Rotation From Account Takeover
Planned DKIM rotation usually has a change ticket, an owner, a defined rollout window and a retiring selector. Many providers publish both old and new keys temporarily so messages can continue verifying during DNS propagation. The domain team should know why the change occurred and which service requested it.
An unexplained update, especially outside business hours or near an Australian public holiday, requires a higher level of suspicion. Compare registrar login records, multi-factor authentication events, DNS management users and provider API activity. Rotate credentials and revoke unknown sessions if the evidence points to compromise.
Protect DNS And Mail Administration
Restrict DNS changes to named administrators and enforce phishing-resistant multi-factor authentication where available. Use registrar lock features, least-privilege access and alerts for modifications to TXT, MX, CNAME and NS records. DNSSEC can add integrity protection, although it does not prevent an authorised attacker from making a valid change.
Maintain an inventory of approved senders and selectors for every business unit, including agencies used for Australian campaigns, receipts and customer notifications. A central record makes it easier to recognise an unexpected service before it sends at scale.
Use Independent Reputation Checks
A domain trust review should combine DNS history, authentication status, sending behaviour and message context. Automated checks can identify missing records, weak DMARC policies, suspicious changes and inconsistent provider relationships, while security staff investigate the business reason behind each result.
For supplier onboarding or an unexpected cold email, use cold sender checks alongside header analysis and out-of-band verification. Australian businesses should confirm payment instructions through a known phone number or established contact, rather than replying to the message or relying on a familiar logo.
A valid DKIM signature is valuable evidence, but a recently changed TXT record changes the risk assessment. Until the modification is explained, the selector is verified and the sending environment is trusted, the domain should receive immediate security review.