WEIDU

A little more signal. A little less noise.

Pause. Trace it.
Make up your mind.

Signal Check helps you examine a link, separate claims from evidence, and keep a record of what you find.

01 / Start with the source

What are you looking at?

This first step stays in this browser. Use a public HTTPS link without a query string, password, or private sharing token.

03 / Put the evidence beside the claim

A claim is a starting point.

Write the exact statement, then record what a source does and does not support. These are your notes and assessments; the tool does not verify them.

Claim wording and evidence notes stay in this page’s memory. Search links send the claim to Google only when you open them. Check the search provider’s privacy terms before using them.

No automatic verdict

04 / Leave a clear record

Keep the uncertainty visible.

Notes are editable. Download a new record after any correction; no public report is published here.

Nothing is saved to browser storage by this app. Use Clear this check before leaving; your browser may retain page memory in its history. Downloaded files remain on your device until you delete them.

Show the working

A check you can inspect.

Method v0.1 · Public beta
Built for learning and careful reading.

  1. Local observations. We read the structure of the link in your browser. A domain name and HTTPS connection do not establish credibility.
  2. Optional retrieval. With your consent, the service checks its supported-host list and robots policy before fetching limited page metadata. It does not bypass login, payment or access restrictions. Retrieval can fail or be incomplete.
  3. Human evidence notes. You choose the claim, source and relationship. Search results and repeated claims are leads, not independent corroboration. Follow the underlying evidence and credit its creator.
  4. Explicit limits. There is no LLM call, hidden truth score or synthetic-media detector. C2PA provenance concerns origin and editing history; it does not by itself establish factual accuracy. No C2PA validation runs in this beta.
Privacy, attribution and corrections

This app does not use analytics, application cookies, browser storage or a report database. The hosting layer may set security cookies, including Cloudflare bot-management cookies. Optional fetches send the entered public URL to the hosting service, which may process connection logs. Publishers receive retrieval requests. External links and searches contact their own providers only when you open them. Avoid personal, confidential or token-bearing links.

Fetched metadata is attributed to the source URL and retrieval time. Short extracts are provided for examination; rights remain with their creators. A blocked or missing field is not evidence of deception. Do not republish someone else’s content or a damaging allegation on the strength of this record.

Correct your notes here and export again. Reports include a method version and uncertainty. Service-wide corrections can be raised through the Weidu website; this beta has no submission or moderation inbox.

Accessibility and feedback

The interface uses labelled controls, keyboard navigation, visible focus, responsive layouts and text in addition to colour. The WCAG 2.2 guidelines guide the design. A full accessibility audit and assistive-technology user testing are still needed. Use the downloadable plain JSON record or browser print view if helpful.

If the automatic page fetch cannot read a source, open it directly and record what you can establish. Dynamic pages, social media and videos may need that manual route.