DMARC p=reject and low trust need reconciliation
A domain with a DMARC p=reject policy and a low trust score can look inconsistent, yet the mismatch is worth fixing. DMARC p=reject asks receiving mail servers to reject messages that fail SPF or DKIM alignment with the visible From domain. A low trust score points to a separate concern: the sending domain or its infrastructure may still look risky to recipients.
The two controls measure different things. DMARC is an authentication and enforcement policy, while a sender-trust score can reflect reputation, domain history, infrastructure quality and observed risk signals. A strict policy can therefore coexist with a weak score when legitimate traffic has not established a clean record, or when important messages are rejected before recipients see them.
For Australian organisations, this matters across a busy, cloud-heavy market. A Sydney consultant, a Melbourne retailer and a Brisbane wholesaler may rely on a web store, CRM, booking system and payment reminders during the same working day. With many employees checking email on phones between meetings, a broken authentication path can quickly affect invoices, password resets and customer service.
The apparent contradiction explained
DMARC p=reject is a strong instruction, but it applies only when a message fails the required authentication checks. A message can pass DMARC because its SPF or DKIM domain aligns with the From address, yet still trigger risk warnings based on the sending server’s reputation, unusual traffic patterns or the sending domain’s history.
The trust score supplies broader context. A low result does not prove that the domain is compromised or that every message is malicious. It may instead identify a new domain, a shared sending IP with poor history, inconsistent sending volumes or infrastructure that recipients have not encountered before. These are risks worth investigating rather than labels to attach to the domain permanently.
The contradiction becomes operationally important when an organisation believes its authentication is sound while recipients and security tools continue to distrust the sending environment. The remedy is to restore consistency across identity, infrastructure and reputation—not by weakening DMARC enforcement.
Read the DMARC evidence
DMARC aggregate reports show how receiving organisations processed recent messages. Their source and disposition figures can reveal whether SPF, DKIM or alignment is failing, which sending services generate most traffic, and whether unknown sources are attempting to use the domain. Reports from the Australian Government, major mailbox providers and overseas recipients can all contribute useful evidence.
A large percentage of rejected recipients needs context. The platform’s guide to high rejection reports explains how to distinguish deliberate filtering from legitimate business mail that fails authentication. High rejection volume can reflect active spoofing, but it can also expose a misconfigured CRM, payment platform or email campaign service.
Reports only cover messages that reached participating receivers. Messages stopped earlier by a gateway may never appear, so the visible report can understate the operational impact. Authentication logs, bounce records and support complaints should be examined alongside DMARC data, particularly when customers in Sydney or Melbourne report missing receipts or delayed quotes.
Map every legitimate sender
Many Australian small and medium-sized businesses use Microsoft 365 or Google Workspace for staff email while relying on separate services for ecommerce, invoices, appointment reminders and transactional notifications. Each service may send through its own infrastructure. A policy that works for one channel may fail for another if SPF includes, DKIM records or domain alignment were never configured.
A useful first step is to create an inventory of every domain used for sending, including inactive subdomains and regional campaign streams. Trusted Sender Score’s bulk domain checks allow teams to compare a large provider portfolio and identify domains that need closer inspection. This is particularly valuable for fragmented organisations that no longer remember every service holding access to their sending identity.
For each provider, confirm that the visible From domain is authorised, DKIM is active and the selectors resolve correctly. Pay particular attention to delegated sending through marketing platforms and payment providers. Removing obsolete records and unauthorised senders prevents attackers from exploiting SPF or DKIM permissions that remain after a platform has been retired.
Repair authentication and reputation
Start with a correct SPF and DKIM setup for the actual sending infrastructure. SPF should include only legitimate sources and remain within the DNS lookup limit, while DKIM should use strong keys, planned rotation and selectors that receiving systems can verify. Alignment matters as much as successful encryption or signature validation: an otherwise valid signature can still fail DMARC if its domain does not match the From domain.
A low score may also require changes to sending behaviour. Dedicated infrastructure, consistent volumes, valid reverse DNS, working TLS and steady growth in legitimate engagement can improve how recipients perceive a sending source. Abrupt spikes, purchased lists and repeated low-quality messages have the opposite effect. Reputation recovery normally takes time and cannot be guaranteed by editing DNS records alone.
Australia’s Spam Act 2003, reinforced by the Spam Prevention Act 2021, generally requires commercial electronic messages to have consent, clear sender identification and a functioning unsubscribe mechanism. These obligations support better complaint and engagement rates, which align with the reputation improvements sought through technical remediation. Australian Security and Data Centre experts at the Australian Signals Directorate also advise organisations to monitor authentication results and act on suspicious activity.
Verify recovery and prevent drift
Record the current score, DMARC disposition, alignment results and legitimate sender list before making changes. Review them again after the next major campaign or provider integration. This creates evidence of improvement and makes it easier to distinguish a transient score change from a persistent infrastructure problem.
Authentication should be treated as an ongoing control rather than a one-off configuration. A new CRM, online booking service or customer mailing platform can introduce another sending path without changing the organisation’s core DNS records. Assigning ownership for domain changes and reviewing external sending services prevents silent drift.
A phone-first workforce will experience authentication failures as missing notifications, inaccessible reset links and customers waiting for payment or delivery updates. Regular checks across mobile applications, webmail, gateways and transaction systems give Australian teams a complete view. A domain that maintains strict DMARC enforcement, clean alignment and a steadily improving trust record gives recipients fewer reasons to hesitate.