OBSERVE · CONNECT · UNDERSTAND
FR EN
Read a domain

PUBLIC DOMAIN DOSSIER

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

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:33 UTC First observation 2026-09-04 19:33 UTC Latest observation 2026-09-04 19:33 UTC
History JSON Markdown

TIME

What changed over time

Initial reference point created today

0Appeared
0Modified
0Stable
0Disappeared

SHORT VIEW

Four readings before the detail

The 12 historical angles remain available below for deeper inspection.

Identity & governance

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

Infrastructure & transport

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

Mail & trust

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

Measured on 2026-09-04 19:33 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
dns_nameserver dns d635eb6b5b4fb83847751ee092d78c2bcd7502462315dc00df6d087a33524979 
"ns42.infomaniak.com"
module_finding dns 1d0b4f05948b02fb3117b7cca24a7aee8bb709a91479e640f815ad20b229943b 
{
    "evidence": null,
    "severity": "medium"
}
module_finding dns c855cc674c3e7d61968122092436cbbafcf7960a260b555d2465fe1916e9a37c 
{
    "evidence": null,
    "severity": "low"
}
spf_record dns e33dceba2650b1667a8c53a62b8fede97fbb74f2c37cce4c66d2dd250953b94b 
"v=spf1 include:spf.infomaniak.ch -all"
module_finding dns 263a892b26d655968d7b657f3bd4b9321786422180c625ed26909a0830935ceb 
{
    "evidence": [
        "ns41.infomaniak.com",
        "ns42.infomaniak.com"
    ],
    "severity": "low"
}
dns_address dns 0189eaf3fd926459fa171c7cf459f6a0d9ef76fed350535f8cc65a71ff3edd10 
"2001:1600::aaaa:0:0:80:5b"
mail_exchanger dns b65c4f6dad97f53bc9a947b5233f37506c1c1be8a26b0d006c350f9574b0fc79 
"mta-gw.infomaniak.ch"
module_finding dns 2565cb51b22be6321893a953fe784e37b90e6c88edb242ef8a7e60631d8933af 
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
dns_nameserver dns a6ccb4d928c1ce991422913b96c7613bd30926e83e8cb06e7d59670bd1982d30 
"ns41.infomaniak.com"
dns_address dns ab69add26295c21a08ac7e120b17789eb8c196cca6833091edd5d21d7991c17c 
"185.125.27.197"
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

