PUBLIC DOMAIN DOSSIER

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

40 useful changes are retained since the previous reading.

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

Measured 2026-09-06 01:58 UTC First observation 2026-09-04 20:04 UTC Latest observation 2026-09-06 01:58 UTC
History Compare JSON Markdown

TIME

What changed over time

Compared with the previous stored reading

14Appeared
2Modified
25Stable
24Disappeared
New

Canary signal

New

Csp evidence

Disappeared

Dependency provider

Disappeared

Dependency provider

Disappeared

Dependency provider

Disappeared

Dependency provider

SHORT VIEW

Four readings before the detail

The 12 historical angles remain available below for deeper inspection.

Identity & governance

  • Not observable from outsideOrigin host
  • To confirmCanary detection
  • To confirmOpenpgp

Infrastructure & transport

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

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

Measured on 2026-09-06 01:58 UTC Engine 2.9.2.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.

Changed

Canary signal

Not observedStructured value changed

Changed

Csp evidence

Not observedStructured value changed

Changed

Provider dependency

CloudflareNot observed

Changed

Provider dependency

formspree.ioNot observed

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 Change observed

Domain identity

Public evidence provides enough material to document this angle

Angle 01

Domain identity

Documented Change observed

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
9changes
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
9
module_finding dns d2262957ddc1a54a6fbe4150df5642764832ae691b7cdf822d997de9bde891e6
{
    "evidence": {
        "reason": "No external validating resolver is used; cryptographic validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
module_finding dns 0a8357527614c71911971cd2bd7c8298089529f20d71ce3c6418f3d55168c2ed
{
    "evidence": null,
    "severity": "low"
}
dns_nameserver dns fe4ee14a5c1362db83cae82716482b4ef3256d9ed717fb0fbba94f57bcc567f6
"ns12.infomaniak.ch"
mail_exchanger dns 6aa9fa9d739df72d315dc69a2157a2c275788c88e4e8f03e4b5aa84dc5829816
"mta-gw.infomaniak.ch"
dns_nameserver dns 72ee9d4fdc0ea7c10eaf7caceb5c10bfca69aeea184ce3f577ffd0c2c5c5b991
"ns11.infomaniak.ch"
module_finding dns de062920a43f206533f9ff956441a57f55f0d5d977e9026b36c27a8ba9826ffd
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
dmarc_record dns 835bec594fc98290188ac35aa0ee8b7062d74f53dba5095ffab97491faf3e014
"v=DMARC1; p=reject;"
spf_record dns b14d59dc6cc8afc330ea6191ba959db10598d4b84f48ca04166c814dad95625f
"v=spf1 include:spf.infomaniak.ch -all"
dns_address dns 431e586d8dc21429fce7e8c1d809284919ff52537703d1741cb06961a30c3643
"2001:1600::aaaa:0:0:80:5a"
dns_address dns 3b5471adab339ffd600c9a2d939559542d41bf984862950ec5d747279ffd628f
"185.125.27.195"
02
Documented Change observed

Infrastructure

Public evidence provides enough material to document this angle

Angle 02

Infrastructure

Documented Change observed

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
12changes
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
12

Unknowns and limitations

2 items still require qualification

module_finding dns d2262957ddc1a54a6fbe4150df5642764832ae691b7cdf822d997de9bde891e6
{
    "evidence": {
        "reason": "No external validating resolver is used; cryptographic validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
module_finding resilience 3f8e66950ae1ab6fb85e4a709c49fd2d95307b6bdbd03b275ea5111971fe9476
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "medium"
}
module_finding dns 0a8357527614c71911971cd2bd7c8298089529f20d71ce3c6418f3d55168c2ed
{
    "evidence": null,
    "severity": "low"
}
dns_nameserver dns fe4ee14a5c1362db83cae82716482b4ef3256d9ed717fb0fbba94f57bcc567f6
"ns12.infomaniak.ch"
mail_exchanger dns 6aa9fa9d739df72d315dc69a2157a2c275788c88e4e8f03e4b5aa84dc5829816
"mta-gw.infomaniak.ch"
dns_nameserver dns 72ee9d4fdc0ea7c10eaf7caceb5c10bfca69aeea184ce3f577ffd0c2c5c5b991
"ns11.infomaniak.ch"
module_finding dns de062920a43f206533f9ff956441a57f55f0d5d977e9026b36c27a8ba9826ffd
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
dmarc_record dns 835bec594fc98290188ac35aa0ee8b7062d74f53dba5095ffab97491faf3e014
"v=DMARC1; p=reject;"
spf_record dns b14d59dc6cc8afc330ea6191ba959db10598d4b84f48ca04166c814dad95625f
"v=spf1 include:spf.infomaniak.ch -all"
dependency_provider dependencies 2a29c8a881892fc8aa98d643422b21022987b7bcb636cf48e6f1762b88b69bea
{
    "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
}
dns_address dns 431e586d8dc21429fce7e8c1d809284919ff52537703d1741cb06961a30c3643
"2001:1600::aaaa:0:0:80:5a"
dns_address dns 3b5471adab339ffd600c9a2d939559542d41bf984862950ec5d747279ffd628f
"185.125.27.195"
03
Documented Change observed

Encryption and transport

Public evidence provides enough material to document this angle

Angle 03

Encryption and transport

Documented Change observed

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
17changes
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
17
tls_valid_to tls 14f53828e0c358ce6af0f60d1bb7acf4407d9b4c2e07aa64f95cb70fb557779c
"2026-10-10T22:06:56+00:00"
http_header headers 9919b71666a6d5ec323da38938248304c6a9a1cf014eba38f20298c9eb1c9cc6
[
    "Apache"
]
http_header headers b424d9591fe23f8239f38d8f36043905e70477fa36c99ca402cc3e1495f9be41
[
    "DENY"
]
http_header headers d49fc28b6ac8edebc38804b8ba13f3fdc38d8e0c57649ac22e789ca1a3944c95
[
    "same-origin"
]
http_header headers 76384d1531b17bd8a82e9ff3aaeb1882dad43d6e72dfa62c3214a99ead7effec
[
    "same-origin"
]
http_header headers 46b1459e43254af92a7faf2bc056463c85ff55382fc015a36dc071b88998d7e3
[
    "strict-origin-when-cross-origin"
]
http_header headers 227dc6f501b71d82f9a79673c197ac8896c96513f279cdc713c751b5f96654bd
[
    "max-age=63072000; includeSubDomains; preload"
]
http_header headers 1e6794682d19880f0b8e2de92013ad293cab940040606a04069a49c786d0de37
[
    "camera=(), geolocation=(), microphone=(), payment=(), usb=(), browsing-topics=()"
]
http_header headers dd4805e8095982d431a55f6f9a511f46cf6a1af265ac6dfb781a83bb32b38a8f
[
    "nosniff"
]
http_header headers 7c035687678c697dece063f114c78493ad352bd12d492579784f3a0bb9997903
[
    "default-src 'none'; base-uri 'none'; connect-src 'none'; font-src 'self'; form-action 'none'; frame-ancestors 'none'; img-src 'self' data:; manifest-src 'self'; media-src 'none'; object-src 'none'; script-src 'self' 'nonce-fOgiln7blLtwRLx5kx8zEg69'; style-src 'self'; worker-src 'none'"
]
tls_issuer tls 0dfef6f8dffd7e48c5cd8aab82eabb360b338875c0693a12b1185bb47cc54f2a
"C = US, O = Let's Encrypt, CN = YR2"
module_finding headers 1347d1fb9eaf9ca107370a1774fb4b914a115562a9513eb631f36ac14fe1e507
{
    "evidence": null,
    "severity": "info"
}
04
Documented Change observed

Mail and trust

Public evidence provides enough material to document this angle

Angle 04

Mail and trust

Documented Change observed

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
12changes
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
12
module_finding mail_trust 50836183a6632e43bad3c32aad9339a2af2e7faf2ab9a4d02dd0eab564f4dc77
{
    "evidence": null,
    "severity": "low"
}
mail_policy_flag mail_trust 4e22812df6e67f96e674045f289122b84bc1c06ec4f07fa96fac161c77ce96d7
false
module_finding dns d2262957ddc1a54a6fbe4150df5642764832ae691b7cdf822d997de9bde891e6
{
    "evidence": {
        "reason": "No external validating resolver is used; cryptographic validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
module_finding dns 0a8357527614c71911971cd2bd7c8298089529f20d71ce3c6418f3d55168c2ed
{
    "evidence": null,
    "severity": "low"
}
dns_nameserver dns fe4ee14a5c1362db83cae82716482b4ef3256d9ed717fb0fbba94f57bcc567f6
"ns12.infomaniak.ch"
dmarc_policy mail_trust 63ce8f9b54b57d943975c2aae21fa2133d4edfbefb539cb56a1fa16cf923c266
"reject"
mail_exchanger dns 6aa9fa9d739df72d315dc69a2157a2c275788c88e4e8f03e4b5aa84dc5829816
"mta-gw.infomaniak.ch"
dns_nameserver dns 72ee9d4fdc0ea7c10eaf7caceb5c10bfca69aeea184ce3f577ffd0c2c5c5b991
"ns11.infomaniak.ch"
module_finding dns de062920a43f206533f9ff956441a57f55f0d5d977e9026b36c27a8ba9826ffd
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
dmarc_record dns 835bec594fc98290188ac35aa0ee8b7062d74f53dba5095ffab97491faf3e014
"v=DMARC1; p=reject;"
module_finding mail_trust 252bd91dca255921f6e054ee88b07418464d6f6e6172ea65887f32eb23f37fea
{
    "evidence": [
        {
            "host": "mta-gw.infomaniak.ch",
            "priority": 5
        }
    ],
    "severity": "low"
}
mail_policy_flag mail_trust 262f48316ea7420747986d5eebd4b7aa7c98ccef2bed3b79b251faff84109963
false
module_finding mail_trust c357fb078c5748397fec72a6bcc2af8b0e8c0d3d3922cb7a65bd3c94073e911e
{
    "evidence": null,
    "severity": "low"
}
spf_record dns b14d59dc6cc8afc330ea6191ba959db10598d4b84f48ca04166c814dad95625f
"v=spf1 include:spf.infomaniak.ch -all"
dns_address dns 431e586d8dc21429fce7e8c1d809284919ff52537703d1741cb06961a30c3643
"2001:1600::aaaa:0:0:80:5a"
dns_address dns 3b5471adab339ffd600c9a2d939559542d41bf984862950ec5d747279ffd628f
"185.125.27.195"
spf_policy mail_trust 70a76fb0da5ca39ec5dd4b0d81aa5ce22b72c6c2ec4249b8173a0e7ffffdc505
"hardfail"
mail_policy_flag mail_trust 1b916e5b0584617311f4b5fc0e60593cb61bd1a3aaed5474ca6c9d129da9074b
false
05
Documented Change observed

DNS and governance

Public evidence provides enough material to document this angle

Angle 05

DNS and governance

Documented Change observed

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
9changes
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
9
module_finding mail_trust 50836183a6632e43bad3c32aad9339a2af2e7faf2ab9a4d02dd0eab564f4dc77
{
    "evidence": null,
    "severity": "low"
}
mail_policy_flag mail_trust 4e22812df6e67f96e674045f289122b84bc1c06ec4f07fa96fac161c77ce96d7
false
module_finding dns d2262957ddc1a54a6fbe4150df5642764832ae691b7cdf822d997de9bde891e6
{
    "evidence": {
        "reason": "No external validating resolver is used; cryptographic validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
module_finding dns 0a8357527614c71911971cd2bd7c8298089529f20d71ce3c6418f3d55168c2ed
{
    "evidence": null,
    "severity": "low"
}
dns_nameserver dns fe4ee14a5c1362db83cae82716482b4ef3256d9ed717fb0fbba94f57bcc567f6
"ns12.infomaniak.ch"
dmarc_policy mail_trust 63ce8f9b54b57d943975c2aae21fa2133d4edfbefb539cb56a1fa16cf923c266
"reject"
mail_exchanger dns 6aa9fa9d739df72d315dc69a2157a2c275788c88e4e8f03e4b5aa84dc5829816
"mta-gw.infomaniak.ch"
dns_nameserver dns 72ee9d4fdc0ea7c10eaf7caceb5c10bfca69aeea184ce3f577ffd0c2c5c5b991
"ns11.infomaniak.ch"
module_finding dns de062920a43f206533f9ff956441a57f55f0d5d977e9026b36c27a8ba9826ffd
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
dmarc_record dns 835bec594fc98290188ac35aa0ee8b7062d74f53dba5095ffab97491faf3e014
"v=DMARC1; p=reject;"
module_finding mail_trust 252bd91dca255921f6e054ee88b07418464d6f6e6172ea65887f32eb23f37fea
{
    "evidence": [
        {
            "host": "mta-gw.infomaniak.ch",
            "priority": 5
        }
    ],
    "severity": "low"
}
mail_policy_flag mail_trust 262f48316ea7420747986d5eebd4b7aa7c98ccef2bed3b79b251faff84109963
false
module_finding mail_trust c357fb078c5748397fec72a6bcc2af8b0e8c0d3d3922cb7a65bd3c94073e911e
{
    "evidence": null,
    "severity": "low"
}
spf_record dns b14d59dc6cc8afc330ea6191ba959db10598d4b84f48ca04166c814dad95625f
"v=spf1 include:spf.infomaniak.ch -all"
dns_address dns 431e586d8dc21429fce7e8c1d809284919ff52537703d1741cb06961a30c3643
"2001:1600::aaaa:0:0:80:5a"
dns_address dns 3b5471adab339ffd600c9a2d939559542d41bf984862950ec5d747279ffd628f
"185.125.27.195"
spf_policy mail_trust 70a76fb0da5ca39ec5dd4b0d81aa5ce22b72c6c2ec4249b8173a0e7ffffdc505
"hardfail"
mail_policy_flag mail_trust 1b916e5b0584617311f4b5fc0e60593cb61bd1a3aaed5474ca6c9d129da9074b
false
06
Documented Change observed

External dependencies

Public evidence provides enough material to document this angle

Angle 06

External dependencies

Documented Change observed

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
12changes
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
12
module_finding dns d2262957ddc1a54a6fbe4150df5642764832ae691b7cdf822d997de9bde891e6
{
    "evidence": {
        "reason": "No external validating resolver is used; cryptographic validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
module_finding dns 0a8357527614c71911971cd2bd7c8298089529f20d71ce3c6418f3d55168c2ed
{
    "evidence": null,
    "severity": "low"
}
dns_nameserver dns fe4ee14a5c1362db83cae82716482b4ef3256d9ed717fb0fbba94f57bcc567f6
"ns12.infomaniak.ch"
mail_exchanger dns 6aa9fa9d739df72d315dc69a2157a2c275788c88e4e8f03e4b5aa84dc5829816
"mta-gw.infomaniak.ch"
dns_nameserver dns 72ee9d4fdc0ea7c10eaf7caceb5c10bfca69aeea184ce3f577ffd0c2c5c5b991
"ns11.infomaniak.ch"
module_finding dns de062920a43f206533f9ff956441a57f55f0d5d977e9026b36c27a8ba9826ffd
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
dmarc_record dns 835bec594fc98290188ac35aa0ee8b7062d74f53dba5095ffab97491faf3e014
"v=DMARC1; p=reject;"
spf_record dns b14d59dc6cc8afc330ea6191ba959db10598d4b84f48ca04166c814dad95625f
"v=spf1 include:spf.infomaniak.ch -all"
dependency_provider dependencies 2a29c8a881892fc8aa98d643422b21022987b7bcb636cf48e6f1762b88b69bea
{
    "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
}
dns_address dns 431e586d8dc21429fce7e8c1d809284919ff52537703d1741cb06961a30c3643
"2001:1600::aaaa:0:0:80:5a"
dns_address dns 3b5471adab339ffd600c9a2d939559542d41bf984862950ec5d747279ffd628f
"185.125.27.195"
07
Documented Change observed

Observable technologies

Public evidence provides enough material to document this angle

Angle 07

Observable technologies

Documented Change observed

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
2changes
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
2
http_header headers 9919b71666a6d5ec323da38938248304c6a9a1cf014eba38f20298c9eb1c9cc6
[
    "Apache"
]
technology technology 5088ed3027d8c04804f585e7ded389816e63ae09834c75aa21f3c9d9ec7efa48
{
    "name": "Apache",
    "version": "",
    "version_exposed": false
}
http_header headers b424d9591fe23f8239f38d8f36043905e70477fa36c99ca402cc3e1495f9be41
[
    "DENY"
]
http_header headers d49fc28b6ac8edebc38804b8ba13f3fdc38d8e0c57649ac22e789ca1a3944c95
[
    "same-origin"
]
http_header headers 76384d1531b17bd8a82e9ff3aaeb1882dad43d6e72dfa62c3214a99ead7effec
[
    "same-origin"
]
http_header headers 46b1459e43254af92a7faf2bc056463c85ff55382fc015a36dc071b88998d7e3
[
    "strict-origin-when-cross-origin"
]
http_header headers 227dc6f501b71d82f9a79673c197ac8896c96513f279cdc713c751b5f96654bd
[
    "max-age=63072000; includeSubDomains; preload"
]
http_header headers 1e6794682d19880f0b8e2de92013ad293cab940040606a04069a49c786d0de37
[
    "camera=(), geolocation=(), microphone=(), payment=(), usb=(), browsing-topics=()"
]
http_header headers dd4805e8095982d431a55f6f9a511f46cf6a1af265ac6dfb781a83bb32b38a8f
[
    "nosniff"
]
http_header headers 7c035687678c697dece063f114c78493ad352bd12d492579784f3a0bb9997903
[
    "default-src 'none'; base-uri 'none'; connect-src 'none'; font-src 'self'; form-action 'none'; frame-ancestors 'none'; img-src 'self' data:; manifest-src 'self'; media-src 'none'; object-src 'none'; script-src 'self' 'nonce-fOgiln7blLtwRLx5kx8zEg69'; style-src 'self'; worker-src 'none'"
]
module_finding headers 1347d1fb9eaf9ca107370a1774fb4b914a115562a9513eb631f36ac14fe1e507
{
    "evidence": null,
    "severity": "info"
}
08
Documented Change observed

Public exposure

Public evidence provides enough material to document this angle

Angle 08

Public exposure

Documented Change observed

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

17evidence
10changes
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
17
Signals
0
Changes
10
module_finding mail_trust 50836183a6632e43bad3c32aad9339a2af2e7faf2ab9a4d02dd0eab564f4dc77
{
    "evidence": null,
    "severity": "low"
}
http_header headers 9919b71666a6d5ec323da38938248304c6a9a1cf014eba38f20298c9eb1c9cc6
[
    "Apache"
]
module_finding dns d2262957ddc1a54a6fbe4150df5642764832ae691b7cdf822d997de9bde891e6
{
    "evidence": {
        "reason": "No external validating resolver is used; cryptographic validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
http_header headers b424d9591fe23f8239f38d8f36043905e70477fa36c99ca402cc3e1495f9be41
[
    "DENY"
]
http_header headers d49fc28b6ac8edebc38804b8ba13f3fdc38d8e0c57649ac22e789ca1a3944c95
[
    "same-origin"
]
module_finding resilience 3f8e66950ae1ab6fb85e4a709c49fd2d95307b6bdbd03b275ea5111971fe9476
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "medium"
}
http_header headers 76384d1531b17bd8a82e9ff3aaeb1882dad43d6e72dfa62c3214a99ead7effec
[
    "same-origin"
]
module_finding dns 0a8357527614c71911971cd2bd7c8298089529f20d71ce3c6418f3d55168c2ed
{
    "evidence": null,
    "severity": "low"
}
http_header headers 46b1459e43254af92a7faf2bc056463c85ff55382fc015a36dc071b88998d7e3
[
    "strict-origin-when-cross-origin"
]
http_header headers 227dc6f501b71d82f9a79673c197ac8896c96513f279cdc713c751b5f96654bd
[
    "max-age=63072000; includeSubDomains; preload"
]
http_header headers 1e6794682d19880f0b8e2de92013ad293cab940040606a04069a49c786d0de37
[
    "camera=(), geolocation=(), microphone=(), payment=(), usb=(), browsing-topics=()"
]
module_finding dns de062920a43f206533f9ff956441a57f55f0d5d977e9026b36c27a8ba9826ffd
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
module_finding mail_trust 252bd91dca255921f6e054ee88b07418464d6f6e6172ea65887f32eb23f37fea
{
    "evidence": [
        {
            "host": "mta-gw.infomaniak.ch",
            "priority": 5
        }
    ],
    "severity": "low"
}
http_header headers dd4805e8095982d431a55f6f9a511f46cf6a1af265ac6dfb781a83bb32b38a8f
[
    "nosniff"
]
module_finding mail_trust c357fb078c5748397fec72a6bcc2af8b0e8c0d3d3922cb7a65bd3c94073e911e
{
    "evidence": null,
    "severity": "low"
}
http_header headers 7c035687678c697dece063f114c78493ad352bd12d492579784f3a0bb9997903
[
    "default-src 'none'; base-uri 'none'; connect-src 'none'; font-src 'self'; form-action 'none'; frame-ancestors 'none'; img-src 'self' data:; manifest-src 'self'; media-src 'none'; object-src 'none'; script-src 'self' 'nonce-fOgiln7blLtwRLx5kx8zEg69'; style-src 'self'; worker-src 'none'"
]
module_finding headers 1347d1fb9eaf9ca107370a1774fb4b914a115562a9513eb631f36ac14fe1e507
{
    "evidence": null,
    "severity": "info"
}
09
Documented Change observed

Documentary trust

Public evidence provides enough material to document this angle

Angle 09

Documentary trust

Documented Change observed

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

17evidence
4changes
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
17
Signals
0
Changes
4
module_finding mail_trust 50836183a6632e43bad3c32aad9339a2af2e7faf2ab9a4d02dd0eab564f4dc77
{
    "evidence": null,
    "severity": "low"
}
http_header headers 9919b71666a6d5ec323da38938248304c6a9a1cf014eba38f20298c9eb1c9cc6
[
    "Apache"
]
module_finding dns d2262957ddc1a54a6fbe4150df5642764832ae691b7cdf822d997de9bde891e6
{
    "evidence": {
        "reason": "No external validating resolver is used; cryptographic validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
http_header headers b424d9591fe23f8239f38d8f36043905e70477fa36c99ca402cc3e1495f9be41
[
    "DENY"
]
http_header headers d49fc28b6ac8edebc38804b8ba13f3fdc38d8e0c57649ac22e789ca1a3944c95
[
    "same-origin"
]
module_finding resilience 3f8e66950ae1ab6fb85e4a709c49fd2d95307b6bdbd03b275ea5111971fe9476
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "medium"
}
http_header headers 76384d1531b17bd8a82e9ff3aaeb1882dad43d6e72dfa62c3214a99ead7effec
[
    "same-origin"
]
module_finding dns 0a8357527614c71911971cd2bd7c8298089529f20d71ce3c6418f3d55168c2ed
{
    "evidence": null,
    "severity": "low"
}
http_header headers 46b1459e43254af92a7faf2bc056463c85ff55382fc015a36dc071b88998d7e3
[
    "strict-origin-when-cross-origin"
]
http_header headers 227dc6f501b71d82f9a79673c197ac8896c96513f279cdc713c751b5f96654bd
[
    "max-age=63072000; includeSubDomains; preload"
]
http_header headers 1e6794682d19880f0b8e2de92013ad293cab940040606a04069a49c786d0de37
[
    "camera=(), geolocation=(), microphone=(), payment=(), usb=(), browsing-topics=()"
]
module_finding dns de062920a43f206533f9ff956441a57f55f0d5d977e9026b36c27a8ba9826ffd
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
module_finding mail_trust 252bd91dca255921f6e054ee88b07418464d6f6e6172ea65887f32eb23f37fea
{
    "evidence": [
        {
            "host": "mta-gw.infomaniak.ch",
            "priority": 5
        }
    ],
    "severity": "low"
}
http_header headers dd4805e8095982d431a55f6f9a511f46cf6a1af265ac6dfb781a83bb32b38a8f
[
    "nosniff"
]
module_finding mail_trust c357fb078c5748397fec72a6bcc2af8b0e8c0d3d3922cb7a65bd3c94073e911e
{
    "evidence": null,
    "severity": "low"
}
http_header headers 7c035687678c697dece063f114c78493ad352bd12d492579784f3a0bb9997903
[
    "default-src 'none'; base-uri 'none'; connect-src 'none'; font-src 'self'; form-action 'none'; frame-ancestors 'none'; img-src 'self' data:; manifest-src 'self'; media-src 'none'; object-src 'none'; script-src 'self' 'nonce-fOgiln7blLtwRLx5kx8zEg69'; style-src 'self'; worker-src 'none'"
]
module_finding headers 1347d1fb9eaf9ca107370a1774fb4b914a115562a9513eb631f36ac14fe1e507
{
    "evidence": null,
    "severity": "info"
}
10
Documented Change observed

Security signals

Public evidence provides enough material to document this angle

Angle 10

Security signals

Documented Change observed

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
33changes
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
31
Signals
2
Changes
33
module_finding mail_trust 50836183a6632e43bad3c32aad9339a2af2e7faf2ab9a4d02dd0eab564f4dc77
{
    "evidence": null,
    "severity": "low"
}
tls_valid_to tls 14f53828e0c358ce6af0f60d1bb7acf4407d9b4c2e07aa64f95cb70fb557779c
"2026-10-10T22:06:56+00:00"
http_header headers 9919b71666a6d5ec323da38938248304c6a9a1cf014eba38f20298c9eb1c9cc6
[
    "Apache"
]
mail_policy_flag mail_trust 4e22812df6e67f96e674045f289122b84bc1c06ec4f07fa96fac161c77ce96d7
false
module_finding dns d2262957ddc1a54a6fbe4150df5642764832ae691b7cdf822d997de9bde891e6
{
    "evidence": {
        "reason": "No external validating resolver is used; cryptographic validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
http_header headers b424d9591fe23f8239f38d8f36043905e70477fa36c99ca402cc3e1495f9be41
[
    "DENY"
]
http_header headers d49fc28b6ac8edebc38804b8ba13f3fdc38d8e0c57649ac22e789ca1a3944c95
[
    "same-origin"
]
module_finding resilience 3f8e66950ae1ab6fb85e4a709c49fd2d95307b6bdbd03b275ea5111971fe9476
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "medium"
}
http_header headers 76384d1531b17bd8a82e9ff3aaeb1882dad43d6e72dfa62c3214a99ead7effec
[
    "same-origin"
]
module_finding dns 0a8357527614c71911971cd2bd7c8298089529f20d71ce3c6418f3d55168c2ed
{
    "evidence": null,
    "severity": "low"
}
http_header headers 46b1459e43254af92a7faf2bc056463c85ff55382fc015a36dc071b88998d7e3
[
    "strict-origin-when-cross-origin"
]
dns_nameserver dns fe4ee14a5c1362db83cae82716482b4ef3256d9ed717fb0fbba94f57bcc567f6
"ns12.infomaniak.ch"
dmarc_policy mail_trust 63ce8f9b54b57d943975c2aae21fa2133d4edfbefb539cb56a1fa16cf923c266
"reject"
http_header headers 227dc6f501b71d82f9a79673c197ac8896c96513f279cdc713c751b5f96654bd
[
    "max-age=63072000; includeSubDomains; preload"
]
mail_exchanger dns 6aa9fa9d739df72d315dc69a2157a2c275788c88e4e8f03e4b5aa84dc5829816
"mta-gw.infomaniak.ch"
dns_nameserver dns 72ee9d4fdc0ea7c10eaf7caceb5c10bfca69aeea184ce3f577ffd0c2c5c5b991
"ns11.infomaniak.ch"
http_header headers 1e6794682d19880f0b8e2de92013ad293cab940040606a04069a49c786d0de37
[
    "camera=(), geolocation=(), microphone=(), payment=(), usb=(), browsing-topics=()"
]
module_finding dns de062920a43f206533f9ff956441a57f55f0d5d977e9026b36c27a8ba9826ffd
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
dmarc_record dns 835bec594fc98290188ac35aa0ee8b7062d74f53dba5095ffab97491faf3e014
"v=DMARC1; p=reject;"
module_finding mail_trust 252bd91dca255921f6e054ee88b07418464d6f6e6172ea65887f32eb23f37fea
{
    "evidence": [
        {
            "host": "mta-gw.infomaniak.ch",
            "priority": 5
        }
    ],
    "severity": "low"
}
http_header headers dd4805e8095982d431a55f6f9a511f46cf6a1af265ac6dfb781a83bb32b38a8f
[
    "nosniff"
]
mail_policy_flag mail_trust 262f48316ea7420747986d5eebd4b7aa7c98ccef2bed3b79b251faff84109963
false
module_finding mail_trust c357fb078c5748397fec72a6bcc2af8b0e8c0d3d3922cb7a65bd3c94073e911e
{
    "evidence": null,
    "severity": "low"
}
http_header headers 7c035687678c697dece063f114c78493ad352bd12d492579784f3a0bb9997903
[
    "default-src 'none'; base-uri 'none'; connect-src 'none'; font-src 'self'; form-action 'none'; frame-ancestors 'none'; img-src 'self' data:; manifest-src 'self'; media-src 'none'; object-src 'none'; script-src 'self' 'nonce-fOgiln7blLtwRLx5kx8zEg69'; style-src 'self'; worker-src 'none'"
]
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
65changes
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
65
12
Documented Stable

Evidence and traceability

Public evidence provides enough material to document this angle

Angle 12

Evidence and traceability

Documented Stable

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

40evidence
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
40
Signals
3
Changes
0
canary_signal canary_passive e0cfb8b63b52ae4a83463c681669b8deb1b0af94865876dead64ac35a7e06d7c
{
    "matches": [],
    "reason": "no_known_passive_signature_observed",
    "signature_version": "2026.09.1",
    "state": "not_observed"
}
module_finding mail_trust 50836183a6632e43bad3c32aad9339a2af2e7faf2ab9a4d02dd0eab564f4dc77
{
    "evidence": null,
    "severity": "low"
}
tls_valid_to tls 14f53828e0c358ce6af0f60d1bb7acf4407d9b4c2e07aa64f95cb70fb557779c
"2026-10-10T22:06:56+00:00"
http_header headers 9919b71666a6d5ec323da38938248304c6a9a1cf014eba38f20298c9eb1c9cc6
[
    "Apache"
]
technology technology 5088ed3027d8c04804f585e7ded389816e63ae09834c75aa21f3c9d9ec7efa48
{
    "name": "Apache",
    "version": "",
    "version_exposed": false
}
mail_policy_flag mail_trust 4e22812df6e67f96e674045f289122b84bc1c06ec4f07fa96fac161c77ce96d7
false
module_finding dns d2262957ddc1a54a6fbe4150df5642764832ae691b7cdf822d997de9bde891e6
{
    "evidence": {
        "reason": "No external validating resolver is used; cryptographic validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
http_header headers b424d9591fe23f8239f38d8f36043905e70477fa36c99ca402cc3e1495f9be41
[
    "DENY"
]
http_header headers d49fc28b6ac8edebc38804b8ba13f3fdc38d8e0c57649ac22e789ca1a3944c95
[
    "same-origin"
]
openpgp_discovery openpgp_discovery 239f4fe5491569e71fad3c28d3af14ebff1846ab7afb8fac082ae3383a91dd3e
{
    "dns_openpgpkey": {
        "reason": "recipient_identity_required",
        "state": "untested"
    },
    "fingerprint": null,
    "mechanisms": [],
    "reason": "security_txt_encryption_not_observed",
    "state": "not_observed",
    "wkd": {
        "reason": "wkd_not_fetched_without_identity",
        "state": "untested"
    }
}
module_finding resilience 3f8e66950ae1ab6fb85e4a709c49fd2d95307b6bdbd03b275ea5111971fe9476
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "medium"
}
http_header headers 76384d1531b17bd8a82e9ff3aaeb1882dad43d6e72dfa62c3214a99ead7effec
[
    "same-origin"
]
module_finding dns 0a8357527614c71911971cd2bd7c8298089529f20d71ce3c6418f3d55168c2ed
{
    "evidence": null,
    "severity": "low"
}
http_header headers 46b1459e43254af92a7faf2bc056463c85ff55382fc015a36dc071b88998d7e3
[
    "strict-origin-when-cross-origin"
]
dns_nameserver dns fe4ee14a5c1362db83cae82716482b4ef3256d9ed717fb0fbba94f57bcc567f6
"ns12.infomaniak.ch"
dmarc_policy mail_trust 63ce8f9b54b57d943975c2aae21fa2133d4edfbefb539cb56a1fa16cf923c266
"reject"
post_quantum_tls pq_tls_probe 2223fe764a87f58549f298574437d77028c32a04594ce38aad2b35abd0c6c2ab
{
    "capability": {
        "capable": false,
        "groups": [],
        "reason": "proc_open_unavailable"
    },
    "group": null,
    "reason": "client_capability_unavailable",
    "state": "untested"
}
http_header headers 227dc6f501b71d82f9a79673c197ac8896c96513f279cdc713c751b5f96654bd
[
    "max-age=63072000; includeSubDomains; preload"
]
mail_exchanger dns 6aa9fa9d739df72d315dc69a2157a2c275788c88e4e8f03e4b5aa84dc5829816
"mta-gw.infomaniak.ch"
dns_nameserver dns 72ee9d4fdc0ea7c10eaf7caceb5c10bfca69aeea184ce3f577ffd0c2c5c5b991
"ns11.infomaniak.ch"
http_header headers 1e6794682d19880f0b8e2de92013ad293cab940040606a04069a49c786d0de37
[
    "camera=(), geolocation=(), microphone=(), payment=(), usb=(), browsing-topics=()"
]
module_finding dns de062920a43f206533f9ff956441a57f55f0d5d977e9026b36c27a8ba9826ffd
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
dmarc_record dns 835bec594fc98290188ac35aa0ee8b7062d74f53dba5095ffab97491faf3e014
"v=DMARC1; p=reject;"
module_finding mail_trust 252bd91dca255921f6e054ee88b07418464d6f6e6172ea65887f32eb23f37fea
{
    "evidence": [
        {
            "host": "mta-gw.infomaniak.ch",
            "priority": 5
        }
    ],
    "severity": "low"
}

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

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

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

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

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

40evidence items available

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

Download evidence JSON
Explore evidence
#01 canary_signal

Evidence: canary_signal

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
{ "matches": [], "reason": "no_known_passive_signature_observed", "signature_version": "2026.09.1", "state": "not_observed" }
Understand
Public observation
Source
canary_signal
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
{
    "matches": [],
    "reason": "no_known_passive_signature_observed",
    "signature_version": "2026.09.1",
    "state": "not_observed"
}

Rule 2026.09.4 · 2026-09-06T01:58:16+00:00

#02 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-06T01:58:16+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-10-10T22:06:56+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-10-10T22:06:56+00:00

Rule 2026.09.4 · 2026-09-06T01:58:16+00:00

#04 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-06T01:58:16+00:00

#05 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-06T01:58:16+00:00

#06 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-06T01:58:16+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": { "reason": "No external validating resolver is used; cryptographic 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; cryptographic validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}

Rule 2026.09.4 · 2026-09-06T01:58:16+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
[ "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-06T01:58:16+00:00

#09 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-06T01:58:16+00:00

#10 openpgp_discovery

Evidence: openpgp_discovery

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
{ "dns_openpgpkey": { "reason": "recipient_identity_required", "state": "untested" }, "fingerprint": null, "mechanisms": [], "reason": "security_txt_encryption_not_observed", "state": "not_observed", "wkd": { "reason": "wkd_not_fetched_without_identity", "state": "untested" } }
Understand
Public observation
Source
openpgp_discovery
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
{
    "dns_openpgpkey": {
        "reason": "recipient_identity_required",
        "state": "untested"
    },
    "fingerprint": null,
    "mechanisms": [],
    "reason": "security_txt_encryption_not_observed",
    "state": "not_observed",
    "wkd": {
        "reason": "wkd_not_fetched_without_identity",
        "state": "untested"
    }
}

Rule 2026.09.4 · 2026-09-06T01:58:16+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-06T01:58:16+00:00

#12 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-06T01:58:16+00:00

#13 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-06T01:58:16+00:00

#14 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
[ "strict-origin-when-cross-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
[
    "strict-origin-when-cross-origin"
]

Rule 2026.09.4 · 2026-09-06T01:58:16+00:00

#15 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.com
View raw data
ns12.infomaniak.ch

Rule 2026.09.4 · 2026-09-06T01:58:16+00:00

#16 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.com
View raw data
reject

Rule 2026.09.4 · 2026-09-06T01:58:16+00:00

#17 post_quantum_tls

Evidence: post_quantum_tls

This check only looks for a public TLS termination negotiating a hybrid key exchange supported by Scanapse.

Passive Medium
Why it matters

It documents cryptographic readiness without confusing it with overall system security.

What to check next

Record the actually negotiated group, tested endpoint, and measurement-client version. Compare results over time and across other public frontends.

Possible action

Do not enable or disable a mechanism merely to obtain a badge. Assess compatibility, TLS termination, clients and cryptographic strategy before changing it.

Observation
{ "capability": { "capable": false, "groups": [], "reason": "proc_open_unavailable" }, "group": null, "reason": "client_capability_unavailable", "state": "untested" }
Understand
Public observation
Source
post_quantum_tls
Reliability
Medium
What this supports
Describe the observed public artefact
What this does not prove
A positive result does not make a site “post-quantum”, and a negative result does not prove no other client could negotiate it.

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
{
    "capability": {
        "capable": false,
        "groups": [],
        "reason": "proc_open_unavailable"
    },
    "group": null,
    "reason": "client_capability_unavailable",
    "state": "untested"
}

Rule 2026.09.4 · 2026-09-06T01:58:16+00:00

#18 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-06T01:58:16+00:00

#19 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.com
View raw data
mta-gw.infomaniak.ch

Rule 2026.09.4 · 2026-09-06T01:58:16+00:00

#20 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.com
View raw data
ns11.infomaniak.ch

Rule 2026.09.4 · 2026-09-06T01:58:16+00:00

#21 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
[ "camera=(), geolocation=(), microphone=(), payment=(), usb=(), browsing-topics=()" ]
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
[
    "camera=(), geolocation=(), microphone=(), payment=(), usb=(), browsing-topics=()"
]

Rule 2026.09.4 · 2026-09-06T01:58:16+00:00

#22 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-06T01:58:16+00:00

#23 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-06T01:58:16+00:00

#24 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-06T01:58:16+00:00

#25 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-06T01:58:16+00:00

#26 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-06T01:58:16+00:00

#27 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-06T01:58:16+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
[ "default-src 'none'; base-uri 'none'; connect-src 'none'; font-src 'self'; form-action 'none'; frame-ancestors 'none'; img-src 'self' data:; manifest-src 'self'; media-src 'none'; object-src 'none'; script-src 'self' 'nonce-fOgiln7blLtwRLx5kx8zEg69'; style-src 'self'; worker-src 'none'" ]
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'; connect-src 'none'; font-src 'self'; form-action 'none'; frame-ancestors 'none'; img-src 'self' data:; manifest-src 'self'; media-src 'none'; object-src 'none'; script-src 'self' 'nonce-fOgiln7blLtwRLx5kx8zEg69'; style-src 'self'; worker-src 'none'"
]

Rule 2026.09.4 · 2026-09-06T01:58:16+00:00

#29 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-06T01:58:16+00:00

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

Rule 2026.09.4 · 2026-09-06T01:58:16+00:00

#31 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-06T01:58:16+00:00

#32 mail_transport_evidence

Evidence: mail_transport_evidence

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
{ "bimi": { "records": [], "state": "not_observed" }, "dane_tlsa": { "query_supported": false, "reason": "tlsa_query_not_available", "records": [], "state": "untested" }, "dkim": { "reason": "no_selector_bruteforce", "state": "untested" }, "mta_sts": { "policy": null, "policy_state": "untested", "records": [], "state": "not_observed" }, "tls_rpt": { "records": [], "state": "not_observed" } }
Understand
Public observation
Source
mail_transport_evidence
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
{
    "bimi": {
        "records": [],
        "state": "not_observed"
    },
    "dane_tlsa": {
        "query_supported": false,
        "reason": "tlsa_query_not_available",
        "records": [],
        "state": "untested"
    },
    "dkim": {
        "reason": "no_selector_bruteforce",
        "state": "untested"
    },
    "mta_sts": {
        "policy": null,
        "policy_state": "untested",
        "records": [],
        "state": "not_observed"
    },
    "tls_rpt": {
        "records": [],
        "state": "not_observed"
    }
}

Rule 2026.09.4 · 2026-09-06T01:58:16+00:00

#33 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-06T01:58:16+00:00

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

Rule 2026.09.4 · 2026-09-06T01:58:16+00:00

#35 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.com && dig AAAA alphatraining64.com
View raw data
185.125.27.195

Rule 2026.09.4 · 2026-09-06T01:58:16+00:00

#36 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.com
View raw data
hardfail

Rule 2026.09.4 · 2026-09-06T01:58:16+00:00

#37 modern_transport_evidence

Evidence: modern_transport_evidence

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
{ "alpn": { "state": "untested", "value": "" }, "certificate": { "cipher": "", "issuer": "C = US, O = Let's Encrypt, CN = YR2", "protocol": "", "san_count": 0, "state": "observed", "valid_from": "2026-07-12T22:06:57+00:00", "valid_to": "2026-10-10T22:06:56+00:00" }, "http2": { "negotiated": "3", "state": "untested" }, "http3_advertised": { "alt_svc": "", "state": "not_observed" }, "ipv4": { "addresses": [ "185.125.27.195" ], "state": "observed" }, "ipv6": { "addresses": [ "2001:1600::aaaa:0:0:80:5a" ], "state": "observed" } }
Understand
Public observation
Source
modern_transport_evidence
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
{
    "alpn": {
        "state": "untested",
        "value": ""
    },
    "certificate": {
        "cipher": "",
        "issuer": "C = US, O = Let's Encrypt, CN = YR2",
        "protocol": "",
        "san_count": 0,
        "state": "observed",
        "valid_from": "2026-07-12T22:06:57+00:00",
        "valid_to": "2026-10-10T22:06:56+00:00"
    },
    "http2": {
        "negotiated": "3",
        "state": "untested"
    },
    "http3_advertised": {
        "alt_svc": "",
        "state": "not_observed"
    },
    "ipv4": {
        "addresses": [
            "185.125.27.195"
        ],
        "state": "observed"
    },
    "ipv6": {
        "addresses": [
            "2001:1600::aaaa:0:0:80:5a"
        ],
        "state": "observed"
    }
}

Rule 2026.09.4 · 2026-09-06T01:58:16+00:00

#38 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-06T01:58:16+00:00

#39 csp_evidence

Evidence: csp_evidence

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
{ "enforced": true, "frame_ancestors": true, "hash_present": false, "nonce_present": true, "object_src": true, "report_only": false, "reporting_endpoint": false, "state": "observed", "strict_dynamic": false, "trusted_types": false }
Understand
Public observation
Source
csp_evidence
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
{
    "enforced": true,
    "frame_ancestors": true,
    "hash_present": false,
    "nonce_present": true,
    "object_src": true,
    "report_only": false,
    "reporting_endpoint": false,
    "state": "observed",
    "strict_dynamic": false,
    "trusted_types": false
}

Rule 2026.09.4 · 2026-09-06T01:58:16+00:00

#40 dnssec_evidence

Evidence: dnssec_evidence

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
{ "chain_consistency": { "reason": "insufficient_record_evidence", "state": "untested" }, "dnskey": { "query_supported": false, "records": [], "state": "untested" }, "ds": { "query_supported": false, "records": [], "state": "untested" }, "validation": { "reason": "no_validating_resolver", "state": "untested" } }
Understand
Public observation
Source
dnssec_evidence
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
{
    "chain_consistency": {
        "reason": "insufficient_record_evidence",
        "state": "untested"
    },
    "dnskey": {
        "query_supported": false,
        "records": [],
        "state": "untested"
    },
    "ds": {
        "query_supported": false,
        "records": [],
        "state": "untested"
    },
    "validation": {
        "reason": "no_validating_resolver",
        "state": "untested"
    }
}

Rule 2026.09.4 · 2026-09-06T01:58:16+00:00

Show technical details
{
    "schema_version": "2.0",
    "engine_version": "2.9.2.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": "fbedc872dac327b5699873f997781f04a79b9c2e82466b012583cece926d8317",
        "display_name": "alphatraining64.com",
        "slug": "alphatraining64-com",
        "entity_type": "domain_subject",
        "auto_created": true,
        "primary_asset": "alphatraining64.com"
    },
    "methodology": {
        "version": "2.3.1",
        "model": "evidence_first",
        "principles": [
            "absence_of_evidence_is_not_evidence_of_absence",
            "unknown_remains_unknown",
            "provider_metadata_is_not_data_location",
            "edge_provider_is_not_origin_host",
            "single_snapshot_does_not_prove_resilience"
        ]
    },
    "trajectory_summary": {
        "has_previous_scan": true,
        "change_counts": {
            "appeared": 14,
            "disappeared": 24,
            "modified": 2,
            "stable": 25
        },
        "observation_count": 40,
        "evidence_count": 40,
        "provider_count": 1,
        "strategic_signal_count": 1,
        "top_signal_count": 1
    }
}