Audit advanced Works with: Any AI

Email Authentication Setup Audit

Table output Has example

Audit email authentication setup covering SPF, DKIM, DMARC and alignment, explained in plain language with fixes.

The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.

[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.

Review the email authentication for my sending domain. Records I can see for sender policy, signing and domain-based message policy: [DNS_RECORDS]. Services that send on behalf of the domain: [SENDING_SERVICES]. Reports received, if any: [REPORT_SUMMARY].

Explain what each record does, check whether every legitimate sender is covered, whether alignment is likely to pass, whether the policy is too loose or too strict, and what could break if tightened. Do not tell me to publish changes without testing.

Return a table with Record, Finding, Risk (red, amber, green) and Next step, a score from 1 to 10 for coverage, alignment and monitoring, and a staged plan with a rollback note. Provider behaviour is [VERIFY] with current documentation.

Also add a table of questions to ask each sending service, such as whether it signs mail with my domain and what it publishes, and mark answers that depend on the provider's documentation [VERIFY].

Then prepare a rollout plan with minimal risk. List every system that sends mail for the domain, who owns it and what it needs to pass authentication, and mark those that are unknown. Propose a staged approach: publish monitoring-only policy, collect reports for a set period, fix legitimate senders, then tighten gradually, with a rollback step at each stage. Provide a checklist for the person making DNS changes, including backing up existing records, checking syntax, allowing for propagation time and testing with several mailbox providers. Explain how to read aggregate reports in plain language and what a normal pattern looks like. Add a communication note for colleagues explaining what might change and whom to contact if mail is rejected. Provider and standards behaviour is [VERIFY] with current documentation, and a qualified administrator should make the changes.

Redact personal data and secrets before pasting anything. If the material includes them, stop, tell me what to remove, and continue only with the redacted version.

Fill in before use

Optional: type your details and the prompt above updates. Nothing is saved or sent.

Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.

Review (invented domain example.test)
Sender policy record: includes the main mail provider but not the invoicing tool, which sends from the domain. Risk amber.
Signing: enabled for the provider; the newsletter tool signs with its own domain, so alignment may fail. Risk amber.
Policy: set to monitor only, no reporting address monitored. Risk amber.
Plan: list senders; add the invoicing tool; set up signing for the newsletter; read reports for four weeks; move to quarantine gradually; rollback step at each stage.
Scores: coverage 5, alignment 4, monitoring 3. Provider behaviour: [VERIFY].

• audit