dns_nameserver dns d635eb6b5b4fb83847751ee092d78c2bcd7502462315dc00df6d087a33524979 
"ns42.infomaniak.com"
module_finding dns 1d0b4f05948b02fb3117b7cca24a7aee8bb709a91479e640f815ad20b229943b 
{
    "evidence": null,
    "severity": "medium"
}
module_finding dns c855cc674c3e7d61968122092436cbbafcf7960a260b555d2465fe1916e9a37c 
{
    "evidence": null,
    "severity": "low"
}
spf_record dns e33dceba2650b1667a8c53a62b8fede97fbb74f2c37cce4c66d2dd250953b94b 
"v=spf1 include:spf.infomaniak.ch -all"
module_finding resilience 21cdb730234499201e257a64804c93095a65c2526bbaedb0a985f9c1bb2bd31b 
{
    "evidence": [
        "ns41.infomaniak.com",
        "ns42.infomaniak.com"
    ],
    "severity": "medium"
}
module_finding dns 263a892b26d655968d7b657f3bd4b9321786422180c625ed26909a0830935ceb 
{
    "evidence": [
        "ns41.infomaniak.com",
        "ns42.infomaniak.com"
    ],
    "severity": "low"
}
dns_address dns 0189eaf3fd926459fa171c7cf459f6a0d9ef76fed350535f8cc65a71ff3edd10 
"2001:1600::aaaa:0:0:80:5b"
dependency_provider dependencies d09005dbfbcdb06ab1a8bd34dafdb314b3911dd978a6457c95ee8ae5d2a94908 
{
    "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
}
mail_exchanger dns b65c4f6dad97f53bc9a947b5233f37506c1c1be8a26b0d006c350f9574b0fc79 
"mta-gw.infomaniak.ch"
module_finding dns 2565cb51b22be6321893a953fe784e37b90e6c88edb242ef8a7e60631d8933af 
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
dns_nameserver dns a6ccb4d928c1ce991422913b96c7613bd30926e83e8cb06e7d59670bd1982d30 
"ns41.infomaniak.com"
dns_address dns ab69add26295c21a08ac7e120b17789eb8c196cca6833091edd5d21d7991c17c 
"185.125.27.197"
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 870e723a67e530e42e82998a8ba81b27b7744d269d5a05648da8343b38bf8192 
[
    "DENY"
]
http_header headers 0b59023eae9b011d37b820632656b235cabcdb193a6168c78e733ea2c4d16904 
[
    "max-age=31536000; includeSubDomains"
]
module_finding headers df087993c76fd3e7d95974b4a5214bf7542037d098932ddb797876b241f1809d 
{
    "evidence": null,
    "severity": "low"
}
http_header headers 484a0681c4de41c0cefbcec1753a6081860dcef3b3c42d692fab244637939433 
[
    "nosniff"
]
http_header headers 637adf493aba1520b430242bd303eecc72693455135ab2e93097de667b110876 
[
    "camera=(), microphone=(), geolocation=()"
]
tls_valid_to tls 94e7d07c71a421321cf46d04e993382afd8ed9f19c3cd8db0d975c36a7cef191 
"2026-12-01T22:27:34+00:00"
module_finding headers fd5ab86bde701889d4fb506087ddecc794d55a9d67035a7c9697b079604941d4 
{
    "evidence": null,
    "severity": "low"
}
http_header headers 37af29a76eee541e58853d531bf111be8e9ea91e4ff8408c1d46cb09460dd50c 
[
    "strict-origin-when-cross-origin"
]
tls_issuer tls f4a80fa3fa078cab9474a16f8fd6e1ed00303ddc48fdfdf01590ab2139130d60 
"C = US, O = Let's Encrypt, CN = YR1"
http_header headers 93dc45b6d4351f22c2c5509bf3bf80c5f83981a06d263171dacc1eb8dc333dda 
[
    "default-src 'self'; img-src 'self' data:; style-src 'self'; script-src 'self' 'nonce-xD/D7+PEZiXPB7QeRtI188fk'; font-src 'self'; connect-src 'self'; form-action 'self'; base-uri 'self'; frame-ancestors 'none'; upgrade-insecure-requests"
]
module_finding headers 2d49216c2c3b908b5afa0adc3936816b816bea8a25dd32b6c0670b0028ac9fa3 
{
    "evidence": null,
    "severity": "info"
}
http_header headers 12f2859684ad8fedb95c7441279b8c2b8f4cd5cfc230b0b4da852b7b77876060 
[
    "Apache"
]
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
1
Changes
0
dns_nameserver dns d635eb6b5b4fb83847751ee092d78c2bcd7502462315dc00df6d087a33524979 
"ns42.infomaniak.com"
mail_policy_flag mail_trust 4a7f769b08a4af121f7970f097647d9651ba2112b4b290efcf6fb8b480b2a459 
false
module_finding mail_trust 56531b4f06c66027a069094dc4608cc357fc8716b1ae35a16b0ad41280ef1e45 
{
    "evidence": [
        {
            "host": "mta-gw.infomaniak.ch",
            "priority": 5
        }
    ],
    "severity": "low"
}
module_finding dns 1d0b4f05948b02fb3117b7cca24a7aee8bb709a91479e640f815ad20b229943b 
{
    "evidence": null,
    "severity": "medium"
}
module_finding dns c855cc674c3e7d61968122092436cbbafcf7960a260b555d2465fe1916e9a37c 
{
    "evidence": null,
    "severity": "low"
}
spf_record dns e33dceba2650b1667a8c53a62b8fede97fbb74f2c37cce4c66d2dd250953b94b 
"v=spf1 include:spf.infomaniak.ch -all"
spf_policy mail_trust 8f2b1c465593737db426be4ddc3f1f2f7cbe34cc2c57914658ee0be13a514e8d 
"hardfail"
mail_policy_flag mail_trust eac49db8dff0f6d4bcb5065a6f31fcb640c0c4bea94e73610bb6f825de046374 
false
module_finding dns 263a892b26d655968d7b657f3bd4b9321786422180c625ed26909a0830935ceb 
{
    "evidence": [
        "ns41.infomaniak.com",
        "ns42.infomaniak.com"
    ],
    "severity": "low"
}
dns_address dns 0189eaf3fd926459fa171c7cf459f6a0d9ef76fed350535f8cc65a71ff3edd10 
"2001:1600::aaaa:0:0:80:5b"
mail_exchanger dns b65c4f6dad97f53bc9a947b5233f37506c1c1be8a26b0d006c350f9574b0fc79 
"mta-gw.infomaniak.ch"
module_finding mail_trust c200b38208842825453a3e8d8b1fba58ab737dff34f41031ee0803c009b42dab 
{
    "evidence": null,
    "severity": "low"
}
module_finding mail_trust 055b77a69b5ef7c66128ac16245be36fc6c26cc0f69a868b9d803150d11d7a68 
{
    "evidence": null,
    "severity": "low"
}
module_finding dns 2565cb51b22be6321893a953fe784e37b90e6c88edb242ef8a7e60631d8933af 
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
dns_nameserver dns a6ccb4d928c1ce991422913b96c7613bd30926e83e8cb06e7d59670bd1982d30 
"ns41.infomaniak.com"
dns_address dns ab69add26295c21a08ac7e120b17789eb8c196cca6833091edd5d21d7991c17c 
"185.125.27.197"
module_finding mail_trust fd70726fd9641962b7c4b97be8478384bc1d12589c713e61a9e0decb21afd1ce 
{
    "evidence": null,
    "severity": "high"
}
mail_policy_flag mail_trust f0f47ede9fa4f0ffba5c7e3cde41b492078d443f60fd4dcb770760bf4711d11d 
false
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
1
Changes
0
dns_nameserver dns d635eb6b5b4fb83847751ee092d78c2bcd7502462315dc00df6d087a33524979 
"ns42.infomaniak.com"
mail_policy_flag mail_trust 4a7f769b08a4af121f7970f097647d9651ba2112b4b290efcf6fb8b480b2a459 
false
module_finding mail_trust 56531b4f06c66027a069094dc4608cc357fc8716b1ae35a16b0ad41280ef1e45 
{
    "evidence": [
        {
            "host": "mta-gw.infomaniak.ch",
            "priority": 5
        }
    ],
    "severity": "low"
}
module_finding dns 1d0b4f05948b02fb3117b7cca24a7aee8bb709a91479e640f815ad20b229943b 
{
    "evidence": null,
    "severity": "medium"
}
module_finding dns c855cc674c3e7d61968122092436cbbafcf7960a260b555d2465fe1916e9a37c 
{
    "evidence": null,
    "severity": "low"
}
spf_record dns e33dceba2650b1667a8c53a62b8fede97fbb74f2c37cce4c66d2dd250953b94b 
"v=spf1 include:spf.infomaniak.ch -all"
spf_policy mail_trust 8f2b1c465593737db426be4ddc3f1f2f7cbe34cc2c57914658ee0be13a514e8d 
"hardfail"
mail_policy_flag mail_trust eac49db8dff0f6d4bcb5065a6f31fcb640c0c4bea94e73610bb6f825de046374 
false
module_finding dns 263a892b26d655968d7b657f3bd4b9321786422180c625ed26909a0830935ceb 
{
    "evidence": [
        "ns41.infomaniak.com",
        "ns42.infomaniak.com"
    ],
    "severity": "low"
}
dns_address dns 0189eaf3fd926459fa171c7cf459f6a0d9ef76fed350535f8cc65a71ff3edd10 
"2001:1600::aaaa:0:0:80:5b"
mail_exchanger dns b65c4f6dad97f53bc9a947b5233f37506c1c1be8a26b0d006c350f9574b0fc79 
"mta-gw.infomaniak.ch"
module_finding mail_trust c200b38208842825453a3e8d8b1fba58ab737dff34f41031ee0803c009b42dab 
{
    "evidence": null,
    "severity": "low"
}
module_finding mail_trust 055b77a69b5ef7c66128ac16245be36fc6c26cc0f69a868b9d803150d11d7a68 
{
    "evidence": null,
    "severity": "low"
}
module_finding dns 2565cb51b22be6321893a953fe784e37b90e6c88edb242ef8a7e60631d8933af 
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
dns_nameserver dns a6ccb4d928c1ce991422913b96c7613bd30926e83e8cb06e7d59670bd1982d30 
"ns41.infomaniak.com"
dns_address dns ab69add26295c21a08ac7e120b17789eb8c196cca6833091edd5d21d7991c17c 
"185.125.27.197"
module_finding mail_trust fd70726fd9641962b7c4b97be8478384bc1d12589c713e61a9e0decb21afd1ce 
{
    "evidence": null,
    "severity": "high"
}
mail_policy_flag mail_trust f0f47ede9fa4f0ffba5c7e3cde41b492078d443f60fd4dcb770760bf4711d11d 
false
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

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

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

