What Signals observes
Begin here when you need to understand provider and customer responsibility. 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.
Trust Centre
A provider address is not automatically your server.
CDN, mail, hosting, anycast and managed-platform evidence stays dependency context unless attribution supports a customer-owned conclusion.
Bounded collection. Explicit permission. No exploitation or authentication attempts.
What this establishes
Understand provider and customer responsibility
The product earns trust by making its boundaries inspectable, not by asking buyers to accept a black box. This page helps you understand provider and customer responsibility. The relevant evidence, owner and limit remain available from the same route.
Useful for: security reviewer · supplier-risk lead.
In practice
How the claim is checked
What Signals can conclude
Shared or provider-managed infrastructure is dependency context and is not automatically customer exposure. Open the relevant report evidence when you need to verify the source, observation time, attribution or qualification behind it.
What remains unknown
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.
What requires human validation
Methodology changes interrupt trends until comparable evidence exists. 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
Evidence you can inspect
Trust claims remain bounded by their source and current evidence.
Clear scope
Shared or provider-managed infrastructure is dependency context and is not automatically customer exposure.
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
Shared infrastructure boundary supports one defined outcome: understand provider and customer responsibility. 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 Shared infrastructure boundary help me decide?
This page helps you understand provider and customer responsibility.
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?
Shared infrastructure boundary supports one defined outcome: understand provider and customer responsibility. 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