OBSERVE · CONNECT · UNDERSTAND
FR EN
Read a domain

PUBLIC DOMAIN DOSSIER

kerkito.com

What is observed, how to verify it and what changed

4 public observations are documented in this dossier.

1 structuring public dependencies are visible.

No useful change is retained since the previous reading.

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

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

TIME

What changed over time

Initial reference point created today

0Appeared
0Modified
0Stable
0Disappeared

SHORT VIEW

Four readings before the detail

The 12 historical angles remain available below for deeper inspection.

Identity & governance

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

Infrastructure & transport

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

Mail & trust

  • ObservedSpf policyhardfail
  • ObservedDmarc policyreject

Dependencies & exposure

  • Not observable from outsideData location

Explanatory record

What Scanapse understands about this domain

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

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

Read the domain folder

The key points for reading this domain folder

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

Key points

Worth looking at today

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

DEPENDENCIES

Critical function concentration

Infomaniak is associated with 3 critical function(s) or observations in the visible scope.

This concentration is descriptive. It does not prove a future outage or the absence of failover mechanisms invisible to the scan.

Territorial and legal context

Which legal context can reasonably be retained

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

To confirm To confirm

Why this context appears

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

What this does not establish

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

Regulatory frameworks

Useful texts for this context

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

To confirmTo determine

Regulatory context to determine

The available public evidence does not establish a sufficiently reliable jurisdiction for automatic legal contextualisation.

This section provides documentary context. It is not legal advice, certification or a compliance verdict.

Trajectory

Useful changes since the previous reading

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

No significant change retained

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

12 knowledge angles

12 angles to understand the domain

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

01
Documented First observation

Domain identity

Public evidence provides enough material to document this angle

Angle 01

Domain identity

Documented First observation

Public evidence provides enough material to document this angle

01

Why it matters

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

02

How to read it

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

03

What it is for

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

04

What it does not prove

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

Material available for this angle

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

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

Mapping version
2.3.1
Evidence
10
Signals
1
Changes
0
spf_record dns 28248f31ef4817ca94a48460984b7f12dff9e9d33c608076f084bf1a94e7fcfb 
"v=spf1 include:spf.infomaniak.ch -all"
mail_exchanger dns 02372dbc178b9d46aa8d4dddb551823687efa411f67347a36c897a992dfabacb 
"mta-gw.infomaniak.ch"
module_finding dns be71b47e5b9137a5e5d86627f824c46492724bbd1aac322424462918fe8fc3d6 
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
dns_address dns c4fef1d23d45cdd9705102bde312c8a2377fa14faf8fa6b2b029bb3c88548556 
"185.125.27.197"
module_finding dns 6714e7dc52c1092516b393abaa87db8e5aec80dd7f11ddfe59f0dc083a7a732b 
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
dns_address dns be7065fcc9bc2f7de1d5bacc2af945582cefd07aab3188adce60207d6dd64f3a 
"2001:1600::aaaa:0:0:80:5b"
dns_nameserver dns b2c35daadc262baa6f1798999f053cb2d48c8b30c66e972b5a6ac38b5594f549 
"ns11.infomaniak.ch"
dmarc_record dns 1addae54be2a0c7f11594eba3086b0ee4cec2f1f9edaff6befc55f553e5577e1 
"v=DMARC1; p=reject;"
caa_record dns c2af972026a6bc103162877b70363ecad05f2316d25d06babf0f693b0a2ac682 
{
    "flags": 0,
    "tag": "issue",
    "value": "letsencrypt.org"
}
dns_nameserver dns 0aeaa4dc5620fdfff1f203f2fc65efc89e16bd517c00bc9d815cbcd052f2da24 
"ns12.infomaniak.ch"
02
Documented First observation

Infrastructure

Public evidence provides enough material to document this angle

Angle 02

Infrastructure

Documented First observation

Public evidence provides enough material to document this angle

01

Why it matters

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

02

How to read it

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

03

What it is for

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

04

What it does not prove

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

Material available for this angle

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

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

Mapping version
2.3.1
Evidence
12
Signals
2
Changes
0

Unknowns and limitations

2 items still require qualification

spf_record dns 28248f31ef4817ca94a48460984b7f12dff9e9d33c608076f084bf1a94e7fcfb 
"v=spf1 include:spf.infomaniak.ch -all"
dependency_provider dependencies 55b24d35753a78f75795d4b5d7bd64e259d50d6a5d5e21bd48fdf687f6ed3496 
{
    "critical": true,
    "hosts": [
        "mta-gw.infomaniak.ch",
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "id": "infomaniak",
    "known": true,
    "name": "Infomaniak",
    "observation_count": 3,
    "services": [
        "dns",
        "hosting",
        "mail"
    ],
    "tracker": false
}
module_finding resilience e460e09b45bc09c74afc27b0f338f6b295e021fa43bfe1e52c7b90497dbda90e 
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "medium"
}
mail_exchanger dns 02372dbc178b9d46aa8d4dddb551823687efa411f67347a36c897a992dfabacb 
"mta-gw.infomaniak.ch"
module_finding dns be71b47e5b9137a5e5d86627f824c46492724bbd1aac322424462918fe8fc3d6 
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
dns_address dns c4fef1d23d45cdd9705102bde312c8a2377fa14faf8fa6b2b029bb3c88548556 
"185.125.27.197"
module_finding dns 6714e7dc52c1092516b393abaa87db8e5aec80dd7f11ddfe59f0dc083a7a732b 
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
dns_address dns be7065fcc9bc2f7de1d5bacc2af945582cefd07aab3188adce60207d6dd64f3a 
"2001:1600::aaaa:0:0:80:5b"
dns_nameserver dns b2c35daadc262baa6f1798999f053cb2d48c8b30c66e972b5a6ac38b5594f549 
"ns11.infomaniak.ch"
dmarc_record dns 1addae54be2a0c7f11594eba3086b0ee4cec2f1f9edaff6befc55f553e5577e1 
"v=DMARC1; p=reject;"
caa_record dns c2af972026a6bc103162877b70363ecad05f2316d25d06babf0f693b0a2ac682 
{
    "flags": 0,
    "tag": "issue",
    "value": "letsencrypt.org"
}
dns_nameserver dns 0aeaa4dc5620fdfff1f203f2fc65efc89e16bd517c00bc9d815cbcd052f2da24 
"ns12.infomaniak.ch"
03
Partial First observation

Encryption and transport

This angle is only partially documented by public evidence

Angle 03

Encryption and transport

Partial First observation

This angle is only partially documented by public evidence

01

Why it matters

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

02

How to read it

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

03

What it is for

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

