Needs work tells you there is a requirement to investigate. The next step is to identify which system owns that requirement and inspect fresh messages from it.

A DNS change, an unsubscribe service and a campaign audience can all affect compliance, but they need different owners and different evidence.

Read the requirement before changing anything

Google shows Compliant, Needs work or No data found. Open the detail beside the affected requirement and record it with the date.

Authentication and alignment belong with the sending platform and DNS owner. Reverse DNS and encrypted transport usually need the infrastructure provider. Unsubscribe handling needs whoever owns the endpoint and audience suppression. Spam complaints need an investigation into recipients and the messages they receive.

Apply the right sender requirements

Gmail requires all senders to authenticate with SPF or DKIM, use appropriate DNS and encrypted transport, follow message-format rules and keep spam rates low. Bulk senders have additional requirements, including both SPF and DKIM, DMARC and the relevant one-click unsubscribe controls.

Bulk status counts traffic from the same primary domain, including its subdomains. Once assigned, Google says it does not expire. A quieter sending day does not remove the classification.

Check every relevant stream

The compliance assessment applies to the primary domain and includes subdomain traffic. If the newsletter looks correct, check other senders before concluding the status is wrong.

A forgotten automation may use different authentication. An old subscription template may lack the expected headers. An unsubscribe request may reach one platform while another continues selecting the person for the same list.

Confirm the fix with fresh evidence

After a change, inspect newly sent messages or endpoint logs. Keep the time of the fix in your investigation notes.

The compliance assessment uses a rolling view across multiple days. Google advises checking again after seven days for updated status. The dashboard also reflects the configuration observed when qualifying messages arrived, so today's DNS result may differ from the historical assessment.

If the warning persists, compare its exact scope with the stream you fixed. Escalate with specific examples once you have checked the other senders that contribute to the domain's traffic.

Sources