PUBLIC DOMAIN DOSSIER

alphatraining64.fr

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:35 UTC First observation 2026-09-04 19:35 UTC Latest observation 2026-09-04 19:35 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
  • Not observable from outsideOrigin host
  • ObservedDepends on providerInfomaniak

Infrastructure & transport

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

Mail & trust

  • ObservedSpf policyhardfail
  • ObservedDmarc policyreject

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 alphatraining64.fr. 4 questions remain open with the available public evidence.

Measured on 2026-09-04 19:35 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.

Probable France

European Union

Why this context appears

  • The country-code domain extension provides a supporting geographic clue

What this does not establish

  • Technical hosting, IP addresses, ASNs and CDN locations do not establish the applicable legal jurisdiction by themselves.
  • A country-code domain is only a contextual clue and does not prove where the organisation is legally established.

Regulatory frameworks

Useful texts for this context

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

European UnionRelevant

GDPR

The observed territorial context links the domain to the European Union. Public privacy signals increase the relevance of this framework without proving internal processing practices.

Official source →
European UnionPotentially relevant

NIS2

The directive may apply to some entities depending on sector, size and role. Scanapse does not infer those conditions from a domain alone.

Official source →

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
module_finding dns ece8b640995503edd3b42ad7b107f2a37bd0a87b0271a1db079ce7cbacb0dc5b
{
    "evidence": null,
    "severity": "low"
}
module_finding dns f5a826b637d63e2fc1b4cd37dec73aa6e129ef5060050833954c8c4e6ef2d9a1
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
dns_address dns 1afd5b0b3f3b65886ccee8062eb3da5f8fa638fb7c91ee2a52de8a26f6370ccf
"2001:1600::aaaa:0:0:80:5a"
module_finding dns 4f2334cec3f76543e19c38d503980f409a2987ee05ec58cdaedcf8d88f0e8a2b
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
dmarc_record dns 57a8e7082fd4431add777a5f505c09b1f2c1665ff0b3c417bea286d3728dd981
"v=DMARC1; p=reject;"
spf_record dns 54eab531534a3c12a1e3dde3468339e00aba7b1c8048de5e302b23f029c33ab7
"v=spf1 include:spf.infomaniak.ch -all"
dns_nameserver dns d4aadcd251c70bed20de983e05bff269ebe02e20793e5159639231bfe26faff6
"ns11.infomaniak.ch"
dns_nameserver dns 328dd692ddbc62e206af9563479675e1f0b3a4f6267ad9994f30356bcd447e28
"ns12.infomaniak.ch"
mail_exchanger dns 56179926e4c6a9b287ed9f43095884fcb0d6d9813c1d6a8d0b9d5c31106ce3c9
"mta-gw.infomaniak.ch"
dns_address dns ca6a184d395627709384f0b7014e460ef83899b67f194b1870fbbaf5e7ce7ad9
"185.125.27.195"
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

dependency_provider dependencies 6b6c76308a7501bd1a0dec43ae6a3e0d95e20c71f8bfea52d088272939f457d9
{
    "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
}
module_finding dns ece8b640995503edd3b42ad7b107f2a37bd0a87b0271a1db079ce7cbacb0dc5b
{
    "evidence": null,
    "severity": "low"
}
module_finding dns f5a826b637d63e2fc1b4cd37dec73aa6e129ef5060050833954c8c4e6ef2d9a1
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
module_finding resilience 456d53beec53a14901667abb04db4c5cdb89ecb9f373543c156f61deb138ea53
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "medium"
}
dns_address dns 1afd5b0b3f3b65886ccee8062eb3da5f8fa638fb7c91ee2a52de8a26f6370ccf
"2001:1600::aaaa:0:0:80:5a"
module_finding dns 4f2334cec3f76543e19c38d503980f409a2987ee05ec58cdaedcf8d88f0e8a2b
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
dmarc_record dns 57a8e7082fd4431add777a5f505c09b1f2c1665ff0b3c417bea286d3728dd981
"v=DMARC1; p=reject;"
spf_record dns 54eab531534a3c12a1e3dde3468339e00aba7b1c8048de5e302b23f029c33ab7
"v=spf1 include:spf.infomaniak.ch -all"
dns_nameserver dns d4aadcd251c70bed20de983e05bff269ebe02e20793e5159639231bfe26faff6
"ns11.infomaniak.ch"
dns_nameserver dns 328dd692ddbc62e206af9563479675e1f0b3a4f6267ad9994f30356bcd447e28
"ns12.infomaniak.ch"
mail_exchanger dns 56179926e4c6a9b287ed9f43095884fcb0d6d9813c1d6a8d0b9d5c31106ce3c9
"mta-gw.infomaniak.ch"
dns_address dns ca6a184d395627709384f0b7014e460ef83899b67f194b1870fbbaf5e7ce7ad9
"185.125.27.195"
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