Mapping version
2.3.1
Evidence
12
Signals
2
Changes
0
dns_nameserver dns d635eb6b5b4fb83847751ee092d78c2bcd7502462315dc00df6d087a33524979 
"ns42.infomaniak.com"
module_finding dns 1d0b4f05948b02fb3117b7cca24a7aee8bb709a91479e640f815ad20b229943b 
{
    "evidence": null,
    "severity": "medium"
}
module_finding dns c855cc674c3e7d61968122092436cbbafcf7960a260b555d2465fe1916e9a37c 
{
    "evidence": null,
    "severity": "low"
}
spf_record dns e33dceba2650b1667a8c53a62b8fede97fbb74f2c37cce4c66d2dd250953b94b 
"v=spf1 include:spf.infomaniak.ch -all"
module_finding dns 263a892b26d655968d7b657f3bd4b9321786422180c625ed26909a0830935ceb 
{
    "evidence": [
        "ns41.infomaniak.com",
        "ns42.infomaniak.com"
    ],
    "severity": "low"
}
dns_address dns 0189eaf3fd926459fa171c7cf459f6a0d9ef76fed350535f8cc65a71ff3edd10 
"2001:1600::aaaa:0:0:80:5b"
dependency_provider dependencies d09005dbfbcdb06ab1a8bd34dafdb314b3911dd978a6457c95ee8ae5d2a94908 
{
    "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
}
mail_exchanger dns b65c4f6dad97f53bc9a947b5233f37506c1c1be8a26b0d006c350f9574b0fc79 
"mta-gw.infomaniak.ch"
module_finding dns 2565cb51b22be6321893a953fe784e37b90e6c88edb242ef8a7e60631d8933af 
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
dns_nameserver dns a6ccb4d928c1ce991422913b96c7613bd30926e83e8cb06e7d59670bd1982d30 
"ns41.infomaniak.com"
dns_address dns ab69add26295c21a08ac7e120b17789eb8c196cca6833091edd5d21d7991c17c 
"185.125.27.197"
cookie privacy ea23ac03b2fd931fcd889aec30b924aff9d2f914a1a7fbc906df3bb7d450db87 
{
    "http_only": true,
    "name": "PHPSESSID",
    "same_site": "lax",
    "secure": true
}
07
Documented First observation

Observable technologies

Public evidence provides enough material to document this angle

Angle 07

Observable technologies

Documented First observation

Public evidence provides enough material to document this angle

01

Why it matters

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

02

How to read it

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

03

What it is for

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

04

What it does not prove

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

Material available for this angle

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

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

