Welcome! This guide shows you how to use OSINT Reality Checker to evaluate security vendors in a clear, repeatable way – without getting lost in marketing language.
This is written for buyers, decision makers, and anyone who needs to choose tools confidently.
1) What you use this tool for
Security vendors often describe their products with phrases like “AI-powered”, “real-time”, “enterprise-grade”, or “next-generation.”
Some of that may be true – but as a buyer, your job is to answer:
“What do we actually know for sure – based on public evidence?”
OSINT Reality Checker helps you do exactly that.
It turns a vendor’s public materials into a structured report that tells you:
- what the vendor claims
- what public proof exists
- what evidence is missing
- what questions you should ask next
2) What you get as a result (in simple terms)
After a scan, you get a report with three practical outcomes:
A) A clear overall rating
A Marketinggrade Score (0–100) shows whether the vendor’s public story is:
- mostly supported by evidence
or - mostly marketing language without verifiable proof
Think of it like a “reality check” score.
B) A list of “proof gaps”
The tool highlights where proof is missing, for example:
- No benchmarks
- No API documentation
- No certification scope
- No clear pricing / SLA
This is your buyer advantage: you instantly know what to request before you commit time or money.
C) A ready-to-use question set for the vendor
Instead of asking vague questions like “tell us about your AI,” you can ask:
“Please share benchmark methodology and metrics (false positives/false negatives, precision/recall, and latency).”
That shifts vendor conversations from storytelling to facts.
3) Before you run your first scan (30 seconds)
Choose the best starting URL
You don’t need to scan every page manually.
Pick one good starting page, such as:
- the main product page
- a security/trust page
- a docs entry page
Best practice: Start with the product page. If the vendor has a “Security / Trust / Compliance” page, scan that next only if needed.
4) Running a scan (Step-by-step)
Step 1 – Open the Scanner
In the left menu, click Scanner.
Step 2 – Paste the vendor URL
Paste the URL of the vendor page you want to evaluate.
Step 3 – Choose scan depth
Choose how thorough the scan should be:
- Basic (fast): Good for a quick first impression
- Standard (recommended): Best for buyer decisions
- Deep (thorough): Use when vendors have many separate pages and scattered documentation
If you’re unsure: choose Standard.
Step 4 – Click “Run Scan”
The tool will now:
- read the content
- detect the main claims
- check for public evidence
- create your report
You’ll see results on-screen and in your workspace history.
5) How to read the results (this is the important part)
5.1 The Marketinggrade Score
This is a quick summary.
- 80–100: unusually well documented publicly
- 50–79: some evidence exists, but important gaps
- 0–49: mostly marketing language and weak public proof
A high score does not mean “secure.”
It means: “the vendor provides verifiable public documentation.”
5.2 Evidence Coverage (what proof was found)
The report checks for five types of proof:
- Certifications / compliance info
- API docs / developer references
- Whitepapers / technical documents
- Benchmarks / evaluation methodology
- Pricing / SLA transparency
If you see Benchmarks: NOT FOUND, that often matters most – because performance claims without benchmarks are hard to trust.
5.3 The Claim Table (your buyer’s goldmine)
This is where you win time and leverage.
Each claim (a sentence or headline from the vendor material) is listed with:
- what type of claim it is (AI / compliance / performance / operations…)
- whether it sounds like marketing language
- what proof is missing
How to use it:
- focus on claims that say something like “missing evidence”
- those are your next questions to the vendor
5.4 The Evidence Explorer (where proof was found)
This section points you to the public sources:
- docs links
- compliance pages
- whitepaper pages
- pricing pages
Use this to verify quickly and save time.
6) The most common buyer workflows (choose one)
Workflow A – Vendor shortlisting (fast)
Use this when you have many vendors and want to cut the list quickly.
- Scan each vendor once (Standard)
- Keep vendors with strong evidence coverage
- Remove vendors with repeated “missing evidence”
- Take the remaining vendors to demos/PoCs
Workflow B – Proof request before demo (recommended)
Use this when vendors look strong but you want to confirm key claims early.
- Scan the vendor
- Find the missing evidence items
- Send a vendor proof request (see template below)
- Only schedule demos when proof is provided
Workflow C – Executive decision briefing
Use this when you need to explain the decision to management.
- Export the report
- Share score + evidence gaps + “next actions”
- Attach vendor answers later
7) Vendor email template (copy/paste)
Subject: Evidence request for product claims (OSINT reality check)
Hello,
we are evaluating your product and want to validate key claims using publicly available evidence.
Please share supporting documents or links for the following items:
- Benchmarks and evaluation methodology (dataset/source, sample size, metrics such as FP/FN or precision/recall, and latency p50/p95)
- Clarification of “AI-powered”: which parts are ML-based vs. rule-based
- Certifications/attestations (scope and date)
- API documentation (OpenAPI/Swagger, SDK links, versioning policy)
- SLA / operational commitments (uptime and support response targets)
Thank you,
[Your name / company]
8) Do I scan once per domain or every page?
In most cases:
✅ One scan per vendor is enough (use the product page as the start URL).
The tool automatically reads additional pages depending on scan depth.
Run a second scan only if:
- the vendor has separate pages for Security/Trust and Docs, and you want maximum completeness
- the vendor has multiple products and you want to evaluate one product line at a time
You do not need to scan every page manually.
9) What if the report says “Update required”?
That means your tool version is older than the minimum allowed build.
Solution: download the newest build here:
https://snooppro.com/osint-reality-checker/
10) Tips to get cleaner, more useful results
- Start on a product page, not the homepage.
- Use Standard depth for fair vendor comparisons.
- Treat “missing evidence” as a procurement request, not an accusation.
- Good vendors will respond with docs and methodology. Weak vendors will avoid specifics.
