# check_dns_health

> Diagnose a domain's DNS and return a verdict, not a raw dump: does the root A record point at this hosting node, is mail configured (MX present, SPF, DKIM, DMARC),…

- Tier: R
- Required scope: read:dns
- Annotations: readOnlyHint, idempotentHint
- Docs: https://api.inleed.com/tools/check-dns-health

## Description

Diagnose a domain's DNS and return a verdict, not a raw dump: does the root A record point at this hosting node, is mail configured (MX present, SPF, DKIM, DMARC), and is the zone delegated — with a plain-language `alerts[]` of what is wrong. This reads the zone from DirectAdmin; it does not query the public internet, so it says what the zone *should* serve. For the raw records use `list_dns_records`; to fix a problem use `create_dns_record` / `update_dns_record`. `isHealthy: true` with an empty `alerts[]` means no problems were found.

## Input schema

- `input` — string (required). A domain, email address, website URL, numeric service id, or hosting-account username the customer actually owns. Resolved to the owning account automatically; the resolved target is echoed back in the response.

## Example call

```json
{
  "name": "check_dns_health",
  "arguments": {
    "input": "example.se"
  }
}
```

## Example conversation

**User:** Is email set up correctly for example.se?

**Assistant:** The A record resolves and MX is present, but SPF is missing. Want me to add it?