OBSERVE · CONNECT · UNDERSTAND
FR EN
Read a domain

PUBLIC DOMAIN DOSSIER

afteralgorithm.com

What is observed, how to verify it and what changed

4 public observations are documented in this dossier.

1 structuring public dependencies are visible.

No useful change is retained since the previous reading.

2 points still require confirmation or cannot be observed from outside.

Measured 2026-09-04 19:30 UTC First observation 2026-09-04 19:30 UTC Latest observation 2026-09-04 19:30 UTC
History JSON Markdown

TIME

What changed over time

Initial reference point created today

0Appeared
0Modified
0Stable
0Disappeared

SHORT VIEW

Four readings before the detail

The 12 historical angles remain available below for deeper inspection.

Identity & governance

  • Not testedCanary detection
  • ObservedDepends on providerInfomaniak
  • Not observable from outsideOrigin host

Infrastructure & transport

  • Not testedPost quantum tls
  • ObservedTls issuerC = US, O = Let's Encrypt, CN = YR1

Mail & trust

  • ObservedDmarc policyreject
  • ObservedSpf policyhardfail

Dependencies & exposure

  • Not observable from outsideData location

Explanatory record

What Scanapse understands about this domain

Scanapse has enough material to describe 11 of 12 knowledge angles for afteralgorithm.com. 4 questions remain open with the available public evidence.

Measured on 2026-09-04 19:30 UTC Engine 2.6.0.1

Read the domain folder

The key points for reading this domain folder

Four key points to understand what Scanapse observed, what can reasonably be retained, and what still needs verification.

Key points

Worth looking at today

Only a few items are shown when they add something genuinely useful to the reading.

DEPENDENCIES

Critical function concentration

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

Which legal context can reasonably be retained

Scanapse distinguishes established, probable and to-confirm jurisdiction and always explains which clues support the reading.

To confirm To confirm

Why this context appears

  • No sufficiently reliable public jurisdiction clue was found in the report

What this does not establish

  • Technical hosting, IP addresses, ASNs and CDN locations do not establish the applicable legal jurisdiction by themselves.
  • The applicable jurisdiction requires additional public or organisational evidence.

Regulatory frameworks

Useful texts for this context

References are selected from the observed context. Their presence explains potential relevance, never automatic compliance.

To confirmTo determine

Regulatory context to determine

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

Useful changes since the previous reading

Only differences that help interpretation are highlighted. Stable or purely technical variations remain available in the evidence.

No significant change retained

The available comparison does not surface a change worth highlighting in the public reading.

12 knowledge angles

12 angles to understand the domain

Each angle explains what is known, why it matters, how to read it, its purpose and its limits.

01
Documented First observation

Domain identity

Public evidence provides enough material to document this angle

Angle 01

Domain identity

Documented First observation

Public evidence provides enough material to document this angle

01

Why it matters

This angle matters because it helps turn isolated public signals into information that can support a decision.

02

How to read it

Scanapse relates public observations, evidence and changes while keeping facts separate from interpretation.

03

What it is for

Provide a usable reading for technical teams, decision-makers and governance roles without exposing unnecessary internal mechanics.

04

What it does not prove

Public evidence is limited to the observed scope and does not prove internal, contractual or unobserved properties.

Material available for this angle

10evidence
0changes
0open questions
Show technical details for this angle

This level supports auditability and reproducibility. It is not required to understand the main reading.

Mapping version
2.3.1
Evidence
10
Signals
1
Changes
0
caa_record dns 541d75d5b02e7de019d72d2f913693bcfd6a1587229c7bb7ccd89f053e8cfe85 
{
    "flags": 0,
    "tag": "issue",
    "value": "letsencrypt.org"
}
dns_address dns 3b30e90b06caf31dab73d2b3e329bba9d27b0074f68077c362108bbffd145186 
"185.125.27.197"
dns_nameserver dns 1720fe80fb9a78c85bf0009ad6ba6772aa973c3e0bc2dd844628b6bdb5fda347 
"ns12.infomaniak.ch"
dns_nameserver dns cc94c091161aa920a04b04288e351259d399134c3a7fe58dd3fd8d599391b632 
"ns11.infomaniak.ch"
dns_address dns e2b65f7da40f35b82ce3d7899ef4090d052f5137b1af73247c794ddf3702fd98 
"2001:1600::aaaa:0:0:80:5b"
spf_record dns 8f77c8064e800e17fb04c675016bcd00c50e40a7bc225ebd5a7243f023f631a2 
"v=spf1 include:spf.infomaniak.ch -all"
mail_exchanger dns d9e30c69760dd42720b851e2be8e78b2f5dc8911c82241dfa4d6e44ca6c045f4 
"mta-gw.infomaniak.ch"
dmarc_record dns 8acfbe18d66e22e4fc276318dd2ab5cee384c0c1f941a9d4c3d2ddf70f36a1dc 
"v=DMARC1; p=reject;"
module_finding dns d18c99530c45c29858a6b448822b26d0b80a52fc4d491d07070d48cbc4c6324d 
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
module_finding dns 030d9119120c6ddfef7395ff3bad740c0de7148ef61664fd3ca57673cc082ff2 
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
02
Documented First observation

Infrastructure

Public evidence provides enough material to document this angle

Angle 02

Infrastructure

Documented First observation

Public evidence provides enough material to document this angle

01

Why it matters

This angle matters because it helps turn isolated public signals into information that can support a decision.

02

How to read it

Scanapse relates public observations, evidence and changes while keeping facts separate from interpretation.

03

What it is for

Provide a usable reading for technical teams, decision-makers and governance roles without exposing unnecessary internal mechanics.

04

What it does not prove

Public evidence is limited to the observed scope and does not prove internal, contractual or unobserved properties.

Material available for this angle

12evidence
0changes
2open questions
Show technical details for this angle

This level supports auditability and reproducibility. It is not required to understand the main reading.

Mapping version
2.3.1
Evidence
12
Signals
2
Changes
0

Unknowns and limitations

2 items still require qualification

caa_record dns 541d75d5b02e7de019d72d2f913693bcfd6a1587229c7bb7ccd89f053e8cfe85 
{
    "flags": 0,
    "tag": "issue",
    "value": "letsencrypt.org"
}
dns_address dns 3b30e90b06caf31dab73d2b3e329bba9d27b0074f68077c362108bbffd145186 
"185.125.27.197"
module_finding resilience b63e0a022b4d0508c24f43867acc1a6ea360dc887b819f9d8986d1493673e8c1 
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "medium"
}
dns_nameserver dns 1720fe80fb9a78c85bf0009ad6ba6772aa973c3e0bc2dd844628b6bdb5fda347 
"ns12.infomaniak.ch"
dns_nameserver dns cc94c091161aa920a04b04288e351259d399134c3a7fe58dd3fd8d599391b632 
"ns11.infomaniak.ch"
dns_address dns e2b65f7da40f35b82ce3d7899ef4090d052f5137b1af73247c794ddf3702fd98 
"2001:1600::aaaa:0:0:80:5b"
spf_record dns 8f77c8064e800e17fb04c675016bcd00c50e40a7bc225ebd5a7243f023f631a2 
"v=spf1 include:spf.infomaniak.ch -all"
dependency_provider dependencies 3023478d1ca921c5f27a0291c59e1fdc71b32fdc30bb01a7af57df33b52e0b92 
{
    "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
}
mail_exchanger dns d9e30c69760dd42720b851e2be8e78b2f5dc8911c82241dfa4d6e44ca6c045f4 
"mta-gw.infomaniak.ch"
dmarc_record dns 8acfbe18d66e22e4fc276318dd2ab5cee384c0c1f941a9d4c3d2ddf70f36a1dc 
"v=DMARC1; p=reject;"
module_finding dns d18c99530c45c29858a6b448822b26d0b80a52fc4d491d07070d48cbc4c6324d 
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
module_finding dns 030d9119120c6ddfef7395ff3bad740c0de7148ef61664fd3ca57673cc082ff2 
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
03
Partial First observation

Encryption and transport

This angle is only partially documented by public evidence

Angle 03

Encryption and transport

Partial First observation

This angle is only partially documented by public evidence

01

Why it matters

This angle matters because it helps turn isolated public signals into information that can support a decision.

02

How to read it

Scanapse relates public observations, evidence and changes while keeping facts separate from interpretation.

03

What it is for

Provide a usable reading for technical teams, decision-makers and governance roles without exposing unnecessary internal mechanics.

04

What it does not prove

Public evidence is limited to the observed scope and does not prove internal, contractual or unobserved properties.

Material available for this angle

12evidence
0changes
1open questions
Show technical details for this angle

This level supports auditability and reproducibility. It is not required to understand the main reading.

Mapping version
2.3.1
Evidence
12
Signals
0
Changes
0

Unknowns and limitations

1 items still require qualification

