Http header
PUBLIC DOMAIN DOSSIER
What is observed, how to verify it and what changed
4 public observations are documented in this dossier.
1 structuring public dependencies are visible.
2 useful changes are retained since the previous reading.
2 points still require confirmation or cannot be observed from outside.
TIME
Compared with the previous stored reading
SHORT VIEW
The 12 historical angles remain available below for deeper inspection.
Explanatory record
What Scanapse understands about this domain
Scanapse has enough material to describe 11 of 12 knowledge angles for webpion.com. 4 questions remain open with the available public evidence.
Read the domain folder
Four key points to understand what Scanapse observed, what can reasonably be retained, and what still needs verification.
Key points
Only a few items are shown when they add something genuinely useful to the reading.
Infomaniak is associated with 3 critical function(s) or observations in the visible scope.
This concentration is descriptive. It does not prove a future outage or the absence of failover mechanisms invisible to the scan.Territorial and legal context
Scanapse distinguishes established, probable and to-confirm jurisdiction and always explains which clues support the reading.
Regulatory frameworks
References are selected from the observed context. Their presence explains potential relevance, never automatic compliance.
The available public evidence does not establish a sufficiently reliable jurisdiction for automatic legal contextualisation.
This section provides documentary context. It is not legal advice, certification or a compliance verdict.
Trajectory
Only differences that help interpretation are highlighted. Stable or purely technical variations remain available in the evidence.
The available comparison does not surface a change worth highlighting in the public reading.
12 knowledge angles
Each angle explains what is known, why it matters, how to read it, its purpose and its limits.
Public evidence provides enough material to document this angle
Public evidence provides enough material to document this angle
This angle is only partially documented by public evidence
Public evidence provides enough material to document this angle
Public evidence provides enough material to document this angle
Public evidence provides enough material to document this angle
Public evidence provides enough material to document this angle
This angle is only partially documented by public evidence
Public evidence provides enough material to document this angle
Public evidence provides enough material to document this angle
This angle still needs additional public evidence
Public evidence provides enough material to document this angle
Overview
An overview of visible relationships and uncertainty areas that still need verification.
Visible relations
Relations are grouped by function. They describe what is publicly visible, not contracts or the full internal architecture.
ns12.infomaniak.ch
ns11.infomaniak.ch
mta-gw.infomaniak.ch
Apache
Infomaniak
Open questions
An unknown becomes useful information when it precisely explains what is missing to reach a conclusion.
An edge service does not reveal the origin hosting provider.
Public provider metadata does not prove where data is actually processed.
This check was not run with a compatible client during this measurement.
Detection of this signal was not enabled for this measurement.
These items do not mean there is a problem. They simply show that useful information is still missing.
Sources and evidence
34 evidence items are available. They remain collapsed to preserve a short reading and can be explored on demand.
Each proof keeps its method, provenance, date, reliability and interpretation limits.
Public mail policies show how the domain frames sending, authentication and email transport.
These mechanisms can reduce domain spoofing and document mail-transport posture.
Relate SPF, DKIM when a selector is known, DMARC, MX, MTA-STS and TLS-RPT. Compare policy changes over time.
Before strengthening a policy, inventory legitimate mail flows and verify alignment. Roll out changes progressively to avoid blocking authorized senders.
Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.
Rule 2026.09.4 · 2026-09-04T13:27:40+00:00
HTTP headers can ask the browser to enforce specific protections.
They are visible, verifiable browser-side defensive layers.
Read each full policy, identify permissive or contradictory directives, and compare responses across the main public routes.
Harden policies progressively from actual application needs. Avoid copying generic templates without functional testing.
Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.
{
"evidence": null,
"severity": "info"
}
Rule 2026.09.4 · 2026-09-04T13:27:40+00:00
DNS shows how a domain resolves and which public services are associated with it.
Consistent, verifiable resolution reduces some spoofing risks and helps explain entity dependencies.
Compare NS, A/AAAA, MX, CAA and the DNSSEC chain with previous measurements to identify delegation or operator changes.
If a change is unexpected, verify registrar and DNS-provider configuration before modifying anything. Document the failover mechanisms that actually exist.
Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.
This command reproduces the public observation without changing the target.
dig A webpion.com && dig AAAA webpion.com
2001:1600::aaaa:0:0:80:5b
Rule 2026.09.4 · 2026-09-04T13:27:40+00:00
DNS shows how a domain resolves and which public services are associated with it.
Consistent, verifiable resolution reduces some spoofing risks and helps explain entity dependencies.
Compare NS, A/AAAA, MX, CAA and the DNSSEC chain with previous measurements to identify delegation or operator changes.
If a change is unexpected, verify registrar and DNS-provider configuration before modifying anything. Document the failover mechanisms that actually exist.
Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.
v=DMARC1; p=reject;
Rule 2026.09.4 · 2026-09-04T13:27:40+00:00
DNS shows how a domain resolves and which public services are associated with it.
Consistent, verifiable resolution reduces some spoofing risks and helps explain entity dependencies.
Compare NS, A/AAAA, MX, CAA and the DNSSEC chain with previous measurements to identify delegation or operator changes.
If a change is unexpected, verify registrar and DNS-provider configuration before modifying anything. Document the failover mechanisms that actually exist.
Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.
This command reproduces the public observation without changing the target.
dig NS webpion.com
ns11.infomaniak.ch
Rule 2026.09.4 · 2026-09-04T13:27:40+00:00
DNS shows how a domain resolves and which public services are associated with it.
Consistent, verifiable resolution reduces some spoofing risks and helps explain entity dependencies.
Compare NS, A/AAAA, MX, CAA and the DNSSEC chain with previous measurements to identify delegation or operator changes.
If a change is unexpected, verify registrar and DNS-provider configuration before modifying anything. Document the failover mechanisms that actually exist.
Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.
This command reproduces the public observation without changing the target.
dig NS webpion.com
ns12.infomaniak.ch
Rule 2026.09.4 · 2026-09-04T13:27:40+00:00
TLS protects the observed connection between the scanner and the public service.
These elements document public-channel protection and the cryptographic mechanisms actually negotiated.
Compare negotiated protocol, issuer, expiry, chain and cryptographic parameters with history. Check other public entry points separately.
Address only observed gaps such as an expiring certificate, invalid chain, or unwanted protocol. Test changes in a controlled environment before deployment.
Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.
This command reproduces the public observation without changing the target.
openssl s_client -connect webpion.com:443 -servername webpion.com </dev/null
C = US, O = Let's Encrypt, CN = YR2
Rule 2026.09.4 · 2026-09-04T13:27:40+00:00
Public mail policies show how the domain frames sending, authentication and email transport.
These mechanisms can reduce domain spoofing and document mail-transport posture.
Relate SPF, DKIM when a selector is known, DMARC, MX, MTA-STS and TLS-RPT. Compare policy changes over time.
Before strengthening a policy, inventory legitimate mail flows and verify alignment. Roll out changes progressively to avoid blocking authorized senders.
Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.
This command reproduces the public observation without changing the target.
dig TXT webpion.com
hardfail
Rule 2026.09.4 · 2026-09-04T13:27:40+00:00
HTTP headers can ask the browser to enforce specific protections.
They are visible, verifiable browser-side defensive layers.
Read each full policy, identify permissive or contradictory directives, and compare responses across the main public routes.
Harden policies progressively from actual application needs. Avoid copying generic templates without functional testing.
Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.
[
"same-origin"
]
Rule 2026.09.4 · 2026-09-04T13:27:40+00:00
TLS protects the observed connection between the scanner and the public service.
These elements document public-channel protection and the cryptographic mechanisms actually negotiated.
Compare negotiated protocol, issuer, expiry, chain and cryptographic parameters with history. Check other public entry points separately.
Address only observed gaps such as an expiring certificate, invalid chain, or unwanted protocol. Test changes in a controlled environment before deployment.
Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.
2026-11-27T21:40:45+00:00
Rule 2026.09.4 · 2026-09-04T13:27:40+00:00
DNS shows how a domain resolves and which public services are associated with it.
Consistent, verifiable resolution reduces some spoofing risks and helps explain entity dependencies.
Compare NS, A/AAAA, MX, CAA and the DNSSEC chain with previous measurements to identify delegation or operator changes.
If a change is unexpected, verify registrar and DNS-provider configuration before modifying anything. Document the failover mechanisms that actually exist.
Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.
{
"evidence": null,
"severity": "low"
}
Rule 2026.09.4 · 2026-09-04T13:27:40+00:00
HTTP headers can ask the browser to enforce specific protections.
They are visible, verifiable browser-side defensive layers.
Read each full policy, identify permissive or contradictory directives, and compare responses across the main public routes.
Harden policies progressively from actual application needs. Avoid copying generic templates without functional testing.
Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.
[
"accelerometer=(), autoplay=(), browsing-topics=(), camera=(), display-capture=(), gamepad=(), geolocation=(), gyroscope=(), hid=(), interest-cohort=(), magnetometer=(), microphone=(), midi=(), payment=(), screen-wake-lock=(), serial=(), usb=(), xr-spatial-tracking=()"
]
Rule 2026.09.4 · 2026-09-04T13:27:40+00:00
HTTP headers can ask the browser to enforce specific protections.
They are visible, verifiable browser-side defensive layers.
Read each full policy, identify permissive or contradictory directives, and compare responses across the main public routes.
Harden policies progressively from actual application needs. Avoid copying generic templates without functional testing.
Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.
[
"default-src 'none'; script-src 'self' 'nonce-33SgrcmoexSdhkS7x-D0P4A4'; script-src-attr 'none'; style-src 'self' 'nonce-33SgrcmoexSdhkS7x-D0P4A4'; style-src-attr 'unsafe-inline'; img-src 'self' data: blob:; font-src 'self'; media-src 'self' blob:; worker-src 'self' blob:; connect-src 'self' blob: data:; manifest-src 'self'; form-action 'self'; frame-ancestors 'none'; base-uri 'none'; object-src 'none'; upgrade-insecure-requests"
]
Rule 2026.09.4 · 2026-09-04T13:27:40+00:00
Public mail policies show how the domain frames sending, authentication and email transport.
These mechanisms can reduce domain spoofing and document mail-transport posture.
Relate SPF, DKIM when a selector is known, DMARC, MX, MTA-STS and TLS-RPT. Compare policy changes over time.
Before strengthening a policy, inventory legitimate mail flows and verify alignment. Roll out changes progressively to avoid blocking authorized senders.
Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.
{
"evidence": null,
"severity": "low"
}
Rule 2026.09.4 · 2026-09-04T13:27:40+00:00
DNS shows how a domain resolves and which public services are associated with it.
Consistent, verifiable resolution reduces some spoofing risks and helps explain entity dependencies.
Compare NS, A/AAAA, MX, CAA and the DNSSEC chain with previous measurements to identify delegation or operator changes.
If a change is unexpected, verify registrar and DNS-provider configuration before modifying anything. Document the failover mechanisms that actually exist.
Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.
This command reproduces the public observation without changing the target.
dig A webpion.com && dig AAAA webpion.com
185.125.27.197
Rule 2026.09.4 · 2026-09-04T13:27:40+00:00
Public mail policies show how the domain frames sending, authentication and email transport.
These mechanisms can reduce domain spoofing and document mail-transport posture.
Relate SPF, DKIM when a selector is known, DMARC, MX, MTA-STS and TLS-RPT. Compare policy changes over time.
Before strengthening a policy, inventory legitimate mail flows and verify alignment. Roll out changes progressively to avoid blocking authorized senders.
Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.
Rule 2026.09.4 · 2026-09-04T13:27:40+00:00
HTTP headers can ask the browser to enforce specific protections.
They are visible, verifiable browser-side defensive layers.
Read each full policy, identify permissive or contradictory directives, and compare responses across the main public routes.
Harden policies progressively from actual application needs. Avoid copying generic templates without functional testing.
Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.
[
"Apache"
]
Rule 2026.09.4 · 2026-09-04T13:27:40+00:00
Public mail policies show how the domain frames sending, authentication and email transport.
These mechanisms can reduce domain spoofing and document mail-transport posture.
Relate SPF, DKIM when a selector is known, DMARC, MX, MTA-STS and TLS-RPT. Compare policy changes over time.
Before strengthening a policy, inventory legitimate mail flows and verify alignment. Roll out changes progressively to avoid blocking authorized senders.
Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.
{
"evidence": null,
"severity": "low"
}
Rule 2026.09.4 · 2026-09-04T13:27:40+00:00
DNS shows how a domain resolves and which public services are associated with it.
Consistent, verifiable resolution reduces some spoofing risks and helps explain entity dependencies.
Compare NS, A/AAAA, MX, CAA and the DNSSEC chain with previous measurements to identify delegation or operator changes.
If a change is unexpected, verify registrar and DNS-provider configuration before modifying anything. Document the failover mechanisms that actually exist.
Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.
This command reproduces the public observation without changing the target.
dig MX webpion.com
mta-gw.infomaniak.ch
Rule 2026.09.4 · 2026-09-04T13:27:40+00:00
Scanapse shows visible providers and third-party services on which the public service depends.
Concentration on one actor or many third parties can affect continuity and governance.
Identify each provider role, functions concentrated on the same actor, and dependencies that appeared or disappeared since the previous scan.
For a critical dependency, document owner, contract, reversibility, failover and rationale. Diversify only after analysing the actual need.
Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.
{
"critical": true,
"hosts": [
"mta-gw.infomaniak.ch",
"ns11.infomaniak.ch",
"ns12.infomaniak.ch"
],
"id": "infomaniak",
"known": true,
"name": "Infomaniak",
"observation_count": 3,
"services": [
"dns",
"hosting",
"mail"
],
"tracker": false
}
Rule 2026.09.4 · 2026-09-04T13:27:40+00:00
DNS shows how a domain resolves and which public services are associated with it.
Consistent, verifiable resolution reduces some spoofing risks and helps explain entity dependencies.
Compare NS, A/AAAA, MX, CAA and the DNSSEC chain with previous measurements to identify delegation or operator changes.
If a change is unexpected, verify registrar and DNS-provider configuration before modifying anything. Document the failover mechanisms that actually exist.
Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.
{
"evidence": {
"reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
"status": "not_tested"
},
"severity": "info"
}
Rule 2026.09.4 · 2026-09-04T13:27:40+00:00
HTTP headers can ask the browser to enforce specific protections.
They are visible, verifiable browser-side defensive layers.
Read each full policy, identify permissive or contradictory directives, and compare responses across the main public routes.
Harden policies progressively from actual application needs. Avoid copying generic templates without functional testing.
Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.
[
"DENY"
]
Rule 2026.09.4 · 2026-09-04T13:27:40+00:00
Public mail policies show how the domain frames sending, authentication and email transport.
These mechanisms can reduce domain spoofing and document mail-transport posture.
Relate SPF, DKIM when a selector is known, DMARC, MX, MTA-STS and TLS-RPT. Compare policy changes over time.
Before strengthening a policy, inventory legitimate mail flows and verify alignment. Roll out changes progressively to avoid blocking authorized senders.
Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.
This command reproduces the public observation without changing the target.
dig TXT _dmarc.webpion.com
reject
Rule 2026.09.4 · 2026-09-04T13:27:40+00:00
HTTP headers can ask the browser to enforce specific protections.
They are visible, verifiable browser-side defensive layers.
Read each full policy, identify permissive or contradictory directives, and compare responses across the main public routes.
Harden policies progressively from actual application needs. Avoid copying generic templates without functional testing.
Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.
[
"same-origin"
]
Rule 2026.09.4 · 2026-09-04T13:27:40+00:00
HTTP headers can ask the browser to enforce specific protections.
They are visible, verifiable browser-side defensive layers.
Read each full policy, identify permissive or contradictory directives, and compare responses across the main public routes.
Harden policies progressively from actual application needs. Avoid copying generic templates without functional testing.
Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.
[
"no-referrer"
]
Rule 2026.09.4 · 2026-09-04T13:27:40+00:00
DNS shows how a domain resolves and which public services are associated with it.
Consistent, verifiable resolution reduces some spoofing risks and helps explain entity dependencies.
Compare NS, A/AAAA, MX, CAA and the DNSSEC chain with previous measurements to identify delegation or operator changes.
If a change is unexpected, verify registrar and DNS-provider configuration before modifying anything. Document the failover mechanisms that actually exist.
Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.
{
"evidence": [
"ns11.infomaniak.ch",
"ns12.infomaniak.ch"
],
"severity": "low"
}
Rule 2026.09.4 · 2026-09-04T13:27:40+00:00
DNS shows how a domain resolves and which public services are associated with it.
Consistent, verifiable resolution reduces some spoofing risks and helps explain entity dependencies.
Compare NS, A/AAAA, MX, CAA and the DNSSEC chain with previous measurements to identify delegation or operator changes.
If a change is unexpected, verify registrar and DNS-provider configuration before modifying anything. Document the failover mechanisms that actually exist.
Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.
v=spf1 include:spf.infomaniak.ch -all
Rule 2026.09.4 · 2026-09-04T13:27:40+00:00
Public mail policies show how the domain frames sending, authentication and email transport.
These mechanisms can reduce domain spoofing and document mail-transport posture.
Relate SPF, DKIM when a selector is known, DMARC, MX, MTA-STS and TLS-RPT. Compare policy changes over time.
Before strengthening a policy, inventory legitimate mail flows and verify alignment. Roll out changes progressively to avoid blocking authorized senders.
Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.
{
"evidence": [
{
"host": "mta-gw.infomaniak.ch",
"priority": 5
}
],
"severity": "low"
}
Rule 2026.09.4 · 2026-09-04T13:27:40+00:00
HTTP headers can ask the browser to enforce specific protections.
They are visible, verifiable browser-side defensive layers.
Read each full policy, identify permissive or contradictory directives, and compare responses across the main public routes.
Harden policies progressively from actual application needs. Avoid copying generic templates without functional testing.
Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.
[
"nosniff"
]
Rule 2026.09.4 · 2026-09-04T13:27:40+00:00
Scanapse shows visible providers and third-party services on which the public service depends.
Concentration on one actor or many third parties can affect continuity and governance.
Identify each provider role, functions concentrated on the same actor, and dependencies that appeared or disappeared since the previous scan.
For a critical dependency, document owner, contract, reversibility, failover and rationale. Diversify only after analysing the actual need.
Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.
{
"name": "Apache",
"version": "",
"version_exposed": false
}
Rule 2026.09.4 · 2026-09-04T13:27:40+00:00
HTTP headers can ask the browser to enforce specific protections.
They are visible, verifiable browser-side defensive layers.
Read each full policy, identify permissive or contradictory directives, and compare responses across the main public routes.
Harden policies progressively from actual application needs. Avoid copying generic templates without functional testing.
Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.
[
"max-age=31536000; includeSubDomains; preload"
]
Rule 2026.09.4 · 2026-09-04T13:27:40+00:00
Scanapse shows visible providers and third-party services on which the public service depends.
Concentration on one actor or many third parties can affect continuity and governance.
Identify each provider role, functions concentrated on the same actor, and dependencies that appeared or disappeared since the previous scan.
For a critical dependency, document owner, contract, reversibility, failover and rationale. Diversify only after analysing the actual need.
Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.
{
"evidence": [
"ns11.infomaniak.ch",
"ns12.infomaniak.ch"
],
"severity": "medium"
}
Rule 2026.09.4 · 2026-09-04T13:27:40+00:00
Public mail policies show how the domain frames sending, authentication and email transport.
These mechanisms can reduce domain spoofing and document mail-transport posture.
Relate SPF, DKIM when a selector is known, DMARC, MX, MTA-STS and TLS-RPT. Compare policy changes over time.
Before strengthening a policy, inventory legitimate mail flows and verify alignment. Roll out changes progressively to avoid blocking authorized senders.
Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.
Rule 2026.09.4 · 2026-09-04T13:27:40+00:00
HTTP headers can ask the browser to enforce specific protections.
They are visible, verifiable browser-side defensive layers.
Read each full policy, identify permissive or contradictory directives, and compare responses across the main public routes.
Harden policies progressively from actual application needs. Avoid copying generic templates without functional testing.
Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.
{
"evidence": "default-src 'none'; script-src 'self' 'nonce-33sgrcmoexsdhks7x-d0p4a4'; script-src-attr 'none'; style-src 'self' 'nonce-33sgrcmoexsdhks7x-d0p4a4'; style-src-attr 'unsafe-inline'; img-src 'self' data: blob:; font-src 'self'; media-src 'self' blob:; worker-src 'self' blob:; connect-src 'self' blob: data:; manifest-src 'self'; form-action 'self'; frame-ancestors 'none'; base-uri 'none'; object-src 'none'; upgrade-insecure-requests",
"severity": "high"
}
Rule 2026.09.4 · 2026-09-04T13:27:40+00:00
{
"schema_version": "2.0",
"engine_version": "2.5.3",
"pattern_version": "2026.09.4",
"scope": {
"mode": "passive",
"coverage": "full",
"access_level": "full",
"access_reason": "public_document_available",
"requests": 2,
"homepage_only": true,
"javascript_executed": false,
"ports_scanned": false,
"private_networks_blocked": true,
"protection_bypassed": false,
"max_body_bytes": 1572864,
"scan_budget_seconds": 24,
"budget_exhausted": false,
"transport": "curl_with_socket_fallback"
},
"entity": {
"id": "5ddcac889405a2a37ffc12e8a5a6f8eec9ac2ac0760e0e4c27408f6fb3f8d3c8",
"display_name": "webpion.com",
"slug": "webpion-com",
"entity_type": "domain_subject",
"auto_created": true,
"primary_asset": "webpion.com"
},
"methodology": {
"version": "2.3.1",
"model": "evidence_first",
"principles": [
"absence_of_evidence_is_not_evidence_of_absence",
"unknown_remains_unknown",
"provider_metadata_is_not_data_location",
"edge_provider_is_not_origin_host",
"single_snapshot_does_not_prove_resilience"
]
},
"trajectory_summary": {
"has_previous_scan": true,
"change_counts": {
"modified": 2,
"stable": 33
},
"observation_count": 34,
"evidence_count": 34,
"provider_count": 1,
"strategic_signal_count": 1,
"top_signal_count": 1
}
}