Security
DNSFilter integration
Use DNSFilter? Connect it to MSProspector to find upsell revenue in your clients. Built for MSPs who want more leads, marketing and sales.
Reads which client sites have a DNS filtering policy and which don't. View-only.
Setup steps are for connected customers — sign in to read them.
What we find in DNSFilter
Which client sites have no DNS-filtering policy attached — a fact the vendor reports directly. Blocked-threat volume not yet wired (Traffic Reports endpoint, unconfirmed response schema).
Every finding lands on your Client Upsell board as a named client with a number beside it — not a report you have to read.
What the DNSFilter connection does
Read — powers Client Upsell
Read your clients' stack
Who is actually protected: endpoints still onboarding, seats never deployed, sites with no filtering policy.
Permissions to prepare with your administrator
Required permissions and account access
- Account Settings → API: dedicated API Key. This key is not scoped to read-only; the connector itself only reads organizations, sites and policies.
Which accounts and records: Use the MSP account covering intended organizations/sites. Do not promise that the vendor key cannot write.
A green credential check proves access to the records tested. Confirm the expected data after the first pull; missing permissions or tenant consent must remain visible.
Read-only
We only ever read — we never change anything in DNSFilter
You make a view-only key using our setup steps. Our connection has no code that can write to DNSFilter, and your key is encrypted and only used to read.
DNSFilter integration — common questions
- How does the DNSFilter integration help my MSP get more leads and sales?
- Client Upsell reads DNSFilter view-only and turns what it finds into upsell opportunities: each one a named client with a number beside it, ready for your account managers to sell.
- What does the DNSFilter integration read?
- Reads which client sites have a DNS filtering policy and which don't. View-only.
- What does MSProspector find in DNSFilter?
- Which client sites have no DNS-filtering policy attached — a fact the vendor reports directly. Blocked-threat volume not yet wired (Traffic Reports endpoint, unconfirmed response schema).
- Is the DNSFilter connection read-only?
- Yes. We only ever read from DNSFilter — our DNSFilter connection has no code that can change anything, and an automated check on every change to our code blocks any that could. Please create a view-only key using the setup steps, so the key itself can't make changes either.