tls_valid_to tls 82803d52bf7912db3fd2a5b397d3e8d5ef89a2370987085f88cbeacf175a00ac 
"2026-11-17T22:16:27+00:00"
http_header headers 49c17c2da1c225878dfc3bbee05ff2fe9fbdc9717961d99d31744fb4c0bbfbf5 
[
    "accelerometer=(), ambient-light-sensor=(), autoplay=(), camera=(), display-capture=(), encrypted-media=(), fullscreen=(self), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), midi=(), payment=(), publickey-credentials-get=(), screen-wake-lock=(), serial=(), usb=(), web-share=(self)"
]
http_header headers e9b746e52c7fb54d8be62fcc262b729e049b73e16b5710b703879fb7f8676fd4 
[
    "max-age=63072000; includeSubDomains; preload"
]
http_header headers 845599b6784ca425db69fd3b404c6a731a63677567898aef0eab3397311429d4 
[
    "nosniff"
]
http_header headers b35c1ac20572c50d0520e3566b46e8f57253c27bdb59055bf973b7dba496d858 
[
    "default-src 'none'; base-uri 'none'; form-action 'self'; frame-ancestors 'none'; object-src 'none'; script-src 'self' 'nonce-8kJ2Bq1lWZg7JTM8V0Ndezms'; style-src 'self'; img-src 'self' data: blob:; media-src 'self' blob:; connect-src 'self'; manifest-src 'self'; font-src 'self'; worker-src 'none'; upgrade-insecure-requests"
]
http_header headers 551d68c1a620bc59ddec6f261e604d6fedafdee56859d62374edb05afa624d1f 
[
    "same-origin"
]
tls_issuer tls 04030180b90c2188619dbace877bdbcb034eed5d75be06bc136c22e331f7a063 
"C = US, O = Let's Encrypt, CN = YR1"
http_header headers 9ebbd1d7485f07f44bc1f2e24d3dd6f9a9233ccb121623423f12a7e849dec599 
[
    "Apache"
]
http_header headers b9c201e9a2ec4f1f84545d6db8cb5e74963185e5e3d81e6d876a9f46b9b69c35 
[
    "no-referrer"
]
http_header headers 9db1c022854fdf7595c6fc1910a69e8a2a384ef4c7aa182e19cbe72f11471ccb 
[
    "same-origin"
]
http_header headers 1cba87d09129cc8ca35ebc46bfbf4165e557b78e024a08cd3a2d105be9e467f1 
[
    "DENY"
]
http_header headers 38ed1994dae2d7220102fd7e755f991ec57a3c2440e0efab5d15db1c5713eeae 
[
    "require-corp"
]
04
Documented First observation

Mail and trust

Public evidence provides enough material to document this angle

Angle 04

Mail and trust

Documented First observation

Public evidence provides enough material to document this angle

01

Why it matters

This angle matters because it helps turn isolated public signals into information that can support a decision.

02

How to read it

Scanapse relates public observations, evidence and changes while keeping facts separate from interpretation.

03

What it is for

Provide a usable reading for technical teams, decision-makers and governance roles without exposing unnecessary internal mechanics.

04

What it does not prove

Public evidence is limited to the observed scope and does not prove internal, contractual or unobserved properties.

Material available for this angle

18evidence
0changes
0open questions
Show technical details for this angle

This level supports auditability and reproducibility. It is not required to understand the main reading.

Mapping version
2.3.1
Evidence
18
Signals
2
Changes
0
module_finding mail_trust cf78e6b247420b6d581f2616c4e413ac4ce200679ebfc4331da7fe93154e23fc 
{
    "evidence": null,
    "severity": "low"
}
caa_record dns 541d75d5b02e7de019d72d2f913693bcfd6a1587229c7bb7ccd89f053e8cfe85 
{
    "flags": 0,
    "tag": "issue",
    "value": "letsencrypt.org"
}
dmarc_policy mail_trust 600e1aaea40a4c32f755c206ece50381665434f8b1d236369be4f2275ec66398 
"reject"
mail_policy_flag mail_trust 2c1158fdd558baaa915b76f935552fa4cf5ca6d1861d82ccffba8ffecab65d1b 
false
dns_address dns 3b30e90b06caf31dab73d2b3e329bba9d27b0074f68077c362108bbffd145186 
"185.125.27.197"
dns_nameserver dns 1720fe80fb9a78c85bf0009ad6ba6772aa973c3e0bc2dd844628b6bdb5fda347 
"ns12.infomaniak.ch"
mail_policy_flag mail_trust 9898ab2c80b95c31179d86e95a3ae67ab35b70a55ca6dd14e7b84f617f0723cc 
false
dns_nameserver dns cc94c091161aa920a04b04288e351259d399134c3a7fe58dd3fd8d599391b632 
"ns11.infomaniak.ch"
dns_address dns e2b65f7da40f35b82ce3d7899ef4090d052f5137b1af73247c794ddf3702fd98 
"2001:1600::aaaa:0:0:80:5b"
spf_policy mail_trust 5812f39287a77ba54590821143740f386230879edeac1611d7b592ad0f99fdb2 
"hardfail"
module_finding mail_trust bd54312ffe886e0bbe4049fdd1528c1f19dddcb1557c9485c1e23567afed293f 
{
    "evidence": null,
    "severity": "low"
}
module_finding mail_trust da56a8ec6a6a32941bdeaf208a0d7a4b32d7c56d7340a62193202965bab7c12e 
{
    "evidence": [
        {
            "host": "mta-gw.infomaniak.ch",
            "priority": 5
        }
    ],
    "severity": "low"
}
spf_record dns 8f77c8064e800e17fb04c675016bcd00c50e40a7bc225ebd5a7243f023f631a2 
"v=spf1 include:spf.infomaniak.ch -all"
mail_exchanger dns d9e30c69760dd42720b851e2be8e78b2f5dc8911c82241dfa4d6e44ca6c045f4 
"mta-gw.infomaniak.ch"
dmarc_record dns 8acfbe18d66e22e4fc276318dd2ab5cee384c0c1f941a9d4c3d2ddf70f36a1dc 
"v=DMARC1; p=reject;"
module_finding dns d18c99530c45c29858a6b448822b26d0b80a52fc4d491d07070d48cbc4c6324d 
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
mail_policy_flag mail_trust 5cfbe3f22890e85dc6d2c40e2b7d7d9be576a127af77fcf1257be684501f34cf 
false
module_finding dns 030d9119120c6ddfef7395ff3bad740c0de7148ef61664fd3ca57673cc082ff2 
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
05
Documented First observation

DNS and governance

Public evidence provides enough material to document this angle

Angle 05

DNS and governance

Documented First observation

Public evidence provides enough material to document this angle

01

Why it matters

This angle matters because it helps turn isolated public signals into information that can support a decision.

02

How to read it

Scanapse relates public observations, evidence and changes while keeping facts separate from interpretation.

03

What it is for

Provide a usable reading for technical teams, decision-makers and governance roles without exposing unnecessary internal mechanics.

04

What it does not prove

Public evidence is limited to the observed scope and does not prove internal, contractual or unobserved properties.

Material available for this angle

18evidence
0changes
0open questions
Show technical details for this angle

This level supports auditability and reproducibility. It is not required to understand the main reading.

Mapping version
2.3.1
Evidence
18
Signals
2
Changes
0
module_finding mail_trust cf78e6b247420b6d581f2616c4e413ac4ce200679ebfc4331da7fe93154e23fc 
{
    "evidence": null,
    "severity": "low"
}
caa_record dns 541d75d5b02e7de019d72d2f913693bcfd6a1587229c7bb7ccd89f053e8cfe85 
{
    "flags": 0,
    "tag": "issue",
    "value": "letsencrypt.org"
}
dmarc_policy mail_trust 600e1aaea40a4c32f755c206ece50381665434f8b1d236369be4f2275ec66398 
"reject"
mail_policy_flag mail_trust 2c1158fdd558baaa915b76f935552fa4cf5ca6d1861d82ccffba8ffecab65d1b 
false
dns_address dns 3b30e90b06caf31dab73d2b3e329bba9d27b0074f68077c362108bbffd145186 
"185.125.27.197"
dns_nameserver dns 1720fe80fb9a78c85bf0009ad6ba6772aa973c3e0bc2dd844628b6bdb5fda347 
"ns12.infomaniak.ch"
mail_policy_flag mail_trust 9898ab2c80b95c31179d86e95a3ae67ab35b70a55ca6dd14e7b84f617f0723cc 
false
dns_nameserver dns cc94c091161aa920a04b04288e351259d399134c3a7fe58dd3fd8d599391b632 
"ns11.infomaniak.ch"
dns_address dns e2b65f7da40f35b82ce3d7899ef4090d052f5137b1af73247c794ddf3702fd98 
"2001:1600::aaaa:0:0:80:5b"
spf_policy mail_trust 5812f39287a77ba54590821143740f386230879edeac1611d7b592ad0f99fdb2 
"hardfail"
module_finding mail_trust bd54312ffe886e0bbe4049fdd1528c1f19dddcb1557c9485c1e23567afed293f 
{
    "evidence": null,
    "severity": "low"
}
module_finding mail_trust da56a8ec6a6a32941bdeaf208a0d7a4b32d7c56d7340a62193202965bab7c12e 
{
    "evidence": [
        {
            "host": "mta-gw.infomaniak.ch",
            "priority": 5
        }
    ],
    "severity": "low"
}
spf_record dns 8f77c8064e800e17fb04c675016bcd00c50e40a7bc225ebd5a7243f023f631a2 
"v=spf1 include:spf.infomaniak.ch -all"
mail_exchanger dns d9e30c69760dd42720b851e2be8e78b2f5dc8911c82241dfa4d6e44ca6c045f4 
"mta-gw.infomaniak.ch"
dmarc_record dns 8acfbe18d66e22e4fc276318dd2ab5cee384c0c1f941a9d4c3d2ddf70f36a1dc 
"v=DMARC1; p=reject;"
module_finding dns d18c99530c45c29858a6b448822b26d0b80a52fc4d491d07070d48cbc4c6324d 
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
mail_policy_flag mail_trust 5cfbe3f22890e85dc6d2c40e2b7d7d9be576a127af77fcf1257be684501f34cf 
false
module_finding dns 030d9119120c6ddfef7395ff3bad740c0de7148ef61664fd3ca57673cc082ff2 
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
06
Documented First observation

External dependencies

Public evidence provides enough material to document this angle

Angle 06

External dependencies

Documented First observation

Public evidence provides enough material to document this angle

01

Why it matters

This angle matters because it helps turn isolated public signals into information that can support a decision.

02

How to read it

Scanapse relates public observations, evidence and changes while keeping facts separate from interpretation.

03

What it is for

Provide a usable reading for technical teams, decision-makers and governance roles without exposing unnecessary internal mechanics.