04

What it does not prove

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

Material available for this angle

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

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

Mapping version
2.3.1
Evidence
12
Signals
0
Changes
0

Unknowns and limitations

1 items still require qualification

http_header headers 76f0bad42cddf88af38f9d30efeb5a16b6255e96aaa9c5cf568735322b29b199 
[
    "default-src 'none'; base-uri 'none'; object-src 'none'; frame-ancestors 'none'; frame-src 'none'; form-action 'self'; script-src 'self' 'nonce-0hAm3unuDcFCdl0I7JhjzZTHThnqjOx-' 'strict-dynamic'; script-src-attr 'none'; style-src 'self'; style-src-attr 'none'; img-src 'self'; font-src 'none'; connect-src 'self'; manifest-src 'self'; worker-src 'self'; media-src 'none'; require-trusted-types-for 'script'; trusted-types kerkito; upgrade-insecure-requests"
]
http_header headers 6d4e3a0b5aee45b26e5750b316e5eb6f1e1e212f111d50afa738f49dedc2edf5 
[
    "no-referrer"
]
http_header headers c9df8d93bf55aa34a71a151c09ea3031bb55864fadee1e2243f202b6cefa6ec6 
[
    "same-origin"
]
http_header headers b133cd799874ada6b32e20469e7b0b36b9172039aedf36e761f5c936ee8fafa8 
[
    "require-corp"
]
http_header headers ca70d8a879a4df346f9c7d2ca139a9f3394297db5f159b15ab7dfdbfd3c1fdcb 
[
    "same-origin"
]
tls_issuer tls aec3cace7940b50fd6d10bf0195883792660596445215e3641e3ac961f110e17 
"C = US, O = Let's Encrypt, CN = YR1"
http_header headers 7e38b79ae6ec9f4470ae4a595a048f6557d5aefad4e15d4ca8e00dbeb0f7d65b 
[
    "nosniff"
]
http_header headers 136051da10f81aac58f61a6a8257bb7dc536059b0dbd6a8073c922b3ffa7369d 
[
    "max-age=63072000; includeSubDomains"
]
http_header headers 46fbc95f96f0007dfd092416ebc721d0bcb51da01730f90dbd13b133dcf19617 
[
    "DENY"
]
http_header headers 3fb841a646830e1652e2c58f9f1c46d63e0c2b558ef015c67881223594e31522 
[
    "Apache"
]
http_header headers 298cb50b85911608b2d556bd896a8869c0234d33ae7b99e5ce822fd7e3f5f256 
[
    "accelerometer=(), ambient-light-sensor=(), autoplay=(), camera=(), display-capture=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(self), payment=(), usb=(), browsing-topics=()"
]
tls_valid_to tls 51f2b8b6e4994a2d73753b9795951f79c043aa95fe7c6d0f326dd5ce325c501b 
"2026-10-06T22:15:36+00:00"
04
Documented First observation

Mail and trust

Public evidence provides enough material to document this angle

Angle 04

Mail and trust

Documented First observation

Public evidence provides enough material to document this angle

01

Why it matters

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

02

How to read it

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

03

What it is for

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

04

What it does not prove

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

Material available for this angle

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

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

Mapping version
2.3.1
Evidence
18
Signals
2
Changes
0
spf_record dns 28248f31ef4817ca94a48460984b7f12dff9e9d33c608076f084bf1a94e7fcfb 
"v=spf1 include:spf.infomaniak.ch -all"
mail_exchanger dns 02372dbc178b9d46aa8d4dddb551823687efa411f67347a36c897a992dfabacb 
"mta-gw.infomaniak.ch"
module_finding dns be71b47e5b9137a5e5d86627f824c46492724bbd1aac322424462918fe8fc3d6 
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
dns_address dns c4fef1d23d45cdd9705102bde312c8a2377fa14faf8fa6b2b029bb3c88548556 
"185.125.27.197"
module_finding dns 6714e7dc52c1092516b393abaa87db8e5aec80dd7f11ddfe59f0dc083a7a732b 
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
dns_address dns be7065fcc9bc2f7de1d5bacc2af945582cefd07aab3188adce60207d6dd64f3a 
"2001:1600::aaaa:0:0:80:5b"
mail_policy_flag mail_trust f5fbf5489e2d7a0790cc6c764ae79b5fd8872e178fe5d5495d0be69e338375f0 
false
module_finding mail_trust 4bc6090689c47b91d49e4b85ea9de5804fa5924e296abaa28bbe4c512ed6e3b3 
{
    "evidence": null,
    "severity": "low"
}
dns_nameserver dns b2c35daadc262baa6f1798999f053cb2d48c8b30c66e972b5a6ac38b5594f549 
"ns11.infomaniak.ch"
spf_policy mail_trust 5cd35987936e7227c748f3d3be77aab6f4b1af3f029888358c8bcac8171a610d 
"hardfail"
mail_policy_flag mail_trust 53c05ff03016ab7a2ffd87ff9c254b50fe55a77caa967525adba64f22a722837 
false
dmarc_record dns 1addae54be2a0c7f11594eba3086b0ee4cec2f1f9edaff6befc55f553e5577e1 
"v=DMARC1; p=reject;"
dmarc_policy mail_trust 2e1e68ccb962b72af01baead513b3b94f3036c29f045e825cc7e3d1da9cf1381 
"reject"
mail_policy_flag mail_trust ab1a1a9de15ebec1aa03a797373fe65f690234be52b48c4c140a4cbb1e9f683a 
false
caa_record dns c2af972026a6bc103162877b70363ecad05f2316d25d06babf0f693b0a2ac682 
{
    "flags": 0,
    "tag": "issue",
    "value": "letsencrypt.org"
}
module_finding mail_trust 13f20fad266c0ee928bf35b6ccc791e706b7c09004b73f54e2ef87b1842cf994 
{
    "evidence": null,
    "severity": "low"
}
dns_nameserver dns 0aeaa4dc5620fdfff1f203f2fc65efc89e16bd517c00bc9d815cbcd052f2da24 
"ns12.infomaniak.ch"
module_finding mail_trust fad352162588d8530188ad74d6fc7a070297ab96a0544b2eb9385cf3fb7a81f1 
{
    "evidence": [
        {
            "host": "mta-gw.infomaniak.ch",
            "priority": 5
        }
    ],
    "severity": "low"
}
05
Documented First observation

DNS and governance

Public evidence provides enough material to document this angle

Angle 05

DNS and governance

Documented First observation

Public evidence provides enough material to document this angle

01

Why it matters

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

02

How to read it

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

03

What it is for

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

04

What it does not prove

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