Mapping version
2.3.1
Evidence
12
Signals
0
Changes
0
http_header headers 870e723a67e530e42e82998a8ba81b27b7744d269d5a05648da8343b38bf8192 
[
    "DENY"
]
http_header headers 0b59023eae9b011d37b820632656b235cabcdb193a6168c78e733ea2c4d16904 
[
    "max-age=31536000; includeSubDomains"
]
module_finding headers df087993c76fd3e7d95974b4a5214bf7542037d098932ddb797876b241f1809d 
{
    "evidence": null,
    "severity": "low"
}
technology technology f9d107b650135e6b153cf1ddafee139dbfd8b2f344046df9394210c225d9977f 
{
    "name": "Apache",
    "version": "",
    "version_exposed": false
}
http_header headers 484a0681c4de41c0cefbcec1753a6081860dcef3b3c42d692fab244637939433 
[
    "nosniff"
]
http_header headers 637adf493aba1520b430242bd303eecc72693455135ab2e93097de667b110876 
[
    "camera=(), microphone=(), geolocation=()"
]
technology technology a30a2d501c400aaba07cba6319a82c4a48ce913a3c7817b297794dc85eacc5f5 
{
    "name": "PHP",
    "version": "",
    "version_exposed": false
}
module_finding headers fd5ab86bde701889d4fb506087ddecc794d55a9d67035a7c9697b079604941d4 
{
    "evidence": null,
    "severity": "low"
}
http_header headers 37af29a76eee541e58853d531bf111be8e9ea91e4ff8408c1d46cb09460dd50c 
[
    "strict-origin-when-cross-origin"
]
http_header headers 93dc45b6d4351f22c2c5509bf3bf80c5f83981a06d263171dacc1eb8dc333dda 
[
    "default-src 'self'; img-src 'self' data:; style-src 'self'; script-src 'self' 'nonce-xD/D7+PEZiXPB7QeRtI188fk'; font-src 'self'; connect-src 'self'; form-action 'self'; base-uri 'self'; frame-ancestors 'none'; upgrade-insecure-requests"
]
module_finding headers 2d49216c2c3b908b5afa0adc3936816b816bea8a25dd32b6c0670b0028ac9fa3 
{
    "evidence": null,
    "severity": "info"
}
http_header headers 12f2859684ad8fedb95c7441279b8c2b8f4cd5cfc230b0b4da852b7b77876060 
[
    "Apache"
]
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

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

Unknowns and limitations

1 items still require qualification

http_header headers 870e723a67e530e42e82998a8ba81b27b7744d269d5a05648da8343b38bf8192 
[
    "DENY"
]
module_finding mail_trust 56531b4f06c66027a069094dc4608cc357fc8716b1ae35a16b0ad41280ef1e45 
{
    "evidence": [
        {
            "host": "mta-gw.infomaniak.ch",
            "priority": 5
        }
    ],
    "severity": "low"
}
module_finding dns 1d0b4f05948b02fb3117b7cca24a7aee8bb709a91479e640f815ad20b229943b 
{
    "evidence": null,
    "severity": "medium"
}
http_header headers 0b59023eae9b011d37b820632656b235cabcdb193a6168c78e733ea2c4d16904 
[
    "max-age=31536000; includeSubDomains"
]
module_finding headers df087993c76fd3e7d95974b4a5214bf7542037d098932ddb797876b241f1809d 
{
    "evidence": null,
    "severity": "low"
}
module_finding dns c855cc674c3e7d61968122092436cbbafcf7960a260b555d2465fe1916e9a37c 
{
    "evidence": null,
    "severity": "low"
}
http_header headers 484a0681c4de41c0cefbcec1753a6081860dcef3b3c42d692fab244637939433 
[
    "nosniff"
]
module_finding transparency de5f5d17014e78e47a472fcdee58d8af152be9f390b45a0ff7aa56bff3a65b74 
{
    "evidence": 403,
    "severity": "medium"
}
module_finding resilience 21cdb730234499201e257a64804c93095a65c2526bbaedb0a985f9c1bb2bd31b 
{
    "evidence": [
        "ns41.infomaniak.com",
        "ns42.infomaniak.com"
    ],
    "severity": "medium"
}
module_finding dns 263a892b26d655968d7b657f3bd4b9321786422180c625ed26909a0830935ceb 
{
    "evidence": [
        "ns41.infomaniak.com",
        "ns42.infomaniak.com"
    ],
    "severity": "low"
}
http_header headers 637adf493aba1520b430242bd303eecc72693455135ab2e93097de667b110876 
[
    "camera=(), microphone=(), geolocation=()"
]
module_finding headers fd5ab86bde701889d4fb506087ddecc794d55a9d67035a7c9697b079604941d4 
{
    "evidence": null,
    "severity": "low"
}
module_finding mail_trust c200b38208842825453a3e8d8b1fba58ab737dff34f41031ee0803c009b42dab 
{
    "evidence": null,
    "severity": "low"
}
http_header headers 37af29a76eee541e58853d531bf111be8e9ea91e4ff8408c1d46cb09460dd50c 
[
    "strict-origin-when-cross-origin"
]
module_finding mail_trust 055b77a69b5ef7c66128ac16245be36fc6c26cc0f69a868b9d803150d11d7a68 
{
    "evidence": null,
    "severity": "low"
}
module_finding transparency 283f9c1959ab5d6896f04c822af8337e23893e10e1abc7942c0b14bbb584db89 
{
    "evidence": null,
    "severity": "medium"
}
http_header headers 93dc45b6d4351f22c2c5509bf3bf80c5f83981a06d263171dacc1eb8dc333dda 
[
    "default-src 'self'; img-src 'self' data:; style-src 'self'; script-src 'self' 'nonce-xD/D7+PEZiXPB7QeRtI188fk'; font-src 'self'; connect-src 'self'; form-action 'self'; base-uri 'self'; frame-ancestors 'none'; upgrade-insecure-requests"
]
module_finding dns 2565cb51b22be6321893a953fe784e37b90e6c88edb242ef8a7e60631d8933af 
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
module_finding headers 2d49216c2c3b908b5afa0adc3936816b816bea8a25dd32b6c0670b0028ac9fa3 
{
    "evidence": null,
    "severity": "info"
}
module_finding mail_trust fd70726fd9641962b7c4b97be8478384bc1d12589c713e61a9e0decb21afd1ce 
{
    "evidence": null,
    "severity": "high"
}
http_header headers 12f2859684ad8fedb95c7441279b8c2b8f4cd5cfc230b0b4da852b7b77876060 
[
    "Apache"
]
cookie privacy ea23ac03b2fd931fcd889aec30b924aff9d2f914a1a7fbc906df3bb7d450db87 
{
    "http_only": true,
    "name": "PHPSESSID",
    "same_site": "lax",
    "secure": true
}
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