04

What it does not prove

Public evidence is limited to the observed scope and does not prove internal, contractual or unobserved properties.

Material available for this angle

11evidence
0changes
0open questions
Show technical details for this angle

This level supports auditability and reproducibility. It is not required to understand the main reading.

Mapping version
2.3.1
Evidence
11
Signals
2
Changes
0
caa_record dns 541d75d5b02e7de019d72d2f913693bcfd6a1587229c7bb7ccd89f053e8cfe85 
{
    "flags": 0,
    "tag": "issue",
    "value": "letsencrypt.org"
}
dns_address dns 3b30e90b06caf31dab73d2b3e329bba9d27b0074f68077c362108bbffd145186 
"185.125.27.197"
dns_nameserver dns 1720fe80fb9a78c85bf0009ad6ba6772aa973c3e0bc2dd844628b6bdb5fda347 
"ns12.infomaniak.ch"
dns_nameserver dns cc94c091161aa920a04b04288e351259d399134c3a7fe58dd3fd8d599391b632 
"ns11.infomaniak.ch"
dns_address dns e2b65f7da40f35b82ce3d7899ef4090d052f5137b1af73247c794ddf3702fd98 
"2001:1600::aaaa:0:0:80:5b"
spf_record dns 8f77c8064e800e17fb04c675016bcd00c50e40a7bc225ebd5a7243f023f631a2 
"v=spf1 include:spf.infomaniak.ch -all"
dependency_provider dependencies 3023478d1ca921c5f27a0291c59e1fdc71b32fdc30bb01a7af57df33b52e0b92 
{
    "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
}
mail_exchanger dns d9e30c69760dd42720b851e2be8e78b2f5dc8911c82241dfa4d6e44ca6c045f4 
"mta-gw.infomaniak.ch"
dmarc_record dns 8acfbe18d66e22e4fc276318dd2ab5cee384c0c1f941a9d4c3d2ddf70f36a1dc 
"v=DMARC1; p=reject;"
module_finding dns d18c99530c45c29858a6b448822b26d0b80a52fc4d491d07070d48cbc4c6324d 
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
module_finding dns 030d9119120c6ddfef7395ff3bad740c0de7148ef61664fd3ca57673cc082ff2 
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
07
Documented First observation

Observable technologies

Public evidence provides enough material to document this angle

Angle 07

Observable technologies

Documented First observation

Public evidence provides enough material to document this angle

01

Why it matters

This angle matters because it helps turn isolated public signals into information that can support a decision.

02

How to read it

Scanapse relates public observations, evidence and changes while keeping facts separate from interpretation.

03

What it is for

Provide a usable reading for technical teams, decision-makers and governance roles without exposing unnecessary internal mechanics.

04

What it does not prove

Public evidence is limited to the observed scope and does not prove internal, contractual or unobserved properties.

Material available for this angle

11evidence
0changes
0open questions
Show technical details for this angle

This level supports auditability and reproducibility. It is not required to understand the main reading.

Mapping version
2.3.1
Evidence
11
Signals
0
Changes
0
http_header headers 49c17c2da1c225878dfc3bbee05ff2fe9fbdc9717961d99d31744fb4c0bbfbf5 
[
    "accelerometer=(), ambient-light-sensor=(), autoplay=(), camera=(), display-capture=(), encrypted-media=(), fullscreen=(self), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), midi=(), payment=(), publickey-credentials-get=(), screen-wake-lock=(), serial=(), usb=(), web-share=(self)"
]
http_header headers e9b746e52c7fb54d8be62fcc262b729e049b73e16b5710b703879fb7f8676fd4 
[
    "max-age=63072000; includeSubDomains; preload"
]
http_header headers 845599b6784ca425db69fd3b404c6a731a63677567898aef0eab3397311429d4 
[
    "nosniff"
]
http_header headers b35c1ac20572c50d0520e3566b46e8f57253c27bdb59055bf973b7dba496d858 
[
    "default-src 'none'; base-uri 'none'; form-action 'self'; frame-ancestors 'none'; object-src 'none'; script-src 'self' 'nonce-8kJ2Bq1lWZg7JTM8V0Ndezms'; style-src 'self'; img-src 'self' data: blob:; media-src 'self' blob:; connect-src 'self'; manifest-src 'self'; font-src 'self'; worker-src 'none'; upgrade-insecure-requests"
]
http_header headers 551d68c1a620bc59ddec6f261e604d6fedafdee56859d62374edb05afa624d1f 
[
    "same-origin"
]
technology technology c463931fc66f5f22a684c2293be4903e2c9cb271478df0fd8a82cd90986aa08f 
{
    "name": "Apache",
    "version": "",
    "version_exposed": false
}
http_header headers 9ebbd1d7485f07f44bc1f2e24d3dd6f9a9233ccb121623423f12a7e849dec599 
[
    "Apache"
]
http_header headers b9c201e9a2ec4f1f84545d6db8cb5e74963185e5e3d81e6d876a9f46b9b69c35 
[
    "no-referrer"
]
http_header headers 9db1c022854fdf7595c6fc1910a69e8a2a384ef4c7aa182e19cbe72f11471ccb 
[
    "same-origin"
]
http_header headers 1cba87d09129cc8ca35ebc46bfbf4165e557b78e024a08cd3a2d105be9e467f1 
[
    "DENY"
]
http_header headers 38ed1994dae2d7220102fd7e755f991ec57a3c2440e0efab5d15db1c5713eeae 
[
    "require-corp"
]
08
Partial First observation

Public exposure

This angle is only partially documented by public evidence

Angle 08

Public exposure

Partial First observation

This angle is only partially documented by public evidence

01

Why it matters

This angle matters because it helps turn isolated public signals into information that can support a decision.

02

How to read it

Scanapse relates public observations, evidence and changes while keeping facts separate from interpretation.

03

What it is for

Provide a usable reading for technical teams, decision-makers and governance roles without exposing unnecessary internal mechanics.

04

What it does not prove

Public evidence is limited to the observed scope and does not prove internal, contractual or unobserved properties.

Material available for this angle

16evidence
0changes
1open questions
Show technical details for this angle

This level supports auditability and reproducibility. It is not required to understand the main reading.

Mapping version
2.3.1
Evidence
16
Signals
0
Changes
0

Unknowns and limitations

1 items still require qualification

module_finding mail_trust cf78e6b247420b6d581f2616c4e413ac4ce200679ebfc4331da7fe93154e23fc 
{
    "evidence": null,
    "severity": "low"
}
http_header headers 49c17c2da1c225878dfc3bbee05ff2fe9fbdc9717961d99d31744fb4c0bbfbf5 
[
    "accelerometer=(), ambient-light-sensor=(), autoplay=(), camera=(), display-capture=(), encrypted-media=(), fullscreen=(self), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), midi=(), payment=(), publickey-credentials-get=(), screen-wake-lock=(), serial=(), usb=(), web-share=(self)"
]
http_header headers e9b746e52c7fb54d8be62fcc262b729e049b73e16b5710b703879fb7f8676fd4 
[
    "max-age=63072000; includeSubDomains; preload"
]
module_finding resilience b63e0a022b4d0508c24f43867acc1a6ea360dc887b819f9d8986d1493673e8c1 
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "medium"
}
http_header headers 845599b6784ca425db69fd3b404c6a731a63677567898aef0eab3397311429d4 
[
    "nosniff"
]
http_header headers b35c1ac20572c50d0520e3566b46e8f57253c27bdb59055bf973b7dba496d858 
[
    "default-src 'none'; base-uri 'none'; form-action 'self'; frame-ancestors 'none'; object-src 'none'; script-src 'self' 'nonce-8kJ2Bq1lWZg7JTM8V0Ndezms'; style-src 'self'; img-src 'self' data: blob:; media-src 'self' blob:; connect-src 'self'; manifest-src 'self'; font-src 'self'; worker-src 'none'; upgrade-insecure-requests"
]
module_finding mail_trust bd54312ffe886e0bbe4049fdd1528c1f19dddcb1557c9485c1e23567afed293f 
{
    "evidence": null,
    "severity": "low"
}
module_finding mail_trust da56a8ec6a6a32941bdeaf208a0d7a4b32d7c56d7340a62193202965bab7c12e 
{
    "evidence": [
        {
            "host": "mta-gw.infomaniak.ch",
            "priority": 5
        }
    ],
    "severity": "low"
}
http_header headers 551d68c1a620bc59ddec6f261e604d6fedafdee56859d62374edb05afa624d1f 
[
    "same-origin"
]
http_header headers 9ebbd1d7485f07f44bc1f2e24d3dd6f9a9233ccb121623423f12a7e849dec599 
[
    "Apache"
]
module_finding dns d18c99530c45c29858a6b448822b26d0b80a52fc4d491d07070d48cbc4c6324d 
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
http_header headers b9c201e9a2ec4f1f84545d6db8cb5e74963185e5e3d81e6d876a9f46b9b69c35 
[
    "no-referrer"
]
http_header headers 9db1c022854fdf7595c6fc1910a69e8a2a384ef4c7aa182e19cbe72f11471ccb 
[
    "same-origin"
]
http_header headers 1cba87d09129cc8ca35ebc46bfbf4165e557b78e024a08cd3a2d105be9e467f1 
[
    "DENY"
]
http_header headers 38ed1994dae2d7220102fd7e755f991ec57a3c2440e0efab5d15db1c5713eeae 
[
    "require-corp"
]
module_finding dns 030d9119120c6ddfef7395ff3bad740c0de7148ef61664fd3ca57673cc082ff2 
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
09
Documented First observation

Documentary trust

Public evidence provides enough material to document this angle

Angle 09

Documentary trust

Documented First observation

Public evidence provides enough material to document this angle

01

Why it matters

This angle matters because it helps turn isolated public signals into information that can support a decision.

