See the conclusion first
Begin here when you need to see which integrations are genuinely available. Stay with the domain, relationship or service state named on the page; the task does not widen silently into a different security or product claim.
Authorised external exposure management
Integrations
This page helps you see which integrations are genuinely available. A domain becomes one clear, traceable assessment, not a collection of disconnected scanner outputs.
Bounded collection. Explicit permission. No exploitation or authentication attempts.
The useful answer
See which integrations are genuinely available
A domain becomes one clear, traceable assessment, not a collection of disconnected scanner outputs. This page helps you see which integrations are genuinely available. The relevant evidence, owner and limit remain available from the same route.
Useful for: MSP operator · platform engineer.
In practice
From permission to useful action
Open the evidence behind it
Portfolio and MSP workflows separate tenants, domains, responsibility and delegated access. Open the relevant report evidence when you need to verify the source, observation time, attribution or qualification behind it.
Keep uncertainty visible
Complete the step shown on the page, then check the resulting state before moving on. Unknown, unavailable and not-applicable outcomes remain distinct, so absence is never presented as a successful or reassuring result.
Carry the same fact into reports and monitoring
Turn the recorded evidence into actions, ownership, monitoring and useful exports. Record the resulting owner, evidence or recovery state where the product provides it, so another person can verify what happened without repeating the task.
What you can rely on
What supports the decision
The conclusion, evidence and limits stay connected.
Clear scope
Portfolio and MSP workflows separate tenants, domains, responsibility and delegated access.
Traceable evidence
The page explains only what the current service state can support.
Honest limits
Unknown or unavailable information remains visible rather than being treated as a positive result.
Important boundary
What this does not mean
Integrations supports one defined outcome: see which integrations are genuinely available. Domain Signals is not a penetration test, certification, data-residency assessment or prediction of breach likelihood. Missing evidence is not evidence of safety.
Questions answered
Read the conclusion and its limits together
What does Integrations help me decide?
This page helps you see which integrations are genuinely available.
What evidence sits behind the answer?
Domain Signals keeps the source, observation time and evidence state alongside each conclusion. The relevant report view provides the technical detail when you need to inspect it.
What should I not conclude?
Integrations supports one defined outcome: see which integrations are genuinely available. Domain Signals is not a penetration test, certification, data-residency assessment or prediction of breach likelihood. Missing evidence is not evidence of safety.
Keep exploring