OBSERVE · CONNECT · UNDERSTAND
FR EN
Read a domain

PUBLIC DOMAIN DOSSIER

kerkenniens.com

What is observed, how to verify it and what changed

3 public observations are documented in this dossier.

1 structuring public dependencies are visible.

8 useful changes are retained since the previous reading.

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

Measured 2026-09-06 02:11 UTC First observation 2026-09-04 19:34 UTC Latest observation 2026-09-06 02:11 UTC
History Compare JSON Markdown

TIME

What changed over time

Compared with the previous stored reading

7Appeared
1Modified
33Stable
0Disappeared
New

Canary signal

New

Csp evidence

New

Dnssec evidence

New

Mail transport evidence

New

Modern transport evidence

Modified

Module finding

SHORT VIEW

Four readings before the detail

The 12 historical angles remain available below for deeper inspection.

Identity & governance

  • ObservedDepends on providerInfomaniak
  • To confirmCanary detection
  • To confirmOpenpgp

Infrastructure & transport

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

Mail & trust

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

Measured on 2026-09-06 02:11 UTC Engine 2.9.3

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

Dnssec evidence

Not observedStructured value changed

Changed

Mail transport evidence

Not observedStructured value changed

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
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
10
Signals
1
Changes
10
dns_address dns 0b8663d1531976872773f6901ce6ed3620696866f8f52635787ced51772c0313 
"185.125.27.197"
module_finding dns 6e5ea515e886219d942e4254eaca80cc583e8dfd0e246ef2f7c523c6b40da5e6 
{
    "evidence": null,
    "severity": "low"
}
dns_nameserver dns 3305f8e2ecc78dc9c904897be60288b3e2d5ccd2a4d5c999e59ca1a059c64695 
"ns41.infomaniak.com"
module_finding dns 9dc78808929646b2c341ffb3d45d119e8aca27be8e0ca5e8d4ce646b781e8014 
{
    "evidence": {
        "reason": "No external validating resolver is used; cryptographic validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
dns_nameserver dns db28680d60cf82ee130b82550bdec42e494fe7f5fbfaea0eb3ea9d744d570eb6 
"ns42.infomaniak.com"
module_finding dns 55c91a813f320721edc07b0768464ea1667e7a865edab8a82160205f5a43bdce 
{
    "evidence": null,
    "severity": "medium"
}
spf_record dns f534957f27c7aeee1c7a49f6ddab6f92744a313c4a833d9bfdbf955c397f3655 
"v=spf1 include:spf.infomaniak.ch -all"
module_finding dns ec04fcdc5bc44b9300c0119f770b275214c0ae6667ad3a6f581c97cf55a9e70d 
{
    "evidence": [
        "ns41.infomaniak.com",
        "ns42.infomaniak.com"
    ],
    "severity": "low"
}
mail_exchanger dns f0d9e70609155fb3e090f3a74d9ee386c7a1fa2476cb7e24e3d73caeeb86b47a 
"mta-gw.infomaniak.ch"
dns_address dns cabe53b1bd9a9fe94e8002839a5962af397fa28d6c1e4a4181f3eb48d2af8580 
"2001:1600::aaaa:0:0:80:5b"
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
10changes
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
10

Unknowns and limitations

2 items still require qualification

dns_address dns 0b8663d1531976872773f6901ce6ed3620696866f8f52635787ced51772c0313 
"185.125.27.197"
module_finding dns 6e5ea515e886219d942e4254eaca80cc583e8dfd0e246ef2f7c523c6b40da5e6 
{
    "evidence": null,
    "severity": "low"
}
dns_nameserver dns 3305f8e2ecc78dc9c904897be60288b3e2d5ccd2a4d5c999e59ca1a059c64695 
"ns41.infomaniak.com"
module_finding resilience be4507f99ec3977171d1508e9dc602c1dfc8c53752f4d5af3ad5803512f8be52 
{
    "evidence": [
        "ns41.infomaniak.com",
        "ns42.infomaniak.com"
    ],
    "severity": "medium"
}
module_finding dns 9dc78808929646b2c341ffb3d45d119e8aca27be8e0ca5e8d4ce646b781e8014 
{
    "evidence": {
        "reason": "No external validating resolver is used; cryptographic validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
dns_nameserver dns db28680d60cf82ee130b82550bdec42e494fe7f5fbfaea0eb3ea9d744d570eb6 
"ns42.infomaniak.com"
module_finding dns 55c91a813f320721edc07b0768464ea1667e7a865edab8a82160205f5a43bdce 
{
    "evidence": null,
    "severity": "medium"
}
spf_record dns f534957f27c7aeee1c7a49f6ddab6f92744a313c4a833d9bfdbf955c397f3655 
"v=spf1 include:spf.infomaniak.ch -all"
module_finding dns ec04fcdc5bc44b9300c0119f770b275214c0ae6667ad3a6f581c97cf55a9e70d 
{
    "evidence": [
        "ns41.infomaniak.com",
        "ns42.infomaniak.com"
    ],
    "severity": "low"
}
mail_exchanger dns f0d9e70609155fb3e090f3a74d9ee386c7a1fa2476cb7e24e3d73caeeb86b47a 
"mta-gw.infomaniak.ch"
dependency_provider dependencies 5cfc7d003dcad7cb6bf1e4f16c462049c380a1ef307cafe8306e26f71df3117c 
{
    "critical": true,
    "hosts": [
        "mta-gw.infomaniak.ch",
        "ns41.infomaniak.com",
        "ns42.infomaniak.com"
    ],
    "id": "infomaniak",
    "known": true,
    "name": "Infomaniak",
    "observation_count": 3,
    "services": [
        "dns",
        "hosting",
        "mail"
    ],
    "tracker": false
}
dns_address dns cabe53b1bd9a9fe94e8002839a5962af397fa28d6c1e4a4181f3eb48d2af8580 
"2001:1600::aaaa:0:0:80:5b"
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
8changes
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
8
tls_issuer tls 5f2efeb3e6b2b48e2f7ae638bfce1ca3ed59654427236f4a77ca7f32eeb8df85 
"C = US, O = Let's Encrypt, CN = YR2"
http_header headers d1faee394df72e23d6affa05e83bba2dcdc40d2793aa889ccd3383d370dd572f 
[
    "Apache"
]
tls_valid_to tls 0683840ea53bd87eb15390fcb53d17b601e5bb81089b0382c0989bf88018b9c5 
"2026-11-05T00:12:58+00:00"
http_header headers 1ea81eaa7a09551d6a0dc3784351a413f8057559b29a4b4d2efb2ba92a4d4405 
[
    "camera=(), microphone=(), geolocation=(), payment=(), usb=(), browsing-topics=()"
]
http_header headers 5c34b1efe4e0a348dbeab8e9e3dbca8f235a7ef946bacb12d796eddd135043f4 
[
    "default-src 'none'; script-src 'self' 'nonce-UQo7PZaK4bqeUiAn8AnRBvTm'; style-src 'self'; img-src 'self' data:; font-src 'self'; connect-src 'self'; form-action 'self'; frame-ancestors 'none'; base-uri 'none'; object-src 'none'; manifest-src 'self'"
]
http_header headers c8965aadb286e0168bca98ad9404d81a36b979db759606f891b4ebe329408b36 
[
    "require-corp"
]
http_header headers d1f7bb45cfa23f39079923263ba0d06b2ba10673ec6c3cfc62bec7b7e92e5462 
[
    "nosniff"
]
http_header headers 9a5932cd1d49f952607dacd5296cf06fdb1bb138e1d61de5ef965af8c43eb333 
[
    "same-origin"
]
http_header headers f7ee91298265ff878a5c700d49531e7f690cac9f57f01e598cf08a635c6054e8 
[
    "same-origin"
]
http_header headers aa3925200641e722fc53bed83fe1520307018839192ce4b4be8198ec8bbc1805 
[
    "DENY"
]
http_header headers c2681925348a08deb0e714001582155a35f94dec31c83afe59cc3d430cae65fd 
[
    "max-age=63072000; includeSubDomains; preload"
]
http_header headers 81c7edd53e1e5be0d6ee3ab1d75499235b9cbf74d3018e6310cbf58114d6b86d 
[
    "strict-origin-when-cross-origin"
]
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
1
Changes
12
dns_address dns 0b8663d1531976872773f6901ce6ed3620696866f8f52635787ced51772c0313 
"185.125.27.197"
module_finding dns 6e5ea515e886219d942e4254eaca80cc583e8dfd0e246ef2f7c523c6b40da5e6 
{
    "evidence": null,
    "severity": "low"
}
dns_nameserver dns 3305f8e2ecc78dc9c904897be60288b3e2d5ccd2a4d5c999e59ca1a059c64695 
"ns41.infomaniak.com"
mail_policy_flag mail_trust b966120436feda796c1afd9c9e65417048bdfa868d118488f43f7acb30591c2b 
false
module_finding mail_trust 6adde282b55ea5ed2276f8d98879a0b4483df9b1d64d7c6bbd6af17143fd5988 
{
    "evidence": null,
    "severity": "low"
}
module_finding mail_trust 3f4d22477c91c7139c2feca2f8522c32fee92b7532cc3115c341f7c04433598b 
{
    "evidence": [
        {
            "host": "mta-gw.infomaniak.ch",
            "priority": 5
        }
    ],
    "severity": "low"
}
spf_policy mail_trust 82355c03ab6513a95e23228363f79dba048e21545fdd016a6ad8dfe688dd4f43 
"hardfail"
module_finding dns 9dc78808929646b2c341ffb3d45d119e8aca27be8e0ca5e8d4ce646b781e8014 
{
    "evidence": {
        "reason": "No external validating resolver is used; cryptographic validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
dns_nameserver dns db28680d60cf82ee130b82550bdec42e494fe7f5fbfaea0eb3ea9d744d570eb6 
"ns42.infomaniak.com"
module_finding dns 55c91a813f320721edc07b0768464ea1667e7a865edab8a82160205f5a43bdce 
{
    "evidence": null,
    "severity": "medium"
}
mail_policy_flag mail_trust d3fe5957ceed216f2723f08d3c13becdb903d41fd8bc126f5de07f2083d1eb6a 
false
spf_record dns f534957f27c7aeee1c7a49f6ddab6f92744a313c4a833d9bfdbf955c397f3655 
"v=spf1 include:spf.infomaniak.ch -all"
mail_policy_flag mail_trust f7bdc573412845c2931ddcf32c0ef1360e123b8f772528b43c1b85983732109b 
false
module_finding dns ec04fcdc5bc44b9300c0119f770b275214c0ae6667ad3a6f581c97cf55a9e70d 
{
    "evidence": [
        "ns41.infomaniak.com",
        "ns42.infomaniak.com"
    ],
    "severity": "low"
}
mail_exchanger dns f0d9e70609155fb3e090f3a74d9ee386c7a1fa2476cb7e24e3d73caeeb86b47a 
"mta-gw.infomaniak.ch"
module_finding mail_trust e13a858123266e1a0fade39982fe99c875a0c5e7ea0278a00e823b0b24cf49fd 
{
    "evidence": null,
    "severity": "low"
}
dns_address dns cabe53b1bd9a9fe94e8002839a5962af397fa28d6c1e4a4181f3eb48d2af8580 
"2001:1600::aaaa:0:0:80:5b"
module_finding mail_trust afcc289968c3d321083d8fcbddec61a721f0b2b32f369ebd2a0efcec173cc5ca 
{
    "evidence": null,
    "severity": "high"
}
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
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
18
Signals
1
Changes
10
dns_address dns 0b8663d1531976872773f6901ce6ed3620696866f8f52635787ced51772c0313 
"185.125.27.197"
module_finding dns 6e5ea515e886219d942e4254eaca80cc583e8dfd0e246ef2f7c523c6b40da5e6 
{
    "evidence": null,
    "severity": "low"
}
dns_nameserver dns 3305f8e2ecc78dc9c904897be60288b3e2d5ccd2a4d5c999e59ca1a059c64695 
"ns41.infomaniak.com"
mail_policy_flag mail_trust b966120436feda796c1afd9c9e65417048bdfa868d118488f43f7acb30591c2b 
false
module_finding mail_trust 6adde282b55ea5ed2276f8d98879a0b4483df9b1d64d7c6bbd6af17143fd5988 
{
    "evidence": null,
    "severity": "low"
}
module_finding mail_trust 3f4d22477c91c7139c2feca2f8522c32fee92b7532cc3115c341f7c04433598b 
{
    "evidence": [
        {
            "host": "mta-gw.infomaniak.ch",
            "priority": 5
        }
    ],
    "severity": "low"
}
spf_policy mail_trust 82355c03ab6513a95e23228363f79dba048e21545fdd016a6ad8dfe688dd4f43 
"hardfail"
module_finding dns 9dc78808929646b2c341ffb3d45d119e8aca27be8e0ca5e8d4ce646b781e8014 
{
    "evidence": {
        "reason": "No external validating resolver is used; cryptographic validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
dns_nameserver dns db28680d60cf82ee130b82550bdec42e494fe7f5fbfaea0eb3ea9d744d570eb6 
"ns42.infomaniak.com"
module_finding dns 55c91a813f320721edc07b0768464ea1667e7a865edab8a82160205f5a43bdce 
{
    "evidence": null,
    "severity": "medium"
}
mail_policy_flag mail_trust d3fe5957ceed216f2723f08d3c13becdb903d41fd8bc126f5de07f2083d1eb6a 
false
spf_record dns f534957f27c7aeee1c7a49f6ddab6f92744a313c4a833d9bfdbf955c397f3655 
"v=spf1 include:spf.infomaniak.ch -all"
mail_policy_flag mail_trust f7bdc573412845c2931ddcf32c0ef1360e123b8f772528b43c1b85983732109b 
false
module_finding dns ec04fcdc5bc44b9300c0119f770b275214c0ae6667ad3a6f581c97cf55a9e70d 
{
    "evidence": [
        "ns41.infomaniak.com",
        "ns42.infomaniak.com"
    ],
    "severity": "low"
}
mail_exchanger dns f0d9e70609155fb3e090f3a74d9ee386c7a1fa2476cb7e24e3d73caeeb86b47a 
"mta-gw.infomaniak.ch"
module_finding mail_trust e13a858123266e1a0fade39982fe99c875a0c5e7ea0278a00e823b0b24cf49fd 
{
    "evidence": null,
    "severity": "low"
}
dns_address dns cabe53b1bd9a9fe94e8002839a5962af397fa28d6c1e4a4181f3eb48d2af8580 
"2001:1600::aaaa:0:0:80:5b"
module_finding mail_trust afcc289968c3d321083d8fcbddec61a721f0b2b32f369ebd2a0efcec173cc5ca 
{
    "evidence": null,
    "severity": "high"
}
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
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
2
Changes
2
dns_address dns 0b8663d1531976872773f6901ce6ed3620696866f8f52635787ced51772c0313 
"185.125.27.197"
module_finding dns 6e5ea515e886219d942e4254eaca80cc583e8dfd0e246ef2f7c523c6b40da5e6 
{
    "evidence": null,
    "severity": "low"
}
dns_nameserver dns 3305f8e2ecc78dc9c904897be60288b3e2d5ccd2a4d5c999e59ca1a059c64695 
"ns41.infomaniak.com"
module_finding dns 9dc78808929646b2c341ffb3d45d119e8aca27be8e0ca5e8d4ce646b781e8014 
{
    "evidence": {
        "reason": "No external validating resolver is used; cryptographic validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
dns_nameserver dns db28680d60cf82ee130b82550bdec42e494fe7f5fbfaea0eb3ea9d744d570eb6 
"ns42.infomaniak.com"
module_finding dns 55c91a813f320721edc07b0768464ea1667e7a865edab8a82160205f5a43bdce 
{
    "evidence": null,
    "severity": "medium"
}
spf_record dns f534957f27c7aeee1c7a49f6ddab6f92744a313c4a833d9bfdbf955c397f3655 
"v=spf1 include:spf.infomaniak.ch -all"
module_finding dns ec04fcdc5bc44b9300c0119f770b275214c0ae6667ad3a6f581c97cf55a9e70d 
{
    "evidence": [
        "ns41.infomaniak.com",
        "ns42.infomaniak.com"
    ],
    "severity": "low"
}
mail_exchanger dns f0d9e70609155fb3e090f3a74d9ee386c7a1fa2476cb7e24e3d73caeeb86b47a 
"mta-gw.infomaniak.ch"
dependency_provider dependencies 5cfc7d003dcad7cb6bf1e4f16c462049c380a1ef307cafe8306e26f71df3117c 
{
    "critical": true,
    "hosts": [
        "mta-gw.infomaniak.ch",
        "ns41.infomaniak.com",
        "ns42.infomaniak.com"
    ],
    "id": "infomaniak",
    "known": true,
    "name": "Infomaniak",
    "observation_count": 3,
    "services": [
        "dns",
        "hosting",
        "mail"
    ],
    "tracker": false
}
dns_address dns cabe53b1bd9a9fe94e8002839a5962af397fa28d6c1e4a4181f3eb48d2af8580 
"2001:1600::aaaa:0:0:80:5b"
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
1changes
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
1
http_header headers d1faee394df72e23d6affa05e83bba2dcdc40d2793aa889ccd3383d370dd572f 
[
    "Apache"
]
http_header headers 1ea81eaa7a09551d6a0dc3784351a413f8057559b29a4b4d2efb2ba92a4d4405 
[
    "camera=(), microphone=(), geolocation=(), payment=(), usb=(), browsing-topics=()"
]
http_header headers 5c34b1efe4e0a348dbeab8e9e3dbca8f235a7ef946bacb12d796eddd135043f4 
[
    "default-src 'none'; script-src 'self' 'nonce-UQo7PZaK4bqeUiAn8AnRBvTm'; style-src 'self'; img-src 'self' data:; font-src 'self'; connect-src 'self'; form-action 'self'; frame-ancestors 'none'; base-uri 'none'; object-src 'none'; manifest-src 'self'"
]
http_header headers c8965aadb286e0168bca98ad9404d81a36b979db759606f891b4ebe329408b36 
[
    "require-corp"
]
http_header headers d1f7bb45cfa23f39079923263ba0d06b2ba10673ec6c3cfc62bec7b7e92e5462 
[
    "nosniff"
]
http_header headers 9a5932cd1d49f952607dacd5296cf06fdb1bb138e1d61de5ef965af8c43eb333 
[
    "same-origin"
]
http_header headers f7ee91298265ff878a5c700d49531e7f690cac9f57f01e598cf08a635c6054e8 
[
    "same-origin"
]
technology technology 26e1f05436ec9fcc2750945ddd5114ffc0a1520710c980dea17751022c5ef0fd 
{
    "name": "Apache",
    "version": "",
    "version_exposed": false
}
http_header headers aa3925200641e722fc53bed83fe1520307018839192ce4b4be8198ec8bbc1805 
[
    "DENY"
]
http_header headers c2681925348a08deb0e714001582155a35f94dec31c83afe59cc3d430cae65fd 
[
    "max-age=63072000; includeSubDomains; preload"
]
http_header headers 81c7edd53e1e5be0d6ee3ab1d75499235b9cbf74d3018e6310cbf58114d6b86d 
[
    "strict-origin-when-cross-origin"
]
08
Documented Stable

Public exposure

Public evidence provides enough material to document this angle

Angle 08

Public exposure

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

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

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

Mapping version
2.3.1
Evidence
19
Signals
0
Changes
0
http_header headers d1faee394df72e23d6affa05e83bba2dcdc40d2793aa889ccd3383d370dd572f 
[
    "Apache"
]
module_finding dns 6e5ea515e886219d942e4254eaca80cc583e8dfd0e246ef2f7c523c6b40da5e6 
{
    "evidence": null,
    "severity": "low"
}
http_header headers 1ea81eaa7a09551d6a0dc3784351a413f8057559b29a4b4d2efb2ba92a4d4405 
[
    "camera=(), microphone=(), geolocation=(), payment=(), usb=(), browsing-topics=()"
]
http_header headers 5c34b1efe4e0a348dbeab8e9e3dbca8f235a7ef946bacb12d796eddd135043f4 
[
    "default-src 'none'; script-src 'self' 'nonce-UQo7PZaK4bqeUiAn8AnRBvTm'; style-src 'self'; img-src 'self' data:; font-src 'self'; connect-src 'self'; form-action 'self'; frame-ancestors 'none'; base-uri 'none'; object-src 'none'; manifest-src 'self'"
]
http_header headers c8965aadb286e0168bca98ad9404d81a36b979db759606f891b4ebe329408b36 
[
    "require-corp"
]
module_finding mail_trust 6adde282b55ea5ed2276f8d98879a0b4483df9b1d64d7c6bbd6af17143fd5988 
{
    "evidence": null,
    "severity": "low"
}
module_finding mail_trust 3f4d22477c91c7139c2feca2f8522c32fee92b7532cc3115c341f7c04433598b 
{
    "evidence": [
        {
            "host": "mta-gw.infomaniak.ch",
            "priority": 5
        }
    ],
    "severity": "low"
}
module_finding resilience be4507f99ec3977171d1508e9dc602c1dfc8c53752f4d5af3ad5803512f8be52 
{
    "evidence": [
        "ns41.infomaniak.com",
        "ns42.infomaniak.com"
    ],
    "severity": "medium"
}
module_finding dns 9dc78808929646b2c341ffb3d45d119e8aca27be8e0ca5e8d4ce646b781e8014 
{
    "evidence": {
        "reason": "No external validating resolver is used; cryptographic validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
module_finding dns 55c91a813f320721edc07b0768464ea1667e7a865edab8a82160205f5a43bdce 
{
    "evidence": null,
    "severity": "medium"
}
http_header headers d1f7bb45cfa23f39079923263ba0d06b2ba10673ec6c3cfc62bec7b7e92e5462 
[
    "nosniff"
]
http_header headers 9a5932cd1d49f952607dacd5296cf06fdb1bb138e1d61de5ef965af8c43eb333 
[
    "same-origin"
]
http_header headers f7ee91298265ff878a5c700d49531e7f690cac9f57f01e598cf08a635c6054e8 
[
    "same-origin"
]
module_finding dns ec04fcdc5bc44b9300c0119f770b275214c0ae6667ad3a6f581c97cf55a9e70d 
{
    "evidence": [
        "ns41.infomaniak.com",
        "ns42.infomaniak.com"
    ],
    "severity": "low"
}
http_header headers aa3925200641e722fc53bed83fe1520307018839192ce4b4be8198ec8bbc1805 
[
    "DENY"
]
module_finding mail_trust e13a858123266e1a0fade39982fe99c875a0c5e7ea0278a00e823b0b24cf49fd 
{
    "evidence": null,
    "severity": "low"
}
http_header headers c2681925348a08deb0e714001582155a35f94dec31c83afe59cc3d430cae65fd 
[
    "max-age=63072000; includeSubDomains; preload"
]
http_header headers 81c7edd53e1e5be0d6ee3ab1d75499235b9cbf74d3018e6310cbf58114d6b86d 
[
    "strict-origin-when-cross-origin"
]
module_finding mail_trust afcc289968c3d321083d8fcbddec61a721f0b2b32f369ebd2a0efcec173cc5ca 
{
    "evidence": null,
    "severity": "high"
}
09
Documented Stable

Documentary trust

Public evidence provides enough material to document this angle

Angle 09

Documentary trust

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

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

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

Mapping version
2.3.1
Evidence
19
Signals
0
Changes
0
http_header headers d1faee394df72e23d6affa05e83bba2dcdc40d2793aa889ccd3383d370dd572f 
[
    "Apache"
]
module_finding dns 6e5ea515e886219d942e4254eaca80cc583e8dfd0e246ef2f7c523c6b40da5e6 
{
    "evidence": null,
    "severity": "low"
}
http_header headers 1ea81eaa7a09551d6a0dc3784351a413f8057559b29a4b4d2efb2ba92a4d4405 
[
    "camera=(), microphone=(), geolocation=(), payment=(), usb=(), browsing-topics=()"
]
http_header headers 5c34b1efe4e0a348dbeab8e9e3dbca8f235a7ef946bacb12d796eddd135043f4 
[
    "default-src 'none'; script-src 'self' 'nonce-UQo7PZaK4bqeUiAn8AnRBvTm'; style-src 'self'; img-src 'self' data:; font-src 'self'; connect-src 'self'; form-action 'self'; frame-ancestors 'none'; base-uri 'none'; object-src 'none'; manifest-src 'self'"
]
http_header headers c8965aadb286e0168bca98ad9404d81a36b979db759606f891b4ebe329408b36 
[
    "require-corp"
]
module_finding mail_trust 6adde282b55ea5ed2276f8d98879a0b4483df9b1d64d7c6bbd6af17143fd5988 
{
    "evidence": null,
    "severity": "low"
}
module_finding mail_trust 3f4d22477c91c7139c2feca2f8522c32fee92b7532cc3115c341f7c04433598b 
{
    "evidence": [
        {
            "host": "mta-gw.infomaniak.ch",
            "priority": 5
        }
    ],
    "severity": "low"
}
module_finding resilience be4507f99ec3977171d1508e9dc602c1dfc8c53752f4d5af3ad5803512f8be52 
{
    "evidence": [
        "ns41.infomaniak.com",
        "ns42.infomaniak.com"
    ],
    "severity": "medium"
}
module_finding dns 9dc78808929646b2c341ffb3d45d119e8aca27be8e0ca5e8d4ce646b781e8014 
{
    "evidence": {
        "reason": "No external validating resolver is used; cryptographic validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
module_finding dns 55c91a813f320721edc07b0768464ea1667e7a865edab8a82160205f5a43bdce 
{
    "evidence": null,
    "severity": "medium"
}
http_header headers d1f7bb45cfa23f39079923263ba0d06b2ba10673ec6c3cfc62bec7b7e92e5462 
[
    "nosniff"
]
http_header headers 9a5932cd1d49f952607dacd5296cf06fdb1bb138e1d61de5ef965af8c43eb333 
[
    "same-origin"
]
http_header headers f7ee91298265ff878a5c700d49531e7f690cac9f57f01e598cf08a635c6054e8 
[
    "same-origin"
]
module_finding dns ec04fcdc5bc44b9300c0119f770b275214c0ae6667ad3a6f581c97cf55a9e70d 
{
    "evidence": [
        "ns41.infomaniak.com",
        "ns42.infomaniak.com"
    ],
    "severity": "low"
}
http_header headers aa3925200641e722fc53bed83fe1520307018839192ce4b4be8198ec8bbc1805 
[
    "DENY"
]
module_finding mail_trust e13a858123266e1a0fade39982fe99c875a0c5e7ea0278a00e823b0b24cf49fd 
{
    "evidence": null,
    "severity": "low"
}
http_header headers c2681925348a08deb0e714001582155a35f94dec31c83afe59cc3d430cae65fd 
[
    "max-age=63072000; includeSubDomains; preload"
]
http_header headers 81c7edd53e1e5be0d6ee3ab1d75499235b9cbf74d3018e6310cbf58114d6b86d 
[
    "strict-origin-when-cross-origin"
]
module_finding mail_trust afcc289968c3d321083d8fcbddec61a721f0b2b32f369ebd2a0efcec173cc5ca 
{
    "evidence": null,
    "severity": "high"
}
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
24changes
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
1
Changes
24
tls_issuer tls 5f2efeb3e6b2b48e2f7ae638bfce1ca3ed59654427236f4a77ca7f32eeb8df85 
"C = US, O = Let's Encrypt, CN = YR2"
dns_address dns 0b8663d1531976872773f6901ce6ed3620696866f8f52635787ced51772c0313 
"185.125.27.197"
http_header headers d1faee394df72e23d6affa05e83bba2dcdc40d2793aa889ccd3383d370dd572f 
[
    "Apache"
]
tls_valid_to tls 0683840ea53bd87eb15390fcb53d17b601e5bb81089b0382c0989bf88018b9c5 
"2026-11-05T00:12:58+00:00"
module_finding dns 6e5ea515e886219d942e4254eaca80cc583e8dfd0e246ef2f7c523c6b40da5e6 
{
    "evidence": null,
    "severity": "low"
}
http_header headers 1ea81eaa7a09551d6a0dc3784351a413f8057559b29a4b4d2efb2ba92a4d4405 
[
    "camera=(), microphone=(), geolocation=(), payment=(), usb=(), browsing-topics=()"
]
dns_nameserver dns 3305f8e2ecc78dc9c904897be60288b3e2d5ccd2a4d5c999e59ca1a059c64695 
"ns41.infomaniak.com"
mail_policy_flag mail_trust b966120436feda796c1afd9c9e65417048bdfa868d118488f43f7acb30591c2b 
false
http_header headers 5c34b1efe4e0a348dbeab8e9e3dbca8f235a7ef946bacb12d796eddd135043f4 
[
    "default-src 'none'; script-src 'self' 'nonce-UQo7PZaK4bqeUiAn8AnRBvTm'; style-src 'self'; img-src 'self' data:; font-src 'self'; connect-src 'self'; form-action 'self'; frame-ancestors 'none'; base-uri 'none'; object-src 'none'; manifest-src 'self'"
]
http_header headers c8965aadb286e0168bca98ad9404d81a36b979db759606f891b4ebe329408b36 
[
    "require-corp"
]
module_finding mail_trust 6adde282b55ea5ed2276f8d98879a0b4483df9b1d64d7c6bbd6af17143fd5988 
{
    "evidence": null,
    "severity": "low"
}
module_finding mail_trust 3f4d22477c91c7139c2feca2f8522c32fee92b7532cc3115c341f7c04433598b 
{
    "evidence": [
        {
            "host": "mta-gw.infomaniak.ch",
            "priority": 5
        }
    ],
    "severity": "low"
}
spf_policy mail_trust 82355c03ab6513a95e23228363f79dba048e21545fdd016a6ad8dfe688dd4f43 
"hardfail"
module_finding resilience be4507f99ec3977171d1508e9dc602c1dfc8c53752f4d5af3ad5803512f8be52 
{
    "evidence": [
        "ns41.infomaniak.com",
        "ns42.infomaniak.com"
    ],
    "severity": "medium"
}
module_finding dns 9dc78808929646b2c341ffb3d45d119e8aca27be8e0ca5e8d4ce646b781e8014 
{
    "evidence": {
        "reason": "No external validating resolver is used; cryptographic validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
dns_nameserver dns db28680d60cf82ee130b82550bdec42e494fe7f5fbfaea0eb3ea9d744d570eb6 
"ns42.infomaniak.com"
module_finding dns 55c91a813f320721edc07b0768464ea1667e7a865edab8a82160205f5a43bdce 
{
    "evidence": null,
    "severity": "medium"
}
http_header headers d1f7bb45cfa23f39079923263ba0d06b2ba10673ec6c3cfc62bec7b7e92e5462 
[
    "nosniff"
]
mail_policy_flag mail_trust d3fe5957ceed216f2723f08d3c13becdb903d41fd8bc126f5de07f2083d1eb6a 
false
spf_record dns f534957f27c7aeee1c7a49f6ddab6f92744a313c4a833d9bfdbf955c397f3655 
"v=spf1 include:spf.infomaniak.ch -all"
http_header headers 9a5932cd1d49f952607dacd5296cf06fdb1bb138e1d61de5ef965af8c43eb333 
[
    "same-origin"
]
http_header headers f7ee91298265ff878a5c700d49531e7f690cac9f57f01e598cf08a635c6054e8 
[
    "same-origin"
]
mail_policy_flag mail_trust f7bdc573412845c2931ddcf32c0ef1360e123b8f772528b43c1b85983732109b 
false
module_finding dns ec04fcdc5bc44b9300c0119f770b275214c0ae6667ad3a6f581c97cf55a9e70d 
{
    "evidence": [
        "ns41.infomaniak.com",
        "ns42.infomaniak.com"
    ],
    "severity": "low"
}
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
41changes
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
41
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
2
Changes
0
tls_issuer tls 5f2efeb3e6b2b48e2f7ae638bfce1ca3ed59654427236f4a77ca7f32eeb8df85 
"C = US, O = Let's Encrypt, CN = YR2"
dns_address dns 0b8663d1531976872773f6901ce6ed3620696866f8f52635787ced51772c0313 
"185.125.27.197"
http_header headers d1faee394df72e23d6affa05e83bba2dcdc40d2793aa889ccd3383d370dd572f 
[
    "Apache"
]
tls_valid_to tls 0683840ea53bd87eb15390fcb53d17b601e5bb81089b0382c0989bf88018b9c5 
"2026-11-05T00:12:58+00:00"
module_finding dns 6e5ea515e886219d942e4254eaca80cc583e8dfd0e246ef2f7c523c6b40da5e6 
{
    "evidence": null,
    "severity": "low"
}
http_header headers 1ea81eaa7a09551d6a0dc3784351a413f8057559b29a4b4d2efb2ba92a4d4405 
[
    "camera=(), microphone=(), geolocation=(), payment=(), usb=(), browsing-topics=()"
]
dns_nameserver dns 3305f8e2ecc78dc9c904897be60288b3e2d5ccd2a4d5c999e59ca1a059c64695 
"ns41.infomaniak.com"
openpgp_discovery openpgp_discovery 57f1f801bc8cf8e0d2f2b271d489d3eec2dd5492a0eeb7262fc1fb4bb3447dcc 
{
    "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"
    }
}
mail_policy_flag mail_trust b966120436feda796c1afd9c9e65417048bdfa868d118488f43f7acb30591c2b 
false
http_header headers 5c34b1efe4e0a348dbeab8e9e3dbca8f235a7ef946bacb12d796eddd135043f4 
[
    "default-src 'none'; script-src 'self' 'nonce-UQo7PZaK4bqeUiAn8AnRBvTm'; style-src 'self'; img-src 'self' data:; font-src 'self'; connect-src 'self'; form-action 'self'; frame-ancestors 'none'; base-uri 'none'; object-src 'none'; manifest-src 'self'"
]
canary_signal canary_passive 1530bc634ce9ef2b49bedf1b48a8d39253658b043215f96ed0a8d55e493dea99 
{
    "matches": [],
    "reason": "no_known_passive_signature_observed",
    "signature_version": "2026.09.1",
    "state": "not_observed"
}
http_header headers c8965aadb286e0168bca98ad9404d81a36b979db759606f891b4ebe329408b36 
[
    "require-corp"
]
dnssec_evidence dnssec_depth 17d68278e46c70cb92b913eb6ffeaffb12d0f6bdf699ba0117c9f77e7de1b307 
{
    "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"
    }
}
module_finding mail_trust 6adde282b55ea5ed2276f8d98879a0b4483df9b1d64d7c6bbd6af17143fd5988 
{
    "evidence": null,
    "severity": "low"
}
modern_transport_evidence modern_transport 12b668ac7a80fbc8452d903f4d3fd48de3d3e0ac2297aedcf4211e9d59b63a32 
{
    "alpn": {
        "state": "untested",
        "value": ""
    },
    "certificate": {
        "cipher": "",
        "issuer": "C = US, O = Let's Encrypt, CN = YR2",
        "protocol": "",
        "san_count": 0,
        "state": "observed",
        "valid_from": "2026-08-07T00:12:59+00:00",
        "valid_to": "2026-11-05T00:12:58+00:00"
    },
    "http2": {
        "negotiated": "3",
        "state": "untested"
    },
    "http3_advertised": {
        "alt_svc": "",
        "state": "not_observed"
    },
    "ipv4": {
        "addresses": [
            "185.125.27.197"
        ],
        "state": "observed"
    },
    "ipv6": {
        "addresses": [
            "2001:1600::aaaa:0:0:80:5b"
        ],
        "state": "observed"
    }
}
module_finding mail_trust 3f4d22477c91c7139c2feca2f8522c32fee92b7532cc3115c341f7c04433598b 
{
    "evidence": [
        {
            "host": "mta-gw.infomaniak.ch",
            "priority": 5
        }
    ],
    "severity": "low"
}
spf_policy mail_trust 82355c03ab6513a95e23228363f79dba048e21545fdd016a6ad8dfe688dd4f43 
"hardfail"
module_finding resilience be4507f99ec3977171d1508e9dc602c1dfc8c53752f4d5af3ad5803512f8be52 
{
    "evidence": [
        "ns41.infomaniak.com",
        "ns42.infomaniak.com"
    ],
    "severity": "medium"
}
csp_evidence csp_depth 20eba0b0ead40827a70736356d7ed5cf10c46fb6aab6e380fb6e4e766c18121c 
{
    "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
}
post_quantum_tls pq_tls_probe bd20024cf918ec0a0435d2f2bf3b18d5a76bb7c532f36e31fe2fdd891d2e1a9e 
{
    "capability": {
        "capable": false,
        "groups": [],
        "reason": "proc_open_unavailable"
    },
    "group": null,
    "reason": "client_capability_unavailable",
    "state": "untested"
}
module_finding dns 9dc78808929646b2c341ffb3d45d119e8aca27be8e0ca5e8d4ce646b781e8014 
{
    "evidence": {
        "reason": "No external validating resolver is used; cryptographic validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
dns_nameserver dns db28680d60cf82ee130b82550bdec42e494fe7f5fbfaea0eb3ea9d744d570eb6 
"ns42.infomaniak.com"
module_finding dns 55c91a813f320721edc07b0768464ea1667e7a865edab8a82160205f5a43bdce 
{
    "evidence": null,
    "severity": "medium"
}
http_header headers d1f7bb45cfa23f39079923263ba0d06b2ba10673ec6c3cfc62bec7b7e92e5462 
[
    "nosniff"
]

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

DNS

2
DNS server Observed

ns41.infomaniak.com

DNS server Observed

ns42.infomaniak.com

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

Rule 2026.09.4 · 2026-09-06T02:11:41+00:00

#02 DNS public records

Evidence: dns_address

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

Passive High
Why it matters

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

What to check next

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

Possible action

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

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

Standards and reference context

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

Verify it yourself

This command reproduces the public observation without changing the target.

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

Rule 2026.09.4 · 2026-09-06T02:11:41+00:00

#03 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-06T02:11:41+00:00

#04 Public TLS endpoint

Evidence: tls_valid_to

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

Active non-intrusive High
Why it matters

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

What to check next

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

Possible action

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

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

Standards and reference context

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

View raw data 
2026-11-05T00:12:58+00:00

Rule 2026.09.4 · 2026-09-06T02:11:41+00:00

#05 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-06T02:11:41+00:00

#06 Public HTTP response

Evidence: http_header

HTTP headers can ask the browser to enforce specific protections.

Active non-intrusive High
Why it matters

They are visible, verifiable browser-side defensive layers.

What to check next

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

Possible action

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

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

Rule 2026.09.4 · 2026-09-06T02:11:41+00:00

#07 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
ns41.infomaniak.com
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 kerkenniens.com
View raw data 
ns41.infomaniak.com

Rule 2026.09.4 · 2026-09-06T02:11:41+00:00

#08 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-06T02:11:41+00:00

#09 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-06T02:11:41+00:00

#10 Public HTTP response

Evidence: http_header

HTTP headers can ask the browser to enforce specific protections.

Active non-intrusive High
Why it matters

They are visible, verifiable browser-side defensive layers.

What to check next

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

Possible action

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

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

Standards and reference context

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

View raw data 
[
    "default-src 'none'; script-src 'self' 'nonce-UQo7PZaK4bqeUiAn8AnRBvTm'; style-src 'self'; img-src 'self' data:; font-src 'self'; connect-src 'self'; form-action 'self'; frame-ancestors 'none'; base-uri 'none'; object-src 'none'; manifest-src 'self'"
]

Rule 2026.09.4 · 2026-09-06T02:11:41+00:00

#11 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-06T02:11:41+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
[ "require-corp" ]
Understand
HTTP response-header inspection
Source
Public HTTP response
Reliability
High
What this supports
Describe defensive policies declared on the observed response
What this does not prove
A header being present does not prove it is optimal or that the application has no vulnerabilities.

Standards and reference context

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

View raw data 
[
    "require-corp"
]

Rule 2026.09.4 · 2026-09-06T02:11:41+00:00

#13 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-06T02:11:41+00:00

#14 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-06T02:11:41+00:00

#15 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-08-07T00:12:59+00:00", "valid_to": "2026-11-05T00:12:58+00:00" }, "http2": { "negotiated": "3", "state": "untested" }, "http3_advertised": { "alt_svc": "", "state": "not_observed" }, "ipv4": { "addresses": [ "185.125.27.197" ], "state": "observed" }, "ipv6": { "addresses": [ "2001:1600::aaaa:0:0:80:5b" ], "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-08-07T00:12:59+00:00",
        "valid_to": "2026-11-05T00:12:58+00:00"
    },
    "http2": {
        "negotiated": "3",
        "state": "untested"
    },
    "http3_advertised": {
        "alt_svc": "",
        "state": "not_observed"
    },
    "ipv4": {
        "addresses": [
            "185.125.27.197"
        ],
        "state": "observed"
    },
    "ipv6": {
        "addresses": [
            "2001:1600::aaaa:0:0:80:5b"
        ],
        "state": "observed"
    }
}

Rule 2026.09.4 · 2026-09-06T02:11:41+00:00

#16 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-06T02:11:41+00:00

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

Rule 2026.09.4 · 2026-09-06T02:11:41+00:00

#18 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": [ "ns41.infomaniak.com", "ns42.infomaniak.com" ], "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": [
        "ns41.infomaniak.com",
        "ns42.infomaniak.com"
    ],
    "severity": "medium"
}

Rule 2026.09.4 · 2026-09-06T02:11:41+00:00

#19 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-06T02:11:41+00:00

#20 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-06T02:11:41+00:00

#21 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-06T02:11:41+00:00

#22 DNS public records

Evidence: dns_nameserver

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

Passive High
Why it matters

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

What to check next

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

Possible action

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

Observation
ns42.infomaniak.com
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 kerkenniens.com
View raw data 
ns42.infomaniak.com

Rule 2026.09.4 · 2026-09-06T02:11:41+00:00

#23 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": "medium" }
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": "medium"
}

Rule 2026.09.4 · 2026-09-06T02:11:41+00:00

#24 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-06T02:11:41+00:00

#25 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-06T02:11:41+00:00

#26 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-06T02:11:41+00:00

#27 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-06T02:11:41+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
[ "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-06T02:11:41+00:00

#29 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-06T02:11:41+00:00

#30 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-06T02:11:41+00:00

#31 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": [ "ns41.infomaniak.com", "ns42.infomaniak.com" ], "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": [
        "ns41.infomaniak.com",
        "ns42.infomaniak.com"
    ],
    "severity": "low"
}

Rule 2026.09.4 · 2026-09-06T02:11:41+00:00

#32 Public HTTP response

Evidence: http_header

HTTP headers can ask the browser to enforce specific protections.

Active non-intrusive High
Why it matters

They are visible, verifiable browser-side defensive layers.

What to check next

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

Possible action

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

Observation
[ "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-06T02:11:41+00:00

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

Rule 2026.09.4 · 2026-09-06T02:11:41+00:00

#34 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-06T02:11:41+00:00

#35 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-06T02:11:41+00:00

#36 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", "ns41.infomaniak.com", "ns42.infomaniak.com" ], "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",
        "ns41.infomaniak.com",
        "ns42.infomaniak.com"
    ],
    "id": "infomaniak",
    "known": true,
    "name": "Infomaniak",
    "observation_count": 3,
    "services": [
        "dns",
        "hosting",
        "mail"
    ],
    "tracker": false
}

Rule 2026.09.4 · 2026-09-06T02:11:41+00:00

#37 DNS public records

Evidence: dns_address

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

Passive High
Why it matters

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

What to check next

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

Possible action

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

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

Standards and reference context

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

Verify it yourself

This command reproduces the public observation without changing the target.

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

Rule 2026.09.4 · 2026-09-06T02:11:41+00:00

#38 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-06T02:11:41+00:00

#39 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-06T02:11:41+00:00

#40 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": "high" }
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": "high"
}

Rule 2026.09.4 · 2026-09-06T02:11:41+00:00

Show technical details 
{
    "schema_version": "2.0",
    "engine_version": "2.9.3",
    "pattern_version": "2026.09.4",
    "scope": {
        "mode": "passive",
        "coverage": "full",
        "access_level": "full",
        "access_reason": "public_document_available",
        "requests": 2,
        "homepage_only": true,
        "javascript_executed": false,
        "ports_scanned": false,
        "private_networks_blocked": true,
        "protection_bypassed": false,
        "max_body_bytes": 1572864,
        "scan_budget_seconds": 24,
        "budget_exhausted": false,
        "transport": "curl_with_socket_fallback"
    },
    "entity": {
        "id": "f532b0ceba278e4d178208bccba3508454a8ed3a72c1c945824b2200f5befd0f",
        "display_name": "kerkenniens.com",
        "slug": "kerkenniens-com",
        "entity_type": "domain_subject",
        "auto_created": true,
        "primary_asset": "kerkenniens.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": 7,
            "modified": 1,
            "stable": 33
        },
        "observation_count": 40,
        "evidence_count": 40,
        "provider_count": 1,
        "strategic_signal_count": 1,
        "top_signal_count": 1
    }
}