02

How to read it

Scanapse relates public observations, evidence and changes while keeping facts separate from interpretation.

03

What it is for

Provide a usable reading for technical teams, decision-makers and governance roles without exposing unnecessary internal mechanics.

04

What it does not prove

Public evidence is limited to the observed scope and does not prove internal, contractual or unobserved properties.

Material available for this angle

16evidence
0changes
0open questions
Show technical details for this angle

This level supports auditability and reproducibility. It is not required to understand the main reading.

Mapping version
2.3.1
Evidence
16
Signals
0
Changes
0
module_finding mail_trust cf78e6b247420b6d581f2616c4e413ac4ce200679ebfc4331da7fe93154e23fc 
{
    "evidence": null,
    "severity": "low"
}
http_header headers 49c17c2da1c225878dfc3bbee05ff2fe9fbdc9717961d99d31744fb4c0bbfbf5 
[
    "accelerometer=(), ambient-light-sensor=(), autoplay=(), camera=(), display-capture=(), encrypted-media=(), fullscreen=(self), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), midi=(), payment=(), publickey-credentials-get=(), screen-wake-lock=(), serial=(), usb=(), web-share=(self)"
]
http_header headers e9b746e52c7fb54d8be62fcc262b729e049b73e16b5710b703879fb7f8676fd4 
[
    "max-age=63072000; includeSubDomains; preload"
]
module_finding resilience b63e0a022b4d0508c24f43867acc1a6ea360dc887b819f9d8986d1493673e8c1 
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "medium"
}
http_header headers 845599b6784ca425db69fd3b404c6a731a63677567898aef0eab3397311429d4 
[
    "nosniff"
]
http_header headers b35c1ac20572c50d0520e3566b46e8f57253c27bdb59055bf973b7dba496d858 
[
    "default-src 'none'; base-uri 'none'; form-action 'self'; frame-ancestors 'none'; object-src 'none'; script-src 'self' 'nonce-8kJ2Bq1lWZg7JTM8V0Ndezms'; style-src 'self'; img-src 'self' data: blob:; media-src 'self' blob:; connect-src 'self'; manifest-src 'self'; font-src 'self'; worker-src 'none'; upgrade-insecure-requests"
]
module_finding mail_trust bd54312ffe886e0bbe4049fdd1528c1f19dddcb1557c9485c1e23567afed293f 
{
    "evidence": null,
    "severity": "low"
}
module_finding mail_trust da56a8ec6a6a32941bdeaf208a0d7a4b32d7c56d7340a62193202965bab7c12e 
{
    "evidence": [
        {
            "host": "mta-gw.infomaniak.ch",
            "priority": 5
        }
    ],
    "severity": "low"
}
http_header headers 551d68c1a620bc59ddec6f261e604d6fedafdee56859d62374edb05afa624d1f 
[
    "same-origin"
]
http_header headers 9ebbd1d7485f07f44bc1f2e24d3dd6f9a9233ccb121623423f12a7e849dec599 
[
    "Apache"
]
module_finding dns d18c99530c45c29858a6b448822b26d0b80a52fc4d491d07070d48cbc4c6324d 
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
http_header headers b9c201e9a2ec4f1f84545d6db8cb5e74963185e5e3d81e6d876a9f46b9b69c35 
[
    "no-referrer"
]
http_header headers 9db1c022854fdf7595c6fc1910a69e8a2a384ef4c7aa182e19cbe72f11471ccb 
[
    "same-origin"
]
http_header headers 1cba87d09129cc8ca35ebc46bfbf4165e557b78e024a08cd3a2d105be9e467f1 
[
    "DENY"
]
http_header headers 38ed1994dae2d7220102fd7e755f991ec57a3c2440e0efab5d15db1c5713eeae 
[
    "require-corp"
]
module_finding dns 030d9119120c6ddfef7395ff3bad740c0de7148ef61664fd3ca57673cc082ff2 
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
10
Documented First observation

Security signals

Public evidence provides enough material to document this angle

Angle 10

Security signals

Documented First observation

Public evidence provides enough material to document this angle

01

Why it matters

This angle matters because it helps turn isolated public signals into information that can support a decision.

02

How to read it

Scanapse relates public observations, evidence and changes while keeping facts separate from interpretation.

03

What it is for

Provide a usable reading for technical teams, decision-makers and governance roles without exposing unnecessary internal mechanics.

04

What it does not prove

Public evidence is limited to the observed scope and does not prove internal, contractual or unobserved properties.

Material available for this angle

31evidence
0changes
2open questions
Show technical details for this angle

This level supports auditability and reproducibility. It is not required to understand the main reading.

Mapping version
2.3.1
Evidence
31
Signals
2
Changes
0

Unknowns and limitations

2 items still require qualification

module_finding mail_trust cf78e6b247420b6d581f2616c4e413ac4ce200679ebfc4331da7fe93154e23fc 
{
    "evidence": null,
    "severity": "low"
}
caa_record dns 541d75d5b02e7de019d72d2f913693bcfd6a1587229c7bb7ccd89f053e8cfe85 
{
    "flags": 0,
    "tag": "issue",
    "value": "letsencrypt.org"
}
tls_valid_to tls 82803d52bf7912db3fd2a5b397d3e8d5ef89a2370987085f88cbeacf175a00ac 
"2026-11-17T22:16:27+00:00"
dmarc_policy mail_trust 600e1aaea40a4c32f755c206ece50381665434f8b1d236369be4f2275ec66398 
"reject"
mail_policy_flag mail_trust 2c1158fdd558baaa915b76f935552fa4cf5ca6d1861d82ccffba8ffecab65d1b 
false
http_header headers 49c17c2da1c225878dfc3bbee05ff2fe9fbdc9717961d99d31744fb4c0bbfbf5 
[
    "accelerometer=(), ambient-light-sensor=(), autoplay=(), camera=(), display-capture=(), encrypted-media=(), fullscreen=(self), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), midi=(), payment=(), publickey-credentials-get=(), screen-wake-lock=(), serial=(), usb=(), web-share=(self)"
]
dns_address dns 3b30e90b06caf31dab73d2b3e329bba9d27b0074f68077c362108bbffd145186 
"185.125.27.197"
http_header headers e9b746e52c7fb54d8be62fcc262b729e049b73e16b5710b703879fb7f8676fd4 
[
    "max-age=63072000; includeSubDomains; preload"
]
module_finding resilience b63e0a022b4d0508c24f43867acc1a6ea360dc887b819f9d8986d1493673e8c1 
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "medium"
}
http_header headers 845599b6784ca425db69fd3b404c6a731a63677567898aef0eab3397311429d4 
[
    "nosniff"
]
dns_nameserver dns 1720fe80fb9a78c85bf0009ad6ba6772aa973c3e0bc2dd844628b6bdb5fda347 
"ns12.infomaniak.ch"
mail_policy_flag mail_trust 9898ab2c80b95c31179d86e95a3ae67ab35b70a55ca6dd14e7b84f617f0723cc 
false
http_header headers b35c1ac20572c50d0520e3566b46e8f57253c27bdb59055bf973b7dba496d858 
[
    "default-src 'none'; base-uri 'none'; form-action 'self'; frame-ancestors 'none'; object-src 'none'; script-src 'self' 'nonce-8kJ2Bq1lWZg7JTM8V0Ndezms'; style-src 'self'; img-src 'self' data: blob:; media-src 'self' blob:; connect-src 'self'; manifest-src 'self'; font-src 'self'; worker-src 'none'; upgrade-insecure-requests"
]
dns_nameserver dns cc94c091161aa920a04b04288e351259d399134c3a7fe58dd3fd8d599391b632 
"ns11.infomaniak.ch"
dns_address dns e2b65f7da40f35b82ce3d7899ef4090d052f5137b1af73247c794ddf3702fd98 
"2001:1600::aaaa:0:0:80:5b"
spf_policy mail_trust 5812f39287a77ba54590821143740f386230879edeac1611d7b592ad0f99fdb2 
"hardfail"
module_finding mail_trust bd54312ffe886e0bbe4049fdd1528c1f19dddcb1557c9485c1e23567afed293f 
{
    "evidence": null,
    "severity": "low"
}
module_finding mail_trust da56a8ec6a6a32941bdeaf208a0d7a4b32d7c56d7340a62193202965bab7c12e 
{
    "evidence": [
        {
            "host": "mta-gw.infomaniak.ch",
            "priority": 5
        }
    ],
    "severity": "low"
}
spf_record dns 8f77c8064e800e17fb04c675016bcd00c50e40a7bc225ebd5a7243f023f631a2 
"v=spf1 include:spf.infomaniak.ch -all"
mail_exchanger dns d9e30c69760dd42720b851e2be8e78b2f5dc8911c82241dfa4d6e44ca6c045f4 
"mta-gw.infomaniak.ch"
http_header headers 551d68c1a620bc59ddec6f261e604d6fedafdee56859d62374edb05afa624d1f 
[
    "same-origin"
]
tls_issuer tls 04030180b90c2188619dbace877bdbcb034eed5d75be06bc136c22e331f7a063 
"C = US, O = Let's Encrypt, CN = YR1"
dmarc_record dns 8acfbe18d66e22e4fc276318dd2ab5cee384c0c1f941a9d4c3d2ddf70f36a1dc 
"v=DMARC1; p=reject;"
http_header headers 9ebbd1d7485f07f44bc1f2e24d3dd6f9a9233ccb121623423f12a7e849dec599 
[
    "Apache"
]
11
To determine First observation

Evolution over time

This angle still needs additional public evidence

Angle 11

Evolution over time

To determine First observation

This angle still needs additional public evidence

01

Why it matters

This angle matters because it helps turn isolated public signals into information that can support a decision.

02

How to read it

Scanapse relates public observations, evidence and changes while keeping facts separate from interpretation.

03

What it is for

