IdeaIntake, Hypothesis, Research
Translate a scanning query
Paste a search written for Censys, Shodan, Netlas, FOFA, or ZoomEye and get it for the other four. Each engine indexes the same things under its own names, so most searches for attacker infrastructure and exposed products cross. One that tests something a single engine computes does not, and the page says why.
Tips
- Paste a search and the other four engines' forms appear as you type.
- A card that says no form names what that engine lacks, so you know what to search by hand.
- Each form has its own link, which opens the search in that engine.
It runs in this browser as you type, and the query is sent nowhere. Nobody has run what it writes against the engines, so check what each search returns.
The same thing in each engine
The names the translator moves between. A blank cell is something that engine has no field for, and a search that tests it is refused for that engine.
| What it tests | Censys Platform | Shodan | Netlas | FOFA | ZoomEye |
|---|
Changes a translation makes to the search
- Every engine but Censys returns one service for each result. Censys returns a host, so the translator puts their conditions inside one
host.services, which asks for all of them on the same service. - Going the other way, a Censys search can ask for a title on one service and a certificate on another. The other engines can only ask for both on one, and the page notes it.
- Shodan joins its terms with and. A search with alternatives becomes one Shodan search for each, up to six.
- Shodan has no filter for a response header, so a header is written as the text Shodan stores in the banner, such as
"Server: nginx". - Shodan, FOFA, and ZoomEye have a field for only some parts of a certificate's name. For the rest, the translator searches the whole certificate for the value and adds a note to the result.
- FOFA and ZoomEye negate one condition at a time, so a search that excludes a group is rewritten to exclude each condition in it.
- Only Censys and Netlas read a regular expression. A search with one stays in those two.
- Censys's earlier search language is read too, and written for the Platform, which Censys is moving every search to.
- Each engine scans its own ports on its own schedule, so the same search returns different servers in each.
Rendered from framework.json v0.136.0, CC BY-NC 4.0. Censys field names are checked against the Platform's field list, from . The translator is scanquery.js, which also writes the detection library's scanning queries for each engine.