Material available for this angle

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

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

Mapping version
2.3.1
Evidence
18
Signals
2
Changes
0
spf_record dns 28248f31ef4817ca94a48460984b7f12dff9e9d33c608076f084bf1a94e7fcfb 
"v=spf1 include:spf.infomaniak.ch -all"
mail_exchanger dns 02372dbc178b9d46aa8d4dddb551823687efa411f67347a36c897a992dfabacb 
"mta-gw.infomaniak.ch"
module_finding dns be71b47e5b9137a5e5d86627f824c46492724bbd1aac322424462918fe8fc3d6 
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
dns_address dns c4fef1d23d45cdd9705102bde312c8a2377fa14faf8fa6b2b029bb3c88548556 
"185.125.27.197"
module_finding dns 6714e7dc52c1092516b393abaa87db8e5aec80dd7f11ddfe59f0dc083a7a732b 
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
dns_address dns be7065fcc9bc2f7de1d5bacc2af945582cefd07aab3188adce60207d6dd64f3a 
"2001:1600::aaaa:0:0:80:5b"
mail_policy_flag mail_trust f5fbf5489e2d7a0790cc6c764ae79b5fd8872e178fe5d5495d0be69e338375f0 
false
module_finding mail_trust 4bc6090689c47b91d49e4b85ea9de5804fa5924e296abaa28bbe4c512ed6e3b3 
{
    "evidence": null,
    "severity": "low"
}
dns_nameserver dns b2c35daadc262baa6f1798999f053cb2d48c8b30c66e972b5a6ac38b5594f549 
"ns11.infomaniak.ch"
spf_policy mail_trust 5cd35987936e7227c748f3d3be77aab6f4b1af3f029888358c8bcac8171a610d 
"hardfail"
mail_policy_flag mail_trust 53c05ff03016ab7a2ffd87ff9c254b50fe55a77caa967525adba64f22a722837 
false
dmarc_record dns 1addae54be2a0c7f11594eba3086b0ee4cec2f1f9edaff6befc55f553e5577e1 
"v=DMARC1; p=reject;"
dmarc_policy mail_trust 2e1e68ccb962b72af01baead513b3b94f3036c29f045e825cc7e3d1da9cf1381 
"reject"
mail_policy_flag mail_trust ab1a1a9de15ebec1aa03a797373fe65f690234be52b48c4c140a4cbb1e9f683a 
false
caa_record dns c2af972026a6bc103162877b70363ecad05f2316d25d06babf0f693b0a2ac682 
{
    "flags": 0,
    "tag": "issue",
    "value": "letsencrypt.org"
}
module_finding mail_trust 13f20fad266c0ee928bf35b6ccc791e706b7c09004b73f54e2ef87b1842cf994 
{
    "evidence": null,
    "severity": "low"
}
dns_nameserver dns 0aeaa4dc5620fdfff1f203f2fc65efc89e16bd517c00bc9d815cbcd052f2da24 
"ns12.infomaniak.ch"
module_finding mail_trust fad352162588d8530188ad74d6fc7a070297ab96a0544b2eb9385cf3fb7a81f1 
{
    "evidence": [
        {
            "host": "mta-gw.infomaniak.ch",
            "priority": 5
        }
    ],
    "severity": "low"
}
06
Documented First observation

External dependencies

Public evidence provides enough material to document this angle

Angle 06

External dependencies

Documented First observation

Public evidence provides enough material to document this angle

01

Why it matters

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

02

How to read it

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

03

What it is for

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

04

What it does not prove

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

Material available for this angle

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

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