Provide a usable reading for technical teams, decision-makers and governance roles without exposing unnecessary internal mechanics.

04

What it does not prove

Public evidence is limited to the observed scope and does not prove internal, contractual or unobserved properties.

Material available for this angle

0evidence
0changes
0open questions
Show technical details for this angle

This level supports auditability and reproducibility. It is not required to understand the main reading.

Mapping version
2.3.1
Evidence
0
Signals
0
Changes
0
12
Documented First observation

Evidence and traceability

Public evidence provides enough material to document this angle

Angle 12

Evidence and traceability

Documented First observation

Public evidence provides enough material to document this angle

01

Why it matters

This angle matters because it helps turn isolated public signals into information that can support a decision.

02

How to read it

Scanapse relates public observations, evidence and changes while keeping facts separate from interpretation.

03

What it is for

Provide a usable reading for technical teams, decision-makers and governance roles without exposing unnecessary internal mechanics.

04

What it does not prove

Public evidence is limited to the observed scope and does not prove internal, contractual or unobserved properties.

Material available for this angle

33evidence
0changes
0open questions
Show technical details for this angle

This level supports auditability and reproducibility. It is not required to understand the main reading.

Mapping version
2.3.1
Evidence
33
Signals
3
Changes
0
module_finding mail_trust cf78e6b247420b6d581f2616c4e413ac4ce200679ebfc4331da7fe93154e23fc 
{
    "evidence": null,
    "severity": "low"
}
caa_record dns 541d75d5b02e7de019d72d2f913693bcfd6a1587229c7bb7ccd89f053e8cfe85 
{
    "flags": 0,
    "tag": "issue",
    "value": "letsencrypt.org"
}
tls_valid_to tls 82803d52bf7912db3fd2a5b397d3e8d5ef89a2370987085f88cbeacf175a00ac 
"2026-11-17T22:16:27+00:00"
dmarc_policy mail_trust 600e1aaea40a4c32f755c206ece50381665434f8b1d236369be4f2275ec66398 
"reject"
mail_policy_flag mail_trust 2c1158fdd558baaa915b76f935552fa4cf5ca6d1861d82ccffba8ffecab65d1b 
false
http_header headers 49c17c2da1c225878dfc3bbee05ff2fe9fbdc9717961d99d31744fb4c0bbfbf5 
[
    "accelerometer=(), ambient-light-sensor=(), autoplay=(), camera=(), display-capture=(), encrypted-media=(), fullscreen=(self), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), midi=(), payment=(), publickey-credentials-get=(), screen-wake-lock=(), serial=(), usb=(), web-share=(self)"
]
dns_address dns 3b30e90b06caf31dab73d2b3e329bba9d27b0074f68077c362108bbffd145186 
"185.125.27.197"
http_header headers e9b746e52c7fb54d8be62fcc262b729e049b73e16b5710b703879fb7f8676fd4 
[
    "max-age=63072000; includeSubDomains; preload"
]
module_finding resilience b63e0a022b4d0508c24f43867acc1a6ea360dc887b819f9d8986d1493673e8c1 
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "medium"
}
http_header headers 845599b6784ca425db69fd3b404c6a731a63677567898aef0eab3397311429d4 
[
    "nosniff"
]
dns_nameserver dns 1720fe80fb9a78c85bf0009ad6ba6772aa973c3e0bc2dd844628b6bdb5fda347 
"ns12.infomaniak.ch"
mail_policy_flag mail_trust 9898ab2c80b95c31179d86e95a3ae67ab35b70a55ca6dd14e7b84f617f0723cc 
false
http_header headers b35c1ac20572c50d0520e3566b46e8f57253c27bdb59055bf973b7dba496d858 
[
    "default-src 'none'; base-uri 'none'; form-action 'self'; frame-ancestors 'none'; object-src 'none'; script-src 'self' 'nonce-8kJ2Bq1lWZg7JTM8V0Ndezms'; style-src 'self'; img-src 'self' data: blob:; media-src 'self' blob:; connect-src 'self'; manifest-src 'self'; font-src 'self'; worker-src 'none'; upgrade-insecure-requests"
]
dns_nameserver dns cc94c091161aa920a04b04288e351259d399134c3a7fe58dd3fd8d599391b632 
"ns11.infomaniak.ch"
dns_address dns e2b65f7da40f35b82ce3d7899ef4090d052f5137b1af73247c794ddf3702fd98 
"2001:1600::aaaa:0:0:80:5b"
spf_policy mail_trust 5812f39287a77ba54590821143740f386230879edeac1611d7b592ad0f99fdb2 
"hardfail"
module_finding mail_trust bd54312ffe886e0bbe4049fdd1528c1f19dddcb1557c9485c1e23567afed293f 
{
    "evidence": null,
    "severity": "low"
}
module_finding mail_trust da56a8ec6a6a32941bdeaf208a0d7a4b32d7c56d7340a62193202965bab7c12e 
{
    "evidence": [
        {
            "host": "mta-gw.infomaniak.ch",
            "priority": 5
        }
    ],
    "severity": "low"
}
spf_record dns 8f77c8064e800e17fb04c675016bcd00c50e40a7bc225ebd5a7243f023f631a2 
"v=spf1 include:spf.infomaniak.ch -all"
dependency_provider dependencies 3023478d1ca921c5f27a0291c59e1fdc71b32fdc30bb01a7af57df33b52e0b92 
{
    "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
}
mail_exchanger dns d9e30c69760dd42720b851e2be8e78b2f5dc8911c82241dfa4d6e44ca6c045f4 
"mta-gw.infomaniak.ch"
http_header headers 551d68c1a620bc59ddec6f261e604d6fedafdee56859d62374edb05afa624d1f 
[
    "same-origin"
]
technology technology c463931fc66f5f22a684c2293be4903e2c9cb271478df0fd8a82cd90986aa08f 
{
    "name": "Apache",
    "version": "",
    "version_exposed": false
}
tls_issuer tls 04030180b90c2188619dbace877bdbcb034eed5d75be06bc136c22e331f7a063 
"C = US, O = Let's Encrypt, CN = YR1"

Overview

What the domain already shows, and what still needs clarification

An overview of visible relationships and uncertainty areas that still need verification.

Visible relations

Visible relations around the domain

Relations are grouped by function. They describe what is publicly visible, not contracts or the full internal architecture.

Observed domain afteralgorithm.com

DNS

2
DNS server Observed

ns11.infomaniak.ch

DNS server Observed

ns12.infomaniak.ch

mail

1
Mail server Observed

mta-gw.infomaniak.ch

technology

1
Observed technology Observed

Apache

external resources

1
External provider or resource Corroborated

Infomaniak

Open questions

4 areas to confirm

An unknown becomes useful information when it precisely explains what is missing to reach a conclusion.

To confirm

Origin hosting

An edge service does not reveal the origin hosting provider.

To confirm

Effective data location

Public provider metadata does not prove where data is actually processed.

To confirm

Post-quantum TLS exchange

This check was not run with a compatible client during this measurement.

To confirm

Public canary signal

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

Evidence supporting this reading

33 evidence items are available. They remain collapsed to preserve a short reading and can be explored on demand.

33evidence items available

Each proof keeps its method, provenance, date, reliability and interpretation limits.

Download evidence JSON
Explore evidence
#01 Mail-related public records

Evidence: module_finding

Public mail policies show how the domain frames sending, authentication and email transport.

Active non-intrusive High
Why it matters

These mechanisms can reduce domain spoofing and document mail-transport posture.

What to check next

Relate SPF, DKIM when a selector is known, DMARC, MX, MTA-STS and TLS-RPT. Compare policy changes over time.

Possible action

Before strengthening a policy, inventory legitimate mail flows and verify alignment. Roll out changes progressively to avoid blocking authorized senders.

Observation
{ "evidence": null, "severity": "low" }
Understand
Public DNS and policy endpoint inspection
Source
Mail-related public records
Reliability
High
What this supports
Describe published mail authentication and transport policies
What this does not prove
They do not prove actual deliverability, every recipient’s behavior, or the absence of phishing.

Standards and reference context

Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.

View raw data 
{
    "evidence": null,
    "severity": "low"
}

Rule 2026.09.4 · 2026-09-04T19:30:18+00:00

#02 DNS public records

Evidence: caa_record

DNS shows how a domain resolves and which public services are associated with it.

Passive High
Why it matters

Consistent, verifiable resolution reduces some spoofing risks and helps explain entity dependencies.

What to check next

Compare NS, A/AAAA, MX, CAA and the DNSSEC chain with previous measurements to identify delegation or operator changes.

Possible action

If a change is unexpected, verify registrar and DNS-provider configuration before modifying anything. Document the failover mechanisms that actually exist.

Observation
{ "flags": 0, "tag": "issue", "value": "letsencrypt.org" }
Understand
Standard DNS resolution and record parsing
Source
DNS public records
Reliability
High
What this supports
Describe public DNS data observed at scan time
What this does not prove
Public DNS does not prove physical server location, contracts, or global availability.

Standards and reference context

Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.

View raw data 
{
    "flags": 0,
    "tag": "issue",
    "value": "letsencrypt.org"
}

Rule 2026.09.4 · 2026-09-04T19:30:18+00:00

#03 Public TLS endpoint

Evidence: tls_valid_to

TLS protects the observed connection between the scanner and the public service.

Active non-intrusive High
Why it matters

These elements document public-channel protection and the cryptographic mechanisms actually negotiated.

What to check next

Compare negotiated protocol, issuer, expiry, chain and cryptographic parameters with history. Check other public entry points separately.

Possible action

Address only observed gaps such as an expiring certificate, invalid chain, or unwanted protocol. Test changes in a controlled environment before deployment.

