Clash / Mihomo Route Inspector
Analyze Clash / Mihomo routing rules, target relations and static notes locally; debug explicit target metadata without turning unknown or earlier runtime conditions into definite matches.
- 1Add config
- 2Analyze routes
- 3View result
Paste or import a configuration, or try the example.
1. Configuration input (Clash / Mihomo YAML)
Up to 256 Ki characters / 1 MiB per file; 2,000 rules, 1,000 targets and 5,000 explicit candidate links. Files and examples only fill input.
Evaluates only an explicit fixed target and supported rule subset. Unknown/logical/runtime conditions and missing metadata stay indeterminate; earlier uncertainty affects later conclusions. No DNS, speed tests, rule-set downloads, client execution or actual group selection.
Static checks and runtime results have different scopes
Input and report stay in page memory and clear on account/language change or leaving. Reports omit node passwords, server addresses, rule-set URLs and raw unknown containers. Rule match values and names may still be private; keep them safe.
Read local rules and target relations with original numbers and explicit static scope.
Workflow
- Paste configuration or read a local file. Examples only fill input. Analyze to retain every original rule number.
- Search/filter/page rules, target relations and static notes; inspect details or copy the full static report.
- Open Target debugging, supply domain/IP/TCP or UDP/port and debug explicitly. Expand condition explanations, filter outcomes and copy the full debug report. Omitted fields remain unknown; target changes discard stale debug results.
Scope
ASCII/Punycode domains/suffixes/keywords, IPv4/IPv6 CIDR, TCP/UDP and integer destination ports. sing-box address fields use OR; port/network use AND. Nonterminal actions are not executed and affect later certainty. Shows the first readable terminal candidate and existing final, without creating outbounds or defaults.
GeoIP, Geosite, rule sets, logical/process/unknown conditions keep original numbers and remain indeterminate. Earlier unknown conditions, missing input or runtime actions cannot be skipped to claim a later real match. Candidates are not live group selection. This is not complete client validation. Batch addresses use the standalone batch rule debugger; interactive flow diagrams and live group selection remain separate work.
Local processing and limits
Page memory only. Input/target changes, account/language changes or leaving discard stale results. Up to 256 Ki configuration characters, 1 MiB file, 2,000 rules, 1,000 targets, 5,000 candidate links and 2 Mi report characters; no truncation. No network, rule-set downloads or uploads. Reports omit node passwords/addresses, provider URLs and unknown raw containers; names, rule values and supplied targets may remain private.
Discussion 0
Ask a question or share something useful for the next reader.
Sign in to comment, reply and vote.
Sign in to join