Skip to main content
Solved

services.extended_service_name not available on the censys platform

  • August 20, 2025
  • 3 replies
  • 55 views

I’m attempting to convert my queries to the new query syntax. There is one field that I use frequently that will not convert: services.extended_service_name. The error I get back is that it is not available on the censys platform.

Is this a known issue? Was this field migrated but not mapped for the query converter tool?

Thanks

Best answer by vitutus

We were able to handle this by replacing “extended_service_name” with “service_name” in the legacy query. This works in the converter by mapping it to “host.services.protocol”. We have 9 queries that use extended_service_name and all of them kept the original search text.

 

 

3 replies

MattK_Censys
Forum|alt.badge.img+2
  • Censys Community Manager
  • August 21, 2025

Hi vitutus, that field was dropped from the Platform. However, there are ways to find those services in Platform that you would normally find using that field in Legacy Search--can you share more about what you’re looking for and I can lend a hand? Feel free to DM me if you’d prefer that.


  • Author
  • New Participant
  • Answer
  • August 25, 2025

We were able to handle this by replacing “extended_service_name” with “service_name” in the legacy query. This works in the converter by mapping it to “host.services.protocol”. We have 9 queries that use extended_service_name and all of them kept the original search text.

 

 


MattK_Censys
Forum|alt.badge.img+2
  • Censys Community Manager
  • August 25, 2025

Hey ​@vitutus , glad to hear you got that sorted. The host.services.protocol field is indeed where many of those values now live.