Observation
2026-11-17T22:16:27+00:00
Understand
TLS handshake and public certificate inspection
Source
Public TLS endpoint
Reliability
High
What this supports
Describe the TLS session and certificate presented to Scanapse
What this does not prove
Strong TLS does not prove application security or origin-server security behind a CDN or reverse proxy.

Standards and reference context

Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.

View raw data 
2026-11-17T22:16:27+00:00

Rule 2026.09.4 · 2026-09-04T19:30:18+00:00

#04 Mail-related public records

Evidence: dmarc_policy

Public mail policies show how the domain frames sending, authentication and email transport.

Active non-intrusive High
Why it matters

These mechanisms can reduce domain spoofing and document mail-transport posture.

What to check next

Relate SPF, DKIM when a selector is known, DMARC, MX, MTA-STS and TLS-RPT. Compare policy changes over time.

Possible action

Before strengthening a policy, inventory legitimate mail flows and verify alignment. Roll out changes progressively to avoid blocking authorized senders.

Observation
reject
Understand
Public DNS and policy endpoint inspection
Source
Mail-related public records
Reliability
High
What this supports
Describe published mail authentication and transport policies
What this does not prove
They do not prove actual deliverability, every recipient’s behavior, or the absence of phishing.

Standards and reference context

Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.

Verify it yourself

This command reproduces the public observation without changing the target.

dig TXT _dmarc.afteralgorithm.com
View raw data 
reject

Rule 2026.09.4 · 2026-09-04T19:30:18+00:00

#05 Mail-related public records

Evidence: mail_policy_flag

Public mail policies show how the domain frames sending, authentication and email transport.

Active non-intrusive High
Why it matters

These mechanisms can reduce domain spoofing and document mail-transport posture.

What to check next

Relate SPF, DKIM when a selector is known, DMARC, MX, MTA-STS and TLS-RPT. Compare policy changes over time.

Possible action

Before strengthening a policy, inventory legitimate mail flows and verify alignment. Roll out changes progressively to avoid blocking authorized senders.

Observation
Understand
Public DNS and policy endpoint inspection
Source
Mail-related public records
Reliability
High
What this supports
Describe published mail authentication and transport policies
What this does not prove
They do not prove actual deliverability, every recipient’s behavior, or the absence of phishing.

Standards and reference context

Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.

View raw data

Rule 2026.09.4 · 2026-09-04T19:30:18+00:00

#06 Public HTTP response

Evidence: http_header

HTTP headers can ask the browser to enforce specific protections.

Active non-intrusive High
Why it matters

They are visible, verifiable browser-side defensive layers.

What to check next

Read each full policy, identify permissive or contradictory directives, and compare responses across the main public routes.

Possible action

Harden policies progressively from actual application needs. Avoid copying generic templates without functional testing.

Observation
[ "accelerometer=(), ambient-light-sensor=(), autoplay=(), camera=(), display-capture=(), encrypted-media=(), fullscreen=(self), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), midi=(), payment=(), publickey-credentials-get=(), screen-wake-lock=(), serial=(), usb=(), web-share=(self)" ]
Understand
HTTP response-header inspection
Source
Public HTTP response
Reliability
High
What this supports
Describe defensive policies declared on the observed response
What this does not prove
A header being present does not prove it is optimal or that the application has no vulnerabilities.

Standards and reference context

Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.

View raw data 
[
    "accelerometer=(), ambient-light-sensor=(), autoplay=(), camera=(), display-capture=(), encrypted-media=(), fullscreen=(self), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), midi=(), payment=(), publickey-credentials-get=(), screen-wake-lock=(), serial=(), usb=(), web-share=(self)"
]

Rule 2026.09.4 · 2026-09-04T19:30:18+00:00

#07 DNS public records

Evidence: dns_address

DNS shows how a domain resolves and which public services are associated with it.

Passive High
Why it matters

Consistent, verifiable resolution reduces some spoofing risks and helps explain entity dependencies.

What to check next

Compare NS, A/AAAA, MX, CAA and the DNSSEC chain with previous measurements to identify delegation or operator changes.

Possible action

If a change is unexpected, verify registrar and DNS-provider configuration before modifying anything. Document the failover mechanisms that actually exist.

Observation
185.125.27.197
Understand
Standard DNS resolution and record parsing
Source
DNS public records
Reliability
High
What this supports
Describe public DNS data observed at scan time
What this does not prove
Public DNS does not prove physical server location, contracts, or global availability.

Standards and reference context

Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.

Verify it yourself

This command reproduces the public observation without changing the target.

dig A afteralgorithm.com && dig AAAA afteralgorithm.com
View raw data 
185.125.27.197

Rule 2026.09.4 · 2026-09-04T19:30:18+00:00

#08 Public HTTP response

Evidence: http_header

HTTP headers can ask the browser to enforce specific protections.

Active non-intrusive High
Why it matters

They are visible, verifiable browser-side defensive layers.

What to check next

Read each full policy, identify permissive or contradictory directives, and compare responses across the main public routes.

Possible action

Harden policies progressively from actual application needs. Avoid copying generic templates without functional testing.

Observation
[ "max-age=63072000; includeSubDomains; preload" ]
Understand
HTTP response-header inspection
Source
Public HTTP response
Reliability
High
What this supports
Describe defensive policies declared on the observed response
What this does not prove
A header being present does not prove it is optimal or that the application has no vulnerabilities.

Standards and reference context

Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.

View raw data 
[
    "max-age=63072000; includeSubDomains; preload"
]

Rule 2026.09.4 · 2026-09-04T19:30:18+00:00

#09 module_finding

Evidence: module_finding

Scanapse shows visible providers and third-party services on which the public service depends.

Passive Medium
Why it matters

Concentration on one actor or many third parties can affect continuity and governance.

What to check next

Identify each provider role, functions concentrated on the same actor, and dependencies that appeared or disappeared since the previous scan.

Possible action

For a critical dependency, document owner, contract, reversibility, failover and rationale. Diversify only after analysing the actual need.

Observation
{ "evidence": [ "ns11.infomaniak.ch", "ns12.infomaniak.ch" ], "severity": "medium" }
Understand
Public observation
Source
module_finding
Reliability
Medium
What this supports
Describe the observed public artefact
What this does not prove
A visible dependency does not prove data location, actual contractual jurisdiction, or hidden subcontractors.

Standards and reference context

Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.

View raw data 
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "medium"
}

Rule 2026.09.4 · 2026-09-04T19:30:18+00:00

#10 Public HTTP response

Evidence: http_header

HTTP headers can ask the browser to enforce specific protections.

Active non-intrusive High
Why it matters

They are visible, verifiable browser-side defensive layers.

What to check next

Read each full policy, identify permissive or contradictory directives, and compare responses across the main public routes.

Possible action

Harden policies progressively from actual application needs. Avoid copying generic templates without functional testing.

Observation
[ "nosniff" ]
Understand
HTTP response-header inspection
Source
Public HTTP response
Reliability
High
What this supports
Describe defensive policies declared on the observed response
What this does not prove
A header being present does not prove it is optimal or that the application has no vulnerabilities.

Standards and reference context

Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.

View raw data 
[
    "nosniff"
]

Rule 2026.09.4 · 2026-09-04T19:30:18+00:00

#11 DNS public records

Evidence: dns_nameserver

DNS shows how a domain resolves and which public services are associated with it.

Passive High
Why it matters

Consistent, verifiable resolution reduces some spoofing risks and helps explain entity dependencies.

What to check next

Compare NS, A/AAAA, MX, CAA and the DNSSEC chain with previous measurements to identify delegation or operator changes.

Possible action

If a change is unexpected, verify registrar and DNS-provider configuration before modifying anything. Document the failover mechanisms that actually exist.

Observation
ns12.infomaniak.ch
Understand
Standard DNS resolution and record parsing
Source
DNS public records
Reliability
High
What this supports
Describe public DNS data observed at scan time
What this does not prove
Public DNS does not prove physical server location, contracts, or global availability.

Standards and reference context

Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.

Verify it yourself

This command reproduces the public observation without changing the target.

dig NS afteralgorithm.com
View raw data 
ns12.infomaniak.ch

Rule 2026.09.4 · 2026-09-04T19:30:18+00:00

#12 Mail-related public records

Evidence: mail_policy_flag

Public mail policies show how the domain frames sending, authentication and email transport.

Active non-intrusive High
Why it matters

These mechanisms can reduce domain spoofing and document mail-transport posture.

What to check next

Relate SPF, DKIM when a selector is known, DMARC, MX, MTA-STS and TLS-RPT. Compare policy changes over time.

Possible action

Before strengthening a policy, inventory legitimate mail flows and verify alignment. Roll out changes progressively to avoid blocking authorized senders.

Observation
Understand
Public DNS and policy endpoint inspection
Source
Mail-related public records
Reliability
High
What this supports
Describe published mail authentication and transport policies
What this does not prove
They do not prove actual deliverability, every recipient’s behavior, or the absence of phishing.

Standards and reference context

Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.

View raw data

Rule 2026.09.4 · 2026-09-04T19:30:18+00:00

#13 Public HTTP response

Evidence: http_header

HTTP headers can ask the browser to enforce specific protections.

Active non-intrusive High
Why it matters

They are visible, verifiable browser-side defensive layers.

What to check next

Read each full policy, identify permissive or contradictory directives, and compare responses across the main public routes.

Possible action

Harden policies progressively from actual application needs. Avoid copying generic templates without functional testing.

Observation
[ "default-src 'none'; base-uri 'none'; form-action 'self'; frame-ancestors 'none'; object-src 'none'; script-src 'self' 'nonce-8kJ2Bq1lWZg7JTM8V0Ndezms'; style-src 'self'; img-src 'self' data: blob:; media-src 'self' blob:; connect-src 'self'; manifest-src 'self'; font-src 'self'; worker-src 'none'; upgrade-insecure-requests" ]
Understand
HTTP response-header inspection
Source
Public HTTP response
Reliability
High
What this supports
Describe defensive policies declared on the observed response
What this does not prove
A header being present does not prove it is optimal or that the application has no vulnerabilities.

