DNS doctor per domain
The DNS doctor checks a domain live in the DNS, not against the data stored at regfish. It therefore sees what any outside resolver sees, including faults caused by delegations, foreign nameservers or half finished migrations.
Where to find it
Section titled “Where to find it”Domains → your domain → Monitoring & protection → DNS doctor, direct address:
dash.regfish.com/my/domains/<tld>/<sld>/health
The four finding classes
Section titled “The four finding classes”At the top sits the summary across all checks, below it the findings by severity:
| Class | Meaning |
|---|---|
| Problems | Something is broken or invalid. Look here first. |
| Warnings | Works, but risky or outdated. |
| Notes | Optional improvement, often hardening. |
| Fine | Checked and unremarkable. |
A typical problem is more than one SPF record: the standard allows exactly one, with two SPF becomes invalid and the recipient sees a PermError. The finding says so and links straight to the fix.
Every finding carries a fix link that leads to the right place, usually into the DNS records with the record prepared.
What the DNS doctor cannot see
Section titled “What the DNS doctor cannot see”One important special case shows up at DKIM: DKIM cannot be enumerated over DNS. The check tries the common selectors. Finding nothing does not prove that no DKIM exists; your mail provider may simply use its own selector. The finding says as much, and it should not be treated blindly as an error.
Relation to the standalone DNS Doctor
Section titled “Relation to the standalone DNS Doctor”The same checking logic exists as its own product with its own API under DNS Doctor. The page here is the view cut down to one domain inside the dash; if you want to check many domains automatically, use the API.