21evidence
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
21
Signals
0
Changes
0
http_header headers 870e723a67e530e42e82998a8ba81b27b7744d269d5a05648da8343b38bf8192 
[
    "DENY"
]
module_finding mail_trust 56531b4f06c66027a069094dc4608cc357fc8716b1ae35a16b0ad41280ef1e45 
{
    "evidence": [
        {
            "host": "mta-gw.infomaniak.ch",
            "priority": 5
        }
    ],
    "severity": "low"
}
module_finding dns 1d0b4f05948b02fb3117b7cca24a7aee8bb709a91479e640f815ad20b229943b 
{
    "evidence": null,
    "severity": "medium"
}
http_header headers 0b59023eae9b011d37b820632656b235cabcdb193a6168c78e733ea2c4d16904 
[
    "max-age=31536000; includeSubDomains"
]
module_finding headers df087993c76fd3e7d95974b4a5214bf7542037d098932ddb797876b241f1809d 
{
    "evidence": null,
    "severity": "low"
}
module_finding dns c855cc674c3e7d61968122092436cbbafcf7960a260b555d2465fe1916e9a37c 
{
    "evidence": null,
    "severity": "low"
}
http_header headers 484a0681c4de41c0cefbcec1753a6081860dcef3b3c42d692fab244637939433 
[
    "nosniff"
]
module_finding transparency de5f5d17014e78e47a472fcdee58d8af152be9f390b45a0ff7aa56bff3a65b74 
{
    "evidence": 403,
    "severity": "medium"
}
module_finding resilience 21cdb730234499201e257a64804c93095a65c2526bbaedb0a985f9c1bb2bd31b 
{
    "evidence": [
        "ns41.infomaniak.com",
        "ns42.infomaniak.com"
    ],
    "severity": "medium"
}
module_finding dns 263a892b26d655968d7b657f3bd4b9321786422180c625ed26909a0830935ceb 
{
    "evidence": [
        "ns41.infomaniak.com",
        "ns42.infomaniak.com"
    ],
    "severity": "low"
}
http_header headers 637adf493aba1520b430242bd303eecc72693455135ab2e93097de667b110876 
[
    "camera=(), microphone=(), geolocation=()"
]
module_finding headers fd5ab86bde701889d4fb506087ddecc794d55a9d67035a7c9697b079604941d4 
{
    "evidence": null,
    "severity": "low"
}
module_finding mail_trust c200b38208842825453a3e8d8b1fba58ab737dff34f41031ee0803c009b42dab 
{
    "evidence": null,
    "severity": "low"
}
http_header headers 37af29a76eee541e58853d531bf111be8e9ea91e4ff8408c1d46cb09460dd50c 
[
    "strict-origin-when-cross-origin"
]
module_finding mail_trust 055b77a69b5ef7c66128ac16245be36fc6c26cc0f69a868b9d803150d11d7a68 
{
    "evidence": null,
    "severity": "low"
}
module_finding transparency 283f9c1959ab5d6896f04c822af8337e23893e10e1abc7942c0b14bbb584db89 
{
    "evidence": null,
    "severity": "medium"
}
http_header headers 93dc45b6d4351f22c2c5509bf3bf80c5f83981a06d263171dacc1eb8dc333dda 
[
    "default-src 'self'; img-src 'self' data:; style-src 'self'; script-src 'self' 'nonce-xD/D7+PEZiXPB7QeRtI188fk'; font-src 'self'; connect-src 'self'; form-action 'self'; base-uri 'self'; frame-ancestors 'none'; upgrade-insecure-requests"
]
module_finding dns 2565cb51b22be6321893a953fe784e37b90e6c88edb242ef8a7e60631d8933af 
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
module_finding headers 2d49216c2c3b908b5afa0adc3936816b816bea8a25dd32b6c0670b0028ac9fa3 
{
    "evidence": null,
    "severity": "info"
}
module_finding mail_trust fd70726fd9641962b7c4b97be8478384bc1d12589c713e61a9e0decb21afd1ce 
{
    "evidence": null,
    "severity": "high"
}
http_header headers 12f2859684ad8fedb95c7441279b8c2b8f4cd5cfc230b0b4da852b7b77876060 
[
    "Apache"
]
10
Partial First observation

Security signals

This angle is only partially documented by public evidence

Angle 10

Security signals

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

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

Unknowns and limitations

2 items still require qualification