13evidence
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
13
Signals
0
Changes
0

Unknowns and limitations

1 items still require qualification

http_header headers 81755e766bd90e75f0ce24dcb863acce199eda94a0d55ff91592fe86cc023141
[
    "max-age=16000000"
]
module_finding headers 5b5d7fe2c53428472153d955f99e02da68976acf39166d565c8a473edf6f8248
{
    "evidence": null,
    "severity": "low"
}
module_finding headers 069a3a6a08fc7f15289e03b2407344855fd2fd0638342849d8bb7f2d903c5d5d
{
    "evidence": null,
    "severity": "medium"
}
module_finding headers 9827c156a712d8476ed08edaf944d1b6f5b4578e9cccf83a799c352ddea0a877
{
    "evidence": "max-age=16000000",
    "severity": "low"
}
tls_issuer tls 7b1b05455571c2663659d20eb9dd76ea4be06b3e511723175a19ee8da08bcd07
"C = US, O = Let's Encrypt, CN = YR1"
module_finding headers 93d596e1ac0e33aa286f39d4563d92ee2aebaa00834829f0d3dec429aa00def3
{
    "evidence": null,
    "severity": "medium"
}
tls_valid_to tls 109b7f1905c0ca8ee773baef7f1f8c630be721d221777533679548a6d84f8947
"2026-09-30T02:12:44+00:00"
module_finding headers ec61b3916449a45cfc69bda3c9be74a171bf08a86473375d6b1297c37468101c
{
    "evidence": null,
    "severity": "critical"
}
module_finding headers 46dab24fd5239254ba2a8d47d686ae75649b3a09862f1f1997fc7dc25ca9804a
{
    "evidence": null,
    "severity": "low"
}
module_finding headers 96a5e4810c225fc5a68d5ddedc8cedbd1b2cbea08860ba7b12d3699d1f2cd2b2
{
    "evidence": null,
    "severity": "info"
}
module_finding headers fea76d72824f04031a1a69bddf0984c5b220d639778c81089527f306085bdd69
{
    "evidence": null,
    "severity": "high"
}
http_header headers 8e808c36aa1e3dda2eea8568a593a8c05d3418eef7c78294156784fdcee7f50e
[
    "Apache"
]
module_finding headers 351ee5b2c83ccb3d46a726cdec09a9eeb5e923124d09c09d310ceefeb4d6185d
{
    "evidence": null,
    "severity": "low"
}
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 1d0ecd61fc0fca902cbb57c3dda97fe543d3eee5a05228d888513d7dc14d6d7b
{
    "evidence": [
        {
            "host": "mta-gw.infomaniak.ch",
            "priority": 5
        }
    ],
    "severity": "low"
}
mail_policy_flag mail_trust f70887aa14c6faed822fae211ee733907cd4669d338428ad61bccc8ebcf26519
false
module_finding dns ece8b640995503edd3b42ad7b107f2a37bd0a87b0271a1db079ce7cbacb0dc5b
{
    "evidence": null,
    "severity": "low"
}
mail_policy_flag mail_trust 6844b8711b7ed52ba4df4f2bd2662e1b5c5521f005302691fca3ece7a763e90a
false
module_finding dns f5a826b637d63e2fc1b4cd37dec73aa6e129ef5060050833954c8c4e6ef2d9a1
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
dns_address dns 1afd5b0b3f3b65886ccee8062eb3da5f8fa638fb7c91ee2a52de8a26f6370ccf
"2001:1600::aaaa:0:0:80:5a"
dmarc_policy mail_trust 5434ba9d5a056312098a7a7dfe83d4dc60c35cb4e22beb89531df0f8beb24168
"reject"
module_finding dns 4f2334cec3f76543e19c38d503980f409a2987ee05ec58cdaedcf8d88f0e8a2b
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
dmarc_record dns 57a8e7082fd4431add777a5f505c09b1f2c1665ff0b3c417bea286d3728dd981
"v=DMARC1; p=reject;"
spf_record dns 54eab531534a3c12a1e3dde3468339e00aba7b1c8048de5e302b23f029c33ab7
"v=spf1 include:spf.infomaniak.ch -all"
dns_nameserver dns d4aadcd251c70bed20de983e05bff269ebe02e20793e5159639231bfe26faff6
"ns11.infomaniak.ch"
mail_policy_flag mail_trust 2cde402e4e4871d40f09ba2fce5d06594419caffdeb204d289c2460ede533739
false
spf_policy mail_trust 6aa587144b6d28f1f11c7949dcf5839a9703cfff1f6248353dd05b1189a7f4ab
"hardfail"
module_finding mail_trust 80ffc38b2d045c53cd3473e63d45fe44cf0275ad26ee895f27d56c51e7769368
{
    "evidence": null,
    "severity": "low"
}
dns_nameserver dns 328dd692ddbc62e206af9563479675e1f0b3a4f6267ad9994f30356bcd447e28
"ns12.infomaniak.ch"
mail_exchanger dns 56179926e4c6a9b287ed9f43095884fcb0d6d9813c1d6a8d0b9d5c31106ce3c9
"mta-gw.infomaniak.ch"
dns_address dns ca6a184d395627709384f0b7014e460ef83899b67f194b1870fbbaf5e7ce7ad9
"185.125.27.195"
module_finding mail_trust 40606a069aea0dd13786bc9233f89ed68540c2dfbee8d49c41f8b94a6e483659
{
    "evidence": null,
    "severity": "low"
}
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 1d0ecd61fc0fca902cbb57c3dda97fe543d3eee5a05228d888513d7dc14d6d7b
{
    "evidence": [
        {
            "host": "mta-gw.infomaniak.ch",
            "priority": 5
        }
    ],
    "severity": "low"
}
mail_policy_flag mail_trust f70887aa14c6faed822fae211ee733907cd4669d338428ad61bccc8ebcf26519
false
module_finding dns ece8b640995503edd3b42ad7b107f2a37bd0a87b0271a1db079ce7cbacb0dc5b
{
    "evidence": null,
    "severity": "low"
}
mail_policy_flag mail_trust 6844b8711b7ed52ba4df4f2bd2662e1b5c5521f005302691fca3ece7a763e90a
false
module_finding dns f5a826b637d63e2fc1b4cd37dec73aa6e129ef5060050833954c8c4e6ef2d9a1
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
dns_address dns 1afd5b0b3f3b65886ccee8062eb3da5f8fa638fb7c91ee2a52de8a26f6370ccf
"2001:1600::aaaa:0:0:80:5a"
dmarc_policy mail_trust 5434ba9d5a056312098a7a7dfe83d4dc60c35cb4e22beb89531df0f8beb24168
"reject"
module_finding dns 4f2334cec3f76543e19c38d503980f409a2987ee05ec58cdaedcf8d88f0e8a2b
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
dmarc_record dns 57a8e7082fd4431add777a5f505c09b1f2c1665ff0b3c417bea286d3728dd981
"v=DMARC1; p=reject;"
spf_record dns 54eab531534a3c12a1e3dde3468339e00aba7b1c8048de5e302b23f029c33ab7
"v=spf1 include:spf.infomaniak.ch -all"
dns_nameserver dns d4aadcd251c70bed20de983e05bff269ebe02e20793e5159639231bfe26faff6
"ns11.infomaniak.ch"
mail_policy_flag mail_trust 2cde402e4e4871d40f09ba2fce5d06594419caffdeb204d289c2460ede533739
false
spf_policy mail_trust 6aa587144b6d28f1f11c7949dcf5839a9703cfff1f6248353dd05b1189a7f4ab
"hardfail"
module_finding mail_trust 80ffc38b2d045c53cd3473e63d45fe44cf0275ad26ee895f27d56c51e7769368
{
    "evidence": null,
    "severity": "low"
}
dns_nameserver dns 328dd692ddbc62e206af9563479675e1f0b3a4f6267ad9994f30356bcd447e28
"ns12.infomaniak.ch"
mail_exchanger dns 56179926e4c6a9b287ed9f43095884fcb0d6d9813c1d6a8d0b9d5c31106ce3c9
"mta-gw.infomaniak.ch"
dns_address dns ca6a184d395627709384f0b7014e460ef83899b67f194b1870fbbaf5e7ce7ad9
"185.125.27.195"
module_finding mail_trust 40606a069aea0dd13786bc9233f89ed68540c2dfbee8d49c41f8b94a6e483659
{
    "evidence": null,
    "severity": "low"
}
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
dependency_provider dependencies 6b6c76308a7501bd1a0dec43ae6a3e0d95e20c71f8bfea52d088272939f457d9
{
    "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
}
module_finding dns ece8b640995503edd3b42ad7b107f2a37bd0a87b0271a1db079ce7cbacb0dc5b
{
    "evidence": null,
    "severity": "low"
}
module_finding dns f5a826b637d63e2fc1b4cd37dec73aa6e129ef5060050833954c8c4e6ef2d9a1
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
dns_address dns 1afd5b0b3f3b65886ccee8062eb3da5f8fa638fb7c91ee2a52de8a26f6370ccf
"2001:1600::aaaa:0:0:80:5a"
module_finding dns 4f2334cec3f76543e19c38d503980f409a2987ee05ec58cdaedcf8d88f0e8a2b
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
dmarc_record dns 57a8e7082fd4431add777a5f505c09b1f2c1665ff0b3c417bea286d3728dd981
"v=DMARC1; p=reject;"
spf_record dns 54eab531534a3c12a1e3dde3468339e00aba7b1c8048de5e302b23f029c33ab7
"v=spf1 include:spf.infomaniak.ch -all"
dns_nameserver dns d4aadcd251c70bed20de983e05bff269ebe02e20793e5159639231bfe26faff6
"ns11.infomaniak.ch"
dns_nameserver dns 328dd692ddbc62e206af9563479675e1f0b3a4f6267ad9994f30356bcd447e28
"ns12.infomaniak.ch"
mail_exchanger dns 56179926e4c6a9b287ed9f43095884fcb0d6d9813c1d6a8d0b9d5c31106ce3c9
"mta-gw.infomaniak.ch"
dns_address dns ca6a184d395627709384f0b7014e460ef83899b67f194b1870fbbaf5e7ce7ad9
"185.125.27.195"
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

