CYBER.COUNTRYTools
METHOD / LIMITS

How checks work

Each tool is designed around a narrow question. The output describes observable structure or locally calculated data, not a broad verdict about whether something is safe.

Four rules

  1. Keep input local. Tool inputs are processed in the browser whenever the tool says so.
  2. Show the basis. Results explain which fields, bytes, or structural clues produced the output.
  3. Name the limit. A structural check is not threat detection, and a match is not proof of trust.
  4. Leave control with the user. QR content is shown as text and is never opened automatically.

What each tool establishes

URL inspector

Parses the address and highlights structural clues. It does not visit the destination or declare it safe.

Checksum

Calculates a local digest and compares exact text. A matching digest only proves the bytes match the supplied reference.

Photo metadata

Reports readable metadata, including location fields when present. A basic scrub copy may alter image quality, profiles, or animation.

QR inspector

Decodes an uploaded image locally and exposes the content as text. It never follows the decoded destination.

Passphrase

Uses browser cryptography and a published word list. Security still depends on keeping the result private and using it correctly.

security.txt

Formats user-provided fields. Publication, ownership, HTTPS, and ongoing maintenance remain the user's responsibility.

How to read a result

Treat each result as one piece of evidence. Pause when an address is unexpected, a checksum differs, a photo contains sensitive metadata, or a decoded QR destination does not match the context in which it appeared.

For a suspected compromise, active fraud, stolen access, or regulated data exposure, preserve evidence and contact an appropriate professional or authority. Cyber.country does not monitor incidents or receive emergency reports.

Maintenance

Tool behavior, source packages, and visible limitations are reviewed when the site changes. Material changes are recorded on the changelog, and third-party code is listed on the open-source page.