Leader
30%of answers name it
The most visible vulnerability scanners on ChatGPT, October 2026
Most cited source
61citations
From ChatGPT
Where engines disagree most
One engine
This page reads ChatGPT only. Set Engine to All to compare them.
Brands
| Rank | Brand | Heralded Score | Mentioned | Recommended | By engine | Mentioned by | Change |
|---|---|---|---|---|---|---|---|
| 1 | | 39 , range 28–57 | 30% | 20% | | First reading | |
| 2 | | 33 , range 20–48 | 20% | 17% | | First reading | |
| 3 | | 31 , range 17–44 | 20% | 10% | | First reading | |
| 4 | | 20 , range 11–37 | 13% | 3% | | First reading | |
| 5 | | 17 , range 5–36 | 10% | 3% | None | First reading | |
| – | | Too few answers | 0% | 0% | | First reading | |
| – | | Too few answers | 0% | 0% | | First reading | |
| – | | Too few answers | 0% | 0% | | First reading | |
| – |  AWS Inspector US | Too few answers | 0% | 0% | | First reading | |
| – | | Too few answers | 0% | 0% | | First reading |
“=” marks brands whose score ranges overlap, so the test cannot separate them. Every brand named in at least three answers is ranked. By engine has one dot per engine (ChatGPT, Google AI Overviews, Gemini and Google AI Mode), darker the more often it names the brand.
Most cited sources
| Rank | Source | Type | Cited in | Engines | Pages cited | Brands its pages mention |
|---|---|---|---|---|---|---|
| 1 | | Community | 73.3% | 1 of 4 | 30 | 11 |
| 2 | Withheld. Run a full Snapshot to see it. | |||||
| 3 | | Vendor site | 30.0% | 1 of 4 | 15 | 8 |
| 4 | Withheld. Run a full Snapshot to see it. | |||||
| 5 | | Community | 13.3% | 1 of 4 | 8 | 3 |
| 6 | | Brand site | 3.3% | 1 of 4 | 5 | 2 |
| 7 | Withheld. Run a full Snapshot to see it. | |||||
| 8 | Withheld. Run a full Snapshot to see it. | |||||
| 9 | Withheld. Run a full Snapshot to see it. | |||||
| 10 | Withheld. Run a full Snapshot to see it. | |||||
The questions, and who wins each
| Question | Language | Wins it |
|---|---|---|
| what vulnerability scanner should a security team use to find software flaws | English | |
| which tool can scan our applications for security vulnerabilities | English | |
| how do small engineering teams scan code for vulnerabilities | English | |
| what can help developers find vulnerabilities before release | English | No brand recommended |
| how can i find vulnerabilities across our applications | English | |
| how do we catch security flaws in code before deployment | English | No brand recommended |
| how can my team find and prioritize software vulnerabilities | English | No brand recommended |
| how do i check whether our software has known vulnerabilities | English | |
| should we scan source code or running applications for vulnerabilities | English | No brand recommended |
| what works better for finding flaws, manual reviews or automated scans | English | No brand recommended |
Each engine's top three
Related leaderboards
-
LeaderQuickBooks
-
LeaderToyota
-
LeaderBlinkist
-
-
LeaderMicrosoft Defender
-
LeaderHubSpot
-
LeaderZendesk
-
-
-
LeaderShopify
-
LeaderMailchimp
-
LeaderCrowdStrike
-
LeaderNetSuite
-
LeaderAdobe Acrobat Sign
-
LeaderRevolut
-
LeaderGusto
-
-
LeaderBitwarden
-
LeaderAsana
-
LeaderZapier
-
LeaderSalesloft
-
LeaderNavan
-
LeaderNordVPN
-
LeaderWix
Method
Each month Heralded asks every engine the same buyer questions, twice each, and reads every answer. An answer counts 0 for a brand it leaves out, 50 for a brand it names and 100 for a brand it recommends, and the Heralded Score is built from those. A brand named in at least three answers gets a score and a place.