OBSERVE · CONNECT · UNDERSTAND
FR EN
Read a domain

PUBLIC DOMAIN DOSSIER

vibelabo.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:29 UTC First observation 2026-09-04 19:29 UTC Latest observation 2026-09-04 19:29 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 testedCanary detection
  • Not observable from outsideOrigin host

Infrastructure & transport

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

Mail & trust

  • ObservedSpf policyhardfail
  • ObservedDmarc policyreject

Dependencies & exposure

  • Not observable from outsideData location

Explanatory record

What Scanapse understands about this domain

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

Measured on 2026-09-04 19:29 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
mail_exchanger dns 8a3a381f747aebe950a94cb76c8a4151b2926e54c66ecc9a174c51a6ea6788f5 
"mta-gw.infomaniak.ch"
dns_address dns bf484b04fa08d2deae98a5f153fe9673cd9dabbd8389b5e604f16bd45c8b9d2c 
"185.125.27.195"
dns_address dns 0a5ac165330bb39dda6596abf3a3598e175825cda0a28906bc673cead269f3b4 
"2001:1600::aaaa:0:0:80:5a"
dns_nameserver dns 215204623a4e137167b28c3159bb23219c9379b64bb80eec868cf29390b3e3ad 
"ns12.infomaniak.ch"
dmarc_record dns 9553b9b16e2140fa66f2e5b6b84f867937723fdb5a7e253cac903ea19bf67e1a 
"v=DMARC1; p=reject;"
module_finding dns beda39936fda94e11c970be2b3b2e92037c729d95c7aa5ee258ca5900ca254a8 
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
module_finding dns a58ea6710ad30858ca7d0bb16f1108a0c73877b54afff5f8235d111588f4fec1 
{
    "evidence": null,
    "severity": "low"
}
module_finding dns 9d1a658aae67245d053125164c002351d9bf710f2d10e14ea9cc6186cb4eb2b7 
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
spf_record dns ea0dfe59df84753a5af90468cee7dfe7ab846c90b54cc7818e9208140dc4b84e 
"v=spf1 include:spf.infomaniak.ch -all"
dns_nameserver dns fdcace831d8cdd0c79a06609401233eeff08b64c21f404b9dba969363eb70bf0 
"ns11.infomaniak.ch"
02
Documented First observation

Infrastructure

Public evidence provides enough material to document this angle

Angle 02

Infrastructure

Documented First observation

Public evidence provides enough material to document this angle

01

Why it matters

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

02

How to read it

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

03

What it is for

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

04

What it does not prove

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

Material available for this angle

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

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

Mapping version
2.3.1
Evidence
12
Signals
2
Changes
0

Unknowns and limitations

2 items still require qualification

mail_exchanger dns 8a3a381f747aebe950a94cb76c8a4151b2926e54c66ecc9a174c51a6ea6788f5 
"mta-gw.infomaniak.ch"
dependency_provider dependencies ba1e01a21a2033b1d33359021bc0cfe6fe9c21d7e50e8b988bca68e930d39ee4 
{
    "critical": true,
    "hosts": [
        "mta-gw.infomaniak.ch",
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "id": "infomaniak",
    "known": true,
    "name": "Infomaniak",
    "observation_count": 3,
    "services": [
        "dns",
        "hosting",
        "mail"
    ],
    "tracker": false
}
dns_address dns bf484b04fa08d2deae98a5f153fe9673cd9dabbd8389b5e604f16bd45c8b9d2c 
"185.125.27.195"
dns_address dns 0a5ac165330bb39dda6596abf3a3598e175825cda0a28906bc673cead269f3b4 
"2001:1600::aaaa:0:0:80:5a"
dns_nameserver dns 215204623a4e137167b28c3159bb23219c9379b64bb80eec868cf29390b3e3ad 
"ns12.infomaniak.ch"
dmarc_record dns 9553b9b16e2140fa66f2e5b6b84f867937723fdb5a7e253cac903ea19bf67e1a 
"v=DMARC1; p=reject;"
module_finding dns beda39936fda94e11c970be2b3b2e92037c729d95c7aa5ee258ca5900ca254a8 
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
module_finding dns a58ea6710ad30858ca7d0bb16f1108a0c73877b54afff5f8235d111588f4fec1 
{
    "evidence": null,
    "severity": "low"
}
module_finding resilience d1e25cffc5f38584baf53d31aeb864f264ec5b7fc56a2214f4324f499f6f7c6f 
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "medium"
}
module_finding dns 9d1a658aae67245d053125164c002351d9bf710f2d10e14ea9cc6186cb4eb2b7 
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
spf_record dns ea0dfe59df84753a5af90468cee7dfe7ab846c90b54cc7818e9208140dc4b84e 
"v=spf1 include:spf.infomaniak.ch -all"
dns_nameserver dns fdcace831d8cdd0c79a06609401233eeff08b64c21f404b9dba969363eb70bf0 
"ns11.infomaniak.ch"
03
Partial First observation

Encryption and transport

This angle is only partially documented by public evidence

