This is a scope concept for discussion, not a service offer or booking. A potential engagement could cover one authorized domain, up to three customer-identified sending services, and one controlled test message from one selected service. Availability, report format, fee, schedule, evidence handling and any customer-specific method must be confirmed in a written quote accepted by both parties before evidence collection.
If included in an accepted quote, the review could record up to three customer-identified services and distinguish a selected, tested service from inventory-only senders. That list would not claim to find every sender on the domain.
A separately agreed scope could cover public MX, SPF and DMARC observations, plus a DKIM selector only when the service or message identifies one. If a test message is included and delivered, receiver-reported SPF, DKIM and DMARC results could be compared with those observations.
A report format would be confirmed in the accepted quote. A draft template demonstrates how it could separate observations, sender coverage, limitations, priorities and verification steps. Any DNS or Microsoft 365 change needs separate scope and explicit approval.
It is not mailbox-wide access, an M365 tenant audit, a full sender-discovery exercise, a test of every recipient or sender, a DKIM cryptographic validation, a malware review, monitoring, a deliverability guarantee, or a DNS/configuration change. Additional tests and remediation are separately scoped. Never email credentials, raw message headers or full DNS exports; agree on a secure evidence channel before work begins.
If the service owner confirms availability, the quote will state the fee, report format and delivery date for the proposed scope. Evidence collection can begin only after both sides accept the same written scope, fee and handling terms.
No. It gives one receiving-system observation for one selected message path. Other senders, recipients, forwarding behavior and future DNS changes may produce different results.
If a future accepted scope includes a test and it is not received, the agreed process would record that no message evidence was available and would not infer a cause from headers that were never obtained. Reviewing a non-delivery report or Microsoft 365 message trace would need its own agreed scope.
No mailbox credentials or mailbox-wide access are needed for this manual review. You select and open the test message, then provide only agreed, redacted header evidence through the agreed channel.
The report can describe a proposed next step, but this engagement makes no changes. Implementation, a named change owner, rollback plan and repeat verification require separate written approval.
Use the free guide for public DNS and message-header helpers, then decide whether a bounded professional review fits your needs.
