Why a hostname is not working

Runs the checks we can run from the authoritative side and returns a verdict for each, with the next action on anything that failed.

Read-only. Nothing here writes a record, re-signs a zone or orders a certificate, so it is safe to call on a schedule and safe to retry.

Always 200 when the hostname exists, including when every check fails - that is the case this endpoint is for, so the verdict is in the body rather than the status code. Each check carries verdict: pass, fail, warn, unknown (we could not find out, which is never the same as fine) or skipped (an earlier answer made it meaningless). summary names the first failure, because it is usually the cause of the ones after it.

get/v1/hostnames/{id}/diagnose

Request

  • Base URL: https://dnsmint.com/api
  • URL: https://dnsmint.com/api/v1/hostnames/{id}/diagnose
  • Auth: HTTP bearer

Path parameters

idstring required

Response

The diagnosis

hostnamestring
summarystring

The first failure, or a statement that the hostname is working.

checked_atstring date-time
checkedAtstring date-time

Deprecated spelling, still accepted. Use checked_at.

Changes

No recorded changes to this operation across all 1 revision of this API.