Angle 03

Encryption and transport

Partial First observation

This angle is only partially documented by public evidence

01

Why it matters

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

02

How to read it

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

03

What it is for

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

04

What it does not prove

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

Material available for this angle

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

Unknowns and limitations

1 items still require qualification

http_header headers d7c72ca1e170fabd6f285771e48fcba4761a5784067554cbd0b09aace1685979 
[
    "same-origin"
]
tls_valid_to tls 1e27c409dbc9192e014bf220403e8f4e98fc1ab156eed7d167992eaa8ea17793 
"2026-10-14T19:42:09+00:00"
module_finding headers 38d8cc42d670db1e40f1f34ec5262b8198402765a346537281fba80d5125cbda 
{
    "evidence": null,
    "severity": "info"
}
module_finding headers a144ae11ea7d56c0341927ee5bbb0b70d795299eab3ae3e54e065b1ad71e844b 
{
    "evidence": "max-age=31536000",
    "severity": "low"
}
http_header headers eb91d82c05515de3bba379e6cfbed039d18982090b318d4a185e0b41c50adff2 
[
    "nosniff"
]
http_header headers f63f813017913ad3e092fc60f285d83499190a5242dc97f41db8875a7e0c0cdc 
[
    "same-origin"
]
http_header headers 33d873f5ce26f3d395a4feb2b3567a454fee2a436e9e9ffe9d435bf7ffae983c 
[
    "Apache"
]
tls_issuer tls debaad33b801d1b3f6077ef3bca06b87a60bccf7acffb7e613e085987c3ce333 
"C = US, O = Let's Encrypt, CN = YR1"
http_header headers 678c4d1d97cfd06a6ef6b99863d1c807b6919bd37fe23398021e3f4a6a8dbba9 
[
    "max-age=31536000"
]
http_header headers b41fbc2c5ce27d472eb8237f8614dc8ef488c79632291d194370acb2c5b32820 
[
    "strict-origin-when-cross-origin"
]
http_header headers 41856d199b7308be07b1c3d582c6c1d65654626eb937177b451ffbd75c36397d 
[
    "default-src 'none'; style-src 'self'; img-src 'self'; manifest-src 'self'; script-src 'none'; font-src 'none'; connect-src 'none'; media-src 'none'; object-src 'none'; frame-src 'none'; frame-ancestors 'none'; base-uri 'none'; form-action 'none'; upgrade-insecure-requests"
]
http_header headers bd108b008510956826fd83d5c1b04cd88d373c54e38faf83e00ff3f863701d5e 
[
    "accelerometer=(), ambient-light-sensor=(), autoplay=(), battery=(), camera=(), display-capture=(), document-domain=(), encrypted-media=(), fullscreen=(self), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), midi=(), payment=(), publickey-credentials-get=(), screen-wake-lock=(), usb=(), xr-spatial-tracking=()"
]
http_header headers fce98e147c128cd116b4d6d5caa807d13b37789273d1fda68ad40688964c96d7 
[
    "DENY"
]
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
mail_exchanger dns 8a3a381f747aebe950a94cb76c8a4151b2926e54c66ecc9a174c51a6ea6788f5 
"mta-gw.infomaniak.ch"
mail_policy_flag mail_trust b404ce365b6da509f4ef0725394f3030e6278fd2179803b19cca1dd9a84c3705 
false
dns_address dns bf484b04fa08d2deae98a5f153fe9673cd9dabbd8389b5e604f16bd45c8b9d2c 
"185.125.27.195"
dns_address dns 0a5ac165330bb39dda6596abf3a3598e175825cda0a28906bc673cead269f3b4 
"2001:1600::aaaa:0:0:80:5a"
dns_nameserver dns 215204623a4e137167b28c3159bb23219c9379b64bb80eec868cf29390b3e3ad 
"ns12.infomaniak.ch"
mail_policy_flag mail_trust 8b360a1eec3cd90022421063e35d83f6d0504c8ceea40856292f8ae5fec8caa2 
false
dmarc_record dns 9553b9b16e2140fa66f2e5b6b84f867937723fdb5a7e253cac903ea19bf67e1a 
"v=DMARC1; p=reject;"
module_finding dns beda39936fda94e11c970be2b3b2e92037c729d95c7aa5ee258ca5900ca254a8 
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
module_finding dns a58ea6710ad30858ca7d0bb16f1108a0c73877b54afff5f8235d111588f4fec1 
{
    "evidence": null,
    "severity": "low"
}
dmarc_policy mail_trust f3cec97f417227a2535d083e0864df7e7929c9542b56e6301cfb9a7437783fb7 
"reject"
module_finding mail_trust 47ad0a252f3c88a9c742267cb6bf8b2113fac130453427cca8f158760cbab89f 
{
    "evidence": null,
    "severity": "low"
}
spf_policy mail_trust 12f023c089b007b4b870eca095767d820162128374baf1d879cff05c1e9ac34b 
"hardfail"
module_finding dns 9d1a658aae67245d053125164c002351d9bf710f2d10e14ea9cc6186cb4eb2b7 
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
spf_record dns ea0dfe59df84753a5af90468cee7dfe7ab846c90b54cc7818e9208140dc4b84e 
"v=spf1 include:spf.infomaniak.ch -all"
mail_policy_flag mail_trust 8d6711838a5a26f6d15efdef859a1cec569f2c54c1a4536dec33de1c68c42477 
false
dns_nameserver dns fdcace831d8cdd0c79a06609401233eeff08b64c21f404b9dba969363eb70bf0 
"ns11.infomaniak.ch"
module_finding mail_trust 452347f5aac84f7b55d9cadb84089288fa2db430d8b220cf56285f278f874830 
{
    "evidence": null,
    "severity": "low"
}
module_finding mail_trust b248b9a7f60ac6a261a9c83f02f7b7c52a72627a361f4f44617f2a1bbb0f8e0c 
{
    "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
mail_exchanger dns 8a3a381f747aebe950a94cb76c8a4151b2926e54c66ecc9a174c51a6ea6788f5 
"mta-gw.infomaniak.ch"
mail_policy_flag mail_trust b404ce365b6da509f4ef0725394f3030e6278fd2179803b19cca1dd9a84c3705 
false
dns_address dns bf484b04fa08d2deae98a5f153fe9673cd9dabbd8389b5e604f16bd45c8b9d2c 
"185.125.27.195"
dns_address dns 0a5ac165330bb39dda6596abf3a3598e175825cda0a28906bc673cead269f3b4 
"2001:1600::aaaa:0:0:80:5a"
dns_nameserver dns 215204623a4e137167b28c3159bb23219c9379b64bb80eec868cf29390b3e3ad 
"ns12.infomaniak.ch"
mail_policy_flag mail_trust 8b360a1eec3cd90022421063e35d83f6d0504c8ceea40856292f8ae5fec8caa2 
false
dmarc_record dns 9553b9b16e2140fa66f2e5b6b84f867937723fdb5a7e253cac903ea19bf67e1a 
"v=DMARC1; p=reject;"
module_finding dns beda39936fda94e11c970be2b3b2e92037c729d95c7aa5ee258ca5900ca254a8 
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
module_finding dns a58ea6710ad30858ca7d0bb16f1108a0c73877b54afff5f8235d111588f4fec1 
{
    "evidence": null,
    "severity": "low"
}
dmarc_policy mail_trust f3cec97f417227a2535d083e0864df7e7929c9542b56e6301cfb9a7437783fb7 
"reject"
module_finding mail_trust 47ad0a252f3c88a9c742267cb6bf8b2113fac130453427cca8f158760cbab89f 
{
    "evidence": null,
    "severity": "low"
}
spf_policy mail_trust 12f023c089b007b4b870eca095767d820162128374baf1d879cff05c1e9ac34b 
"hardfail"
module_finding dns 9d1a658aae67245d053125164c002351d9bf710f2d10e14ea9cc6186cb4eb2b7 
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
spf_record dns ea0dfe59df84753a5af90468cee7dfe7ab846c90b54cc7818e9208140dc4b84e 
"v=spf1 include:spf.infomaniak.ch -all"
mail_policy_flag mail_trust 8d6711838a5a26f6d15efdef859a1cec569f2c54c1a4536dec33de1c68c42477 
false
dns_nameserver dns fdcace831d8cdd0c79a06609401233eeff08b64c21f404b9dba969363eb70bf0 
"ns11.infomaniak.ch"
module_finding mail_trust 452347f5aac84f7b55d9cadb84089288fa2db430d8b220cf56285f278f874830 
{
    "evidence": null,
    "severity": "low"
}
module_finding mail_trust b248b9a7f60ac6a261a9c83f02f7b7c52a72627a361f4f44617f2a1bbb0f8e0c 
{
    "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
mail_exchanger dns 8a3a381f747aebe950a94cb76c8a4151b2926e54c66ecc9a174c51a6ea6788f5 
"mta-gw.infomaniak.ch"
dependency_provider dependencies ba1e01a21a2033b1d33359021bc0cfe6fe9c21d7e50e8b988bca68e930d39ee4 
{
    "critical": true,
    "hosts": [
        "mta-gw.infomaniak.ch",
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "id": "infomaniak",
    "known": true,
    "name": "Infomaniak",
    "observation_count": 3,
    "services": [
        "dns",
        "hosting",
        "mail"
    ],
    "tracker": false
}
dns_address dns bf484b04fa08d2deae98a5f153fe9673cd9dabbd8389b5e604f16bd45c8b9d2c 
"185.125.27.195"
dns_address dns 0a5ac165330bb39dda6596abf3a3598e175825cda0a28906bc673cead269f3b4 
"2001:1600::aaaa:0:0:80:5a"
dns_nameserver dns 215204623a4e137167b28c3159bb23219c9379b64bb80eec868cf29390b3e3ad 
"ns12.infomaniak.ch"
dmarc_record dns 9553b9b16e2140fa66f2e5b6b84f867937723fdb5a7e253cac903ea19bf67e1a 
"v=DMARC1; p=reject;"
module_finding dns beda39936fda94e11c970be2b3b2e92037c729d95c7aa5ee258ca5900ca254a8 
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
module_finding dns a58ea6710ad30858ca7d0bb16f1108a0c73877b54afff5f8235d111588f4fec1 
{
    "evidence": null,
    "severity": "low"
}
module_finding dns 9d1a658aae67245d053125164c002351d9bf710f2d10e14ea9cc6186cb4eb2b7 
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
spf_record dns ea0dfe59df84753a5af90468cee7dfe7ab846c90b54cc7818e9208140dc4b84e 
"v=spf1 include:spf.infomaniak.ch -all"
dns_nameserver dns fdcace831d8cdd0c79a06609401233eeff08b64c21f404b9dba969363eb70bf0 
"ns11.infomaniak.ch"
07
Documented First observation

Observable technologies

Public evidence provides enough material to document this angle

Angle 07

Observable technologies

Documented First observation

Public evidence provides enough material to document this angle

01

Why it matters

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

02

How to read it

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

03

What it is for

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

04

What it does not prove

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

Material available for this angle

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 d7c72ca1e170fabd6f285771e48fcba4761a5784067554cbd0b09aace1685979 
[
    "same-origin"
]
module_finding headers 38d8cc42d670db1e40f1f34ec5262b8198402765a346537281fba80d5125cbda 
{
    "evidence": null,
    "severity": "info"
}
module_finding headers a144ae11ea7d56c0341927ee5bbb0b70d795299eab3ae3e54e065b1ad71e844b 
{
    "evidence": "max-age=31536000",
    "severity": "low"
}
http_header headers eb91d82c05515de3bba379e6cfbed039d18982090b318d4a185e0b41c50adff2 
[
    "nosniff"
]
http_header headers f63f813017913ad3e092fc60f285d83499190a5242dc97f41db8875a7e0c0cdc 
[
    "same-origin"
]
http_header headers 33d873f5ce26f3d395a4feb2b3567a454fee2a436e9e9ffe9d435bf7ffae983c 
[
    "Apache"
]
http_header headers 678c4d1d97cfd06a6ef6b99863d1c807b6919bd37fe23398021e3f4a6a8dbba9 
[
    "max-age=31536000"
]
technology technology 972195ff7fba98d6c8b0597d4897a4179a3e6824c0f54b19a2c05bafe069fbbe 
{
    "name": "Apache",
    "version": "",
    "version_exposed": false
}
http_header headers b41fbc2c5ce27d472eb8237f8614dc8ef488c79632291d194370acb2c5b32820 
[
    "strict-origin-when-cross-origin"
]
http_header headers 41856d199b7308be07b1c3d582c6c1d65654626eb937177b451ffbd75c36397d 
[
    "default-src 'none'; style-src 'self'; img-src 'self'; manifest-src 'self'; script-src 'none'; font-src 'none'; connect-src 'none'; media-src 'none'; object-src 'none'; frame-src 'none'; frame-ancestors 'none'; base-uri 'none'; form-action 'none'; upgrade-insecure-requests"
]
http_header headers bd108b008510956826fd83d5c1b04cd88d373c54e38faf83e00ff3f863701d5e 
[
    "accelerometer=(), ambient-light-sensor=(), autoplay=(), battery=(), camera=(), display-capture=(), document-domain=(), encrypted-media=(), fullscreen=(self), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), midi=(), payment=(), publickey-credentials-get=(), screen-wake-lock=(), usb=(), xr-spatial-tracking=()"
]
http_header headers fce98e147c128cd116b4d6d5caa807d13b37789273d1fda68ad40688964c96d7 
[
    "DENY"
]
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

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

Unknowns and limitations

1 items still require qualification

http_header headers d7c72ca1e170fabd6f285771e48fcba4761a5784067554cbd0b09aace1685979 
[
    "same-origin"
]
module_finding headers 38d8cc42d670db1e40f1f34ec5262b8198402765a346537281fba80d5125cbda 
{
    "evidence": null,
    "severity": "info"
}
module_finding headers a144ae11ea7d56c0341927ee5bbb0b70d795299eab3ae3e54e065b1ad71e844b 
{
    "evidence": "max-age=31536000",
    "severity": "low"
}
http_header headers eb91d82c05515de3bba379e6cfbed039d18982090b318d4a185e0b41c50adff2 
[
    "nosniff"
]
http_header headers f63f813017913ad3e092fc60f285d83499190a5242dc97f41db8875a7e0c0cdc 
[
    "same-origin"
]
http_header headers 33d873f5ce26f3d395a4feb2b3567a454fee2a436e9e9ffe9d435bf7ffae983c 
[
    "Apache"
]
http_header headers 678c4d1d97cfd06a6ef6b99863d1c807b6919bd37fe23398021e3f4a6a8dbba9 
[
    "max-age=31536000"
]
module_finding dns beda39936fda94e11c970be2b3b2e92037c729d95c7aa5ee258ca5900ca254a8 
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
module_finding dns a58ea6710ad30858ca7d0bb16f1108a0c73877b54afff5f8235d111588f4fec1 
{
    "evidence": null,
    "severity": "low"
}
http_header headers b41fbc2c5ce27d472eb8237f8614dc8ef488c79632291d194370acb2c5b32820 
[
    "strict-origin-when-cross-origin"
]
module_finding mail_trust 47ad0a252f3c88a9c742267cb6bf8b2113fac130453427cca8f158760cbab89f 
{
    "evidence": null,
    "severity": "low"
}
module_finding resilience d1e25cffc5f38584baf53d31aeb864f264ec5b7fc56a2214f4324f499f6f7c6f 
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "medium"
}
http_header headers 41856d199b7308be07b1c3d582c6c1d65654626eb937177b451ffbd75c36397d 
[
    "default-src 'none'; style-src 'self'; img-src 'self'; manifest-src 'self'; script-src 'none'; font-src 'none'; connect-src 'none'; media-src 'none'; object-src 'none'; frame-src 'none'; frame-ancestors 'none'; base-uri 'none'; form-action 'none'; upgrade-insecure-requests"
]
http_header headers bd108b008510956826fd83d5c1b04cd88d373c54e38faf83e00ff3f863701d5e 
[
    "accelerometer=(), ambient-light-sensor=(), autoplay=(), battery=(), camera=(), display-capture=(), document-domain=(), encrypted-media=(), fullscreen=(self), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), midi=(), payment=(), publickey-credentials-get=(), screen-wake-lock=(), usb=(), xr-spatial-tracking=()"
]
module_finding dns 9d1a658aae67245d053125164c002351d9bf710f2d10e14ea9cc6186cb4eb2b7 
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
http_header headers fce98e147c128cd116b4d6d5caa807d13b37789273d1fda68ad40688964c96d7 
[
    "DENY"
]
module_finding mail_trust 452347f5aac84f7b55d9cadb84089288fa2db430d8b220cf56285f278f874830 
{
    "evidence": null,
    "severity": "low"
}
module_finding mail_trust b248b9a7f60ac6a261a9c83f02f7b7c52a72627a361f4f44617f2a1bbb0f8e0c 
{
    "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

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
0
Changes
0
http_header headers d7c72ca1e170fabd6f285771e48fcba4761a5784067554cbd0b09aace1685979 
[
    "same-origin"
]
module_finding headers 38d8cc42d670db1e40f1f34ec5262b8198402765a346537281fba80d5125cbda 
{
    "evidence": null,
    "severity": "info"
}
module_finding headers a144ae11ea7d56c0341927ee5bbb0b70d795299eab3ae3e54e065b1ad71e844b 
{
    "evidence": "max-age=31536000",
    "severity": "low"
}
http_header headers eb91d82c05515de3bba379e6cfbed039d18982090b318d4a185e0b41c50adff2 
[
    "nosniff"
]
http_header headers f63f813017913ad3e092fc60f285d83499190a5242dc97f41db8875a7e0c0cdc 
[
    "same-origin"
]
http_header headers 33d873f5ce26f3d395a4feb2b3567a454fee2a436e9e9ffe9d435bf7ffae983c 
[
    "Apache"
]
http_header headers 678c4d1d97cfd06a6ef6b99863d1c807b6919bd37fe23398021e3f4a6a8dbba9 
[
    "max-age=31536000"
]
module_finding dns beda39936fda94e11c970be2b3b2e92037c729d95c7aa5ee258ca5900ca254a8 
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
module_finding dns a58ea6710ad30858ca7d0bb16f1108a0c73877b54afff5f8235d111588f4fec1 
{
    "evidence": null,
    "severity": "low"
}
http_header headers b41fbc2c5ce27d472eb8237f8614dc8ef488c79632291d194370acb2c5b32820 
[
    "strict-origin-when-cross-origin"
]
module_finding mail_trust 47ad0a252f3c88a9c742267cb6bf8b2113fac130453427cca8f158760cbab89f 
{
    "evidence": null,
    "severity": "low"
}
module_finding resilience d1e25cffc5f38584baf53d31aeb864f264ec5b7fc56a2214f4324f499f6f7c6f 
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "medium"
}
http_header headers 41856d199b7308be07b1c3d582c6c1d65654626eb937177b451ffbd75c36397d 
[
    "default-src 'none'; style-src 'self'; img-src 'self'; manifest-src 'self'; script-src 'none'; font-src 'none'; connect-src 'none'; media-src 'none'; object-src 'none'; frame-src 'none'; frame-ancestors 'none'; base-uri 'none'; form-action 'none'; upgrade-insecure-requests"
]
http_header headers bd108b008510956826fd83d5c1b04cd88d373c54e38faf83e00ff3f863701d5e 
[
    "accelerometer=(), ambient-light-sensor=(), autoplay=(), battery=(), camera=(), display-capture=(), document-domain=(), encrypted-media=(), fullscreen=(self), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), midi=(), payment=(), publickey-credentials-get=(), screen-wake-lock=(), usb=(), xr-spatial-tracking=()"
]
module_finding dns 9d1a658aae67245d053125164c002351d9bf710f2d10e14ea9cc6186cb4eb2b7 
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
http_header headers fce98e147c128cd116b4d6d5caa807d13b37789273d1fda68ad40688964c96d7 
[
    "DENY"
]
module_finding mail_trust 452347f5aac84f7b55d9cadb84089288fa2db430d8b220cf56285f278f874830 
{
    "evidence": null,
    "severity": "low"
}
module_finding mail_trust b248b9a7f60ac6a261a9c83f02f7b7c52a72627a361f4f44617f2a1bbb0f8e0c 
{
    "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

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

Unknowns and limitations

2 items still require qualification

mail_exchanger dns 8a3a381f747aebe950a94cb76c8a4151b2926e54c66ecc9a174c51a6ea6788f5 
"mta-gw.infomaniak.ch"
http_header headers d7c72ca1e170fabd6f285771e48fcba4761a5784067554cbd0b09aace1685979 
[
    "same-origin"
]
tls_valid_to tls 1e27c409dbc9192e014bf220403e8f4e98fc1ab156eed7d167992eaa8ea17793 
"2026-10-14T19:42:09+00:00"
mail_policy_flag mail_trust b404ce365b6da509f4ef0725394f3030e6278fd2179803b19cca1dd9a84c3705 
false
dns_address dns bf484b04fa08d2deae98a5f153fe9673cd9dabbd8389b5e604f16bd45c8b9d2c 
"185.125.27.195"
module_finding headers 38d8cc42d670db1e40f1f34ec5262b8198402765a346537281fba80d5125cbda 
{
    "evidence": null,
    "severity": "info"
}
dns_address dns 0a5ac165330bb39dda6596abf3a3598e175825cda0a28906bc673cead269f3b4 
"2001:1600::aaaa:0:0:80:5a"
dns_nameserver dns 215204623a4e137167b28c3159bb23219c9379b64bb80eec868cf29390b3e3ad 
"ns12.infomaniak.ch"
module_finding headers a144ae11ea7d56c0341927ee5bbb0b70d795299eab3ae3e54e065b1ad71e844b 
{
    "evidence": "max-age=31536000",
    "severity": "low"
}
mail_policy_flag mail_trust 8b360a1eec3cd90022421063e35d83f6d0504c8ceea40856292f8ae5fec8caa2 
false
http_header headers eb91d82c05515de3bba379e6cfbed039d18982090b318d4a185e0b41c50adff2 
[
    "nosniff"
]
http_header headers f63f813017913ad3e092fc60f285d83499190a5242dc97f41db8875a7e0c0cdc 
[
    "same-origin"
]
http_header headers 33d873f5ce26f3d395a4feb2b3567a454fee2a436e9e9ffe9d435bf7ffae983c 
[
    "Apache"
]
dmarc_record dns 9553b9b16e2140fa66f2e5b6b84f867937723fdb5a7e253cac903ea19bf67e1a 
"v=DMARC1; p=reject;"
tls_issuer tls debaad33b801d1b3f6077ef3bca06b87a60bccf7acffb7e613e085987c3ce333 
"C = US, O = Let's Encrypt, CN = YR1"
http_header headers 678c4d1d97cfd06a6ef6b99863d1c807b6919bd37fe23398021e3f4a6a8dbba9 
[
    "max-age=31536000"
]
module_finding dns beda39936fda94e11c970be2b3b2e92037c729d95c7aa5ee258ca5900ca254a8 
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
module_finding dns a58ea6710ad30858ca7d0bb16f1108a0c73877b54afff5f8235d111588f4fec1 
{
    "evidence": null,
    "severity": "low"
}
dmarc_policy mail_trust f3cec97f417227a2535d083e0864df7e7929c9542b56e6301cfb9a7437783fb7 
"reject"
http_header headers b41fbc2c5ce27d472eb8237f8614dc8ef488c79632291d194370acb2c5b32820 
[
    "strict-origin-when-cross-origin"
]
module_finding mail_trust 47ad0a252f3c88a9c742267cb6bf8b2113fac130453427cca8f158760cbab89f 
{
    "evidence": null,
    "severity": "low"
}
spf_policy mail_trust 12f023c089b007b4b870eca095767d820162128374baf1d879cff05c1e9ac34b 
"hardfail"
module_finding resilience d1e25cffc5f38584baf53d31aeb864f264ec5b7fc56a2214f4324f499f6f7c6f 
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "medium"
}
http_header headers 41856d199b7308be07b1c3d582c6c1d65654626eb937177b451ffbd75c36397d 
[
    "default-src 'none'; style-src 'self'; img-src 'self'; manifest-src 'self'; script-src 'none'; font-src 'none'; connect-src 'none'; media-src 'none'; object-src 'none'; frame-src 'none'; frame-ancestors 'none'; base-uri 'none'; form-action 'none'; upgrade-insecure-requests"
]
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

34evidence
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
34
Signals
3
Changes
0
mail_exchanger dns 8a3a381f747aebe950a94cb76c8a4151b2926e54c66ecc9a174c51a6ea6788f5 
"mta-gw.infomaniak.ch"
http_header headers d7c72ca1e170fabd6f285771e48fcba4761a5784067554cbd0b09aace1685979 
[
    "same-origin"
]
tls_valid_to tls 1e27c409dbc9192e014bf220403e8f4e98fc1ab156eed7d167992eaa8ea17793 
"2026-10-14T19:42:09+00:00"
dependency_provider dependencies ba1e01a21a2033b1d33359021bc0cfe6fe9c21d7e50e8b988bca68e930d39ee4 
{
    "critical": true,
    "hosts": [
        "mta-gw.infomaniak.ch",
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "id": "infomaniak",
    "known": true,
    "name": "Infomaniak",
    "observation_count": 3,
    "services": [
        "dns",
        "hosting",
        "mail"
    ],
    "tracker": false
}
mail_policy_flag mail_trust b404ce365b6da509f4ef0725394f3030e6278fd2179803b19cca1dd9a84c3705 
false
dns_address dns bf484b04fa08d2deae98a5f153fe9673cd9dabbd8389b5e604f16bd45c8b9d2c 
"185.125.27.195"
module_finding headers 38d8cc42d670db1e40f1f34ec5262b8198402765a346537281fba80d5125cbda 
{
    "evidence": null,
    "severity": "info"
}
dns_address dns 0a5ac165330bb39dda6596abf3a3598e175825cda0a28906bc673cead269f3b4 
"2001:1600::aaaa:0:0:80:5a"
dns_nameserver dns 215204623a4e137167b28c3159bb23219c9379b64bb80eec868cf29390b3e3ad 
"ns12.infomaniak.ch"
module_finding headers a144ae11ea7d56c0341927ee5bbb0b70d795299eab3ae3e54e065b1ad71e844b 
{
    "evidence": "max-age=31536000",
    "severity": "low"
}
mail_policy_flag mail_trust 8b360a1eec3cd90022421063e35d83f6d0504c8ceea40856292f8ae5fec8caa2 
false
http_header headers eb91d82c05515de3bba379e6cfbed039d18982090b318d4a185e0b41c50adff2 
[
    "nosniff"
]
http_header headers f63f813017913ad3e092fc60f285d83499190a5242dc97f41db8875a7e0c0cdc 
[
    "same-origin"
]
http_header headers 33d873f5ce26f3d395a4feb2b3567a454fee2a436e9e9ffe9d435bf7ffae983c 
[
    "Apache"
]
dmarc_record dns 9553b9b16e2140fa66f2e5b6b84f867937723fdb5a7e253cac903ea19bf67e1a 
"v=DMARC1; p=reject;"
tls_issuer tls debaad33b801d1b3f6077ef3bca06b87a60bccf7acffb7e613e085987c3ce333 
"C = US, O = Let's Encrypt, CN = YR1"
http_header headers 678c4d1d97cfd06a6ef6b99863d1c807b6919bd37fe23398021e3f4a6a8dbba9 
[
    "max-age=31536000"
]
module_finding dns beda39936fda94e11c970be2b3b2e92037c729d95c7aa5ee258ca5900ca254a8 
{
    "evidence": [
        "ns11.infomaniak.ch",
        "ns12.infomaniak.ch"
    ],
    "severity": "low"
}
technology technology 972195ff7fba98d6c8b0597d4897a4179a3e6824c0f54b19a2c05bafe069fbbe 
{
    "name": "Apache",
    "version": "",
    "version_exposed": false
}
module_finding dns a58ea6710ad30858ca7d0bb16f1108a0c73877b54afff5f8235d111588f4fec1 
{
    "evidence": null,
    "severity": "low"
}
dmarc_policy mail_trust f3cec97f417227a2535d083e0864df7e7929c9542b56e6301cfb9a7437783fb7 
"reject"
http_header headers b41fbc2c5ce27d472eb8237f8614dc8ef488c79632291d194370acb2c5b32820 
[
    "strict-origin-when-cross-origin"
]
module_finding mail_trust 47ad0a252f3c88a9c742267cb6bf8b2113fac130453427cca8f158760cbab89f 
{
    "evidence": null,
    "severity": "low"
}
spf_policy mail_trust 12f023c089b007b4b870eca095767d820162128374baf1d879cff05c1e9ac34b 
"hardfail"

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

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

34evidence items available

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

Download evidence JSON
Explore evidence
#01 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 vibelabo.com
View raw data 
mta-gw.infomaniak.ch

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

#03 Public TLS endpoint

Evidence: tls_valid_to

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

Active non-intrusive High
Why it matters

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

What to check next

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

Possible action

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

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

Standards and reference context

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

View raw data 
2026-10-14T19:42:09+00:00

Rule 2026.09.4 · 2026-09-04T19:29:52+00:00

#04 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:29:52+00:00

#05 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:29:52+00:00

#06 DNS public records

Evidence: dns_address

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

Passive High
Why it matters

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

What to check next

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

Possible action

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

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

Standards and reference context

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

Verify it yourself

This command reproduces the public observation without changing the target.

dig A vibelabo.com && dig AAAA vibelabo.com
View raw data 
185.125.27.195

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

#08 DNS public records

Evidence: dns_address

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

Passive High
Why it matters

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

What to check next

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

Possible action

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

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

Standards and reference context

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

Verify it yourself

This command reproduces the public observation without changing the target.

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

Rule 2026.09.4 · 2026-09-04T19:29:52+00:00

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

Rule 2026.09.4 · 2026-09-04T19:29:52+00:00

#10 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": "max-age=31536000", "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": "max-age=31536000",
    "severity": "low"
}

Rule 2026.09.4 · 2026-09-04T19:29:52+00:00

#11 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:29:52+00:00

#12 Public HTTP response

Evidence: http_header

HTTP headers can ask the browser to enforce specific protections.

Active non-intrusive High
Why it matters

They are visible, verifiable browser-side defensive layers.

What to check next

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

Possible action

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

Observation
[ "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:29:52+00:00

#13 Public HTTP response

Evidence: http_header

HTTP headers can ask the browser to enforce specific protections.

Active non-intrusive High
Why it matters

They are visible, verifiable browser-side defensive layers.

What to check next

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

Possible action

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

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

Standards and reference context

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

View raw data 
[
    "same-origin"
]

Rule 2026.09.4 · 2026-09-04T19:29:52+00:00

#14 Public HTTP response

Evidence: http_header

HTTP headers can ask the browser to enforce specific protections.

Active non-intrusive High
Why it matters

They are visible, verifiable browser-side defensive layers.

What to check next

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

Possible action

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

Observation
[ "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:29:52+00:00

#15 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:29:52+00:00

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

Rule 2026.09.4 · 2026-09-04T19:29:52+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
[ "max-age=31536000" ]
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"
]

Rule 2026.09.4 · 2026-09-04T19:29:52+00:00

#18 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:29:52+00:00

#19 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:29:52+00:00

#20 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:29:52+00:00

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

Rule 2026.09.4 · 2026-09-04T19:29:52+00:00

#22 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:29:52+00:00

#23 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:29:52+00:00

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

Rule 2026.09.4 · 2026-09-04T19:29:52+00:00

#25 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:29:52+00:00

#26 Public HTTP response

Evidence: http_header

HTTP headers can ask the browser to enforce specific protections.

Active non-intrusive High
Why it matters

They are visible, verifiable browser-side defensive layers.

What to check next

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

Possible action

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

Observation
[ "default-src 'none'; style-src 'self'; img-src 'self'; manifest-src 'self'; script-src 'none'; font-src 'none'; connect-src 'none'; media-src 'none'; object-src 'none'; frame-src 'none'; frame-ancestors 'none'; base-uri 'none'; form-action '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'; style-src 'self'; img-src 'self'; manifest-src 'self'; script-src 'none'; font-src 'none'; connect-src 'none'; media-src 'none'; object-src 'none'; frame-src 'none'; frame-ancestors 'none'; base-uri 'none'; form-action 'none'; upgrade-insecure-requests"
]

Rule 2026.09.4 · 2026-09-04T19:29:52+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
[ "accelerometer=(), ambient-light-sensor=(), autoplay=(), battery=(), camera=(), display-capture=(), document-domain=(), encrypted-media=(), fullscreen=(self), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), midi=(), payment=(), publickey-credentials-get=(), screen-wake-lock=(), usb=(), xr-spatial-tracking=()" ]
Understand
HTTP response-header inspection
Source
Public HTTP response
Reliability
High
What this supports
Describe defensive policies declared on the observed response
What this does not prove
A header being present does not prove it is optimal or that the application has no vulnerabilities.

Standards and reference context

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

View raw data 
[
    "accelerometer=(), ambient-light-sensor=(), autoplay=(), battery=(), camera=(), display-capture=(), document-domain=(), encrypted-media=(), fullscreen=(self), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), midi=(), payment=(), publickey-credentials-get=(), screen-wake-lock=(), usb=(), xr-spatial-tracking=()"
]

Rule 2026.09.4 · 2026-09-04T19:29:52+00:00

#28 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:29:52+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
[ "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:29:52+00:00

#30 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:29:52+00:00

#31 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:29:52+00:00

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

Rule 2026.09.4 · 2026-09-04T19:29:52+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": 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:29:52+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": [ { "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:29:52+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": "0fc627eea1bfe85f464721a8d30d4042d72aee882cbc0311f5f33bfb93dd2eaa",
        "display_name": "vibelabo.com",
        "slug": "vibelabo-com",
        "entity_type": "domain_subject",
        "auto_created": true,
        "primary_asset": "vibelabo.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": 34,
        "evidence_count": 34,
        "provider_count": 1,
        "strategic_signal_count": 1,
        "top_signal_count": 1
    }
}