Mapping version
2.3.1
Evidence
11
Signals
2
Changes
0
spf_record dns 28248f31ef4817ca94a48460984b7f12dff9e9d33c608076f084bf1a94e7fcfb 
"v=spf1 include:spf.infomaniak.ch -all"
dependency_provider dependencies 55b24d35753a78f75795d4b5d7bd64e259d50d6a5d5e21bd48fdf687f6ed3496 
{
    "critical": true,
    "hosts": [
        "mta-gw.infomaniak.ch",
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "id": "infomaniak",
    "known": true,
    "name": "Infomaniak",
    "observation_count": 3,
    "services": [
        "dns",
        "hosting",
        "mail"
    ],
    "tracker": false
}
mail_exchanger dns 02372dbc178b9d46aa8d4dddb551823687efa411f67347a36c897a992dfabacb 
"mta-gw.infomaniak.ch"
module_finding dns be71b47e5b9137a5e5d86627f824c46492724bbd1aac322424462918fe8fc3d6 
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
dns_address dns c4fef1d23d45cdd9705102bde312c8a2377fa14faf8fa6b2b029bb3c88548556 
"185.125.27.197"
module_finding dns 6714e7dc52c1092516b393abaa87db8e5aec80dd7f11ddfe59f0dc083a7a732b 
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
dns_address dns be7065fcc9bc2f7de1d5bacc2af945582cefd07aab3188adce60207d6dd64f3a 
"2001:1600::aaaa:0:0:80:5b"
dns_nameserver dns b2c35daadc262baa6f1798999f053cb2d48c8b30c66e972b5a6ac38b5594f549 
"ns11.infomaniak.ch"
dmarc_record dns 1addae54be2a0c7f11594eba3086b0ee4cec2f1f9edaff6befc55f553e5577e1 
"v=DMARC1; p=reject;"
caa_record dns c2af972026a6bc103162877b70363ecad05f2316d25d06babf0f693b0a2ac682 
{
    "flags": 0,
    "tag": "issue",
    "value": "letsencrypt.org"
}
dns_nameserver dns 0aeaa4dc5620fdfff1f203f2fc65efc89e16bd517c00bc9d815cbcd052f2da24 
"ns12.infomaniak.ch"
07
Documented First observation

Observable technologies

Public evidence provides enough material to document this angle

Angle 07

Observable technologies

Documented First observation

Public evidence provides enough material to document this angle

01

Why it matters

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

02

How to read it

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

03

What it is for

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

04

What it does not prove

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

Material available for this angle

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

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

Mapping version
2.3.1
Evidence
11
Signals
0
Changes
0
http_header headers 76f0bad42cddf88af38f9d30efeb5a16b6255e96aaa9c5cf568735322b29b199 
[
    "default-src 'none'; base-uri 'none'; object-src 'none'; frame-ancestors 'none'; frame-src 'none'; form-action 'self'; script-src 'self' 'nonce-0hAm3unuDcFCdl0I7JhjzZTHThnqjOx-' 'strict-dynamic'; script-src-attr 'none'; style-src 'self'; style-src-attr 'none'; img-src 'self'; font-src 'none'; connect-src 'self'; manifest-src 'self'; worker-src 'self'; media-src 'none'; require-trusted-types-for 'script'; trusted-types kerkito; upgrade-insecure-requests"
]
http_header headers 6d4e3a0b5aee45b26e5750b316e5eb6f1e1e212f111d50afa738f49dedc2edf5 
[
    "no-referrer"
]
http_header headers c9df8d93bf55aa34a71a151c09ea3031bb55864fadee1e2243f202b6cefa6ec6 
[
    "same-origin"
]
http_header headers b133cd799874ada6b32e20469e7b0b36b9172039aedf36e761f5c936ee8fafa8 
[
    "require-corp"
]
http_header headers ca70d8a879a4df346f9c7d2ca139a9f3394297db5f159b15ab7dfdbfd3c1fdcb 
[
    "same-origin"
]
technology technology 906c502ada3f61fc120f0bd809a88369ec00784e3c8a2618a15a425639ae61c3 
{
    "name": "Apache",
    "version": "",
    "version_exposed": false
}
http_header headers 7e38b79ae6ec9f4470ae4a595a048f6557d5aefad4e15d4ca8e00dbeb0f7d65b 
[
    "nosniff"
]
http_header headers 136051da10f81aac58f61a6a8257bb7dc536059b0dbd6a8073c922b3ffa7369d 
[
    "max-age=63072000; includeSubDomains"
]
http_header headers 46fbc95f96f0007dfd092416ebc721d0bcb51da01730f90dbd13b133dcf19617 
[
    "DENY"
]
http_header headers 3fb841a646830e1652e2c58f9f1c46d63e0c2b558ef015c67881223594e31522 
[
    "Apache"
]
http_header headers 298cb50b85911608b2d556bd896a8869c0234d33ae7b99e5ce822fd7e3f5f256 
[
    "accelerometer=(), ambient-light-sensor=(), autoplay=(), camera=(), display-capture=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(self), payment=(), usb=(), browsing-topics=()"
]
08
Partial First observation

Public exposure

This angle is only partially documented by public evidence

Angle 08

Public exposure

Partial First observation

This angle is only partially documented by public evidence

01

Why it matters

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

02

How to read it

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

03

What it is for

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

04

What it does not prove

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

Material available for this angle

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

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

Mapping version
2.3.1
Evidence
16
Signals
0
Changes
0

Unknowns and limitations

1 items still require qualification

http_header headers 76f0bad42cddf88af38f9d30efeb5a16b6255e96aaa9c5cf568735322b29b199 
[
    "default-src 'none'; base-uri 'none'; object-src 'none'; frame-ancestors 'none'; frame-src 'none'; form-action 'self'; script-src 'self' 'nonce-0hAm3unuDcFCdl0I7JhjzZTHThnqjOx-' 'strict-dynamic'; script-src-attr 'none'; style-src 'self'; style-src-attr 'none'; img-src 'self'; font-src 'none'; connect-src 'self'; manifest-src 'self'; worker-src 'self'; media-src 'none'; require-trusted-types-for 'script'; trusted-types kerkito; upgrade-insecure-requests"
]
module_finding resilience e460e09b45bc09c74afc27b0f338f6b295e021fa43bfe1e52c7b90497dbda90e 
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "medium"
}
http_header headers 6d4e3a0b5aee45b26e5750b316e5eb6f1e1e212f111d50afa738f49dedc2edf5 
[
    "no-referrer"
]
http_header headers c9df8d93bf55aa34a71a151c09ea3031bb55864fadee1e2243f202b6cefa6ec6 
[
    "same-origin"
]
module_finding dns be71b47e5b9137a5e5d86627f824c46492724bbd1aac322424462918fe8fc3d6 
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
module_finding dns 6714e7dc52c1092516b393abaa87db8e5aec80dd7f11ddfe59f0dc083a7a732b 
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
http_header headers b133cd799874ada6b32e20469e7b0b36b9172039aedf36e761f5c936ee8fafa8 
[
    "require-corp"
]
http_header headers ca70d8a879a4df346f9c7d2ca139a9f3394297db5f159b15ab7dfdbfd3c1fdcb 
[
    "same-origin"
]
module_finding mail_trust 4bc6090689c47b91d49e4b85ea9de5804fa5924e296abaa28bbe4c512ed6e3b3 
{
    "evidence": null,
    "severity": "low"
}
http_header headers 7e38b79ae6ec9f4470ae4a595a048f6557d5aefad4e15d4ca8e00dbeb0f7d65b 
[
    "nosniff"
]
http_header headers 136051da10f81aac58f61a6a8257bb7dc536059b0dbd6a8073c922b3ffa7369d 
[
    "max-age=63072000; includeSubDomains"
]
http_header headers 46fbc95f96f0007dfd092416ebc721d0bcb51da01730f90dbd13b133dcf19617 
[
    "DENY"
]
http_header headers 3fb841a646830e1652e2c58f9f1c46d63e0c2b558ef015c67881223594e31522 
[
    "Apache"
]
module_finding mail_trust 13f20fad266c0ee928bf35b6ccc791e706b7c09004b73f54e2ef87b1842cf994 
{
    "evidence": null,
    "severity": "low"
}
http_header headers 298cb50b85911608b2d556bd896a8869c0234d33ae7b99e5ce822fd7e3f5f256 
[
    "accelerometer=(), ambient-light-sensor=(), autoplay=(), camera=(), display-capture=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(self), payment=(), usb=(), browsing-topics=()"
]
module_finding mail_trust fad352162588d8530188ad74d6fc7a070297ab96a0544b2eb9385cf3fb7a81f1 
{
    "evidence": [
        {
            "host": "mta-gw.infomaniak.ch",
            "priority": 5
        }
    ],
    "severity": "low"
}
09
Documented First observation

Documentary trust

Public evidence provides enough material to document this angle

Angle 09

Documentary trust

Documented First observation

Public evidence provides enough material to document this angle

01

Why it matters

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

02

How to read it

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

03

What it is for

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

04

What it does not prove

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

Material available for this angle

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

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

