Product help
Include the workspace, page, approximate time and correlation reference. Do not send passwords, magic links, API keys, full report evidence or customer secrets.
Bounded collection. Explicit permission. No exploitation or authentication attempts.
What to do
Each guide takes you from the current screen or state to one safe, testable outcome. This page helps you raise and track a product support request. The relevant evidence, owner and limit remain available from the same route.
Useful for: customer.
In practice
Begin here when you need to raise and track a product support request. 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.
The product uses managed access while public purchase remains disabled. Open the relevant report evidence when you need to verify the source, observation time, attribution or qualification behind it.
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.
Contact support with the correlation reference, never credentials or secret values. 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
Confirm the workspace, domain and evidence state before completing a task.
The product uses managed access while public purchase remains disabled.
The page explains only what the current service state can support.
Unknown or unavailable information remains visible rather than being treated as a positive result.
Important boundary
Product support supports one defined outcome: raise and track a product support request. Domain Signals is not a penetration test, certification, data-residency assessment or prediction of breach likelihood. Missing evidence is not evidence of safety.
Secure public journey
We collect only what is needed to respond. Do not include passwords, API keys or report evidence in this form.
Questions answered
This page helps you raise and track a product support request.
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.
Product support supports one defined outcome: raise and track a product support request. 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