# HALOWERK postweg – MX Count Check for DKIM Selector

> HALOWERK postweg – MX Count Check for DKIM Selector is a paid API for AI agents from postweg.halowerk.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-11-16).

Checks the number of MX records associated with a given DKIM selector on a domain.

## Facts

- Endpoint: POST https://postweg.halowerk.com/v1/pruef/postweg/mx/dkim-selektor?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/halowerk-postweg-mx-count-check-for-dkim-selector-9cfe46f9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_c5bMOww7q0mF-l91rPP01

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability halowerk-postweg-mx-count-check-for-dkim-selector-9cfe46f9 -d '<json body>'
```

Example prompt: Can you check how many MX records are associated with the DKIM selector 'google' for the domain example.com?

## When to prefer this

Use this endpoint when you need to audit or verify the number of MX records associated with a specific DKIM selector on a domain, particularly during email infrastructure setup, security audits, or deliverability troubleshooting. It is specifically designed for DKIM-selector-scoped MX record counts, distinguishing it from generic MX lookup tools.

## Known failure modes

- Domain not found or does not exist — DNS resolution fails
- DKIM selector not provided or invalid format — validation error
- No MX records found — returns zero count
- Domain has no public DNS records — lookup returns empty
- Network timeout during DNS query
- Invalid target address format — schema validation error

## How this service works

Prüft am Objekt dkim-selektor den Befund Zahl der MX-Einträge.

## Output

Returns the count of MX records found in DNS for the specified DKIM selector and target domain, along with associated diagnostic findings about the mail exchange configuration.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "ziel": {
   "oneOf": [
    {
     "type": "string",
     "maxLength": 2048,
     "minLength": 1,
     "description": "Öffentliche HTTP(S)-Adresse; bei DNS-Befunden Domain oder öffentliche IP."
    },
    {
     "type": "object",
     "required": [
      "adresse"
     ],
     "properties": {
      "adresse": {
       "type": "string",
       "maxLength": 2048,
       "minLength": 1
      },
      "selektor": {
       "type": "string",
       "maxLength": 240,
       "minLength": 1,
       "description": "CSS-Selektor: genau ein Objekt, sonst erster Treffer des Objektfilters."
      },
      "vergleich": {
       "type": "string",
       "maxLength": 2048,
       "description": "Öffentliche Vergleichsadresse für Link-, Sitemap- oder Sprachbefunde."
      },
      "user_agent": {
       "type": "string",
       "pattern": "^[A-Za-z0-9_-]{1,80}$"
      },
      "dkim_selektor": {
       "type": "string",
       "pattern": "^[A-Za-z0-9_-]{1,63}$"
      }
     },
     "additionalProperties": false
    }
   ]
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/halowerk-postweg-mx-count-check-for-dkim-selector-9cfe46f9/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from postweg.halowerk.com](https://www.zero.xyz/host/postweg.halowerk.com/llms.txt)
