Good afternoon, the “*” symbol worked fine on the old platform, for example, I want to find cameras by a specific domain and make a request: “camera*.keenetic.*” at the same time, I get several hundred results (including cameravilla.keenetic.pro; camerahome.keenetic.link and many others), but when on a new platform I enter the same query “camera*.keenetic.*” I only get one response, for example: viagesu-camera.keenetic.link.
The "*" sign is simply ignored in any combinations.
At first, I thought these were temporary difficulties when switching to a new platform, but today I still could not adequately create a query so that the “*” symbol would work as indicated in the manual.
Page 1 / 1
Hey DenT, the * character no longer works as a wildcard in the Censys Query Language syntax used in the Platform. For reference, this is mentioned in our transition guides in the docs alongside some other syntax changes.
To replicate the query you provided in your second screenshot in the Platform, you need to use regex and target web properties. You could do something like:
web.hostname=~`^camera.*\.keenetic\..*$` and web.endpoints.http.status_code="302"
You may see fewer results in the Platform as Platform data is generally refreshed more frequently than Legacy Search data. When I checked some of the results of your second screenshot search query in Legacy Search, they had services.observed_at dates in February.
Additionally, you can use the query converter in Platform to convert Legacy Search queries into Platform compatible ones. If you’re using a wildcard from Legacy Search, then you’ll need to put the wildcard in a field query, like so:
As a side note, a full document on using regex in CenQL is coming soon.
Hope this helps - let me know if you have any follow-up questions.
As a side note, a full document on using regex in CenQL is coming soon.
Can’t wait to see that.
To replicate the query you provided in your second screenshot in the Platform, you need to use regex and target web properties. You could do something like:
web.hostname=~`^camera.*\.keenetic\..*$` and web.endpoints.http.status_code="302"
it turns out that it is no longer possible to use the service for free?:(
Queries that incorporate regex are only available to Platform users on the Starter tier or above.
As a side note, a full document on using regex in CenQL is coming soon.
Thank you for providing the documents, @MattK_Censys. I wanted to ask: Is the CenQL regex compatible with PCRE, or are there any restrictions? If there are, please document those as well
Hey Rittick, there is regex syntax in PCRE that is not accepted in CenQL regex and there is syntax in CenQL regex that is not accepted in PCRE. The best guide is what is published in the doc I linked above. Are there specific things from PCRE that you want to know whether they work in CenQL? I can check on that for you.
Hey Rittick, there is regex syntax in PCRE that is not accepted in CenQL regex and there is syntax in CenQL regex that is not accepted in PCRE. The best guide is what is published in the doc I linked above. Are there specific things from PCRE that you want to know whether they work in CenQL? I can check on that for you.
I wasn’t able to explore regex on the new platform yet, will let you know when I get access to higher and play with regex. Thanks for insight.
You need a Censys account in order to create a Censys Community account. When you click the button below, you will be redirected to login using your existing Censys credentials. If you do not already have a Censys Community account, you will be prompted to create one after logging into your Censys account.
You need a Censys account in order to create a Censys Community account. When you click the button below, you will be redirected to login using your existing Censys credentials. If you do not already have a Censys Community account, you will be prompted to create one after logging into your Censys account.
