MONIX :: OPEN DIAGNOSTIC PLATFORM

Website Reconnaissance & Continuous Health Monitoring

Instant security header audits, TLS verification, SEO crawl directive analysis, subdomain discovery, scheduled 5-minute uptime checks (GitHub Actions), and webhook alerting for registered targets.

Zero-Auth Instant Reconnaissance
Quick probe:

Comprehensive Platform Capabilities

Security Headers & TLS Chain

Strict audit of HSTS, CSP, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, plus certificate issuer and expiry telemetry.

Native Subdomain Enumeration

Passive Certificate Transparency log lookup via crt.sh, wildcard DNS filtering, and active HTTP status & IP probing.

Continuous Uptime Monitoring

Registered targets are pinged every 5 minutes by a GitHub Actions workflow calling /api/cron/uptime. Incidents open after 2 consecutive failures; 24h and 30d uptime come from stored check history.

Public Status Pages

Custom status portals at /status/[site] with 24-hour response time latency charts and 30-day incident logs.

Certificate Expiry Alerts

Nightly TLS certificate verification with customizable 14-day advance expiration warnings dispatched via webhooks.

Real-Time Webhook Alerting

Dispatches JSON event payloads for incident.started, incident.resolved, and cert warnings with 1x auto-retry.

Inspection Pipeline Highlights

  • Zero Authentication Wall — Instant scans from the Inspector. No sign-in or account required.
  • Permanent Public Artifacts — Every scan produces a shareable report at /r/[slug].
  • SEO & Discoverability Checks — Meta tags, Open Graph preview tags, robots.txt, XML sitemap verification.
  • Core Web Vitals — Largest Contentful Paint (LCP), Cumulative Layout Shift (CLS), and lab metrics.
  • Rate-Limited & Protected — Sliding window rate limiter (5 scans/hour/IP) preventing abuse.

Frequently Asked Questions

Q: Is any authentication required to inspect a website?

No. Monix is completely unauthenticated for public inspections. Anyone can open the Inspector, enter any public URL, and instantly generate a diagnostic report.

Q: How does the uptime monitoring worker operate?

Uptime checks run every 5 minutes via the GitHub Actions workflow at .github/workflows/uptime-cron.yml, which POSTs to /api/cron/uptime. An incident opens after 2 consecutive failed checks and closes automatically when the target recovers.

Q: How do I view or configure public status pages?

You can view public status pages at /status/[site] or search them in the Status Directory.