Mapping version
2.3.1
Evidence
16
Signals
0
Changes
0
http_header headers 76f0bad42cddf88af38f9d30efeb5a16b6255e96aaa9c5cf568735322b29b199 
[
    "default-src 'none'; base-uri 'none'; object-src 'none'; frame-ancestors 'none'; frame-src 'none'; form-action 'self'; script-src 'self' 'nonce-0hAm3unuDcFCdl0I7JhjzZTHThnqjOx-' 'strict-dynamic'; script-src-attr 'none'; style-src 'self'; style-src-attr 'none'; img-src 'self'; font-src 'none'; connect-src 'self'; manifest-src 'self'; worker-src 'self'; media-src 'none'; require-trusted-types-for 'script'; trusted-types kerkito; upgrade-insecure-requests"
]
module_finding resilience e460e09b45bc09c74afc27b0f338f6b295e021fa43bfe1e52c7b90497dbda90e 
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "medium"
}
http_header headers 6d4e3a0b5aee45b26e5750b316e5eb6f1e1e212f111d50afa738f49dedc2edf5 
[
    "no-referrer"
]
http_header headers c9df8d93bf55aa34a71a151c09ea3031bb55864fadee1e2243f202b6cefa6ec6 
[
    "same-origin"
]
module_finding dns be71b47e5b9137a5e5d86627f824c46492724bbd1aac322424462918fe8fc3d6 
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
module_finding dns 6714e7dc52c1092516b393abaa87db8e5aec80dd7f11ddfe59f0dc083a7a732b 
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
http_header headers b133cd799874ada6b32e20469e7b0b36b9172039aedf36e761f5c936ee8fafa8 
[
    "require-corp"
]
http_header headers ca70d8a879a4df346f9c7d2ca139a9f3394297db5f159b15ab7dfdbfd3c1fdcb 
[
    "same-origin"
]
module_finding mail_trust 4bc6090689c47b91d49e4b85ea9de5804fa5924e296abaa28bbe4c512ed6e3b3 
{
    "evidence": null,
    "severity": "low"
}
http_header headers 7e38b79ae6ec9f4470ae4a595a048f6557d5aefad4e15d4ca8e00dbeb0f7d65b 
[
    "nosniff"
]
http_header headers 136051da10f81aac58f61a6a8257bb7dc536059b0dbd6a8073c922b3ffa7369d 
[
    "max-age=63072000; includeSubDomains"
]
http_header headers 46fbc95f96f0007dfd092416ebc721d0bcb51da01730f90dbd13b133dcf19617 
[
    "DENY"
]
http_header headers 3fb841a646830e1652e2c58f9f1c46d63e0c2b558ef015c67881223594e31522 
[
    "Apache"
]
module_finding mail_trust 13f20fad266c0ee928bf35b6ccc791e706b7c09004b73f54e2ef87b1842cf994 
{
    "evidence": null,
    "severity": "low"
}
http_header headers 298cb50b85911608b2d556bd896a8869c0234d33ae7b99e5ce822fd7e3f5f256 
[
    "accelerometer=(), ambient-light-sensor=(), autoplay=(), camera=(), display-capture=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(self), payment=(), usb=(), browsing-topics=()"
]
module_finding mail_trust fad352162588d8530188ad74d6fc7a070297ab96a0544b2eb9385cf3fb7a81f1 
{
    "evidence": [
        {
            "host": "mta-gw.infomaniak.ch",
            "priority": 5
        }
    ],
    "severity": "low"
}
10
Documented First observation

Security signals

Public evidence provides enough material to document this angle

Angle 10

Security signals

Documented First observation

Public evidence provides enough material to document this angle

01

Why it matters

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

02

How to read it

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

03

What it is for

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

04

What it does not prove

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

Material available for this angle

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

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

Mapping version
2.3.1
Evidence
31
Signals
2
Changes
0

Unknowns and limitations

2 items still require qualification

http_header headers 76f0bad42cddf88af38f9d30efeb5a16b6255e96aaa9c5cf568735322b29b199 
[
    "default-src 'none'; base-uri 'none'; object-src 'none'; frame-ancestors 'none'; frame-src 'none'; form-action 'self'; script-src 'self' 'nonce-0hAm3unuDcFCdl0I7JhjzZTHThnqjOx-' 'strict-dynamic'; script-src-attr 'none'; style-src 'self'; style-src-attr 'none'; img-src 'self'; font-src 'none'; connect-src 'self'; manifest-src 'self'; worker-src 'self'; media-src 'none'; require-trusted-types-for 'script'; trusted-types kerkito; upgrade-insecure-requests"
]
spf_record dns 28248f31ef4817ca94a48460984b7f12dff9e9d33c608076f084bf1a94e7fcfb 
"v=spf1 include:spf.infomaniak.ch -all"
module_finding resilience e460e09b45bc09c74afc27b0f338f6b295e021fa43bfe1e52c7b90497dbda90e 
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "medium"
}
mail_exchanger dns 02372dbc178b9d46aa8d4dddb551823687efa411f67347a36c897a992dfabacb 
"mta-gw.infomaniak.ch"
http_header headers 6d4e3a0b5aee45b26e5750b316e5eb6f1e1e212f111d50afa738f49dedc2edf5 
[
    "no-referrer"
]
http_header headers c9df8d93bf55aa34a71a151c09ea3031bb55864fadee1e2243f202b6cefa6ec6 
[
    "same-origin"
]
module_finding dns be71b47e5b9137a5e5d86627f824c46492724bbd1aac322424462918fe8fc3d6 
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
dns_address dns c4fef1d23d45cdd9705102bde312c8a2377fa14faf8fa6b2b029bb3c88548556 
"185.125.27.197"
module_finding dns 6714e7dc52c1092516b393abaa87db8e5aec80dd7f11ddfe59f0dc083a7a732b 
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
http_header headers b133cd799874ada6b32e20469e7b0b36b9172039aedf36e761f5c936ee8fafa8 
[
    "require-corp"
]
dns_address dns be7065fcc9bc2f7de1d5bacc2af945582cefd07aab3188adce60207d6dd64f3a 
"2001:1600::aaaa:0:0:80:5b"
http_header headers ca70d8a879a4df346f9c7d2ca139a9f3394297db5f159b15ab7dfdbfd3c1fdcb 
[
    "same-origin"
]
mail_policy_flag mail_trust f5fbf5489e2d7a0790cc6c764ae79b5fd8872e178fe5d5495d0be69e338375f0 
false
module_finding mail_trust 4bc6090689c47b91d49e4b85ea9de5804fa5924e296abaa28bbe4c512ed6e3b3 
{
    "evidence": null,
    "severity": "low"
}
dns_nameserver dns b2c35daadc262baa6f1798999f053cb2d48c8b30c66e972b5a6ac38b5594f549 
"ns11.infomaniak.ch"
tls_issuer tls aec3cace7940b50fd6d10bf0195883792660596445215e3641e3ac961f110e17 
"C = US, O = Let's Encrypt, CN = YR1"
http_header headers 7e38b79ae6ec9f4470ae4a595a048f6557d5aefad4e15d4ca8e00dbeb0f7d65b 
[
    "nosniff"
]
spf_policy mail_trust 5cd35987936e7227c748f3d3be77aab6f4b1af3f029888358c8bcac8171a610d 
"hardfail"
http_header headers 136051da10f81aac58f61a6a8257bb7dc536059b0dbd6a8073c922b3ffa7369d 
[
    "max-age=63072000; includeSubDomains"
]
mail_policy_flag mail_trust 53c05ff03016ab7a2ffd87ff9c254b50fe55a77caa967525adba64f22a722837 
false
dmarc_record dns 1addae54be2a0c7f11594eba3086b0ee4cec2f1f9edaff6befc55f553e5577e1 
"v=DMARC1; p=reject;"
http_header headers 46fbc95f96f0007dfd092416ebc721d0bcb51da01730f90dbd13b133dcf19617 
[
    "DENY"
]
dmarc_policy mail_trust 2e1e68ccb962b72af01baead513b3b94f3036c29f045e825cc7e3d1da9cf1381 
"reject"
http_header headers 3fb841a646830e1652e2c58f9f1c46d63e0c2b558ef015c67881223594e31522 
[
    "Apache"
]
11
To determine First observation