dns_nameserver dns d635eb6b5b4fb83847751ee092d78c2bcd7502462315dc00df6d087a33524979 
"ns42.infomaniak.com"
http_header headers 870e723a67e530e42e82998a8ba81b27b7744d269d5a05648da8343b38bf8192 
[
    "DENY"
]
mail_policy_flag mail_trust 4a7f769b08a4af121f7970f097647d9651ba2112b4b290efcf6fb8b480b2a459 
false
module_finding mail_trust 56531b4f06c66027a069094dc4608cc357fc8716b1ae35a16b0ad41280ef1e45 
{
    "evidence": [
        {
            "host": "mta-gw.infomaniak.ch",
            "priority": 5
        }
    ],
    "severity": "low"
}
module_finding dns 1d0b4f05948b02fb3117b7cca24a7aee8bb709a91479e640f815ad20b229943b 
{
    "evidence": null,
    "severity": "medium"
}
http_header headers 0b59023eae9b011d37b820632656b235cabcdb193a6168c78e733ea2c4d16904 
[
    "max-age=31536000; includeSubDomains"
]
module_finding headers df087993c76fd3e7d95974b4a5214bf7542037d098932ddb797876b241f1809d 
{
    "evidence": null,
    "severity": "low"
}
module_finding dns c855cc674c3e7d61968122092436cbbafcf7960a260b555d2465fe1916e9a37c 
{
    "evidence": null,
    "severity": "low"
}
spf_record dns e33dceba2650b1667a8c53a62b8fede97fbb74f2c37cce4c66d2dd250953b94b 
"v=spf1 include:spf.infomaniak.ch -all"
spf_policy mail_trust 8f2b1c465593737db426be4ddc3f1f2f7cbe34cc2c57914658ee0be13a514e8d 
"hardfail"
mail_policy_flag mail_trust eac49db8dff0f6d4bcb5065a6f31fcb640c0c4bea94e73610bb6f825de046374 
false
http_header headers 484a0681c4de41c0cefbcec1753a6081860dcef3b3c42d692fab244637939433 
[
    "nosniff"
]
module_finding transparency de5f5d17014e78e47a472fcdee58d8af152be9f390b45a0ff7aa56bff3a65b74 
{
    "evidence": 403,
    "severity": "medium"
}
module_finding resilience 21cdb730234499201e257a64804c93095a65c2526bbaedb0a985f9c1bb2bd31b 
{
    "evidence": [
        "ns41.infomaniak.com",
        "ns42.infomaniak.com"
    ],
    "severity": "medium"
}
module_finding dns 263a892b26d655968d7b657f3bd4b9321786422180c625ed26909a0830935ceb 
{
    "evidence": [
        "ns41.infomaniak.com",
        "ns42.infomaniak.com"
    ],
    "severity": "low"
}
http_header headers 637adf493aba1520b430242bd303eecc72693455135ab2e93097de667b110876 
[
    "camera=(), microphone=(), geolocation=()"
]
tls_valid_to tls 94e7d07c71a421321cf46d04e993382afd8ed9f19c3cd8db0d975c36a7cef191 
"2026-12-01T22:27:34+00:00"
dns_address dns 0189eaf3fd926459fa171c7cf459f6a0d9ef76fed350535f8cc65a71ff3edd10 
"2001:1600::aaaa:0:0:80:5b"
mail_exchanger dns b65c4f6dad97f53bc9a947b5233f37506c1c1be8a26b0d006c350f9574b0fc79 
"mta-gw.infomaniak.ch"
module_finding headers fd5ab86bde701889d4fb506087ddecc794d55a9d67035a7c9697b079604941d4 
{
    "evidence": null,
    "severity": "low"
}
module_finding mail_trust c200b38208842825453a3e8d8b1fba58ab737dff34f41031ee0803c009b42dab 
{
    "evidence": null,
    "severity": "low"
}
http_header headers 37af29a76eee541e58853d531bf111be8e9ea91e4ff8408c1d46cb09460dd50c 
[
    "strict-origin-when-cross-origin"
]
module_finding mail_trust 055b77a69b5ef7c66128ac16245be36fc6c26cc0f69a868b9d803150d11d7a68 
{
    "evidence": null,
    "severity": "low"
}
tls_issuer tls f4a80fa3fa078cab9474a16f8fd6e1ed00303ddc48fdfdf01590ab2139130d60 
"C = US, O = Let's Encrypt, CN = YR1"
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

