PUBLIC DOMAIN DOSSIER

architekia.com

What is observed, how to verify it and what changed

4 public observations are documented in this dossier.

1 structuring public dependencies are visible.

No useful change is retained since the previous reading.

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

Measured 2026-09-04 19:30 UTC First observation 2026-09-04 19:30 UTC Latest observation 2026-09-04 19:30 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

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

Infrastructure & transport

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

Mail & trust

  • ObservedDmarc policyreject
  • ObservedSpf policyhardfail

Dependencies & exposure

  • Not observable from outsideData location

Explanatory record

What Scanapse understands about this domain

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

Measured on 2026-09-04 19:30 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_address dns b8823eab01fe90224510d195408ada927b74469feec0afcf803e426c295f527b
"2001:1600::aaaa:0:0:80:5b"
dmarc_record dns 92994ebe4622e95791aab2c76459cb42c643f4b68cc7f9096db9a4ad30a3fca0
"v=DMARC1; p=reject;"
dns_nameserver dns eb166440f84d02087392db1fdaa3e9bc83a0c4259d64ed6180f40390badfe41d
"ns12.infomaniak.ch"
spf_record dns 9802ce4c159fdaa97ba1ec6e5b492d6f1d791a8bac6fdd32480c144f19af1205
"v=spf1 include:spf.infomaniak.ch -all"
caa_record dns 523a442a5cec34bc894e2d24c0d594ee3b0315eafd3766f9b081857908913b25
{
    "flags": 0,
    "tag": "issue",
    "value": "letsencrypt.org"
}
module_finding dns d0dbf7012d6d888c482c52aa69d6592b83a05b2b56d5c29d53faedc31f69c937
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
mail_exchanger dns fd562871665c748505d320c82fb332b66836b200791d88d38c1e103f4884a3cb
"mta-gw.infomaniak.ch"
dns_address dns 0eccf7062135a87481a4e6077cb932cbe9ab86bf3d9d28ad8f11cb34138f4923
"185.125.27.197"
dns_nameserver dns 7503a456306e2fe9e85710ef167927e871112d42d046848b36ace025fc25f276
"ns11.infomaniak.ch"
module_finding dns cbd3b6693a900f0842e668d8aa1a5d01effbcf3434e8aa9fd8a5071fd6e8183e
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
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_address dns b8823eab01fe90224510d195408ada927b74469feec0afcf803e426c295f527b
"2001:1600::aaaa:0:0:80:5b"
module_finding resilience f9237674f5f47482e825beb24fc796cf3155145814f89d7615784514ca612f9c
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "medium"
}
dmarc_record dns 92994ebe4622e95791aab2c76459cb42c643f4b68cc7f9096db9a4ad30a3fca0
"v=DMARC1; p=reject;"
dns_nameserver dns eb166440f84d02087392db1fdaa3e9bc83a0c4259d64ed6180f40390badfe41d
"ns12.infomaniak.ch"
dependency_provider dependencies 9a7288cf9681f0bd26a8788da2065d63532107e80fa100ded9b1b8f6c2e30521
{
    "critical": true,
    "hosts": [
        "mta-gw.infomaniak.ch",
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "id": "infomaniak",
    "known": true,
    "name": "Infomaniak",
    "observation_count": 3,
    "services": [
        "dns",
        "hosting",
        "mail"
    ],
    "tracker": false
}
spf_record dns 9802ce4c159fdaa97ba1ec6e5b492d6f1d791a8bac6fdd32480c144f19af1205
"v=spf1 include:spf.infomaniak.ch -all"
caa_record dns 523a442a5cec34bc894e2d24c0d594ee3b0315eafd3766f9b081857908913b25
{
    "flags": 0,
    "tag": "issue",
    "value": "letsencrypt.org"
}
module_finding dns d0dbf7012d6d888c482c52aa69d6592b83a05b2b56d5c29d53faedc31f69c937
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
mail_exchanger dns fd562871665c748505d320c82fb332b66836b200791d88d38c1e103f4884a3cb
"mta-gw.infomaniak.ch"
dns_address dns 0eccf7062135a87481a4e6077cb932cbe9ab86bf3d9d28ad8f11cb34138f4923
"185.125.27.197"
dns_nameserver dns 7503a456306e2fe9e85710ef167927e871112d42d046848b36ace025fc25f276
"ns11.infomaniak.ch"
module_finding dns cbd3b6693a900f0842e668d8aa1a5d01effbcf3434e8aa9fd8a5071fd6e8183e
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
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 131c20245363784e635dc34558fc775434f4d137a045ff5cbb83082911a1e9a2
[
    "same-origin"
]
tls_issuer tls b6823ff1b78bf9680263948c88e4880b73a078a1a93dc76036b80de906749732
"C = US, O = Let's Encrypt, CN = YR1"
http_header headers c1fb1c6f48aebcded339d21d1078f7405b3a7800c78f0a9b9baccc565f274610
[
    "accelerometer=(), autoplay=(), camera=(), display-capture=(), fullscreen=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=(), local-network=(), browsing-topics=()"
]
http_header headers 2b23206d6163fe54924106065a2bcea09ef392c8e5519e9b8219699f49bbaf30
[
    "require-corp"
]
http_header headers 6d194af25dcdad3fc5e64e128dff2c8b4addf643d1e3f3c8899cdc765ab10222
[
    "default-src 'none'; base-uri 'none'; form-action 'self'; frame-ancestors 'none'; frame-src 'none'; object-src 'none'; script-src 'nonce-JbWSs5BcbSqGRvXolp6A39S9' 'strict-dynamic'; script-src-attr 'none'; require-trusted-types-for 'script'; style-src 'self'; style-src-attr 'none'; img-src 'self' data:; font-src 'none'; connect-src 'none'; manifest-src 'self'; worker-src 'none'; media-src 'none'; upgrade-insecure-requests"
]
http_header headers 2c657459fb29d04ec5ac1190a6c68b6ab69e661f600f7299836e9fa01435aff9
[
    "nosniff"
]
http_header headers 20becb878f2c3281f89cc6b8c45f9a123b83a63c80428ff66ee0b5b0f0c74bc7
[
    "max-age=63072000; includeSubDomains; preload"
]
http_header headers 4269343dcb776ad1c9d9825fda279a593ab5f0ee9dba0da533bbdc4449dfab3e
[
    "no-referrer"
]
http_header headers 7e90c5c67a69646bb4f88eb8a22bac80a70f6bd7fcf6203def108c6b62ba1487
[
    "DENY"
]
http_header headers 356abb2bffab59863a46c3380a563f66d2e6369b52e294059b0f7ac796ef9f5c
[
    "same-origin"
]
http_header headers f2dbb0e2c051e7563683fa63bcd4f445f41620bd91e1688d5302921084a50b92
[
    "Apache"
]
tls_valid_to tls 1d6c1169b0ff892cfe759f0d7ae57f58938eacd26c01d3400a58c65f1d2db7ac
"2026-09-29T18:06:51+00:00"
04
Documented First observation

Mail and trust

Public evidence provides enough material to document this angle

Angle 04

Mail and trust

Documented First observation

Public evidence provides enough material to document this angle

01

Why it matters

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

02

How to read it

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

03

What it is for

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

04

What it does not prove

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

Material available for this angle

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

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

Mapping version
2.3.1
Evidence
18
Signals
2
Changes
0
dns_address dns b8823eab01fe90224510d195408ada927b74469feec0afcf803e426c295f527b
"2001:1600::aaaa:0:0:80:5b"
dmarc_record dns 92994ebe4622e95791aab2c76459cb42c643f4b68cc7f9096db9a4ad30a3fca0
"v=DMARC1; p=reject;"
dns_nameserver dns eb166440f84d02087392db1fdaa3e9bc83a0c4259d64ed6180f40390badfe41d
"ns12.infomaniak.ch"
spf_record dns 9802ce4c159fdaa97ba1ec6e5b492d6f1d791a8bac6fdd32480c144f19af1205
"v=spf1 include:spf.infomaniak.ch -all"
dmarc_policy mail_trust 016773e3f1caa7e8702af01026070a0ef675cbcac3612a356ba17b790ec73453
"reject"
mail_policy_flag mail_trust b029acd83dd65c5b781a6ebc1c3f960e34d60857a8acc09725632b3ac4159367
false
module_finding mail_trust a347b2311596edbc2e620272b0f5752e3113d1ee6fe1261a52bfbe9f8dd2a598
{
    "evidence": null,
    "severity": "low"
}
mail_policy_flag mail_trust 2a77ce8ba75d196de33f423bc8761ff2aadb5555277577691f190d759b7eff8a
false
caa_record dns 523a442a5cec34bc894e2d24c0d594ee3b0315eafd3766f9b081857908913b25
{
    "flags": 0,
    "tag": "issue",
    "value": "letsencrypt.org"
}
module_finding dns d0dbf7012d6d888c482c52aa69d6592b83a05b2b56d5c29d53faedc31f69c937
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
module_finding mail_trust 06402f3227430eb69fef81835f57efc53c1bb2481391024a1fa6af7cdba04563
{
    "evidence": null,
    "severity": "low"
}
mail_exchanger dns fd562871665c748505d320c82fb332b66836b200791d88d38c1e103f4884a3cb
"mta-gw.infomaniak.ch"
spf_policy mail_trust 1005593357b1b897f4300cfd2bc26cb0afcaf8207df6f7eb8e3a9271192f36fb
"hardfail"
dns_address dns 0eccf7062135a87481a4e6077cb932cbe9ab86bf3d9d28ad8f11cb34138f4923
"185.125.27.197"
mail_policy_flag mail_trust 7c13948e2c2e88af763183be78f7fe12c93598bdd2039b5491561549e2b56af9
false
dns_nameserver dns 7503a456306e2fe9e85710ef167927e871112d42d046848b36ace025fc25f276
"ns11.infomaniak.ch"
module_finding dns cbd3b6693a900f0842e668d8aa1a5d01effbcf3434e8aa9fd8a5071fd6e8183e
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
module_finding mail_trust df361d1c929ffc89c3a9debfe385364333f4e2cf17605c166993ee49f08e67d0
{
    "evidence": [
        {
            "host": "mta-gw.infomaniak.ch",
            "priority": 5
        }
    ],
    "severity": "low"
}
05
Documented First observation

DNS and governance

Public evidence provides enough material to document this angle

Angle 05

DNS and governance

Documented First observation

Public evidence provides enough material to document this angle

01

Why it matters

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

02

How to read it

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

03

What it is for

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

04

What it does not prove

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

Material available for this angle

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

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

Mapping version
2.3.1
Evidence
18
Signals
2
Changes
0
dns_address dns b8823eab01fe90224510d195408ada927b74469feec0afcf803e426c295f527b
"2001:1600::aaaa:0:0:80:5b"
dmarc_record dns 92994ebe4622e95791aab2c76459cb42c643f4b68cc7f9096db9a4ad30a3fca0
"v=DMARC1; p=reject;"
dns_nameserver dns eb166440f84d02087392db1fdaa3e9bc83a0c4259d64ed6180f40390badfe41d
"ns12.infomaniak.ch"
spf_record dns 9802ce4c159fdaa97ba1ec6e5b492d6f1d791a8bac6fdd32480c144f19af1205
"v=spf1 include:spf.infomaniak.ch -all"
dmarc_policy mail_trust 016773e3f1caa7e8702af01026070a0ef675cbcac3612a356ba17b790ec73453
"reject"
mail_policy_flag mail_trust b029acd83dd65c5b781a6ebc1c3f960e34d60857a8acc09725632b3ac4159367
false
module_finding mail_trust a347b2311596edbc2e620272b0f5752e3113d1ee6fe1261a52bfbe9f8dd2a598
{
    "evidence": null,
    "severity": "low"
}
mail_policy_flag mail_trust 2a77ce8ba75d196de33f423bc8761ff2aadb5555277577691f190d759b7eff8a
false
caa_record dns 523a442a5cec34bc894e2d24c0d594ee3b0315eafd3766f9b081857908913b25
{
    "flags": 0,
    "tag": "issue",
    "value": "letsencrypt.org"
}
module_finding dns d0dbf7012d6d888c482c52aa69d6592b83a05b2b56d5c29d53faedc31f69c937
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
module_finding mail_trust 06402f3227430eb69fef81835f57efc53c1bb2481391024a1fa6af7cdba04563
{
    "evidence": null,
    "severity": "low"
}
mail_exchanger dns fd562871665c748505d320c82fb332b66836b200791d88d38c1e103f4884a3cb
"mta-gw.infomaniak.ch"
spf_policy mail_trust 1005593357b1b897f4300cfd2bc26cb0afcaf8207df6f7eb8e3a9271192f36fb
"hardfail"
dns_address dns 0eccf7062135a87481a4e6077cb932cbe9ab86bf3d9d28ad8f11cb34138f4923
"185.125.27.197"
mail_policy_flag mail_trust 7c13948e2c2e88af763183be78f7fe12c93598bdd2039b5491561549e2b56af9
false
dns_nameserver dns 7503a456306e2fe9e85710ef167927e871112d42d046848b36ace025fc25f276
"ns11.infomaniak.ch"
module_finding dns cbd3b6693a900f0842e668d8aa1a5d01effbcf3434e8aa9fd8a5071fd6e8183e
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
module_finding mail_trust df361d1c929ffc89c3a9debfe385364333f4e2cf17605c166993ee49f08e67d0
{
    "evidence": [
        {
            "host": "mta-gw.infomaniak.ch",
            "priority": 5
        }
    ],
    "severity": "low"
}
06
Documented First observation

External dependencies

Public evidence provides enough material to document this angle

Angle 06

External dependencies

Documented First observation

Public evidence provides enough material to document this angle

01

Why it matters

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

02

How to read it

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

03

What it is for

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

04

What it does not prove

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

Material available for this angle

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

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

Mapping version
2.3.1
Evidence
11
Signals
2
Changes
0
dns_address dns b8823eab01fe90224510d195408ada927b74469feec0afcf803e426c295f527b
"2001:1600::aaaa:0:0:80:5b"
dmarc_record dns 92994ebe4622e95791aab2c76459cb42c643f4b68cc7f9096db9a4ad30a3fca0
"v=DMARC1; p=reject;"
dns_nameserver dns eb166440f84d02087392db1fdaa3e9bc83a0c4259d64ed6180f40390badfe41d
"ns12.infomaniak.ch"
dependency_provider dependencies 9a7288cf9681f0bd26a8788da2065d63532107e80fa100ded9b1b8f6c2e30521
{
    "critical": true,
    "hosts": [
        "mta-gw.infomaniak.ch",
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "id": "infomaniak",
    "known": true,
    "name": "Infomaniak",
    "observation_count": 3,
    "services": [
        "dns",
        "hosting",
        "mail"
    ],
    "tracker": false
}
spf_record dns 9802ce4c159fdaa97ba1ec6e5b492d6f1d791a8bac6fdd32480c144f19af1205
"v=spf1 include:spf.infomaniak.ch -all"
caa_record dns 523a442a5cec34bc894e2d24c0d594ee3b0315eafd3766f9b081857908913b25
{
    "flags": 0,
    "tag": "issue",
    "value": "letsencrypt.org"
}
module_finding dns d0dbf7012d6d888c482c52aa69d6592b83a05b2b56d5c29d53faedc31f69c937
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
mail_exchanger dns fd562871665c748505d320c82fb332b66836b200791d88d38c1e103f4884a3cb
"mta-gw.infomaniak.ch"
dns_address dns 0eccf7062135a87481a4e6077cb932cbe9ab86bf3d9d28ad8f11cb34138f4923
"185.125.27.197"
dns_nameserver dns 7503a456306e2fe9e85710ef167927e871112d42d046848b36ace025fc25f276
"ns11.infomaniak.ch"
module_finding dns cbd3b6693a900f0842e668d8aa1a5d01effbcf3434e8aa9fd8a5071fd6e8183e
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
07
Documented First observation

Observable technologies

Public evidence provides enough material to document this angle

Angle 07

Observable technologies

Documented First observation

Public evidence provides enough material to document this angle

01

Why it matters

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

02

How to read it

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

03

What it is for

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

04

What it does not prove

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

Material available for this angle

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

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

Mapping version
2.3.1
Evidence
11
Signals
0
Changes
0
http_header headers 131c20245363784e635dc34558fc775434f4d137a045ff5cbb83082911a1e9a2
[
    "same-origin"
]
http_header headers c1fb1c6f48aebcded339d21d1078f7405b3a7800c78f0a9b9baccc565f274610
[
    "accelerometer=(), autoplay=(), camera=(), display-capture=(), fullscreen=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=(), local-network=(), browsing-topics=()"
]
http_header headers 2b23206d6163fe54924106065a2bcea09ef392c8e5519e9b8219699f49bbaf30
[
    "require-corp"
]
technology technology b11b0df7a8e78bcc47e1b313e25b446797db64a104f829c262b8efb94c806ee3
{
    "name": "Apache",
    "version": "",
    "version_exposed": false
}
http_header headers 6d194af25dcdad3fc5e64e128dff2c8b4addf643d1e3f3c8899cdc765ab10222
[
    "default-src 'none'; base-uri 'none'; form-action 'self'; frame-ancestors 'none'; frame-src 'none'; object-src 'none'; script-src 'nonce-JbWSs5BcbSqGRvXolp6A39S9' 'strict-dynamic'; script-src-attr 'none'; require-trusted-types-for 'script'; style-src 'self'; style-src-attr 'none'; img-src 'self' data:; font-src 'none'; connect-src 'none'; manifest-src 'self'; worker-src 'none'; media-src 'none'; upgrade-insecure-requests"
]
http_header headers 2c657459fb29d04ec5ac1190a6c68b6ab69e661f600f7299836e9fa01435aff9
[
    "nosniff"
]
http_header headers 20becb878f2c3281f89cc6b8c45f9a123b83a63c80428ff66ee0b5b0f0c74bc7
[
    "max-age=63072000; includeSubDomains; preload"
]
http_header headers 4269343dcb776ad1c9d9825fda279a593ab5f0ee9dba0da533bbdc4449dfab3e
[
    "no-referrer"
]
http_header headers 7e90c5c67a69646bb4f88eb8a22bac80a70f6bd7fcf6203def108c6b62ba1487
[
    "DENY"
]
http_header headers 356abb2bffab59863a46c3380a563f66d2e6369b52e294059b0f7ac796ef9f5c
[
    "same-origin"
]
http_header headers f2dbb0e2c051e7563683fa63bcd4f445f41620bd91e1688d5302921084a50b92
[
    "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

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

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

Mapping version
2.3.1
Evidence
16
Signals
0
Changes
0

Unknowns and limitations

1 items still require qualification

module_finding resilience f9237674f5f47482e825beb24fc796cf3155145814f89d7615784514ca612f9c
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "medium"
}
http_header headers 131c20245363784e635dc34558fc775434f4d137a045ff5cbb83082911a1e9a2
[
    "same-origin"
]
http_header headers c1fb1c6f48aebcded339d21d1078f7405b3a7800c78f0a9b9baccc565f274610
[
    "accelerometer=(), autoplay=(), camera=(), display-capture=(), fullscreen=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=(), local-network=(), browsing-topics=()"
]
http_header headers 2b23206d6163fe54924106065a2bcea09ef392c8e5519e9b8219699f49bbaf30
[
    "require-corp"
]
http_header headers 6d194af25dcdad3fc5e64e128dff2c8b4addf643d1e3f3c8899cdc765ab10222
[
    "default-src 'none'; base-uri 'none'; form-action 'self'; frame-ancestors 'none'; frame-src 'none'; object-src 'none'; script-src 'nonce-JbWSs5BcbSqGRvXolp6A39S9' 'strict-dynamic'; script-src-attr 'none'; require-trusted-types-for 'script'; style-src 'self'; style-src-attr 'none'; img-src 'self' data:; font-src 'none'; connect-src 'none'; manifest-src 'self'; worker-src 'none'; media-src 'none'; upgrade-insecure-requests"
]
module_finding mail_trust a347b2311596edbc2e620272b0f5752e3113d1ee6fe1261a52bfbe9f8dd2a598
{
    "evidence": null,
    "severity": "low"
}
http_header headers 2c657459fb29d04ec5ac1190a6c68b6ab69e661f600f7299836e9fa01435aff9
[
    "nosniff"
]
module_finding dns d0dbf7012d6d888c482c52aa69d6592b83a05b2b56d5c29d53faedc31f69c937
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
http_header headers 20becb878f2c3281f89cc6b8c45f9a123b83a63c80428ff66ee0b5b0f0c74bc7
[
    "max-age=63072000; includeSubDomains; preload"
]
http_header headers 4269343dcb776ad1c9d9825fda279a593ab5f0ee9dba0da533bbdc4449dfab3e
[
    "no-referrer"
]
module_finding mail_trust 06402f3227430eb69fef81835f57efc53c1bb2481391024a1fa6af7cdba04563
{
    "evidence": null,
    "severity": "low"
}
http_header headers 7e90c5c67a69646bb4f88eb8a22bac80a70f6bd7fcf6203def108c6b62ba1487
[
    "DENY"
]
http_header headers 356abb2bffab59863a46c3380a563f66d2e6369b52e294059b0f7ac796ef9f5c
[
    "same-origin"
]
http_header headers f2dbb0e2c051e7563683fa63bcd4f445f41620bd91e1688d5302921084a50b92
[
    "Apache"
]
module_finding dns cbd3b6693a900f0842e668d8aa1a5d01effbcf3434e8aa9fd8a5071fd6e8183e
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
module_finding mail_trust df361d1c929ffc89c3a9debfe385364333f4e2cf17605c166993ee49f08e67d0
{
    "evidence": [
        {
            "host": "mta-gw.infomaniak.ch",
            "priority": 5
        }
    ],
    "severity": "low"
}
09
Documented First observation

Documentary trust

Public evidence provides enough material to document this angle

Angle 09

Documentary trust

Documented First observation

Public evidence provides enough material to document this angle

01

Why it matters

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

02

How to read it

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

03

What it is for

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

04

What it does not prove

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

Material available for this angle

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

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

Mapping version
2.3.1
Evidence
16
Signals
0
Changes
0
module_finding resilience f9237674f5f47482e825beb24fc796cf3155145814f89d7615784514ca612f9c
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "medium"
}
http_header headers 131c20245363784e635dc34558fc775434f4d137a045ff5cbb83082911a1e9a2
[
    "same-origin"
]
http_header headers c1fb1c6f48aebcded339d21d1078f7405b3a7800c78f0a9b9baccc565f274610
[
    "accelerometer=(), autoplay=(), camera=(), display-capture=(), fullscreen=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=(), local-network=(), browsing-topics=()"
]
http_header headers 2b23206d6163fe54924106065a2bcea09ef392c8e5519e9b8219699f49bbaf30
[
    "require-corp"
]
http_header headers 6d194af25dcdad3fc5e64e128dff2c8b4addf643d1e3f3c8899cdc765ab10222
[
    "default-src 'none'; base-uri 'none'; form-action 'self'; frame-ancestors 'none'; frame-src 'none'; object-src 'none'; script-src 'nonce-JbWSs5BcbSqGRvXolp6A39S9' 'strict-dynamic'; script-src-attr 'none'; require-trusted-types-for 'script'; style-src 'self'; style-src-attr 'none'; img-src 'self' data:; font-src 'none'; connect-src 'none'; manifest-src 'self'; worker-src 'none'; media-src 'none'; upgrade-insecure-requests"
]
module_finding mail_trust a347b2311596edbc2e620272b0f5752e3113d1ee6fe1261a52bfbe9f8dd2a598
{
    "evidence": null,
    "severity": "low"
}
http_header headers 2c657459fb29d04ec5ac1190a6c68b6ab69e661f600f7299836e9fa01435aff9
[
    "nosniff"
]
module_finding dns d0dbf7012d6d888c482c52aa69d6592b83a05b2b56d5c29d53faedc31f69c937
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
http_header headers 20becb878f2c3281f89cc6b8c45f9a123b83a63c80428ff66ee0b5b0f0c74bc7
[
    "max-age=63072000; includeSubDomains; preload"
]
http_header headers 4269343dcb776ad1c9d9825fda279a593ab5f0ee9dba0da533bbdc4449dfab3e
[
    "no-referrer"
]
module_finding mail_trust 06402f3227430eb69fef81835f57efc53c1bb2481391024a1fa6af7cdba04563
{
    "evidence": null,
    "severity": "low"
}
http_header headers 7e90c5c67a69646bb4f88eb8a22bac80a70f6bd7fcf6203def108c6b62ba1487
[
    "DENY"
]
http_header headers 356abb2bffab59863a46c3380a563f66d2e6369b52e294059b0f7ac796ef9f5c
[
    "same-origin"
]
http_header headers f2dbb0e2c051e7563683fa63bcd4f445f41620bd91e1688d5302921084a50b92
[
    "Apache"
]
module_finding dns cbd3b6693a900f0842e668d8aa1a5d01effbcf3434e8aa9fd8a5071fd6e8183e
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
module_finding mail_trust df361d1c929ffc89c3a9debfe385364333f4e2cf17605c166993ee49f08e67d0
{
    "evidence": [
        {
            "host": "mta-gw.infomaniak.ch",
            "priority": 5
        }
    ],
    "severity": "low"
}
10
Documented First observation

Security signals

Public evidence provides enough material to document this angle

Angle 10

Security signals

Documented First observation

Public evidence provides enough material to document this angle

01

Why it matters

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

02

How to read it

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

03

What it is for

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

04

What it does not prove

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

Material available for this angle

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

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

Mapping version
2.3.1
Evidence
31
Signals
2
Changes
0

Unknowns and limitations

2 items still require qualification

dns_address dns b8823eab01fe90224510d195408ada927b74469feec0afcf803e426c295f527b
"2001:1600::aaaa:0:0:80:5b"
module_finding resilience f9237674f5f47482e825beb24fc796cf3155145814f89d7615784514ca612f9c
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "medium"
}
http_header headers 131c20245363784e635dc34558fc775434f4d137a045ff5cbb83082911a1e9a2
[
    "same-origin"
]
dmarc_record dns 92994ebe4622e95791aab2c76459cb42c643f4b68cc7f9096db9a4ad30a3fca0
"v=DMARC1; p=reject;"
dns_nameserver dns eb166440f84d02087392db1fdaa3e9bc83a0c4259d64ed6180f40390badfe41d
"ns12.infomaniak.ch"
tls_issuer tls b6823ff1b78bf9680263948c88e4880b73a078a1a93dc76036b80de906749732
"C = US, O = Let's Encrypt, CN = YR1"
http_header headers c1fb1c6f48aebcded339d21d1078f7405b3a7800c78f0a9b9baccc565f274610
[
    "accelerometer=(), autoplay=(), camera=(), display-capture=(), fullscreen=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=(), local-network=(), browsing-topics=()"
]
http_header headers 2b23206d6163fe54924106065a2bcea09ef392c8e5519e9b8219699f49bbaf30
[
    "require-corp"
]
spf_record dns 9802ce4c159fdaa97ba1ec6e5b492d6f1d791a8bac6fdd32480c144f19af1205
"v=spf1 include:spf.infomaniak.ch -all"
dmarc_policy mail_trust 016773e3f1caa7e8702af01026070a0ef675cbcac3612a356ba17b790ec73453
"reject"
http_header headers 6d194af25dcdad3fc5e64e128dff2c8b4addf643d1e3f3c8899cdc765ab10222
[
    "default-src 'none'; base-uri 'none'; form-action 'self'; frame-ancestors 'none'; frame-src 'none'; object-src 'none'; script-src 'nonce-JbWSs5BcbSqGRvXolp6A39S9' 'strict-dynamic'; script-src-attr 'none'; require-trusted-types-for 'script'; style-src 'self'; style-src-attr 'none'; img-src 'self' data:; font-src 'none'; connect-src 'none'; manifest-src 'self'; worker-src 'none'; media-src 'none'; upgrade-insecure-requests"
]
mail_policy_flag mail_trust b029acd83dd65c5b781a6ebc1c3f960e34d60857a8acc09725632b3ac4159367
false
module_finding mail_trust a347b2311596edbc2e620272b0f5752e3113d1ee6fe1261a52bfbe9f8dd2a598
{
    "evidence": null,
    "severity": "low"
}
mail_policy_flag mail_trust 2a77ce8ba75d196de33f423bc8761ff2aadb5555277577691f190d759b7eff8a
false
caa_record dns 523a442a5cec34bc894e2d24c0d594ee3b0315eafd3766f9b081857908913b25
{
    "flags": 0,
    "tag": "issue",
    "value": "letsencrypt.org"
}
http_header headers 2c657459fb29d04ec5ac1190a6c68b6ab69e661f600f7299836e9fa01435aff9
[
    "nosniff"
]
module_finding dns d0dbf7012d6d888c482c52aa69d6592b83a05b2b56d5c29d53faedc31f69c937
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
http_header headers 20becb878f2c3281f89cc6b8c45f9a123b83a63c80428ff66ee0b5b0f0c74bc7
[
    "max-age=63072000; includeSubDomains; preload"
]
http_header headers 4269343dcb776ad1c9d9825fda279a593ab5f0ee9dba0da533bbdc4449dfab3e
[
    "no-referrer"
]
module_finding mail_trust 06402f3227430eb69fef81835f57efc53c1bb2481391024a1fa6af7cdba04563
{
    "evidence": null,
    "severity": "low"
}
http_header headers 7e90c5c67a69646bb4f88eb8a22bac80a70f6bd7fcf6203def108c6b62ba1487
[
    "DENY"
]
http_header headers 356abb2bffab59863a46c3380a563f66d2e6369b52e294059b0f7ac796ef9f5c
[
    "same-origin"
]
mail_exchanger dns fd562871665c748505d320c82fb332b66836b200791d88d38c1e103f4884a3cb
"mta-gw.infomaniak.ch"
spf_policy mail_trust 1005593357b1b897f4300cfd2bc26cb0afcaf8207df6f7eb8e3a9271192f36fb
"hardfail"
11
To determine First observation

