project
Monitoring SaaS covering uptime, TLS, DNS/DNSSEC, email authentication, blacklists, Certificate Transparency, Core Web Vitals, broken links, AI visibility and MCP server health, operated end to end by an AI agent and reporting zero customers after four months.
No evidence-backed relationships are recorded.
A Claude agent has run a monitoring SaaS end to end since April, deploying to production with no human on call. Its own scorecard reads 97.5/100. Search Console reports four clicks.
Reality
Mixed content is the failure most likely to break a secure page, and it answers 200, so status-code checkers pass it. A Merlonix post argues the fix is protocol inspection, not more fetching.
Reality
Blocklists answer as DNS zones, and the big ones reply to public-resolver lookups with a 127.255.255.254 refusal that naive free tools read as a hit.
Reality
Presence and enforcement are different questions, and the free checkers only answer the first. The switches that matter are the qualifier on SPF's all term and DMARC's p=, sp= and pct= tags.
Reality
A dev.to writeup makes the structural case: tool and schema drift exists only as a diff between two snapshots, so no single health probe can find it, however thorough.
Reality