37evidence
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
37
Signals
2
Changes
0
dns_nameserver dns d635eb6b5b4fb83847751ee092d78c2bcd7502462315dc00df6d087a33524979 
"ns42.infomaniak.com"
http_header headers 870e723a67e530e42e82998a8ba81b27b7744d269d5a05648da8343b38bf8192 
[
    "DENY"
]
mail_policy_flag mail_trust 4a7f769b08a4af121f7970f097647d9651ba2112b4b290efcf6fb8b480b2a459 
false
module_finding mail_trust 56531b4f06c66027a069094dc4608cc357fc8716b1ae35a16b0ad41280ef1e45 
{
    "evidence": [
        {
            "host": "mta-gw.infomaniak.ch",
            "priority": 5
        }
    ],
    "severity": "low"
}
module_finding dns 1d0b4f05948b02fb3117b7cca24a7aee8bb709a91479e640f815ad20b229943b 
{
    "evidence": null,
    "severity": "medium"
}
http_header headers 0b59023eae9b011d37b820632656b235cabcdb193a6168c78e733ea2c4d16904 
[
    "max-age=31536000; includeSubDomains"
]
module_finding headers df087993c76fd3e7d95974b4a5214bf7542037d098932ddb797876b241f1809d 
{
    "evidence": null,
    "severity": "low"
}
module_finding dns c855cc674c3e7d61968122092436cbbafcf7960a260b555d2465fe1916e9a37c 
{
    "evidence": null,
    "severity": "low"
}
spf_record dns e33dceba2650b1667a8c53a62b8fede97fbb74f2c37cce4c66d2dd250953b94b 
"v=spf1 include:spf.infomaniak.ch -all"
spf_policy mail_trust 8f2b1c465593737db426be4ddc3f1f2f7cbe34cc2c57914658ee0be13a514e8d 
"hardfail"
technology technology f9d107b650135e6b153cf1ddafee139dbfd8b2f344046df9394210c225d9977f 
{
    "name": "Apache",
    "version": "",
    "version_exposed": false
}
mail_policy_flag mail_trust eac49db8dff0f6d4bcb5065a6f31fcb640c0c4bea94e73610bb6f825de046374 
false
http_header headers 484a0681c4de41c0cefbcec1753a6081860dcef3b3c42d692fab244637939433 
[
    "nosniff"
]
module_finding transparency de5f5d17014e78e47a472fcdee58d8af152be9f390b45a0ff7aa56bff3a65b74 
{
    "evidence": 403,
    "severity": "medium"
}
module_finding resilience 21cdb730234499201e257a64804c93095a65c2526bbaedb0a985f9c1bb2bd31b 
{
    "evidence": [
        "ns41.infomaniak.com",
        "ns42.infomaniak.com"
    ],
    "severity": "medium"
}
module_finding dns 263a892b26d655968d7b657f3bd4b9321786422180c625ed26909a0830935ceb 
{
    "evidence": [
        "ns41.infomaniak.com",
        "ns42.infomaniak.com"
    ],
    "severity": "low"
}
http_header headers 637adf493aba1520b430242bd303eecc72693455135ab2e93097de667b110876 
[
    "camera=(), microphone=(), geolocation=()"
]
tls_valid_to tls 94e7d07c71a421321cf46d04e993382afd8ed9f19c3cd8db0d975c36a7cef191 
"2026-12-01T22:27:34+00:00"
dns_address dns 0189eaf3fd926459fa171c7cf459f6a0d9ef76fed350535f8cc65a71ff3edd10 
"2001:1600::aaaa:0:0:80:5b"
dependency_provider dependencies d09005dbfbcdb06ab1a8bd34dafdb314b3911dd978a6457c95ee8ae5d2a94908 
{
    "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
}
technology technology a30a2d501c400aaba07cba6319a82c4a48ce913a3c7817b297794dc85eacc5f5 
{
    "name": "PHP",
    "version": "",
    "version_exposed": false
}
mail_exchanger dns b65c4f6dad97f53bc9a947b5233f37506c1c1be8a26b0d006c350f9574b0fc79 
"mta-gw.infomaniak.ch"
module_finding headers fd5ab86bde701889d4fb506087ddecc794d55a9d67035a7c9697b079604941d4 
{
    "evidence": null,
    "severity": "low"
}
module_finding mail_trust c200b38208842825453a3e8d8b1fba58ab737dff34f41031ee0803c009b42dab 
{
    "evidence": null,
    "severity": "low"
}

Overview

What the domain already shows, and what still needs clarification

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

Visible relations

Visible relations around the domain

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

Observed domain esskifa.com

DNS

2
DNS server Observed

ns42.infomaniak.com

DNS server Observed

ns41.infomaniak.com

mail

1
Mail server Observed

mta-gw.infomaniak.ch

technology

2
Observed technology Observed

Apache

Observed technology Observed

PHP

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

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

37evidence items available

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

Download evidence JSON
Explore evidence
#01 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 esskifa.com
View raw data 
ns42.infomaniak.com

Rule 2026.09.4 · 2026-09-04T19:33:51+00:00

#02 Public HTTP response

Evidence: http_header

HTTP headers can ask the browser to enforce specific protections.

Active non-intrusive High
Why it matters

They are visible, verifiable browser-side defensive layers.

What to check next

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

Possible action

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

