Updated November 2026

Oh Dear vs DNS Spy vs DomainCareHQ for small web agencies

Three tools that get compared constantly and are not really in the same category. One watches uptime, one watches DNS, one produces a client deliverable. Knowing which job you are buying for makes the price comparison obvious.

The comparison usually starts with price: €149 a month versus $39 a month. That is the wrong first question, because the two products are answering different questions. Oh Dear answers "is the site working". DNS Spy answers "did the zone change". DomainCareHQ answers "what does the client receive".

What each tool actually does

ToolList priceCore jobBest fit
Oh Dear€149/mo for 50 sites, €249/mo for 100Uptime, WordPress depth, broken links, DNS snapshotAgency with a WordPress-heavy book that wants one dashboard
DNS Spy$49/mo for 100 domainsDNS change monitoring and historyAgency that only cares about zone drift
URIports$30 to $120/moDMARC aggregate reporting and email authenticationAgency that needs per-message DMARC visibility
DomainCareHQ$39/mo for 50 domains, $69/mo for 150DNS diff, SPF lookups, DMARC policy, TLS, RDAP, monthly client reportAgency that sells care plans and needs an artifact

Oh Dear: the strongest product, if your book is WordPress

Oh Dear has been around long enough to be trusted, and it does real work: uptime, broken links, mixed content, scheduled task monitoring, and a WordPress view deep enough to see core and plugin versions. If 80% of your clients are WordPress and the care plan includes updates, it is a reasonable central dashboard.

The gap is the output. It tells you a site is up. It does not produce a client-facing document that says the certificate has 41 days left, the SPF record is one lookup from breaking, and the domain registration renews in 212 days. G2 reviewers also keep landing on the same complaint: the price rises fast as site counts rise.

DNS Spy: honest scope, narrow job

DNS Spy watches zones and history. If the failure you are worried about is a developer changing an MX record during a migration, it does that job well and cheaply for the domain count. It will not tell you the SPF record has eleven lookups, and it will not tell your client anything at all.

URIports: DMARC, at message level

URIports does the thing we deliberately do not: it ingests DMARC aggregate reports and shows per-sender traffic. If your clients need to see who is spoofing them, that is a different product and worth the money. It is not a maintenance artifact for a $150 care plan.

DomainCareHQ: the retention layer

The bet behind DomainCareHQ is that the report is the product. Checks run every six hours against the seven DNS record types, count SPF lookups recursively, read the DMARC policy, connect to port 443 for certificate expiry and chain validity, and query RDAP for registration expiry. On the 1st, each client gets one email with your logo on it.

The cost of that bet is scope. No uptime pings, no plugin updates, no DMARC aggregate ingestion, no CMS integrations. If those are what keeps your care plan alive, keep your current tool and add this underneath it.

Where the price difference goes

At €149 a month you are paying for a broad monitoring product with a large feature surface. At $39 a month you are paying for a narrow engine plus the document. Neither is overpriced. They are simply not the same purchase, and the annual option makes the second one $390 a year.

The tie-breaker question

Ask what you send a client on a $150 care plan each month to prove value. If the answer is "nothing, we just fix things", the retention problem is the report, not the monitoring. If the answer is a 12-page dashboard export nobody opens, the problem is the format. If the client already receives a document you are proud of, buy the cheapest tool that produces the numbers in it.

The full feature matrix has the line-by-line comparison, including where Oh Dear wins.