12evidence
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
12
Signals
0
Changes
0
http_header headers 81755e766bd90e75f0ce24dcb863acce199eda94a0d55ff91592fe86cc023141
[
    "max-age=16000000"
]
module_finding headers 5b5d7fe2c53428472153d955f99e02da68976acf39166d565c8a473edf6f8248
{
    "evidence": null,
    "severity": "low"
}
module_finding headers 069a3a6a08fc7f15289e03b2407344855fd2fd0638342849d8bb7f2d903c5d5d
{
    "evidence": null,
    "severity": "medium"
}
module_finding headers 9827c156a712d8476ed08edaf944d1b6f5b4578e9cccf83a799c352ddea0a877
{
    "evidence": "max-age=16000000",
    "severity": "low"
}
module_finding headers 93d596e1ac0e33aa286f39d4563d92ee2aebaa00834829f0d3dec429aa00def3
{
    "evidence": null,
    "severity": "medium"
}
module_finding headers ec61b3916449a45cfc69bda3c9be74a171bf08a86473375d6b1297c37468101c
{
    "evidence": null,
    "severity": "critical"
}
module_finding headers 46dab24fd5239254ba2a8d47d686ae75649b3a09862f1f1997fc7dc25ca9804a
{
    "evidence": null,
    "severity": "low"
}
technology technology c3c8230079e371668745df57ca0b7296d6e4b4f5e19aaba005f439104baab787
{
    "name": "Apache",
    "version": "",
    "version_exposed": false
}
module_finding headers 96a5e4810c225fc5a68d5ddedc8cedbd1b2cbea08860ba7b12d3699d1f2cd2b2
{
    "evidence": null,
    "severity": "info"
}
module_finding headers fea76d72824f04031a1a69bddf0984c5b220d639778c81089527f306085bdd69
{
    "evidence": null,
    "severity": "high"
}
http_header headers 8e808c36aa1e3dda2eea8568a593a8c05d3418eef7c78294156784fdcee7f50e
[
    "Apache"
]
module_finding headers 351ee5b2c83ccb3d46a726cdec09a9eeb5e923124d09c09d310ceefeb4d6185d
{
    "evidence": null,
    "severity": "low"
}
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

