# HALOWERK postweg – MX Record Count Check on Nameserver

> HALOWERK postweg – MX Record Count Check on Nameserver 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 found on a given nameserver (or domain/IP) and returns the finding.

## Facts

- Endpoint: POST https://postweg.halowerk.com/v1/pruef/postweg/mx/nameserver?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-record-count-check-on-nameserver-b3dc799b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_aKtThI3R3UP2w2gFDcp7T

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-record-count-check-on-nameserver-b3dc799b -d '<json body>'
```

Example prompt: Can you check how many MX records are configured on the nameserver for example.com and tell me if the count looks correct for email delivery?

## When to prefer this

Use this endpoint when you need to programmatically verify the MX record count on a nameserver for a specific domain or IP, especially as part of an email infrastructure audit, pre-launch DNS check, or automated monitoring pipeline. It is preferable to general DNS lookup tools when you want a structured, validated finding rather than raw DNS output, and when checking specifically the nameserver-level MX record count rather than SPF, DMARC, or DKIM records (which are handled by sibling endpoints).

## Known failure modes

- Invalid or unreachable domain/IP returns an error or zero count
- Domain with no MX records returns a count of zero
- Malformed input (e.g. URL exceeding 2048 chars) triggers a validation error
- Private or non-public IP/domain may be rejected
- Rate limiting or payment failure ($0.001 USDC per call) may block the request

## How this service works

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

## Output

Returns a structured finding indicating the number of MX records found on the specified nameserver for the given domain or IP target, allowing the caller to assess whether email routing DNS is correctly configured.

## 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-record-count-check-on-nameserver-b3dc799b/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)
