What does Lemwatch monitor?

Lemwatch runs 20+ automated checks per site: uptime, response time, SSL/TLS expiry, domain expiry, DNS changes, sitemap health, broken links, content changes, SEO audits, mobile usability, security headers, and more.

Yes. The free tier monitors up to 5 sites. Pro is $19/month for 50 sites and Agency is $59/month for 100 sites, both with full feature access.

How is Lemwatch different from UptimeRobot or Pingdom?

Lemwatch bundles uptime, change detection, SEO audits, security scans, and a public API in one platform — features competitors charge separately for. It also includes team workspaces, white-labelled status pages, and a webhook system out of the box.

Does Lemwatch send alerts?

Yes. Lemwatch supports email, browser push, webhooks, and per-site notification routing so the right person hears about the right incident.

Is there a public API?

Yes. Pro and Agency plans get a public REST API with webhooks for sites, checks, incidents, and reports.

DNS_PROBE_FINISHED_NXDOMAIN on Mac

macOS caches DNS in mDNSResponder, and a VPN or split-DNS profile can keep resolving the name against an internal server that has no such record.

Why it happens on Mac

macOS caches DNS in mDNSResponder, and a VPN or split-DNS profile can keep resolving the name against an internal server that has no such record.

The fix on Mac

Run `sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder`, disconnect any VPN, then retry.

If that didn't fix it

Mac has its own failure mode, but DNS_PROBE_FINISHED_NXDOMAIN has a wider set of causes. The most common one overall is: The A or CNAME record for the hostname does not exist.

Add the missing record at the DNS provider. Remember that the apex and www are separate records.

Check your own domain

The DNS lookup queries public resolvers directly and shows the A, AAAA, CNAME and NS records that actually exist — which instantly separates 'record missing' from 'my resolver is stale'.

Frequently asked questions

Why does DNS_PROBE_FINISHED_NXDOMAIN happen on Mac?

macOS caches DNS in mDNSResponder, and a VPN or split-DNS profile can keep resolving the name against an internal server that has no such record.

How do I fix DNS_PROBE_FINISHED_NXDOMAIN on Mac?

Run `sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder`, disconnect any VPN, then retry.

What does DNS_PROBE_FINISHED_NXDOMAIN mean?

The DNS lookup completed and the authoritative answer was 'this name does not exist'. Either the record is genuinely missing, the domain lapsed, or a recent DNS change has not propagated to the resolver you are using.

Lemwatch — All-in-One Website MonitoringUptime, performance, SEO, security, and change detection in one platform. Free tier available.Pricing · Features · Sign Up