19evidence
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
19
Signals
0
Changes
0

Unknowns and limitations

1 items still require qualification

module_finding mail_trust 1d0ecd61fc0fca902cbb57c3dda97fe543d3eee5a05228d888513d7dc14d6d7b
{
    "evidence": [
        {
            "host": "mta-gw.infomaniak.ch",
            "priority": 5
        }
    ],
    "severity": "low"
}
http_header headers 81755e766bd90e75f0ce24dcb863acce199eda94a0d55ff91592fe86cc023141
[
    "max-age=16000000"
]
module_finding transparency e7a3bd5fff903d30b73646dc177452f2397b0d19d6c5170307c2f58baf2a7e1b
{
    "evidence": 404,
    "severity": "medium"
}
module_finding headers 5b5d7fe2c53428472153d955f99e02da68976acf39166d565c8a473edf6f8248
{
    "evidence": null,
    "severity": "low"
}
module_finding dns ece8b640995503edd3b42ad7b107f2a37bd0a87b0271a1db079ce7cbacb0dc5b
{
    "evidence": null,
    "severity": "low"
}
module_finding headers 069a3a6a08fc7f15289e03b2407344855fd2fd0638342849d8bb7f2d903c5d5d
{
    "evidence": null,
    "severity": "medium"
}
module_finding dns f5a826b637d63e2fc1b4cd37dec73aa6e129ef5060050833954c8c4e6ef2d9a1
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
module_finding resilience 456d53beec53a14901667abb04db4c5cdb89ecb9f373543c156f61deb138ea53
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "medium"
}
module_finding headers 9827c156a712d8476ed08edaf944d1b6f5b4578e9cccf83a799c352ddea0a877
{
    "evidence": "max-age=16000000",
    "severity": "low"
}
module_finding headers 93d596e1ac0e33aa286f39d4563d92ee2aebaa00834829f0d3dec429aa00def3
{
    "evidence": null,
    "severity": "medium"
}
module_finding dns 4f2334cec3f76543e19c38d503980f409a2987ee05ec58cdaedcf8d88f0e8a2b
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
module_finding headers ec61b3916449a45cfc69bda3c9be74a171bf08a86473375d6b1297c37468101c
{
    "evidence": null,
    "severity": "critical"
}
module_finding headers 46dab24fd5239254ba2a8d47d686ae75649b3a09862f1f1997fc7dc25ca9804a
{
    "evidence": null,
    "severity": "low"
}
module_finding headers 96a5e4810c225fc5a68d5ddedc8cedbd1b2cbea08860ba7b12d3699d1f2cd2b2
{
    "evidence": null,
    "severity": "info"
}
module_finding headers fea76d72824f04031a1a69bddf0984c5b220d639778c81089527f306085bdd69
{
    "evidence": null,
    "severity": "high"
}
module_finding mail_trust 80ffc38b2d045c53cd3473e63d45fe44cf0275ad26ee895f27d56c51e7769368
{
    "evidence": null,
    "severity": "low"
}
http_header headers 8e808c36aa1e3dda2eea8568a593a8c05d3418eef7c78294156784fdcee7f50e
[
    "Apache"
]
module_finding headers 351ee5b2c83ccb3d46a726cdec09a9eeb5e923124d09c09d310ceefeb4d6185d
{
    "evidence": null,
    "severity": "low"
}
module_finding mail_trust 40606a069aea0dd13786bc9233f89ed68540c2dfbee8d49c41f8b94a6e483659
{
    "evidence": null,
    "severity": "low"
}
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

