This Alpha release turns website troubleshooting into one read-only diagnoseWebsite workflow that correlates DNS, trusted TLS, and HTTP evidence, identifies the layer to inspect first, preserves raw probe results for agents and automation, and validates targets before network access; the public website guide now prepares that single command while retaining the three specialized probes for deeper inspection.
Diagnose a website with one command
- Add
diagnoseWebsite, a read-only workflow that correlates DNS resolution,
trusted TLS certificate validation, and HTTP reachability in one result. It
reportsoverall_status,primary_issue_layer, per-layer status, findings,
prioritized next actions, and the raw evidence from every completed probe. - Preserve useful evidence instead of manufacturing certainty: an authoritative
DNS name-not-found result skips downstream checks that cannot succeed, while
resolver, TLS-engine, or HTTP-probe failures remain explicit partial diagnostic
evidence rather than being mislabeled as website outages. - Harden the input boundary before network access. The workflow defaults bare
hostnames to HTTPS and rejects non-HTTPS schemes, embedded credentials, query
strings, fragments, shell-sensitive input, numeric-address forms, and invalid
ports before starting a probe. - Turn the bilingual website-triage guide into a one-command first success while
keepingcheckDns,checkSslCertificate, andcheckUrlStatusavailable as
transparent deep probes. The guide, agent briefing, command catalog, Spanish
metadata, safety policy, and GitHub documentation now describe the same
89-command product surface.
QZX — Quick Zap Exchange, created and maintained by Alejandro Sánchez.