Observation
[ "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:33:51+00:00

#03 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:33:51+00:00

#04 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:33:51+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": "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-04T19:33:51+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
[ "max-age=31536000; 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=31536000; includeSubDomains"
]

Rule 2026.09.4 · 2026-09-04T19:33:51+00:00

#07 Public HTTP response

Evidence: module_finding

HTTP headers can ask the browser to enforce specific protections.

Active non-intrusive High
Why it matters

They are visible, verifiable browser-side defensive layers.

What to check next

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

Possible action

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

Observation
{ "evidence": null, "severity": "low" }
Understand
HTTP response-header inspection
Source
Public HTTP response
Reliability
High
What this supports
Describe defensive policies declared on the observed response
What this does not prove
A header being present does not prove it is optimal or that the application has no vulnerabilities.

Standards and reference context

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

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

Rule 2026.09.4 · 2026-09-04T19:33:51+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": null, "severity": "low" }
Understand
Standard DNS resolution and record parsing
Source
DNS public records
Reliability
High
What this supports
Describe public DNS data observed at scan time
What this does not prove
Public DNS does not prove physical server location, contracts, or global availability.

Standards and reference context

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

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

Rule 2026.09.4 · 2026-09-04T19:33:51+00:00

#09 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:33:51+00:00

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

Rule 2026.09.4 · 2026-09-04T19:33:51+00:00

#11 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:33:51+00:00

#12 Mail-related public records

Evidence: mail_policy_flag

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

Active non-intrusive High
Why it matters

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

What to check next

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

Possible action

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

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

Standards and reference context

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

View raw data

Rule 2026.09.4 · 2026-09-04T19:33:51+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
[ "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:33:51+00:00

#14 Public transparency endpoint

Evidence: module_finding

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

Passive Medium
Why it matters

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

What to check next

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

Possible action

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

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

Standards and reference context

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

View raw data 
{
    "evidence": 403,
    "severity": "medium"
}

Rule 2026.09.4 · 2026-09-04T19:33:51+00:00

#15 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-04T19:33:51+00:00

#16 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-04T19:33:51+00:00

#17 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=()" ]
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=()"
]

Rule 2026.09.4 · 2026-09-04T19:33:51+00:00

#18 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-12-01T22:27:34+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-12-01T22:27:34+00:00

Rule 2026.09.4 · 2026-09-04T19:33:51+00:00

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

Rule 2026.09.4 · 2026-09-04T19:33:51+00:00

#20 Observed public resources

Evidence: dependency_provider

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

Passive Medium
Why it matters

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

What to check next

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

Possible action

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

Observation
{ "critical": true, "hosts": [ "mta-gw.infomaniak.ch", "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-04T19:33:51+00:00

#21 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": "PHP", "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": "PHP",
    "version": "",
    "version_exposed": false
}

Rule 2026.09.4 · 2026-09-04T19:33:51+00:00

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

Rule 2026.09.4 · 2026-09-04T19:33:51+00:00

#23 Public HTTP response

Evidence: module_finding

HTTP headers can ask the browser to enforce specific protections.

Active non-intrusive High
Why it matters

They are visible, verifiable browser-side defensive layers.

What to check next

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

Possible action

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

Observation
{ "evidence": null, "severity": "low" }
Understand
HTTP response-header inspection
Source
Public HTTP response
Reliability
High
What this supports
Describe defensive policies declared on the observed response
What this does not prove
A header being present does not prove it is optimal or that the application has no vulnerabilities.

Standards and reference context

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

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

Rule 2026.09.4 · 2026-09-04T19:33:51+00:00

#24 Mail-related public records

Evidence: module_finding

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

Active non-intrusive High
Why it matters

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

What to check next

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

Possible action

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

Observation
{ "evidence": 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:33:51+00:00

#25 Public HTTP response

Evidence: http_header

HTTP headers can ask the browser to enforce specific protections.

Active non-intrusive High
Why it matters

They are visible, verifiable browser-side defensive layers.

What to check next

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

Possible action

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

Observation
[ "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-04T19:33:51+00:00

#26 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:33:51+00:00

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

Rule 2026.09.4 · 2026-09-04T19:33:51+00:00

#28 Public transparency endpoint

Evidence: module_finding

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

Passive Medium
Why it matters

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

What to check next

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

Possible action

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

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

Standards and reference context

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

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

Rule 2026.09.4 · 2026-09-04T19:33:51+00:00

#29 Public HTTP response

Evidence: http_header

HTTP headers can ask the browser to enforce specific protections.

Active non-intrusive High
Why it matters

They are visible, verifiable browser-side defensive layers.

What to check next

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

Possible action

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

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

Standards and reference context

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

View raw data 
[
    "default-src 'self'; img-src 'self' data:; style-src 'self'; script-src 'self' 'nonce-xD/D7+PEZiXPB7QeRtI188fk'; font-src 'self'; connect-src 'self'; form-action 'self'; base-uri 'self'; frame-ancestors 'none'; upgrade-insecure-requests"
]

Rule 2026.09.4 · 2026-09-04T19:33:51+00:00

#30 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:33:51+00:00

#31 DNS public records

Evidence: dns_nameserver

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

Passive High
Why it matters

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

What to check next

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

Possible action

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

Observation
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 esskifa.com
View raw data 
ns41.infomaniak.com

Rule 2026.09.4 · 2026-09-04T19:33:51+00:00

#32 Public HTTP response

Evidence: module_finding

HTTP headers can ask the browser to enforce specific protections.

Active non-intrusive High
Why it matters

They are visible, verifiable browser-side defensive layers.

What to check next

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

Possible action

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

Observation
{ "evidence": null, "severity": "info" }
Understand
HTTP response-header inspection
Source
Public HTTP response
Reliability
High
What this supports
Describe defensive policies declared on the observed response
What this does not prove
A header being present does not prove it is optimal or that the application has no vulnerabilities.

Standards and reference context

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

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

Rule 2026.09.4 · 2026-09-04T19:33:51+00:00

#33 DNS public records

Evidence: dns_address

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

Passive High
Why it matters

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

What to check next

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

Possible action

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

Observation
185.125.27.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 esskifa.com && dig AAAA esskifa.com
View raw data 
185.125.27.197

Rule 2026.09.4 · 2026-09-04T19:33:51+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": "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-04T19:33:51+00:00

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

#36 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:33:51+00:00

#37 Observed public page

Evidence: cookie

Scanapse describes only privacy signals visible on the observed public journey.

Passive Medium
Why it matters

This separates what the browser actually encounters from what cannot be measured externally.

What to check next

Relate visible cookies and third parties to actual features, then compare those observations with internal documentation when the organisation has it.

Possible action

Remove unnecessary trackers or cookies and document the purposes of required elements. Any legal assessment must remain separate from the external scan.

Observation
{ "http_only": true, "name": "PHPSESSID", "same_site": "lax", "secure": true }
Understand
Visible cookies and tracker signatures on the public response
Source
Observed public page
Reliability
Medium
What this supports
Describe visible privacy-related signals
What this does not prove
This observation is never a GDPR audit and does not reveal every purpose or internal processing activity.

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 
{
    "http_only": true,
    "name": "PHPSESSID",
    "same_site": "lax",
    "secure": true
}

Rule 2026.09.4 · 2026-09-04T19:33:51+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": "c6d07fac725aff31749ea38172cca1966c098868a68731ff327d24837b8fd8e3",
        "display_name": "esskifa.com",
        "slug": "esskifa-com",
        "entity_type": "domain_subject",
        "auto_created": true,
        "primary_asset": "esskifa.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": 37,
        "evidence_count": 37,
        "provider_count": 1,
        "strategic_signal_count": 1,
        "top_signal_count": 1
    }
}