# Check Deliverability Posture Across an Account List

**Use case:** 

Runs the deliverability check over a whole list, so SPF, DKIM and DMARC posture is compared side by side rather than one company at a time.

## Input

```json
{
  "domain": "smartlead.ai",
  "domains": [
    "outreach.io",
    "salesloft.com",
    "apollo.io"
  ],
  "scan_sending_domains": true,
  "sending_domain_depth": "deep",
  "check_deliverability": true,
  "batchSize": 3,
  "max_sending_domain_probes": 80,
  "request_timeout_ms": 9000,
  "dns_timeout_ms": 4000,
  "skipCache": false,
  "qa_test_mode": false,
  "source_tag": "outbound-infrastructure-fingerprint:check-deliverability-across-an-account-list"
}
```

## Output

```json
{
  "domain": {
    "label": "Domain",
    "format": "string"
  },
  "runs_outbound": {
    "label": "Runs Outbound",
    "format": "string"
  },
  "confidence": {
    "label": "Confidence",
    "format": "number"
  },
  "sending_domain_count": {
    "label": "Sending Domain Count",
    "format": "integer"
  },
  "sending_domain_names": {
    "label": "Sending Domain Names",
    "format": "string"
  },
  "sending_platform_names": {
    "label": "Sending Platform Names",
    "format": "string"
  },
  "inbox_provider_label": {
    "label": "Inbox Provider Label",
    "format": "string"
  },
  "dmarc_policy": {
    "label": "DMARC Policy",
    "format": "string"
  },
  "deliverability_score": {
    "label": "Deliverability Score",
    "format": "integer"
  }
}
```

## About this Actor

This example demonstrates how to use [Outbound Stack Detector Cold Email Sending Domains Clay](https://apify.com/mambalabs/outbound-infrastructure-fingerprint.md) with a specific input configuration. Visit the [Actor detail page](https://apify.com/mambalabs/outbound-infrastructure-fingerprint.md) to learn more, explore other use cases, and run it yourself.


## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
This Task's input is already configured above — use it as-is rather than inventing a new one.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For full API examples (JavaScript, Python, CLI, MCP, OpenAPI), see this Task's Actor page: https://apify.com/mambalabs/outbound-infrastructure-fingerprint.md

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).