Evolution over time

This angle still needs additional public evidence

Angle 11

Evolution over time

To determine First observation

This angle still needs additional public evidence

01

Why it matters

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

02

How to read it

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

03

What it is for

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

04

What it does not prove

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

Material available for this angle

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

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

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

Evidence and traceability

Public evidence provides enough material to document this angle

Angle 12

Evidence and traceability

Documented First observation

Public evidence provides enough material to document this angle

01

Why it matters

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

02

How to read it

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

03

What it is for

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

04

What it does not prove

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

Material available for this angle

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

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

Mapping version
2.3.1
Evidence
33
Signals
3
Changes
0
http_header headers 76f0bad42cddf88af38f9d30efeb5a16b6255e96aaa9c5cf568735322b29b199 
[
    "default-src 'none'; base-uri 'none'; object-src 'none'; frame-ancestors 'none'; frame-src 'none'; form-action 'self'; script-src 'self' 'nonce-0hAm3unuDcFCdl0I7JhjzZTHThnqjOx-' 'strict-dynamic'; script-src-attr 'none'; style-src 'self'; style-src-attr 'none'; img-src 'self'; font-src 'none'; connect-src 'self'; manifest-src 'self'; worker-src 'self'; media-src 'none'; require-trusted-types-for 'script'; trusted-types kerkito; upgrade-insecure-requests"
]
spf_record dns 28248f31ef4817ca94a48460984b7f12dff9e9d33c608076f084bf1a94e7fcfb 
"v=spf1 include:spf.infomaniak.ch -all"
dependency_provider dependencies 55b24d35753a78f75795d4b5d7bd64e259d50d6a5d5e21bd48fdf687f6ed3496 
{
    "critical": true,
    "hosts": [
        "mta-gw.infomaniak.ch",
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "id": "infomaniak",
    "known": true,
    "name": "Infomaniak",
    "observation_count": 3,
    "services": [
        "dns",
        "hosting",
        "mail"
    ],
    "tracker": false
}
module_finding resilience e460e09b45bc09c74afc27b0f338f6b295e021fa43bfe1e52c7b90497dbda90e 
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "medium"
}
mail_exchanger dns 02372dbc178b9d46aa8d4dddb551823687efa411f67347a36c897a992dfabacb 
"mta-gw.infomaniak.ch"
http_header headers 6d4e3a0b5aee45b26e5750b316e5eb6f1e1e212f111d50afa738f49dedc2edf5 
[
    "no-referrer"
]
http_header headers c9df8d93bf55aa34a71a151c09ea3031bb55864fadee1e2243f202b6cefa6ec6 
[
    "same-origin"
]
module_finding dns be71b47e5b9137a5e5d86627f824c46492724bbd1aac322424462918fe8fc3d6 
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
dns_address dns c4fef1d23d45cdd9705102bde312c8a2377fa14faf8fa6b2b029bb3c88548556 
"185.125.27.197"
module_finding dns 6714e7dc52c1092516b393abaa87db8e5aec80dd7f11ddfe59f0dc083a7a732b 
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
http_header headers b133cd799874ada6b32e20469e7b0b36b9172039aedf36e761f5c936ee8fafa8 
[
    "require-corp"
]
dns_address dns be7065fcc9bc2f7de1d5bacc2af945582cefd07aab3188adce60207d6dd64f3a 
"2001:1600::aaaa:0:0:80:5b"
http_header headers ca70d8a879a4df346f9c7d2ca139a9f3394297db5f159b15ab7dfdbfd3c1fdcb 
[
    "same-origin"
]
mail_policy_flag mail_trust f5fbf5489e2d7a0790cc6c764ae79b5fd8872e178fe5d5495d0be69e338375f0 
false
module_finding mail_trust 4bc6090689c47b91d49e4b85ea9de5804fa5924e296abaa28bbe4c512ed6e3b3 
{
    "evidence": null,
    "severity": "low"
}
dns_nameserver dns b2c35daadc262baa6f1798999f053cb2d48c8b30c66e972b5a6ac38b5594f549 
"ns11.infomaniak.ch"
technology technology 906c502ada3f61fc120f0bd809a88369ec00784e3c8a2618a15a425639ae61c3 
{
    "name": "Apache",
    "version": "",
    "version_exposed": false
}
tls_issuer tls aec3cace7940b50fd6d10bf0195883792660596445215e3641e3ac961f110e17 
"C = US, O = Let's Encrypt, CN = YR1"
http_header headers 7e38b79ae6ec9f4470ae4a595a048f6557d5aefad4e15d4ca8e00dbeb0f7d65b 
[
    "nosniff"
]
spf_policy mail_trust 5cd35987936e7227c748f3d3be77aab6f4b1af3f029888358c8bcac8171a610d 
"hardfail"
http_header headers 136051da10f81aac58f61a6a8257bb7dc536059b0dbd6a8073c922b3ffa7369d 
[
    "max-age=63072000; includeSubDomains"
]
mail_policy_flag mail_trust 53c05ff03016ab7a2ffd87ff9c254b50fe55a77caa967525adba64f22a722837 
false
dmarc_record dns 1addae54be2a0c7f11594eba3086b0ee4cec2f1f9edaff6befc55f553e5577e1 
"v=DMARC1; p=reject;"
http_header headers 46fbc95f96f0007dfd092416ebc721d0bcb51da01730f90dbd13b133dcf19617 
[
    "DENY"
]

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

DNS

2
DNS server Observed

