DNS health check
Run the basic DNS checks on a domain and see each one as passed, missing, misconfigured or not tested.
- Name servers, SOA, web and mail records
- Each finding explained
- Unknown states kept, never guessed
Give it something to look up — Glee will do the digging.
How the dns health check works
Most website and email outages that are not the server's fault are DNS: a lapsed name server, a missing record after a migration, mail records pointing at a host that no longer exists. A DNS health check runs the basic questions in one pass so the broken one stands out.
This check queries the domain's name servers and core records — SOA, A, AAAA, MX and TXT — and reports a finding for each: present and consistent, missing, misconfigured, or not tested because a step before it failed. Every finding carries the record it is based on, so a result can be verified with any DNS tool.
What each field means
- Findings
- One line per check, with the record it is based on.
Where this check stops
- Missing, misconfigured, not tested and request-failed are different states and are kept apart; there is no single overall score.
The same check, through the API
Same calculation, same answer, with a key. 3 credits per check ($0.30 per 1,000). A free account includes 1,000 credits a month.
GET /v1/dns/acme.com Host: gleanzy.com Authorization: Bearer $GLEANZY_KEY
Frequently asked
How often should I check?
After any DNS change or provider move, and before relying on a new domain.