Standards and reference context

Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.

View raw data 
[
    "default-src 'none'; base-uri 'none'; form-action 'self'; frame-ancestors 'none'; object-src 'none'; script-src 'self' 'nonce-8kJ2Bq1lWZg7JTM8V0Ndezms'; style-src 'self'; img-src 'self' data: blob:; media-src 'self' blob:; connect-src 'self'; manifest-src 'self'; font-src 'self'; worker-src 'none'; upgrade-insecure-requests"
]

Rule 2026.09.4 · 2026-09-04T19:30:18+00:00

#14 DNS public records

Evidence: dns_nameserver

DNS shows how a domain resolves and which public services are associated with it.

Passive High
Why it matters

Consistent, verifiable resolution reduces some spoofing risks and helps explain entity dependencies.

What to check next

Compare NS, A/AAAA, MX, CAA and the DNSSEC chain with previous measurements to identify delegation or operator changes.

Possible action

If a change is unexpected, verify registrar and DNS-provider configuration before modifying anything. Document the failover mechanisms that actually exist.

Observation
ns11.infomaniak.ch
Understand
Standard DNS resolution and record parsing
Source
DNS public records
Reliability
High
What this supports
Describe public DNS data observed at scan time
What this does not prove
Public DNS does not prove physical server location, contracts, or global availability.

Standards and reference context

Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.

Verify it yourself

This command reproduces the public observation without changing the target.

dig NS afteralgorithm.com
View raw data 
ns11.infomaniak.ch

Rule 2026.09.4 · 2026-09-04T19:30:18+00:00

#15 DNS public records

Evidence: dns_address

DNS shows how a domain resolves and which public services are associated with it.

Passive High
Why it matters

Consistent, verifiable resolution reduces some spoofing risks and helps explain entity dependencies.

What to check next

Compare NS, A/AAAA, MX, CAA and the DNSSEC chain with previous measurements to identify delegation or operator changes.

Possible action

If a change is unexpected, verify registrar and DNS-provider configuration before modifying anything. Document the failover mechanisms that actually exist.

Observation
2001:1600::aaaa:0:0:80:5b
Understand
Standard DNS resolution and record parsing
Source
DNS public records
Reliability
High
What this supports
Describe public DNS data observed at scan time
What this does not prove
Public DNS does not prove physical server location, contracts, or global availability.

Standards and reference context

Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.

Verify it yourself

This command reproduces the public observation without changing the target.

dig A afteralgorithm.com && dig AAAA afteralgorithm.com
View raw data 
2001:1600::aaaa:0:0:80:5b

Rule 2026.09.4 · 2026-09-04T19:30:18+00:00

#16 Mail-related public records

Evidence: spf_policy

Public mail policies show how the domain frames sending, authentication and email transport.

Active non-intrusive High
Why it matters

These mechanisms can reduce domain spoofing and document mail-transport posture.

What to check next

Relate SPF, DKIM when a selector is known, DMARC, MX, MTA-STS and TLS-RPT. Compare policy changes over time.

Possible action

Before strengthening a policy, inventory legitimate mail flows and verify alignment. Roll out changes progressively to avoid blocking authorized senders.

Observation
hardfail
Understand
Public DNS and policy endpoint inspection
Source
Mail-related public records
Reliability
High
What this supports
Describe published mail authentication and transport policies
What this does not prove
They do not prove actual deliverability, every recipient’s behavior, or the absence of phishing.

Standards and reference context

Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.

Verify it yourself

This command reproduces the public observation without changing the target.

dig TXT afteralgorithm.com
View raw data 
hardfail

Rule 2026.09.4 · 2026-09-04T19:30:18+00:00

#17 Mail-related public records

Evidence: module_finding

Public mail policies show how the domain frames sending, authentication and email transport.

Active non-intrusive High
Why it matters

These mechanisms can reduce domain spoofing and document mail-transport posture.

What to check next

Relate SPF, DKIM when a selector is known, DMARC, MX, MTA-STS and TLS-RPT. Compare policy changes over time.

Possible action

Before strengthening a policy, inventory legitimate mail flows and verify alignment. Roll out changes progressively to avoid blocking authorized senders.

Observation
{ "evidence": null, "severity": "low" }
Understand
Public DNS and policy endpoint inspection
Source
Mail-related public records
Reliability
High
What this supports
Describe published mail authentication and transport policies
What this does not prove
They do not prove actual deliverability, every recipient’s behavior, or the absence of phishing.

Standards and reference context

Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.

View raw data 
{
    "evidence": null,
    "severity": "low"
}

Rule 2026.09.4 · 2026-09-04T19:30:18+00:00

#18 Mail-related public records

Evidence: module_finding

Public mail policies show how the domain frames sending, authentication and email transport.

Active non-intrusive High
Why it matters

These mechanisms can reduce domain spoofing and document mail-transport posture.

What to check next

Relate SPF, DKIM when a selector is known, DMARC, MX, MTA-STS and TLS-RPT. Compare policy changes over time.

Possible action

Before strengthening a policy, inventory legitimate mail flows and verify alignment. Roll out changes progressively to avoid blocking authorized senders.

Observation
{ "evidence": [ { "host": "mta-gw.infomaniak.ch", "priority": 5 } ], "severity": "low" }
Understand
Public DNS and policy endpoint inspection
Source
Mail-related public records
Reliability
High
What this supports
Describe published mail authentication and transport policies
What this does not prove
They do not prove actual deliverability, every recipient’s behavior, or the absence of phishing.

Standards and reference context

Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.

View raw data 
{
    "evidence": [
        {
            "host": "mta-gw.infomaniak.ch",
            "priority": 5
        }
    ],
    "severity": "low"
}

Rule 2026.09.4 · 2026-09-04T19:30:18+00:00

#19 DNS public records

Evidence: spf_record

DNS shows how a domain resolves and which public services are associated with it.

Passive High
Why it matters

Consistent, verifiable resolution reduces some spoofing risks and helps explain entity dependencies.

What to check next

Compare NS, A/AAAA, MX, CAA and the DNSSEC chain with previous measurements to identify delegation or operator changes.

Possible action

If a change is unexpected, verify registrar and DNS-provider configuration before modifying anything. Document the failover mechanisms that actually exist.

Observation
v=spf1 include:spf.infomaniak.ch -all
Understand
Standard DNS resolution and record parsing
Source
DNS public records
Reliability
High
What this supports
Describe public DNS data observed at scan time
What this does not prove
Public DNS does not prove physical server location, contracts, or global availability.

Standards and reference context

Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.

View raw data 
v=spf1 include:spf.infomaniak.ch -all

Rule 2026.09.4 · 2026-09-04T19:30:18+00:00

#20 Observed public resources

Evidence: dependency_provider

Scanapse shows visible providers and third-party services on which the public service depends.

Passive Medium
Why it matters

Concentration on one actor or many third parties can affect continuity and governance.

What to check next

Identify each provider role, functions concentrated on the same actor, and dependencies that appeared or disappeared since the previous scan.

Possible action

For a critical dependency, document owner, contract, reversibility, failover and rationale. Diversify only after analysing the actual need.