Evolution over time

This angle still needs additional public evidence

Angle 11

Evolution over time

To determine First observation

This angle still needs additional public evidence

01

Why it matters

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

02

How to read it

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

03

What it is for

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

04

What it does not prove

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

Material available for this angle

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

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

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

Evidence and traceability

Public evidence provides enough material to document this angle

Angle 12

Evidence and traceability

Documented First observation

Public evidence provides enough material to document this angle

01

Why it matters

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

02

How to read it

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

03

What it is for

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

04

What it does not prove

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

Material available for this angle

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

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

Mapping version
2.3.1
Evidence
33
Signals
3
Changes
0
dns_address dns b8823eab01fe90224510d195408ada927b74469feec0afcf803e426c295f527b
"2001:1600::aaaa:0:0:80:5b"
module_finding resilience f9237674f5f47482e825beb24fc796cf3155145814f89d7615784514ca612f9c
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "medium"
}
http_header headers 131c20245363784e635dc34558fc775434f4d137a045ff5cbb83082911a1e9a2
[
    "same-origin"
]
dmarc_record dns 92994ebe4622e95791aab2c76459cb42c643f4b68cc7f9096db9a4ad30a3fca0
"v=DMARC1; p=reject;"
dns_nameserver dns eb166440f84d02087392db1fdaa3e9bc83a0c4259d64ed6180f40390badfe41d
"ns12.infomaniak.ch"
tls_issuer tls b6823ff1b78bf9680263948c88e4880b73a078a1a93dc76036b80de906749732
"C = US, O = Let's Encrypt, CN = YR1"
http_header headers c1fb1c6f48aebcded339d21d1078f7405b3a7800c78f0a9b9baccc565f274610
[
    "accelerometer=(), autoplay=(), camera=(), display-capture=(), fullscreen=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=(), local-network=(), browsing-topics=()"
]
dependency_provider dependencies 9a7288cf9681f0bd26a8788da2065d63532107e80fa100ded9b1b8f6c2e30521
{
    "critical": true,
    "hosts": [
        "mta-gw.infomaniak.ch",
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "id": "infomaniak",
    "known": true,
    "name": "Infomaniak",
    "observation_count": 3,
    "services": [
        "dns",
        "hosting",
        "mail"
    ],
    "tracker": false
}
http_header headers 2b23206d6163fe54924106065a2bcea09ef392c8e5519e9b8219699f49bbaf30
[
    "require-corp"
]
spf_record dns 9802ce4c159fdaa97ba1ec6e5b492d6f1d791a8bac6fdd32480c144f19af1205
"v=spf1 include:spf.infomaniak.ch -all"
technology technology b11b0df7a8e78bcc47e1b313e25b446797db64a104f829c262b8efb94c806ee3
{
    "name": "Apache",
    "version": "",
    "version_exposed": false
}
dmarc_policy mail_trust 016773e3f1caa7e8702af01026070a0ef675cbcac3612a356ba17b790ec73453
"reject"
http_header headers 6d194af25dcdad3fc5e64e128dff2c8b4addf643d1e3f3c8899cdc765ab10222
[
    "default-src 'none'; base-uri 'none'; form-action 'self'; frame-ancestors 'none'; frame-src 'none'; object-src 'none'; script-src 'nonce-JbWSs5BcbSqGRvXolp6A39S9' 'strict-dynamic'; script-src-attr 'none'; require-trusted-types-for 'script'; style-src 'self'; style-src-attr 'none'; img-src 'self' data:; font-src 'none'; connect-src 'none'; manifest-src 'self'; worker-src 'none'; media-src 'none'; upgrade-insecure-requests"
]
mail_policy_flag mail_trust b029acd83dd65c5b781a6ebc1c3f960e34d60857a8acc09725632b3ac4159367
false
module_finding mail_trust a347b2311596edbc2e620272b0f5752e3113d1ee6fe1261a52bfbe9f8dd2a598
{
    "evidence": null,
    "severity": "low"
}
mail_policy_flag mail_trust 2a77ce8ba75d196de33f423bc8761ff2aadb5555277577691f190d759b7eff8a
false
caa_record dns 523a442a5cec34bc894e2d24c0d594ee3b0315eafd3766f9b081857908913b25
{
    "flags": 0,
    "tag": "issue",
    "value": "letsencrypt.org"
}
http_header headers 2c657459fb29d04ec5ac1190a6c68b6ab69e661f600f7299836e9fa01435aff9
[
    "nosniff"
]
module_finding dns d0dbf7012d6d888c482c52aa69d6592b83a05b2b56d5c29d53faedc31f69c937
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
http_header headers 20becb878f2c3281f89cc6b8c45f9a123b83a63c80428ff66ee0b5b0f0c74bc7
[
    "max-age=63072000; includeSubDomains; preload"
]
http_header headers 4269343dcb776ad1c9d9825fda279a593ab5f0ee9dba0da533bbdc4449dfab3e
[
    "no-referrer"
]
module_finding mail_trust 06402f3227430eb69fef81835f57efc53c1bb2481391024a1fa6af7cdba04563
{
    "evidence": null,
    "severity": "low"
}
http_header headers 7e90c5c67a69646bb4f88eb8a22bac80a70f6bd7fcf6203def108c6b62ba1487
[
    "DENY"
]
http_header headers 356abb2bffab59863a46c3380a563f66d2e6369b52e294059b0f7ac796ef9f5c
[
    "same-origin"
]

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

DNS

2
DNS server Observed

ns12.infomaniak.ch

DNS server Observed

ns11.infomaniak.ch

mail

1
Mail server Observed

mta-gw.infomaniak.ch

technology

1
Observed technology Observed

Apache

external resources

1
External provider or resource Corroborated

Infomaniak

Open questions

4 areas to confirm

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

To confirm

Origin hosting

An edge service does not reveal the origin hosting provider.

To confirm

Effective data location

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

To confirm

Post-quantum TLS exchange

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

To confirm

Public canary signal

Detection of this signal was not enabled for this measurement.

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

Sources and evidence

Evidence supporting this reading

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

33evidence items available

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

Download evidence JSON
Explore evidence
#01 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 architekia.com && dig AAAA architekia.com
View raw data
2001:1600::aaaa:0:0:80:5b

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

#02 module_finding

Evidence: module_finding

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

Passive Medium
Why it matters

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

What to check next

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

Possible action

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

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

Standards and reference context

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

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

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

#03 Public HTTP response

Evidence: http_header

HTTP headers can ask the browser to enforce specific protections.

Active non-intrusive High
Why it matters

They are visible, verifiable browser-side defensive layers.

What to check next

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

Possible action

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

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

Standards and reference context

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

View raw data
[
    "same-origin"
]

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

#04 DNS public records

Evidence: dmarc_record

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

Passive High
Why it matters

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

What to check next

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

Possible action

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

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

Standards and reference context

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

View raw data
v=DMARC1; p=reject;

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

#05 DNS public records

Evidence: dns_nameserver

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

Passive High
Why it matters

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

What to check next

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

Possible action

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

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

Standards and reference context

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

Verify it yourself

This command reproduces the public observation without changing the target.

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

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

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

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

#07 Public HTTP response

Evidence: http_header

HTTP headers can ask the browser to enforce specific protections.

Active non-intrusive High
Why it matters

They are visible, verifiable browser-side defensive layers.

What to check next

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

Possible action

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

Observation
[ "accelerometer=(), autoplay=(), camera=(), display-capture=(), fullscreen=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=(), local-network=(), browsing-topics=()" ]
Understand
HTTP response-header inspection
Source
Public HTTP response
Reliability
High
What this supports
Describe defensive policies declared on the observed response
What this does not prove
A header being present does not prove it is optimal or that the application has no vulnerabilities.

Standards and reference context

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

View raw data
[
    "accelerometer=(), autoplay=(), camera=(), display-capture=(), fullscreen=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=(), local-network=(), browsing-topics=()"
]

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

#08 Observed public resources

Evidence: dependency_provider

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

Passive Medium
Why it matters

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

What to check next

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

Possible action

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

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

Standards and reference context

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

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

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

#09 Public HTTP response

Evidence: http_header

HTTP headers can ask the browser to enforce specific protections.

Active non-intrusive High
Why it matters

They are visible, verifiable browser-side defensive layers.

What to check next

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

Possible action

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

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

Standards and reference context

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

View raw data
[
    "require-corp"
]

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

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

#12 Mail-related public records

Evidence: dmarc_policy

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

Active non-intrusive High
Why it matters

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

What to check next

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

Possible action

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

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

Standards and reference context

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

Verify it yourself

This command reproduces the public observation without changing the target.

dig TXT _dmarc.architekia.com
View raw data
reject

Rule 2026.09.4 · 2026-09-04T19:30:04+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
[ "default-src 'none'; base-uri 'none'; form-action 'self'; frame-ancestors 'none'; frame-src 'none'; object-src 'none'; script-src 'nonce-JbWSs5BcbSqGRvXolp6A39S9' 'strict-dynamic'; script-src-attr 'none'; require-trusted-types-for 'script'; style-src 'self'; style-src-attr 'none'; img-src 'self' data:; font-src 'none'; connect-src 'none'; manifest-src 'self'; worker-src 'none'; media-src '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 'none'; base-uri 'none'; form-action 'self'; frame-ancestors 'none'; frame-src 'none'; object-src 'none'; script-src 'nonce-JbWSs5BcbSqGRvXolp6A39S9' 'strict-dynamic'; script-src-attr 'none'; require-trusted-types-for 'script'; style-src 'self'; style-src-attr 'none'; img-src 'self' data:; font-src 'none'; connect-src 'none'; manifest-src 'self'; worker-src 'none'; media-src 'none'; upgrade-insecure-requests"
]

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

#14 Mail-related public records

Evidence: mail_policy_flag

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

Active non-intrusive High
Why it matters

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

What to check next

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

Possible action

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

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

Standards and reference context

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

View raw data

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

#15 Mail-related public records

Evidence: module_finding

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

Active non-intrusive High
Why it matters

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

What to check next

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

Possible action

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

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

Standards and reference context

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

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

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

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

#17 DNS public records

Evidence: caa_record

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

Passive High
Why it matters

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

What to check next

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

Possible action

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

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

Standards and reference context

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

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

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

#18 Public HTTP response

Evidence: http_header

HTTP headers can ask the browser to enforce specific protections.

Active non-intrusive High
Why it matters

They are visible, verifiable browser-side defensive layers.

What to check next

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

Possible action

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

Observation
[ "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:30:04+00:00

#19 DNS public records

Evidence: module_finding

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

Passive High
Why it matters

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

What to check next

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

Possible action

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

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

Standards and reference context

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

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

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

#20 Public HTTP response

Evidence: http_header

HTTP headers can ask the browser to enforce specific protections.

Active non-intrusive High
Why it matters

They are visible, verifiable browser-side defensive layers.

What to check next

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

Possible action

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

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

Standards and reference context

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

View raw data
[
    "max-age=63072000; includeSubDomains; preload"
]

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

#21 Public HTTP response

Evidence: http_header

HTTP headers can ask the browser to enforce specific protections.

Active non-intrusive High
Why it matters

They are visible, verifiable browser-side defensive layers.

What to check next

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

Possible action

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

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

Standards and reference context

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

View raw data
[
    "no-referrer"
]

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

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

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

#24 Public HTTP response

Evidence: http_header

HTTP headers can ask the browser to enforce specific protections.

Active non-intrusive High
Why it matters

They are visible, verifiable browser-side defensive layers.

What to check next

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

Possible action

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

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

Standards and reference context

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

View raw data
[
    "same-origin"
]

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

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

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

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

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

#27 Public HTTP response

Evidence: http_header

HTTP headers can ask the browser to enforce specific protections.

Active non-intrusive High
Why it matters

They are visible, verifiable browser-side defensive layers.

What to check next

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

Possible action

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

Observation
[ "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:30:04+00:00

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

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

#29 Mail-related public records

Evidence: mail_policy_flag

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

Active non-intrusive High
Why it matters

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

What to check next

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

Possible action

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

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

Standards and reference context

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

View raw data

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

#30 DNS public records

Evidence: dns_nameserver

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

Passive High
Why it matters

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

What to check next

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

Possible action

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

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

Standards and reference context

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

Verify it yourself

This command reproduces the public observation without changing the target.

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

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

#31 DNS public records

Evidence: module_finding

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

Passive High
Why it matters

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

What to check next

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

Possible action

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

Observation
{ "evidence": { "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:30:04+00:00

#32 Public TLS endpoint

Evidence: tls_valid_to

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

Active non-intrusive High
Why it matters

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

What to check next

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

Possible action

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

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

Standards and reference context

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

View raw data
2026-09-29T18:06:51+00:00

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

#33 Mail-related public records

Evidence: module_finding

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

Active non-intrusive High
Why it matters

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

What to check next

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

Possible action

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

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

Standards and reference context

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

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

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

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