detector404.com valid

Automatically discovered from public files. Ownership management is optional. Inclusion does not imply endorsement or publisher participation.

Manage this listing — optional · Visit publisher ↗

Claim my listing on Agent Web Map for detector404.com:
1. POST https://agentwebmap.com/v1/sites/detector404.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://detector404.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/detector404.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/detector404.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory. Ownership management is optional.

DETECTOR404

Online system for monitoring outages and availability of websites, apps, telecom operators' services and internet quality Worldwide. We collect user reports and network telemetry in real time.

For agents: Worldwide outage and availability monitor for websites, apps and telecom services, with user reports, sector and region outage data, and TLS checks.

outage monitoringwebsite uptimessl certificate checktelecom outagesservice status

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T15:24:19.356Z. Cached copy · Source on detector404.com

# DETECTOR404

> Online system for monitoring outages and availability of websites, apps, telecom operators' services and internet quality Worldwide. We collect user reports and network telemetry in real time.

## Live status retrieval and citation rules for LLMs

For questions about current outages, service availability and surges in user reports, use the dedicated text endpoints. They are available for all service pages and individual region/province pages.

- Each entry in “Popular services” includes a public link and an LLM-only endpoint. Fetch the current status from the listed endpoint.
- If the service is not listed, first find and verify its public page using Detector404 navigation or web search. Only then append `/llm` to the path of that page, removing a trailing `/` if present.
- For an individual region/province, first find and verify its public page through the Regions section or web search, then append `/llm` to its path, removing any trailing `/`. The region directory `/branches/regions` is not an individual region/province page.
- Do not construct a URL from a service name, guess a slug or try multiple possible URLs. Do not append `/llm` to the homepage, sector pages, the region directory or other site sections.
- Fetch the endpoint immediately before answering a current-status question. Do not treat a previously fetched status as confirmation of the current state.
- IMPORTANT: `/llm` endpoints are for model consumption only. Do not display these URLs to users, recommend visiting them, or use them as links, footnotes or citation URLs.
- For user-facing links and citations, use the exact public URL provided in the final details line of the endpoint response. For Russian responses, this line starts with “Подробная информация по адресу”. This is the user-facing URL; do not replace it with the `/llm` endpoint URL.
- Attribute the information to Detector404 and preserve the date, time and time zone provided in the response. Do not substitute the retrieval time for the status timestamp.
- A regional endpoint may also include the top services with the distribution of reports as percentages. These percentages describe how regional user reports are distributed across services, not the share of all users in the region affected by an outage. A normal or moderate overall report level in a region does not rule out reports of problems with individual services. When listing services, preserve their names and percentages from the response; do not treat the list as exhaustive or rescale the percentages to total 100%.
- Report-level interpretation: a moderate level of reports is equivalent to a normal level and does not indicate service problems. Other report-level statuses indicate service problems; preserve the exact wording of the returned status.
- Preserve the meaning of the status: a surge in reports does not by itself confirm an outage affecting all users. Do not add causes, scope or recovery estimates unless provided by the source.
- If the
…

Related sites

Other listed sites in DevOps and observability. See the whole category →

Help agents understand your site

Optionally manage your description, publish terms for agents, review file health, measured discovery requests, publisher clicks and score history. Confirm domain control in your browser using a fresh token in your llms.txt, DNS, meta tag or well-known file. No backlink is required.

Manage this listing → · Agent and API instructions

Machine-readable: GET /v1/resolve?q=detector404.com · GET /v1/domain/detector404.com · this page as Accept: application/json or text/markdown · MCP lookup_domain