Is Conductor Monitoring safe?
Conductor Monitoring sends active account-domain page URLs to Conductor's GraphQL API for monitoring checks.
When you are signed in, the extension watches active-tab changes and completed page loads, then checks whether the current page belongs to one of your Conductor account domains. Matching page URLs are sent to Conductor's GraphQL API to request page indexability, issue counts, prioritization, and prefetch data.
Who publishes itConductor Website Monitoring - no other listings under this identity, 1 shared hostname
Conductor Website Monitoring - no other listings under this identity, 1 shared hostname
What this publisher told the store about itself, and the other listings that told it the same thing.
Shared hosts - 1 hostname
Hostnames hardcoded in this extension that few other listings call. That can mean one operator behind both, and it can equally mean a small shared vendor, so it is context rather than a conclusion. Hosts that many listings call are left out: they are services, not connections.
AI-generated. Findings may contain errors. Those marked Verified have been manually reviewed.
Publishers can request a review.
Where it sends data
Destinations our analysis observed Conductor Monitoring contacting. Sending data somewhere is not a finding on its own - an extension that syncs your settings has to talk to its own server - but it is where your data can go, and who else it goes to.
- data.cm.conductor.com
Conductor Monitoring sends data to data.cm.conductor.com. No other extension we have analysed sends data here.