19evidence
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
19
Signals
0
Changes
0
module_finding mail_trust 1d0ecd61fc0fca902cbb57c3dda97fe543d3eee5a05228d888513d7dc14d6d7b
{
    "evidence": [
        {
            "host": "mta-gw.infomaniak.ch",
            "priority": 5
        }
    ],
    "severity": "low"
}
http_header headers 81755e766bd90e75f0ce24dcb863acce199eda94a0d55ff91592fe86cc023141
[
    "max-age=16000000"
]
module_finding transparency e7a3bd5fff903d30b73646dc177452f2397b0d19d6c5170307c2f58baf2a7e1b
{
    "evidence": 404,
    "severity": "medium"
}
module_finding headers 5b5d7fe2c53428472153d955f99e02da68976acf39166d565c8a473edf6f8248
{
    "evidence": null,
    "severity": "low"
}
module_finding dns ece8b640995503edd3b42ad7b107f2a37bd0a87b0271a1db079ce7cbacb0dc5b
{
    "evidence": null,
    "severity": "low"
}
module_finding headers 069a3a6a08fc7f15289e03b2407344855fd2fd0638342849d8bb7f2d903c5d5d
{
    "evidence": null,
    "severity": "medium"
}
module_finding dns f5a826b637d63e2fc1b4cd37dec73aa6e129ef5060050833954c8c4e6ef2d9a1
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
module_finding resilience 456d53beec53a14901667abb04db4c5cdb89ecb9f373543c156f61deb138ea53
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "medium"
}
module_finding headers 9827c156a712d8476ed08edaf944d1b6f5b4578e9cccf83a799c352ddea0a877
{
    "evidence": "max-age=16000000",
    "severity": "low"
}
module_finding headers 93d596e1ac0e33aa286f39d4563d92ee2aebaa00834829f0d3dec429aa00def3
{
    "evidence": null,
    "severity": "medium"
}
module_finding dns 4f2334cec3f76543e19c38d503980f409a2987ee05ec58cdaedcf8d88f0e8a2b
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
module_finding headers ec61b3916449a45cfc69bda3c9be74a171bf08a86473375d6b1297c37468101c
{
    "evidence": null,
    "severity": "critical"
}
module_finding headers 46dab24fd5239254ba2a8d47d686ae75649b3a09862f1f1997fc7dc25ca9804a
{
    "evidence": null,
    "severity": "low"
}
module_finding headers 96a5e4810c225fc5a68d5ddedc8cedbd1b2cbea08860ba7b12d3699d1f2cd2b2
{
    "evidence": null,
    "severity": "info"
}
module_finding headers fea76d72824f04031a1a69bddf0984c5b220d639778c81089527f306085bdd69
{
    "evidence": null,
    "severity": "high"
}
module_finding mail_trust 80ffc38b2d045c53cd3473e63d45fe44cf0275ad26ee895f27d56c51e7769368
{
    "evidence": null,
    "severity": "low"
}
http_header headers 8e808c36aa1e3dda2eea8568a593a8c05d3418eef7c78294156784fdcee7f50e
[
    "Apache"
]
module_finding headers 351ee5b2c83ccb3d46a726cdec09a9eeb5e923124d09c09d310ceefeb4d6185d
{
    "evidence": null,
    "severity": "low"
}
module_finding mail_trust 40606a069aea0dd13786bc9233f89ed68540c2dfbee8d49c41f8b94a6e483659
{
    "evidence": null,
    "severity": "low"
}
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

