Halowerk Domain Intel — MX/TransIP Article Endpoint

Choose this endpoint when you need MX record and mail policy data for a domain without any signup or API key, and especially when you want to compare current MX records against a known historical baseline to detect changes. It is well-suited for automated security monitoring, domain auditing pipelines, and one-off investigations where pay-per-call via x402 USDC micropayments is preferred over subscription APIs. Prefer alternatives if you need bulk batch lookups at lower per-query cost, or if you need real-time streaming DNS monitoring rather than point-in-time lookups.

• Invalid or malformed domain name returns a validation error
• Domain does not exist in DNS — returns empty or NXDOMAIN result
• Baseline schema mismatch (missing required fields like observed_at or records) causes a 422 or schema validation error
• Payment not settled via x402 protocol returns a 402 Payment Required response
• Rate limiting or upstream DNS resolution failure may return a 503 or timeout
• Overly long domain name (>253 characters) rejected by input validation