ns12.infomaniak.ch

DNS server Observed

ns11.infomaniak.ch

mail

1
Mail server Observed

mta-gw.infomaniak.ch

technology

1
Observed technology Observed

Apache

external resources

1
External provider or resource Corroborated

Infomaniak

Open questions

4 areas to confirm

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

To confirm

Origin hosting

An edge service does not reveal the origin hosting provider.

To confirm

Effective data location

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

To confirm

Post-quantum TLS exchange

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

To confirm

Public canary signal

Detection of this signal was not enabled for this measurement.

These items do not mean there is a problem. They simply show that useful information is still missing.

Sources and evidence

Evidence supporting this reading

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

33evidence items available

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

Download evidence JSON
Explore evidence
#01 Public HTTP response

Evidence: http_header

HTTP headers can ask the browser to enforce specific protections.

Active non-intrusive High
Why it matters

They are visible, verifiable browser-side defensive layers.

What to check next

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

Possible action

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

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

Standards and reference context

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

View raw data 
[
    "default-src 'none'; base-uri 'none'; object-src 'none'; frame-ancestors 'none'; frame-src 'none'; form-action 'self'; script-src 'self' 'nonce-0hAm3unuDcFCdl0I7JhjzZTHThnqjOx-' 'strict-dynamic'; script-src-attr 'none'; style-src 'self'; style-src-attr 'none'; img-src 'self'; font-src 'none'; connect-src 'self'; manifest-src 'self'; worker-src 'self'; media-src 'none'; require-trusted-types-for 'script'; trusted-types kerkito; upgrade-insecure-requests"
]

Rule 2026.09.4 · 2026-09-04T19:31:05+00:00

#02 DNS public records

Evidence: spf_record

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

Passive High
Why it matters

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

What to check next

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

Possible action

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

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

Standards and reference context

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

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

Rule 2026.09.4 · 2026-09-04T19:31:05+00:00

#03 Observed public resources

Evidence: dependency_provider

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

Passive Medium
Why it matters

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

What to check next

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

Possible action

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

Observation
{ "critical": true, "hosts": [ "mta-gw.infomaniak.ch", "ns11.infomaniak.ch", "ns12.infomaniak.ch" ], "id": "infomaniak", "known": true, "name": "Infomaniak", "observation_count": 3, "services": [ "dns", "hosting", "mail" ], "tracker": false }
Understand
Public HTML/resource dependency extraction and provider matching
Source
Observed public resources
Reliability
Medium
What this supports
Describe visible third-party dependencies
What this does not prove
A visible dependency does not prove data location, actual contractual jurisdiction, or hidden subcontractors.

Standards and reference context

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

View raw data 
{
    "critical": true,
    "hosts": [
        "mta-gw.infomaniak.ch",
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "id": "infomaniak",
    "known": true,
    "name": "Infomaniak",
    "observation_count": 3,
    "services": [
        "dns",
        "hosting",
        "mail"
    ],
    "tracker": false
}

Rule 2026.09.4 · 2026-09-04T19:31:05+00:00

#04 module_finding

Evidence: module_finding

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

Passive Medium
Why it matters

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

What to check next

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

Possible action

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

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

Standards and reference context

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

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

Rule 2026.09.4 · 2026-09-04T19:31:05+00:00

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

Rule 2026.09.4 · 2026-09-04T19:31:05+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
[ "no-referrer" ]
Understand
HTTP response-header inspection
Source
Public HTTP response
Reliability
High
What this supports
Describe defensive policies declared on the observed response
What this does not prove
A header being present does not prove it is optimal or that the application has no vulnerabilities.

Standards and reference context

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

View raw data 
[
    "no-referrer"
]

Rule 2026.09.4 · 2026-09-04T19:31:05+00:00

#07 Public HTTP response

Evidence: http_header

HTTP headers can ask the browser to enforce specific protections.

Active non-intrusive High
Why it matters

They are visible, verifiable browser-side defensive layers.

What to check next

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

Possible action

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

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

Standards and reference context

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

View raw data 
[
    "same-origin"
]

Rule 2026.09.4 · 2026-09-04T19:31:05+00:00

#08 DNS public records

Evidence: module_finding

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

Passive High
Why it matters

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

What to check next

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

Possible action

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

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

Standards and reference context

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

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

Rule 2026.09.4 · 2026-09-04T19:31:05+00:00

#09 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 kerkito.com && dig AAAA kerkito.com
View raw data 
185.125.27.197

Rule 2026.09.4 · 2026-09-04T19:31:05+00:00

#10 DNS public records

Evidence: module_finding

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

Passive High
Why it matters

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

What to check next

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

Possible action

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

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

Standards and reference context

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

View raw data 
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}

Rule 2026.09.4 · 2026-09-04T19:31:05+00:00

#11 Public HTTP response

Evidence: http_header

HTTP headers can ask the browser to enforce specific protections.

Active non-intrusive High
Why it matters

They are visible, verifiable browser-side defensive layers.

What to check next

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

Possible action

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

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

Standards and reference context

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

View raw data 
[
    "require-corp"
]

Rule 2026.09.4 · 2026-09-04T19:31:05+00:00

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

Rule 2026.09.4 · 2026-09-04T19:31:05+00:00

#13 Public HTTP response

Evidence: http_header

HTTP headers can ask the browser to enforce specific protections.

Active non-intrusive High
Why it matters

They are visible, verifiable browser-side defensive layers.

What to check next

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

Possible action

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

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

Standards and reference context

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

View raw data 
[
    "same-origin"
]

Rule 2026.09.4 · 2026-09-04T19:31:05+00:00

#14 Mail-related public records

Evidence: mail_policy_flag

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

Active non-intrusive High
Why it matters

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

What to check next

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

Possible action

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

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

Standards and reference context

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

View raw data

Rule 2026.09.4 · 2026-09-04T19:31:05+00:00

#15 Mail-related public records

Evidence: module_finding

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

Active non-intrusive High
Why it matters

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

What to check next

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

Possible action

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

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

Standards and reference context

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

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

Rule 2026.09.4 · 2026-09-04T19:31:05+00:00

#16 DNS public records

Evidence: dns_nameserver

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

Passive High
Why it matters

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

What to check next

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

Possible action

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

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

Standards and reference context

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

Verify it yourself

This command reproduces the public observation without changing the target.

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

Rule 2026.09.4 · 2026-09-04T19:31:05+00:00

#17 technology

Evidence: technology

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

Passive Medium
Why it matters

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

What to check next

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

Possible action

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

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

Standards and reference context

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

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

Rule 2026.09.4 · 2026-09-04T19:31:05+00:00

