Five sources per IP in the pool, no averages that hide the bad ones.

"Why pay for an audit when MXToolbox is free?"

MXToolbox and similar checkers run one of the five sources (DNSBL sweep) and produce a list of present and absent listings; the value is real but the scope is partial. The audit engagement covers four additional sources MXToolbox does not see (Validity, Postmaster, SNDS, FBL) and produces per-IP scoring that aggregates the five into a unified picture with explicit keep, recover, or replace decisions. The analytical work is comparing pool members against pool-level signal to surface hidden variance, identifying which pool member is dragging the average, calculating volume-weighted contribution per IP, and writing the prioritized action list. MXToolbox returns the DNSBL data; the audit interprets the data alongside four other dimensions in the context of the customer's specific pool architecture and traffic patterns. The customer can run MXToolbox internally; the analytical interpretation requires expertise the audit packages as a standalone deliverable.

"What if we already know which IP is the problem?"

If the customer team has already identified the problematic IP and only needs remediation, the audit is unnecessary; the Sender Score Recovery or Reputation Recovery engagement is the right answer. The audit value applies when the pool contains hidden variance that the customer team has not yet identified; if the team has done the per-IP analysis and confirmed which IPs are healthy versus problematic, EMP skips the audit and runs the recovery engagement directly. The diagnosis call separates these cases: customers with documented per-IP analysis go to recovery; customers without it go to audit first. Approximately 30 percent of inbound audit inquiries are actually recovery cases that the customer team confused with audit; the diagnosis call surfaces the misalignment and recommends the correct engagement.

"How does EMP access Microsoft SNDS and Gmail Postmaster?"

Both require customer-side authorization because the data is private to the IP owner. Gmail Postmaster Tools requires the customer to add EMP's audit Google account as a delegate, which the customer can do in 5 minutes through the Postmaster Tools interface; alternative is the customer team pulls the data and shares the export. Microsoft SNDS requires the customer to add EMP's audit Microsoft account to their SNDS authorized users; same 5-minute setup. Validity Sender Score does not require special access because senderscore.org permits anonymous IP queries (free tier with rate limits) and the EMP audit account has the Validity API access for higher-volume querying. DNSBL sweeps do not require customer-side access because the lists are public DNS queries. The access provisioning happens during Phase 01 of the engagement and is the only customer-side dependency before EMP starts the source queries.

"Does the audit work for ESPs auditing their customer pools?"

Yes, ESP-of-record use case is one of the audit's primary customer segments. ESPs onboarding new customers run the audit to verify the pool reputation state at the moment of onboarding rather than discovering issues 30-90 days later when the reputation has already infected the ESP's shared infrastructure. The audit also runs as the diagnostic when an existing ESP customer's deliverability degrades and the ESP needs to determine whether the issue is the customer's pool, the ESP's infrastructure, or external factors. For ESP use cases the Enterprise Pool tier typically applies because the audited pool spans multiple tenants the ESP serves; the per-tenant segmentation analysis included at that tier surfaces which tenant is producing the issue rather than treating the pool as monolithic.

"What if we lack access to Postmaster and SNDS because the previous team set them up?"

The access recovery is part of Phase 01 of the audit. Postmaster Tools access recovery requires DNS verification of the sending domain; the customer adds a TXT record EMP provides, the verification completes within hours, and EMP either takes the account ownership or adds the customer team as new administrators. SNDS access recovery requires Microsoft verification through their account recovery process; the timeline is variable (1-7 days depending on Microsoft response) but the process is straightforward when the customer can demonstrate IP ownership through ARIN records or hosting provider documentation. If access recovery cannot complete within Phase 01, the audit proceeds with the sources that are accessible and notes the missing dimensions in the document; the customer can engage EMP for a supplementary audit after access recovery completes for the difference in scope.

"What is the cost difference if we follow up with recovery work?"

EMP credits the audit fee toward subsequent Sender Score Recovery or Reputation Recovery engagements run within 90 days of the audit delivery. The Standard Pool Audit at 2,900 USD credits in full toward Sender Score Severe Recovery at 5,800 USD, making the combined cost 5,800 USD rather than 8,700 USD if booked separately; the same credit structure applies to other tier combinations. The credit is one-time per customer and limited to 90 days from audit delivery to prevent indefinite price gaming. Customers who execute remediation internally and do not engage EMP for recovery pay only the audit fee; the credit structure exists to align EMP incentives with customer outcomes rather than to penalize the internal-execution path.