33evidence
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
33
Signals
2
Changes
0

Unknowns and limitations

2 items still require qualification

module_finding mail_trust 1d0ecd61fc0fca902cbb57c3dda97fe543d3eee5a05228d888513d7dc14d6d7b
{
    "evidence": [
        {
            "host": "mta-gw.infomaniak.ch",
            "priority": 5
        }
    ],
    "severity": "low"
}
http_header headers 81755e766bd90e75f0ce24dcb863acce199eda94a0d55ff91592fe86cc023141
[
    "max-age=16000000"
]
mail_policy_flag mail_trust f70887aa14c6faed822fae211ee733907cd4669d338428ad61bccc8ebcf26519
false
module_finding transparency e7a3bd5fff903d30b73646dc177452f2397b0d19d6c5170307c2f58baf2a7e1b
{
    "evidence": 404,
    "severity": "medium"
}
module_finding headers 5b5d7fe2c53428472153d955f99e02da68976acf39166d565c8a473edf6f8248
{
    "evidence": null,
    "severity": "low"
}
module_finding dns ece8b640995503edd3b42ad7b107f2a37bd0a87b0271a1db079ce7cbacb0dc5b
{
    "evidence": null,
    "severity": "low"
}
mail_policy_flag mail_trust 6844b8711b7ed52ba4df4f2bd2662e1b5c5521f005302691fca3ece7a763e90a
false
module_finding headers 069a3a6a08fc7f15289e03b2407344855fd2fd0638342849d8bb7f2d903c5d5d
{
    "evidence": null,
    "severity": "medium"
}
module_finding dns f5a826b637d63e2fc1b4cd37dec73aa6e129ef5060050833954c8c4e6ef2d9a1
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
module_finding resilience 456d53beec53a14901667abb04db4c5cdb89ecb9f373543c156f61deb138ea53
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "medium"
}
module_finding headers 9827c156a712d8476ed08edaf944d1b6f5b4578e9cccf83a799c352ddea0a877
{
    "evidence": "max-age=16000000",
    "severity": "low"
}
dns_address dns 1afd5b0b3f3b65886ccee8062eb3da5f8fa638fb7c91ee2a52de8a26f6370ccf
"2001:1600::aaaa:0:0:80:5a"
tls_issuer tls 7b1b05455571c2663659d20eb9dd76ea4be06b3e511723175a19ee8da08bcd07
"C = US, O = Let's Encrypt, CN = YR1"
dmarc_policy mail_trust 5434ba9d5a056312098a7a7dfe83d4dc60c35cb4e22beb89531df0f8beb24168
"reject"
module_finding headers 93d596e1ac0e33aa286f39d4563d92ee2aebaa00834829f0d3dec429aa00def3
{
    "evidence": null,
    "severity": "medium"
}
module_finding dns 4f2334cec3f76543e19c38d503980f409a2987ee05ec58cdaedcf8d88f0e8a2b
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
dmarc_record dns 57a8e7082fd4431add777a5f505c09b1f2c1665ff0b3c417bea286d3728dd981
"v=DMARC1; p=reject;"
tls_valid_to tls 109b7f1905c0ca8ee773baef7f1f8c630be721d221777533679548a6d84f8947
"2026-09-30T02:12:44+00:00"
spf_record dns 54eab531534a3c12a1e3dde3468339e00aba7b1c8048de5e302b23f029c33ab7
"v=spf1 include:spf.infomaniak.ch -all"
module_finding headers ec61b3916449a45cfc69bda3c9be74a171bf08a86473375d6b1297c37468101c
{
    "evidence": null,
    "severity": "critical"
}
dns_nameserver dns d4aadcd251c70bed20de983e05bff269ebe02e20793e5159639231bfe26faff6
"ns11.infomaniak.ch"
module_finding headers 46dab24fd5239254ba2a8d47d686ae75649b3a09862f1f1997fc7dc25ca9804a
{
    "evidence": null,
    "severity": "low"
}
mail_policy_flag mail_trust 2cde402e4e4871d40f09ba2fce5d06594419caffdeb204d289c2460ede533739
false
module_finding headers 96a5e4810c225fc5a68d5ddedc8cedbd1b2cbea08860ba7b12d3699d1f2cd2b2
{
    "evidence": null,
    "severity": "info"
}
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

