Dotcom-Monitor
Unclaimed verified 22 aug 2026Website Monitoring & Real-Browser Testing for Logins, Carts & APIs
TL;DR
Dotcom-Monitor is a synthetic monitoring platform that tests websites, APIs, infrastructure, and complete browser-based user journeys from global locations. It is intended for ecommerce, SaaS, agencies, and IT teams that need to verify real transactions—not just whether a URL responds. Its main differentiator is the combination of real-browser testing, API monitoring, detailed diagnostics, and broad protocol coverage in one dedicated platform.
What Users Actually Pay
No user-reported pricing yet.
Our Take
Dotcom-Monitor occupies the space between lightweight uptime-monitoring tools and full observability platforms. It goes beyond basic HTTP checks by executing browser-based workflows and validating transactions, making it useful when a site can return a successful status code while a login, JavaScript component, API dependency, or checkout process is actually broken. Its strongest value proposition is depth without requiring a complete observability stack. Real Chrome and Edge testing, multi-step journeys, API authentication and validation, global checkpoints, screenshots, waterfalls, video capture, and private agents give technical teams substantial diagnostic capability. The platform also supports a wide range of infrastructure and network checks, which broadens its usefulness beyond purely web-focused monitoring. External user feedback is broadly favorable, particularly regarding monitoring coverage, reporting, diagnostics, setup for common use cases, and customer support. However, several reviewers describe the product as expensive compared with simpler uptime tools, and some find the pricing structure difficult to understand. Other criticisms include a dense or dated interface in some areas, setup complexity, limited quotas, and the lack of a single unified performance overview. Dotcom-Monitor is best suited to organizations with business-critical websites, customer portals, APIs, or distributed services that need proactive validation from outside their environment. It may be excessive for a small site that only needs inexpensive uptime alerts, and larger engineering organizations may prefer Datadog, New Relic, Dynatrace, or another unified observability platform if logs, traces, APM, infrastructure metrics, and synthetic monitoring must be managed together.
Alternatives
Ranked by Revuo score — paid tiers never affect order.
Pros
- + Strong real-browser and transaction monitoring for logins, forms, carts, checkouts, and other multi-step workflows.
- + Broad coverage across websites, web applications, APIs, DNS, SSL, email, ports, FTP, UDP, WebSockets, VoIP, and related services.
- + Detailed diagnostics and reporting, including waterfalls, screenshots, response data, graphs, traceroutes, and video capture.
- + Generally straightforward setup for common website and API monitoring scenarios.
- + Reviewers frequently mention responsive support and helpful onboarding.
Cons
- - Pricing can be expensive for smaller organizations or teams comparing the product with basic uptime tools.
- - The pricing structure and separation of monitoring categories can be difficult to understand.
- - Some users describe the interface as dense, cumbersome, or dated in certain areas.
- - Advanced setup and configuration can require technical effort and careful alert-recipient management.
- - Users report limitations involving quotas, update frequency, geographic coverage, error explanations, or the absence of a unified performance dashboard.
MCP Integrations
1 server9 toolsKnow when your n8n workflows, URLs, and AI apps break, before your customers do
9 tools
nocrash_list_watchesList every watched item with its current status (green/yellow/red), optionally filtered by status. Also returns an overall health summary using the same display buckets (needs_help, needs_a_look, fine, waiting) the dashboard and nocrash_get_health show, so totals never contradict across tools. Each watch includes `last_error_message` (most recent error seen, regardless of current status) and `last_error_state` ("current" or "resolved"); both are nil when the watch has never errored.nocrash_get_healthGet overall health across every watched item — total count, counts by dashboard bucket (needs_help, needs_a_look, fine, waiting), overall status, last check time, and a plain-language one-liner. Counts use the same display-status precedence as the dashboard, so `needs_help` excludes never-pinged or unreachable items that still carry stale raw-red status.nocrash_get_watchGet full details for one watched item: schedule, recent activity, error history, and next expected run. `last_error_message` is the most recent error string seen, regardless of current status; use `last_error_state` ("current" or "resolved") to tell whether it's the current problem or already cleared. Both are nil when the watch has never errored.nocrash_list_eventsList event history across your watched items — filter by watch, by event type, or pass `event_id` to fetch a single event in full detail. Event types span the full range NoCrash watches for: routine check-ins, failures, recoveries, missed runs, silent step-level breakage, workflow on/off changes upstream, and browser-side errors from vibe-coded apps (script crashes, unhandled promise rejections, failed network calls, page loads).nocrash_get_briefGet the latest daily brief — the most recently generated plain-language summary of what happened overnight across your watched items. Read-only; never triggers fresh AI generation.nocrash_search_errorsSearch every error event by keyword. Matches against error messages, failing node names, plain-language error context, and AI-suggested fixes across all your watched items.nocrash_send_pingSend a heartbeat for a watched item to confirm the workflow is running. This is a write — it resets the failure count and updates status to green.nocrash_report_failureReport that a workflow failed. Records the error and updates the watched item's status. Include as much detail as possible — error message, failing step, and any context an agent or human will need to debug.nocrash_refresh_watchForce a fresh check of a watched item now instead of waiting for the next scheduled poll. Shares the dashboard refresh cooldown — 60-second wait between refreshes and a 10-per-hour ceiling per connection. Push-based watches (JS snippet) update on their own when data arrives and can't be refreshed on demand. The refresh runs asynchronously, so the new status appears on the item a few seconds later.
Last checked Aug 23, 2026
Compare With
Reviews
No reviews yet. Be the first to review Dotcom-Monitor!