Observation
{ "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 }
Understand
Public HTML/resource dependency extraction and provider matching
Source
Observed public resources
Reliability
Medium
What this supports
Describe visible third-party dependencies
What this does not prove
A visible dependency does not prove data location, actual contractual jurisdiction, or hidden subcontractors.

Standards and reference context

Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.

View raw data 
{
    "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-04T19:30:18+00:00

#21 DNS public records

Evidence: mail_exchanger

DNS shows how a domain resolves and which public services are associated with it.

Passive High
Why it matters

Consistent, verifiable resolution reduces some spoofing risks and helps explain entity dependencies.

What to check next

Compare NS, A/AAAA, MX, CAA and the DNSSEC chain with previous measurements to identify delegation or operator changes.

Possible action

If a change is unexpected, verify registrar and DNS-provider configuration before modifying anything. Document the failover mechanisms that actually exist.

Observation
mta-gw.infomaniak.ch
Understand
Standard DNS resolution and record parsing
Source
DNS public records
Reliability
High
What this supports
Describe public DNS data observed at scan time
What this does not prove
Public DNS does not prove physical server location, contracts, or global availability.

Standards and reference context

Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.

Verify it yourself

This command reproduces the public observation without changing the target.

dig MX afteralgorithm.com
View raw data 
mta-gw.infomaniak.ch

Rule 2026.09.4 · 2026-09-04T19:30:18+00:00

#22 Public HTTP response

Evidence: http_header

HTTP headers can ask the browser to enforce specific protections.

Active non-intrusive High
Why it matters

They are visible, verifiable browser-side defensive layers.

What to check next

Read each full policy, identify permissive or contradictory directives, and compare responses across the main public routes.

Possible action

Harden policies progressively from actual application needs. Avoid copying generic templates without functional testing.

Observation
[ "same-origin" ]
Understand
HTTP response-header inspection
Source
Public HTTP response
Reliability
High
What this supports
Describe defensive policies declared on the observed response
What this does not prove
A header being present does not prove it is optimal or that the application has no vulnerabilities.

Standards and reference context

Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.

View raw data 
[
    "same-origin"
]

Rule 2026.09.4 · 2026-09-04T19:30:18+00:00

#23 technology

Evidence: technology

Scanapse shows visible providers and third-party services on which the public service depends.

Passive Medium
Why it matters

Concentration on one actor or many third parties can affect continuity and governance.

What to check next

Identify each provider role, functions concentrated on the same actor, and dependencies that appeared or disappeared since the previous scan.

Possible action

For a critical dependency, document owner, contract, reversibility, failover and rationale. Diversify only after analysing the actual need.

Observation
{ "name": "Apache", "version": "", "version_exposed": false }
Understand
Public observation
Source
technology
Reliability
Medium
What this supports
Describe the observed public artefact
What this does not prove
A visible dependency does not prove data location, actual contractual jurisdiction, or hidden subcontractors.

Standards and reference context

Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.

View raw data 
{
    "name": "Apache",
    "version": "",
    "version_exposed": false
}

Rule 2026.09.4 · 2026-09-04T19:30:18+00:00

#24 Public TLS endpoint

Evidence: tls_issuer

TLS protects the observed connection between the scanner and the public service.

Active non-intrusive High
Why it matters

These elements document public-channel protection and the cryptographic mechanisms actually negotiated.

What to check next

Compare negotiated protocol, issuer, expiry, chain and cryptographic parameters with history. Check other public entry points separately.

Possible action

Address only observed gaps such as an expiring certificate, invalid chain, or unwanted protocol. Test changes in a controlled environment before deployment.

Observation
C = US, O = Let's Encrypt, CN = YR1
Understand
TLS handshake and public certificate inspection
Source
Public TLS endpoint
Reliability
High
What this supports
Describe the TLS session and certificate presented to Scanapse
What this does not prove
Strong TLS does not prove application security or origin-server security behind a CDN or reverse proxy.

Standards and reference context

Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.

Verify it yourself

This command reproduces the public observation without changing the target.

openssl s_client -connect afteralgorithm.com:443 -servername afteralgorithm.com </dev/null
View raw data 
C = US, O = Let's Encrypt, CN = YR1

Rule 2026.09.4 · 2026-09-04T19:30:18+00:00

#25 DNS public records

Evidence: dmarc_record

DNS shows how a domain resolves and which public services are associated with it.

Passive High
Why it matters

Consistent, verifiable resolution reduces some spoofing risks and helps explain entity dependencies.

What to check next

Compare NS, A/AAAA, MX, CAA and the DNSSEC chain with previous measurements to identify delegation or operator changes.

Possible action

If a change is unexpected, verify registrar and DNS-provider configuration before modifying anything. Document the failover mechanisms that actually exist.

Observation
v=DMARC1; p=reject;
Understand
Standard DNS resolution and record parsing
Source
DNS public records
Reliability
High
What this supports
Describe public DNS data observed at scan time
What this does not prove
Public DNS does not prove physical server location, contracts, or global availability.

Standards and reference context

Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.

View raw data 
v=DMARC1; p=reject;

Rule 2026.09.4 · 2026-09-04T19:30:18+00:00

#26 Public HTTP response

Evidence: http_header

HTTP headers can ask the browser to enforce specific protections.

Active non-intrusive High
Why it matters

They are visible, verifiable browser-side defensive layers.

What to check next

Read each full policy, identify permissive or contradictory directives, and compare responses across the main public routes.

Possible action

Harden policies progressively from actual application needs. Avoid copying generic templates without functional testing.

Observation
[ "Apache" ]
Understand
HTTP response-header inspection
Source
Public HTTP response
Reliability
High
What this supports
Describe defensive policies declared on the observed response
What this does not prove
A header being present does not prove it is optimal or that the application has no vulnerabilities.

Standards and reference context

Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.

View raw data 
[
    "Apache"
]

Rule 2026.09.4 · 2026-09-04T19:30:18+00:00

#27 DNS public records

Evidence: module_finding

DNS shows how a domain resolves and which public services are associated with it.

Passive High
Why it matters

Consistent, verifiable resolution reduces some spoofing risks and helps explain entity dependencies.

What to check next

Compare NS, A/AAAA, MX, CAA and the DNSSEC chain with previous measurements to identify delegation or operator changes.

Possible action

If a change is unexpected, verify registrar and DNS-provider configuration before modifying anything. Document the failover mechanisms that actually exist.

Observation
{ "evidence": [ "ns11.infomaniak.ch", "ns12.infomaniak.ch" ], "severity": "low" }
Understand
Standard DNS resolution and record parsing
Source
DNS public records
Reliability
High
What this supports
Describe public DNS data observed at scan time
What this does not prove
Public DNS does not prove physical server location, contracts, or global availability.

Standards and reference context

Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.

View raw data 
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}

Rule 2026.09.4 · 2026-09-04T19:30:18+00:00

#28 Public HTTP response

Evidence: http_header

HTTP headers can ask the browser to enforce specific protections.

Active non-intrusive High
Why it matters

They are visible, verifiable browser-side defensive layers.

What to check next

Read each full policy, identify permissive or contradictory directives, and compare responses across the main public routes.

Possible action

Harden policies progressively from actual application needs. Avoid copying generic templates without functional testing.

Observation
[ "no-referrer" ]
Understand
HTTP response-header inspection
Source
Public HTTP response
Reliability
High
What this supports
Describe defensive policies declared on the observed response
What this does not prove
A header being present does not prove it is optimal or that the application has no vulnerabilities.

Standards and reference context

Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.

View raw data 
[
    "no-referrer"
]

Rule 2026.09.4 · 2026-09-04T19:30:18+00:00

#29 Public HTTP response

Evidence: http_header

HTTP headers can ask the browser to enforce specific protections.

Active non-intrusive High
Why it matters

They are visible, verifiable browser-side defensive layers.

What to check next

Read each full policy, identify permissive or contradictory directives, and compare responses across the main public routes.

Possible action

Harden policies progressively from actual application needs. Avoid copying generic templates without functional testing.

Observation
[ "same-origin" ]
Understand
HTTP response-header inspection
Source
Public HTTP response
Reliability
High
What this supports
Describe defensive policies declared on the observed response
What this does not prove
A header being present does not prove it is optimal or that the application has no vulnerabilities.

Standards and reference context

Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.

View raw data 
[
    "same-origin"
]

Rule 2026.09.4 · 2026-09-04T19:30:18+00:00

#30 Public HTTP response

Evidence: http_header

HTTP headers can ask the browser to enforce specific protections.

Active non-intrusive High
Why it matters

They are visible, verifiable browser-side defensive layers.

What to check next

Read each full policy, identify permissive or contradictory directives, and compare responses across the main public routes.

Possible action

Harden policies progressively from actual application needs. Avoid copying generic templates without functional testing.

Observation
[ "DENY" ]
Understand
HTTP response-header inspection
Source
Public HTTP response
Reliability
High
What this supports
Describe defensive policies declared on the observed response
What this does not prove
A header being present does not prove it is optimal or that the application has no vulnerabilities.

Standards and reference context

Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.

View raw data 
[
    "DENY"
]

Rule 2026.09.4 · 2026-09-04T19:30:18+00:00

#31 Mail-related public records

Evidence: mail_policy_flag

Public mail policies show how the domain frames sending, authentication and email transport.

Active non-intrusive High
Why it matters

These mechanisms can reduce domain spoofing and document mail-transport posture.

What to check next

Relate SPF, DKIM when a selector is known, DMARC, MX, MTA-STS and TLS-RPT. Compare policy changes over time.

Possible action

Before strengthening a policy, inventory legitimate mail flows and verify alignment. Roll out changes progressively to avoid blocking authorized senders.

Observation
Understand
Public DNS and policy endpoint inspection
Source
Mail-related public records
Reliability
High
What this supports
Describe published mail authentication and transport policies
What this does not prove
They do not prove actual deliverability, every recipient’s behavior, or the absence of phishing.

Standards and reference context

Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.

View raw data

Rule 2026.09.4 · 2026-09-04T19:30:18+00:00

#32 Public HTTP response

Evidence: http_header

HTTP headers can ask the browser to enforce specific protections.

Active non-intrusive High
Why it matters

They are visible, verifiable browser-side defensive layers.

What to check next

Read each full policy, identify permissive or contradictory directives, and compare responses across the main public routes.

Possible action

Harden policies progressively from actual application needs. Avoid copying generic templates without functional testing.

Observation
[ "require-corp" ]
Understand
HTTP response-header inspection
Source
Public HTTP response
Reliability
High
What this supports
Describe defensive policies declared on the observed response
What this does not prove
A header being present does not prove it is optimal or that the application has no vulnerabilities.

Standards and reference context

Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.

View raw data 
[
    "require-corp"
]

Rule 2026.09.4 · 2026-09-04T19:30:18+00:00

#33 DNS public records

Evidence: module_finding

DNS shows how a domain resolves and which public services are associated with it.

Passive High
Why it matters

Consistent, verifiable resolution reduces some spoofing risks and helps explain entity dependencies.

What to check next

Compare NS, A/AAAA, MX, CAA and the DNSSEC chain with previous measurements to identify delegation or operator changes.

Possible action

If a change is unexpected, verify registrar and DNS-provider configuration before modifying anything. Document the failover mechanisms that actually exist.

Observation
{ "evidence": { "reason": "No external validating resolver is used; DS validation is intentionally not inferred.", "status": "not_tested" }, "severity": "info" }
Understand
Standard DNS resolution and record parsing
Source
DNS public records
Reliability
High
What this supports
Describe public DNS data observed at scan time
What this does not prove
Public DNS does not prove physical server location, contracts, or global availability.

Standards and reference context

Regulatory references are contextual only. Scanapse does not determine whether a framework applies to the organization and does not issue an automatic compliance verdict.

View raw data 
{
    "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-04T19:30:18+00:00

Show technical details 
{
    "schema_version": "2.0",
    "engine_version": "2.6.0.1",
    "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": "8ae58782ca998e26dd96131a993859139372007a72a8bd359a045236dae44d61",
        "display_name": "afteralgorithm.com",
        "slug": "afteralgorithm-com",
        "entity_type": "domain_subject",
        "auto_created": true,
        "primary_asset": "afteralgorithm.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": false,
        "change_counts": [],
        "observation_count": 33,
        "evidence_count": 33,
        "provider_count": 1,
        "strategic_signal_count": 1,
        "top_signal_count": 1
    }
}