OZ
Oraclez
Admin Login/Register

Oraclez Help

Everything you need to use Oraclez like a pro: quick start, understanding results, module details, privacy, API, FAQs, and troubleshooting.

Quick Start
Search a domain

Go to Home, enter a domain, optionally enable Telegram analysis, and run.

Understanding results
TrustScore & modules

Domains receive a 0–100 score; details are available per module (Archive, Content, Behavior, External, Telegram) with JSON downloads.

Downloads
Raw JSON per module

Download each module’s JSON for downstream analytics or SIEM ingestion.

What is Oraclez and how does it work?

Oraclez is a website risk assessment engine. It blends AI, OSINT, and behavioral analysis to surface risk signals, anomalies, and trust indicators. Results include a single TrustScore plus detailed, module‑specific outputs.

  • Archive: Visual history and archivals (sudden changes, domain age, visual patterns).
  • Content: Page content analysis (exaggerated claims, phishing signals, inconsistencies).
  • Behavior: Client/network behavior (suspicious requests, trackers, redirects).
  • External: External/OSINT signals (domain/IP reputation, blocklists, DNS, social).
  • Telegram: Optional: channel/message analysis to validate claims and detect risk.

Quick Start

  1. Go to the Home page.
  2. Enter a domain like example.com or a full URL.
  3. Optionally enable Telegram analysis and provide a channel handle or link.
  4. Click “Search” or “Run Analysis”.
  5. Review the TrustScore, module cards, and download JSON outputs.

Tip: The “History” page lists your recent analyses with previews and scores.

TrustScore (0–100)

0–39 (High Risk)
Strong negative signals; proceed with extreme caution.
40–69 (Uncertain)
Requires deeper review and claim verification.
70–84 (Moderate→Good)
Mostly positive indicators; investigate flagged items.
85–100 (Confident)
Strong, stable positive signals.

TrustScore is a weighted summary across modules. Always verify module details, strengths/weaknesses, and sources before making decisions.

Modules

Archive

Screenshots, archivals, and sudden-change detection. Useful for spotting rapid rebrands and visual inconsistencies.

Content

Page text/structure analysis to detect exaggerated claims, phishing cues, risky keywords, inconsistencies, or missing legal info.

Behavior

Network requests, redirects, trackers, hidden loads, and user events. Helps identify data leakage or aggressive behavior.

External

External signals including domain/IP reputation, blocklists, DNS, social presence, and other OSINT sources.

Telegram (optional)

Collects messages/metadata from a related channel/group to detect pump‑and‑dump patterns, scams, or marketing inconsistencies.

Each module’s raw JSON can be downloaded.

Privacy & Data Security

  • Your input (domain/options) is sent to the server to run analysis (POST /api/run).
  • Analysis history is kept to enable re‑use and show recent scans (GET /api/history).
  • If Telegram is enabled, a valid session/cookie may be required and is used only for that run.
  • Avoid sharing sensitive data publicly; review outputs before distributing.

Detailed privacy policy and Terms will be published under Legal.

API (experimental)

POST /api/run

Run analysis for a domain (and optionally a Telegram channel).

{
  "url": "https://example.com",
  "hasTelegram": false,
  "telegramChannel": "@channel_or_link"
}
GET /api/history

List recent analyses with domain, score, and preview.

GET /api/metrics

Retrieve scoring parameters/metrics (if configured).

APIs may change without notice. Production use will require keys, quotas, and an agreement.

FAQ

Is the TrustScore definitive?

No. It’s a probabilistic, weighted summary. Always review module details and use human judgment.

How do I download raw data?

Each module card provides a “Download JSON” link on the results page. You can also use the API.

What does Telegram analysis require?

Some channels require a valid session/login. If provided, it’s used only for that specific run.

Are false positives/negatives possible?

Yes. The web is dynamic. Re‑check over time and corroborate with other sources.

Troubleshooting

  • No score shown: Insufficient data or module errors. Try again later.
  • JSON download disabled: The module output was not generated or failed.
  • Timeout/slow scans: The target may be slow or external sources blocked; runs can take longer.
  • Telegram: Limited channels require a valid session; re‑authenticate if needed.

Support & Contact

For feature requests, bug notes, or security questions:

  • In‑app issue submission (coming soon)
  • Support email (coming soon)

Until official channels launch, use this Help page and the Blog.