35evidence
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
35
Signals
3
Changes
0
module_finding mail_trust 1d0ecd61fc0fca902cbb57c3dda97fe543d3eee5a05228d888513d7dc14d6d7b
{
    "evidence": [
        {
            "host": "mta-gw.infomaniak.ch",
            "priority": 5
        }
    ],
    "severity": "low"
}
http_header headers 81755e766bd90e75f0ce24dcb863acce199eda94a0d55ff91592fe86cc023141
[
    "max-age=16000000"
]
dependency_provider dependencies 6b6c76308a7501bd1a0dec43ae6a3e0d95e20c71f8bfea52d088272939f457d9
{
    "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_policy_flag mail_trust f70887aa14c6faed822fae211ee733907cd4669d338428ad61bccc8ebcf26519
false
module_finding transparency e7a3bd5fff903d30b73646dc177452f2397b0d19d6c5170307c2f58baf2a7e1b
{
    "evidence": 404,
    "severity": "medium"
}
module_finding headers 5b5d7fe2c53428472153d955f99e02da68976acf39166d565c8a473edf6f8248
{
    "evidence": null,
    "severity": "low"
}
module_finding dns ece8b640995503edd3b42ad7b107f2a37bd0a87b0271a1db079ce7cbacb0dc5b
{
    "evidence": null,
    "severity": "low"
}
mail_policy_flag mail_trust 6844b8711b7ed52ba4df4f2bd2662e1b5c5521f005302691fca3ece7a763e90a
false
module_finding headers 069a3a6a08fc7f15289e03b2407344855fd2fd0638342849d8bb7f2d903c5d5d
{
    "evidence": null,
    "severity": "medium"
}
module_finding dns f5a826b637d63e2fc1b4cd37dec73aa6e129ef5060050833954c8c4e6ef2d9a1
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
module_finding resilience 456d53beec53a14901667abb04db4c5cdb89ecb9f373543c156f61deb138ea53
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "medium"
}
module_finding headers 9827c156a712d8476ed08edaf944d1b6f5b4578e9cccf83a799c352ddea0a877
{
    "evidence": "max-age=16000000",
    "severity": "low"
}
dns_address dns 1afd5b0b3f3b65886ccee8062eb3da5f8fa638fb7c91ee2a52de8a26f6370ccf
"2001:1600::aaaa:0:0:80:5a"
tls_issuer tls 7b1b05455571c2663659d20eb9dd76ea4be06b3e511723175a19ee8da08bcd07
"C = US, O = Let's Encrypt, CN = YR1"
dmarc_policy mail_trust 5434ba9d5a056312098a7a7dfe83d4dc60c35cb4e22beb89531df0f8beb24168
"reject"
module_finding headers 93d596e1ac0e33aa286f39d4563d92ee2aebaa00834829f0d3dec429aa00def3
{
    "evidence": null,
    "severity": "medium"
}
module_finding dns 4f2334cec3f76543e19c38d503980f409a2987ee05ec58cdaedcf8d88f0e8a2b
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
dmarc_record dns 57a8e7082fd4431add777a5f505c09b1f2c1665ff0b3c417bea286d3728dd981
"v=DMARC1; p=reject;"
tls_valid_to tls 109b7f1905c0ca8ee773baef7f1f8c630be721d221777533679548a6d84f8947
"2026-09-30T02:12:44+00:00"
spf_record dns 54eab531534a3c12a1e3dde3468339e00aba7b1c8048de5e302b23f029c33ab7
"v=spf1 include:spf.infomaniak.ch -all"
module_finding headers ec61b3916449a45cfc69bda3c9be74a171bf08a86473375d6b1297c37468101c
{
    "evidence": null,
    "severity": "critical"
}
dns_nameserver dns d4aadcd251c70bed20de983e05bff269ebe02e20793e5159639231bfe26faff6
"ns11.infomaniak.ch"
module_finding headers 46dab24fd5239254ba2a8d47d686ae75649b3a09862f1f1997fc7dc25ca9804a
{
    "evidence": null,
    "severity": "low"
}
mail_policy_flag mail_trust 2cde402e4e4871d40f09ba2fce5d06594419caffdeb204d289c2460ede533739
false

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 alphatraining64.fr

DNS

2
DNS server Observed

ns12.infomaniak.ch

DNS server Observed

ns11.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

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

35evidence 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": [ { "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:35:04+00:00

#02 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=16000000" ]
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=16000000"
]

Rule 2026.09.4 · 2026-09-04T19:35:04+00:00

#03 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:35:04+00:00

#04 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:35:04+00:00

#05 Public transparency endpoint

Evidence: module_finding

Public artefacts such as security.txt make some technical processes verifiable.

Passive Medium
Why it matters

A documented reporting channel supports responsible coordination when an issue is found.

What to check next

Check expiry, contact, Canonical, Policy, Encryption and any signature. Compare the file with previous scans.

Possible action

Publish a compliant security.txt only when a real handling channel exists, keep it current, and align contacts with the internal reporting process.

Observation
{ "evidence": 404, "severity": "medium" }
Understand
Public transparency artefact inspection
Source
Public transparency endpoint
Reliability
Medium
What this supports
Describe published disclosure mechanisms
What this does not prove
A file being present does not prove response speed or overall organizational maturity.

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": 404,
    "severity": "medium"
}