#18 Public TLS endpoint

Evidence: tls_issuer

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

Active non-intrusive High
Why it matters

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

What to check next

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

Possible action

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

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

Standards and reference context

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

Verify it yourself

This command reproduces the public observation without changing the target.

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

Rule 2026.09.4 · 2026-09-04T19:31:05+00:00

#19 Public HTTP response

Evidence: http_header

HTTP headers can ask the browser to enforce specific protections.

Active non-intrusive High
Why it matters

They are visible, verifiable browser-side defensive layers.

What to check next

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

Possible action

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

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

Standards and reference context

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

View raw data 
[
    "nosniff"
]

Rule 2026.09.4 · 2026-09-04T19:31:05+00:00

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

Rule 2026.09.4 · 2026-09-04T19:31:05+00:00

#21 Public HTTP response

Evidence: http_header

HTTP headers can ask the browser to enforce specific protections.

Active non-intrusive High
Why it matters

They are visible, verifiable browser-side defensive layers.

What to check next

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

Possible action

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

Observation
[ "max-age=63072000; includeSubDomains" ]
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"
]

Rule 2026.09.4 · 2026-09-04T19:31:05+00:00

#22 Mail-related public records

Evidence: mail_policy_flag

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

Active non-intrusive High
Why it matters

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

What to check next

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

Possible action

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

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

Standards and reference context

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

View raw data

Rule 2026.09.4 · 2026-09-04T19:31:05+00:00

#23 DNS public records

Evidence: dmarc_record

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

Passive High
Why it matters

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

What to check next

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

Possible action

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

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

Standards and reference context

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

View raw data 
v=DMARC1; p=reject;

Rule 2026.09.4 · 2026-09-04T19:31:05+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
[ "DENY" ]
Understand
HTTP response-header inspection
Source
Public HTTP response
Reliability
High
What this supports
Describe defensive policies declared on the observed response
What this does not prove
A header being present does not prove it is optimal or that the application has no vulnerabilities.

Standards and reference context

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

View raw data 
[
    "DENY"
]

Rule 2026.09.4 · 2026-09-04T19:31:05+00:00

#25 Mail-related public records

Evidence: dmarc_policy

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

Active non-intrusive High
Why it matters

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

What to check next

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

Possible action

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

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

Standards and reference context

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

Verify it yourself

This command reproduces the public observation without changing the target.

dig TXT _dmarc.kerkito.com
View raw data 
reject

Rule 2026.09.4 · 2026-09-04T19:31:05+00:00

#26 Public HTTP response

Evidence: http_header

HTTP headers can ask the browser to enforce specific protections.

Active non-intrusive High
Why it matters

They are visible, verifiable browser-side defensive layers.

What to check next

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

Possible action

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

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

Standards and reference context

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

View raw data 
[
    "Apache"
]

Rule 2026.09.4 · 2026-09-04T19:31:05+00:00

#27 Mail-related public records

Evidence: mail_policy_flag

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

Active non-intrusive High
Why it matters

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

What to check next

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

Possible action

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

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

Standards and reference context

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

View raw data

Rule 2026.09.4 · 2026-09-04T19:31:05+00:00

#28 DNS public records

Evidence: caa_record

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

Passive High
Why it matters

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

What to check next

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

Possible action

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

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

Standards and reference context

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

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

Rule 2026.09.4 · 2026-09-04T19:31:05+00:00

#29 Mail-related public records

Evidence: module_finding

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

Active non-intrusive High
Why it matters

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

What to check next

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

Possible action

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

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

Standards and reference context

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

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

Rule 2026.09.4 · 2026-09-04T19:31:05+00:00

#30 DNS public records

Evidence: dns_nameserver

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

Passive High
Why it matters

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

What to check next

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

Possible action

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

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

Standards and reference context

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

Verify it yourself

This command reproduces the public observation without changing the target.

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

Rule 2026.09.4 · 2026-09-04T19:31:05+00:00

#31 Public HTTP response

Evidence: http_header

HTTP headers can ask the browser to enforce specific protections.

Active non-intrusive High
Why it matters

They are visible, verifiable browser-side defensive layers.

What to check next

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

Possible action

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

Observation
[ "accelerometer=(), ambient-light-sensor=(), autoplay=(), camera=(), display-capture=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(self), 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 
[
    "accelerometer=(), ambient-light-sensor=(), autoplay=(), camera=(), display-capture=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(self), payment=(), usb=(), browsing-topics=()"
]

Rule 2026.09.4 · 2026-09-04T19:31:05+00:00

#32 Public TLS endpoint

Evidence: tls_valid_to

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

Active non-intrusive High
Why it matters

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

What to check next

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

Possible action

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

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

Standards and reference context

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

View raw data 
2026-10-06T22:15:36+00:00

Rule 2026.09.4 · 2026-09-04T19:31:05+00:00

#33 Mail-related public records

Evidence: module_finding

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

Active non-intrusive High
Why it matters

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

What to check next

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

Possible action

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

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

Standards and reference context

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

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

Rule 2026.09.4 · 2026-09-04T19:31:05+00:00

Show technical details 
{
    "schema_version": "2.0",
    "engine_version": "2.6.0.1",
    "pattern_version": "2026.09.4",
    "scope": {
        "mode": "passive",
        "coverage": "full",
        "access_level": "full",
        "access_reason": "public_document_available",
        "requests": 2,
        "homepage_only": true,
        "javascript_executed": false,
        "ports_scanned": false,
        "private_networks_blocked": true,
        "protection_bypassed": false,
        "max_body_bytes": 1572864,
        "scan_budget_seconds": 24,
        "budget_exhausted": false,
        "transport": "curl_with_socket_fallback"
    },
    "entity": {
        "id": "52cb57e735b8b36578115c12f1b7fbc6c6c9bc6ce16c4fa987b1800fd7d4d869",
        "display_name": "kerkito.com",
        "slug": "kerkito-com",
        "entity_type": "domain_subject",
        "auto_created": true,
        "primary_asset": "kerkito.com"
    },
    "methodology": {
        "version": "2.3.1",
        "model": "evidence_first",
        "principles": [
            "absence_of_evidence_is_not_evidence_of_absence",
            "unknown_remains_unknown",
            "provider_metadata_is_not_data_location",
            "edge_provider_is_not_origin_host",
            "single_snapshot_does_not_prove_resilience"
        ]
    },
    "trajectory_summary": {
        "has_previous_scan": false,
        "change_counts": [],
        "observation_count": 33,
        "evidence_count": 33,
        "provider_count": 1,
        "strategic_signal_count": 1,
        "top_signal_count": 1
    }
}