Rule 2026.09.4 · 2026-09-04T19:35:04+00:00

#06 Public HTTP response

Evidence: module_finding

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
{ "evidence": null, "severity": "low" }
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
{
    "evidence": null,
    "severity": "low"
}

Rule 2026.09.4 · 2026-09-04T19:35:04+00:00

#07 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": null, "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": null,
    "severity": "low"
}

Rule 2026.09.4 · 2026-09-04T19:35:04+00:00

#08 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:35:04+00:00

#09 Public HTTP response

Evidence: module_finding

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
{ "evidence": null, "severity": "medium" }
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
{
    "evidence": null,
    "severity": "medium"
}

Rule 2026.09.4 · 2026-09-04T19:35:04+00:00

#10 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:35:04+00:00

#11 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:35:04+00:00

#12 Public HTTP response

Evidence: module_finding

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
{ "evidence": "max-age=16000000", "severity": "low" }
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
{
    "evidence": "max-age=16000000",
    "severity": "low"
}

Rule 2026.09.4 · 2026-09-04T19:35:04+00:00

#13 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:5a
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 alphatraining64.fr && dig AAAA alphatraining64.fr
View raw data
2001:1600::aaaa:0:0:80:5a

Rule 2026.09.4 · 2026-09-04T19:35:04+00:00

#14 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 alphatraining64.fr:443 -servername alphatraining64.fr </dev/null
View raw data
C = US, O = Let's Encrypt, CN = YR1

Rule 2026.09.4 · 2026-09-04T19:35:04+00:00

#15 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.alphatraining64.fr
View raw data
reject

Rule 2026.09.4 · 2026-09-04T19:35:04+00:00

#16 Public HTTP response

Evidence: module_finding

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
{ "evidence": null, "severity": "medium" }
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
{
    "evidence": null,
    "severity": "medium"
}

Rule 2026.09.4 · 2026-09-04T19:35:04+00:00

#17 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:35:04+00:00

#18 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:35:04+00:00

#19 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-09-30T02:12:44+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-09-30T02:12:44+00:00

Rule 2026.09.4 · 2026-09-04T19:35:04+00:00

#20 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:35:04+00:00

#21 Public HTTP response

Evidence: module_finding

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
{ "evidence": null, "severity": "critical" }
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
{
    "evidence": null,
    "severity": "critical"
}

Rule 2026.09.4 · 2026-09-04T19:35:04+00:00

#22 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 alphatraining64.fr
View raw data
ns11.infomaniak.ch

Rule 2026.09.4 · 2026-09-04T19:35:04+00:00

#23 Public HTTP response

Evidence: module_finding

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
{ "evidence": null, "severity": "low" }
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
{
    "evidence": null,
    "severity": "low"
}

Rule 2026.09.4 · 2026-09-04T19:35:04+00:00

#24 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:35:04+00:00

#25 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:35:04+00:00

#26 Public HTTP response

Evidence: module_finding

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
{ "evidence": null, "severity": "info" }
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
{
    "evidence": null,
    "severity": "info"
}

Rule 2026.09.4 · 2026-09-04T19:35:04+00:00

#27 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 alphatraining64.fr
View raw data
hardfail

Rule 2026.09.4 · 2026-09-04T19:35:04+00:00

#28 Public HTTP response

Evidence: module_finding

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
{ "evidence": null, "severity": "high" }
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
{
    "evidence": null,
    "severity": "high"
}

Rule 2026.09.4 · 2026-09-04T19:35:04+00:00

#29 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:35:04+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
[ "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:35:04+00:00

#31 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 alphatraining64.fr
View raw data
ns12.infomaniak.ch

Rule 2026.09.4 · 2026-09-04T19:35:04+00:00

#32 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 alphatraining64.fr
View raw data
mta-gw.infomaniak.ch

Rule 2026.09.4 · 2026-09-04T19:35:04+00:00

#33 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.195
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 alphatraining64.fr && dig AAAA alphatraining64.fr
View raw data
185.125.27.195

Rule 2026.09.4 · 2026-09-04T19:35:04+00:00

#34 Public HTTP response

Evidence: module_finding

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
{ "evidence": null, "severity": "low" }
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
{
    "evidence": null,
    "severity": "low"
}

Rule 2026.09.4 · 2026-09-04T19:35:04+00:00

#35 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:35:04+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": "d758e8056be4544d3f5197838a2772032cd7c76a136f6c1427bb3f58bd2d6108",
        "display_name": "alphatraining64.fr",
        "slug": "alphatraining64-fr",
        "entity_type": "domain_subject",
        "auto_created": true,
        "primary_asset": "alphatraining64.fr"
    },
    "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": 35,
        "evidence_count": 35,
        "provider_count": 1,
        "strategic_signal_count": 1,
        "top_signal_count": 1
    }
}