PUBLIC DOMAIN DOSSIER

darfoufa.com

What is observed, how to verify it and what changed

3 public observations are documented in this dossier.

1 structuring public dependencies are visible.

No useful change is retained since the previous reading.

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

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

Infrastructure & transport

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

Mail & trust

  • ObservedSpf policyhardfail

Dependencies & exposure

  • Not observable from outsideData location

Explanatory record

What Scanapse understands about this domain

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

Measured on 2026-09-04 19:34 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

OVHcloud is associated with 5 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

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
1
Changes
0
mail_exchanger dns d62438acd8b408dda45a4d5dd0f386246dd9c32c20858b287a6dc2ef58cbc207
"mx2.mail.ovh.net"
module_finding dns d07f5ca3ad98f3c189277eee8bd1fa15746bf89d3cb89038cb6fbe07be80b2e8
{
    "evidence": null,
    "severity": "low"
}
mail_exchanger dns 053d5910e8d57a51bf283891e6e891b1d6692cfaa95ca2faf5d3a69c3e6c6300
"mx1.mail.ovh.net"
module_finding dns 280ba78273e5be6a147f01e76835d8bbd412a630bd2b81785a64506a2020836b
{
    "evidence": [
        "dns105.ovh.net",
        "ns105.ovh.net"
    ],
    "severity": "low"
}
mail_exchanger dns 28e7bc31967581ceed476fc91d9f075bb52b7ca82e987d568e09ef944f4f34f4
"mx3.mail.ovh.net"
module_finding dns b108711770fefd7f319365c442db97bdf90b2600245de84c718a2770394db43c
{
    "evidence": null,
    "severity": "medium"
}
dns_nameserver dns 0961c865d3699291e541caea89381e85d921514d32225d2d21e2b2da786e1c35
"ns105.ovh.net"
dns_address dns 8ea92001c1d6563aa207bd34e68795958ce6b7f380c9ca3fc21dbd931cc40b18
"2001:1600::aaaa:0:0:80:5b"
dns_nameserver dns feb7593b3cf89689461e7d222099bacd97e0b2b287c30b79d13a13ba9a559abb
"dns105.ovh.net"
module_finding dns fe8a94e75df7e0a503249011b3ed7913161c33e69a475d7b9653e8fe4dd69bc4
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
dns_address dns ad8c2535aced5553de5e041a3b2352c6300d103fb6603b9f052e4dc26c2060d1
"185.125.27.197"
spf_record dns 5ab1bd4ca14fd5545e69cf2c11261399fd99c410e2d2e906b646cdf0c08243ac
"v=spf1 include:mx.ovh.com -all"
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

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

Unknowns and limitations

2 items still require qualification

dependency_provider dependencies 4812963b2a4ee296bdb646d565d1813753193b13e85b5cc7368ec2d2f1e32bba
{
    "critical": true,
    "hosts": [
        "dns105.ovh.net",
        "mx1.mail.ovh.net",
        "mx2.mail.ovh.net",
        "mx3.mail.ovh.net",
        "ns105.ovh.net"
    ],
    "id": "ovhcloud",
    "known": true,
    "name": "OVHcloud",
    "observation_count": 5,
    "services": [
        "cloud",
        "dns",
        "hosting"
    ],
    "tracker": false
}
mail_exchanger dns d62438acd8b408dda45a4d5dd0f386246dd9c32c20858b287a6dc2ef58cbc207
"mx2.mail.ovh.net"
module_finding dns d07f5ca3ad98f3c189277eee8bd1fa15746bf89d3cb89038cb6fbe07be80b2e8
{
    "evidence": null,
    "severity": "low"
}
module_finding resilience a13d72220e1a5d1af403bb91cfe04d58a2d3f7ca974cebca5584aaed52d84f3a
{
    "evidence": [
        "dns105.ovh.net",
        "ns105.ovh.net"
    ],
    "severity": "medium"
}
mail_exchanger dns 053d5910e8d57a51bf283891e6e891b1d6692cfaa95ca2faf5d3a69c3e6c6300
"mx1.mail.ovh.net"
module_finding dns 280ba78273e5be6a147f01e76835d8bbd412a630bd2b81785a64506a2020836b
{
    "evidence": [
        "dns105.ovh.net",
        "ns105.ovh.net"
    ],
    "severity": "low"
}
mail_exchanger dns 28e7bc31967581ceed476fc91d9f075bb52b7ca82e987d568e09ef944f4f34f4
"mx3.mail.ovh.net"
module_finding dns b108711770fefd7f319365c442db97bdf90b2600245de84c718a2770394db43c
{
    "evidence": null,
    "severity": "medium"
}
dns_nameserver dns 0961c865d3699291e541caea89381e85d921514d32225d2d21e2b2da786e1c35
"ns105.ovh.net"
dns_address dns 8ea92001c1d6563aa207bd34e68795958ce6b7f380c9ca3fc21dbd931cc40b18
"2001:1600::aaaa:0:0:80:5b"
dns_nameserver dns feb7593b3cf89689461e7d222099bacd97e0b2b287c30b79d13a13ba9a559abb
"dns105.ovh.net"
module_finding dns fe8a94e75df7e0a503249011b3ed7913161c33e69a475d7b9653e8fe4dd69bc4
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
dns_address dns ad8c2535aced5553de5e041a3b2352c6300d103fb6603b9f052e4dc26c2060d1
"185.125.27.197"
spf_record dns 5ab1bd4ca14fd5545e69cf2c11261399fd99c410e2d2e906b646cdf0c08243ac
"v=spf1 include:mx.ovh.com -all"
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 26c894e98d62e2a109d0dade0b305a0c1ad167e062d581a174db374623b18e80
[
    "max-age=63072000; includeSubDomains; preload"
]
tls_issuer tls 458ee8e291926a8313e41be3f16125d53cb4f5e15757cb9488baceb56970d405
"C = US, O = Let's Encrypt, CN = YR2"
http_header headers 66aa1d5671b55805ff383577b69c7cc5b70f8ac0cb29e7c86d030caeeaa529fb
[
    "nosniff"
]
http_header headers deaad91874a75a5429ef518eef962fc909fa481b977a552a429b38af731598e7
[
    "same-origin"
]
http_header headers 169c31f34701ac8b4fd49cf157571457f19837c74564edbb681eb4cff54822b4
[
    "DENY"
]
http_header headers 82b4eb137e4ceb39df539fa73c652e252491f9014705fff17baba457fa36aeee
[
    "strict-origin-when-cross-origin"
]
http_header headers 998dce3408962c40df12f57cccdcf882c46b8c36fd6a32871700ed4b1f285ed1
[
    "accelerometer=(), autoplay=(), camera=(), display-capture=(), encrypted-media=(), fullscreen=(self), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), midi=(), payment=(), publickey-credentials-get=(), screen-wake-lock=(), usb=()"
]
http_header headers cbee82497783f4c74c11dcd51fe98e22e45414038c8c2868858dd00273be034b
[
    "default-src 'self'; base-uri 'self'; form-action 'self'; frame-ancestors 'none'; object-src 'none'; img-src 'self' data: https:; style-src 'self'; script-src 'self'; connect-src 'self'; font-src 'self'; manifest-src 'self'; media-src 'self'; worker-src 'self'; upgrade-insecure-requests; block-all-mixed-content"
]
http_header headers e846af19205bad86e03451978bd31a50982558da543ebef7387c867419631ef9
[
    "same-origin"
]
http_header headers b20b94ee864b9af06549c2509659b6d6f3fcd40f51d9643e549b32cb792cdfb9
[
    "Apache"
]
module_finding headers d6961aadbcc4466945c6a15063e6919cee353f2c85d1b41dd7123b22bd0ab25c
{
    "evidence": null,
    "severity": "info"
}
tls_valid_to tls 10c561a44ca1440e09b0379f23f871857ec5c734c7ebbe6b8bd716ecc2feed94
"2026-11-06T17:51:10+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

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

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

Mapping version
2.3.1
Evidence
19
Signals
1
Changes
0
mail_exchanger dns d62438acd8b408dda45a4d5dd0f386246dd9c32c20858b287a6dc2ef58cbc207
"mx2.mail.ovh.net"
module_finding mail_trust 9d8979021e2696d7251c1210fd52d01f90adea61a302e4f4a1d7fe41321dccd7
{
    "evidence": null,
    "severity": "low"
}
module_finding dns d07f5ca3ad98f3c189277eee8bd1fa15746bf89d3cb89038cb6fbe07be80b2e8
{
    "evidence": null,
    "severity": "low"
}
module_finding mail_trust 4612d76b0293caf6f86ff0f2ed6ed3ee5b85001b42326d61072bb64600ee3705
{
    "evidence": null,
    "severity": "high"
}
mail_policy_flag mail_trust 13a99ae02a2e051fedb9b0ec3af7381994c9eccd9f350d862d00eda00b262a31
false
module_finding mail_trust e5a77c9d31bee4948a48c7e5f96465d60ae991d71572a5e1bf5699c1caf066fb
{
    "evidence": null,
    "severity": "low"
}
mail_exchanger dns 053d5910e8d57a51bf283891e6e891b1d6692cfaa95ca2faf5d3a69c3e6c6300
"mx1.mail.ovh.net"
module_finding dns 280ba78273e5be6a147f01e76835d8bbd412a630bd2b81785a64506a2020836b
{
    "evidence": [
        "dns105.ovh.net",
        "ns105.ovh.net"
    ],
    "severity": "low"
}
mail_exchanger dns 28e7bc31967581ceed476fc91d9f075bb52b7ca82e987d568e09ef944f4f34f4
"mx3.mail.ovh.net"
module_finding dns b108711770fefd7f319365c442db97bdf90b2600245de84c718a2770394db43c
{
    "evidence": null,
    "severity": "medium"
}
dns_nameserver dns 0961c865d3699291e541caea89381e85d921514d32225d2d21e2b2da786e1c35
"ns105.ovh.net"
mail_policy_flag mail_trust 8ce27d0dd8d99cf8ec9bc11220cb983e5e256c7d79a713d0298ebdab95a2a8b1
false
dns_address dns 8ea92001c1d6563aa207bd34e68795958ce6b7f380c9ca3fc21dbd931cc40b18
"2001:1600::aaaa:0:0:80:5b"
mail_policy_flag mail_trust 112a568b00103ffb2a6b781ed5c59115bc90b7869a6912f5b3f6f3ba525557d6
false
dns_nameserver dns feb7593b3cf89689461e7d222099bacd97e0b2b287c30b79d13a13ba9a559abb
"dns105.ovh.net"
module_finding dns fe8a94e75df7e0a503249011b3ed7913161c33e69a475d7b9653e8fe4dd69bc4
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
spf_policy mail_trust ee6e64a562507c2b6a152088e883eb23b730775ad266b52791602685b456aba0
"hardfail"
dns_address dns ad8c2535aced5553de5e041a3b2352c6300d103fb6603b9f052e4dc26c2060d1
"185.125.27.197"
spf_record dns 5ab1bd4ca14fd5545e69cf2c11261399fd99c410e2d2e906b646cdf0c08243ac
"v=spf1 include:mx.ovh.com -all"
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

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

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

Mapping version
2.3.1
Evidence
19
Signals
1
Changes
0
mail_exchanger dns d62438acd8b408dda45a4d5dd0f386246dd9c32c20858b287a6dc2ef58cbc207
"mx2.mail.ovh.net"
module_finding mail_trust 9d8979021e2696d7251c1210fd52d01f90adea61a302e4f4a1d7fe41321dccd7
{
    "evidence": null,
    "severity": "low"
}
module_finding dns d07f5ca3ad98f3c189277eee8bd1fa15746bf89d3cb89038cb6fbe07be80b2e8
{
    "evidence": null,
    "severity": "low"
}
module_finding mail_trust 4612d76b0293caf6f86ff0f2ed6ed3ee5b85001b42326d61072bb64600ee3705
{
    "evidence": null,
    "severity": "high"
}
mail_policy_flag mail_trust 13a99ae02a2e051fedb9b0ec3af7381994c9eccd9f350d862d00eda00b262a31
false
module_finding mail_trust e5a77c9d31bee4948a48c7e5f96465d60ae991d71572a5e1bf5699c1caf066fb
{
    "evidence": null,
    "severity": "low"
}
mail_exchanger dns 053d5910e8d57a51bf283891e6e891b1d6692cfaa95ca2faf5d3a69c3e6c6300
"mx1.mail.ovh.net"
module_finding dns 280ba78273e5be6a147f01e76835d8bbd412a630bd2b81785a64506a2020836b
{
    "evidence": [
        "dns105.ovh.net",
        "ns105.ovh.net"
    ],
    "severity": "low"
}
mail_exchanger dns 28e7bc31967581ceed476fc91d9f075bb52b7ca82e987d568e09ef944f4f34f4
"mx3.mail.ovh.net"
module_finding dns b108711770fefd7f319365c442db97bdf90b2600245de84c718a2770394db43c
{
    "evidence": null,
    "severity": "medium"
}
dns_nameserver dns 0961c865d3699291e541caea89381e85d921514d32225d2d21e2b2da786e1c35
"ns105.ovh.net"
mail_policy_flag mail_trust 8ce27d0dd8d99cf8ec9bc11220cb983e5e256c7d79a713d0298ebdab95a2a8b1
false
dns_address dns 8ea92001c1d6563aa207bd34e68795958ce6b7f380c9ca3fc21dbd931cc40b18
"2001:1600::aaaa:0:0:80:5b"
mail_policy_flag mail_trust 112a568b00103ffb2a6b781ed5c59115bc90b7869a6912f5b3f6f3ba525557d6
false
dns_nameserver dns feb7593b3cf89689461e7d222099bacd97e0b2b287c30b79d13a13ba9a559abb
"dns105.ovh.net"
module_finding dns fe8a94e75df7e0a503249011b3ed7913161c33e69a475d7b9653e8fe4dd69bc4
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
spf_policy mail_trust ee6e64a562507c2b6a152088e883eb23b730775ad266b52791602685b456aba0
"hardfail"
dns_address dns ad8c2535aced5553de5e041a3b2352c6300d103fb6603b9f052e4dc26c2060d1
"185.125.27.197"
spf_record dns 5ab1bd4ca14fd5545e69cf2c11261399fd99c410e2d2e906b646cdf0c08243ac
"v=spf1 include:mx.ovh.com -all"
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

13evidence
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
13
Signals
2
Changes
0
dependency_provider dependencies 4812963b2a4ee296bdb646d565d1813753193b13e85b5cc7368ec2d2f1e32bba
{
    "critical": true,
    "hosts": [
        "dns105.ovh.net",
        "mx1.mail.ovh.net",
        "mx2.mail.ovh.net",
        "mx3.mail.ovh.net",
        "ns105.ovh.net"
    ],
    "id": "ovhcloud",
    "known": true,
    "name": "OVHcloud",
    "observation_count": 5,
    "services": [
        "cloud",
        "dns",
        "hosting"
    ],
    "tracker": false
}
mail_exchanger dns d62438acd8b408dda45a4d5dd0f386246dd9c32c20858b287a6dc2ef58cbc207
"mx2.mail.ovh.net"
module_finding dns d07f5ca3ad98f3c189277eee8bd1fa15746bf89d3cb89038cb6fbe07be80b2e8
{
    "evidence": null,
    "severity": "low"
}
mail_exchanger dns 053d5910e8d57a51bf283891e6e891b1d6692cfaa95ca2faf5d3a69c3e6c6300
"mx1.mail.ovh.net"
module_finding dns 280ba78273e5be6a147f01e76835d8bbd412a630bd2b81785a64506a2020836b
{
    "evidence": [
        "dns105.ovh.net",
        "ns105.ovh.net"
    ],
    "severity": "low"
}
mail_exchanger dns 28e7bc31967581ceed476fc91d9f075bb52b7ca82e987d568e09ef944f4f34f4
"mx3.mail.ovh.net"
module_finding dns b108711770fefd7f319365c442db97bdf90b2600245de84c718a2770394db43c
{
    "evidence": null,
    "severity": "medium"
}
dns_nameserver dns 0961c865d3699291e541caea89381e85d921514d32225d2d21e2b2da786e1c35
"ns105.ovh.net"
dns_address dns 8ea92001c1d6563aa207bd34e68795958ce6b7f380c9ca3fc21dbd931cc40b18
"2001:1600::aaaa:0:0:80:5b"
dns_nameserver dns feb7593b3cf89689461e7d222099bacd97e0b2b287c30b79d13a13ba9a559abb
"dns105.ovh.net"
module_finding dns fe8a94e75df7e0a503249011b3ed7913161c33e69a475d7b9653e8fe4dd69bc4
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
dns_address dns ad8c2535aced5553de5e041a3b2352c6300d103fb6603b9f052e4dc26c2060d1
"185.125.27.197"
spf_record dns 5ab1bd4ca14fd5545e69cf2c11261399fd99c410e2d2e906b646cdf0c08243ac
"v=spf1 include:mx.ovh.com -all"
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
technology technology 54133f661a7f127fcda75608d34f4ccb018bc7d23d2c632ed991695790a239b1
{
    "name": "Apache",
    "version": "",
    "version_exposed": false
}
http_header headers 26c894e98d62e2a109d0dade0b305a0c1ad167e062d581a174db374623b18e80
[
    "max-age=63072000; includeSubDomains; preload"
]
http_header headers 66aa1d5671b55805ff383577b69c7cc5b70f8ac0cb29e7c86d030caeeaa529fb
[
    "nosniff"
]
http_header headers deaad91874a75a5429ef518eef962fc909fa481b977a552a429b38af731598e7
[
    "same-origin"
]
http_header headers 169c31f34701ac8b4fd49cf157571457f19837c74564edbb681eb4cff54822b4
[
    "DENY"
]
http_header headers 82b4eb137e4ceb39df539fa73c652e252491f9014705fff17baba457fa36aeee
[
    "strict-origin-when-cross-origin"
]
http_header headers 998dce3408962c40df12f57cccdcf882c46b8c36fd6a32871700ed4b1f285ed1
[
    "accelerometer=(), autoplay=(), camera=(), display-capture=(), encrypted-media=(), fullscreen=(self), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), midi=(), payment=(), publickey-credentials-get=(), screen-wake-lock=(), usb=()"
]
http_header headers cbee82497783f4c74c11dcd51fe98e22e45414038c8c2868858dd00273be034b
[
    "default-src 'self'; base-uri 'self'; form-action 'self'; frame-ancestors 'none'; object-src 'none'; img-src 'self' data: https:; style-src 'self'; script-src 'self'; connect-src 'self'; font-src 'self'; manifest-src 'self'; media-src 'self'; worker-src 'self'; upgrade-insecure-requests; block-all-mixed-content"
]
http_header headers e846af19205bad86e03451978bd31a50982558da543ebef7387c867419631ef9
[
    "same-origin"
]
http_header headers b20b94ee864b9af06549c2509659b6d6f3fcd40f51d9643e549b32cb792cdfb9
[
    "Apache"
]
module_finding headers d6961aadbcc4466945c6a15063e6919cee353f2c85d1b41dd7123b22bd0ab25c
{
    "evidence": null,
    "severity": "info"
}
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 26c894e98d62e2a109d0dade0b305a0c1ad167e062d581a174db374623b18e80
[
    "max-age=63072000; includeSubDomains; preload"
]
module_finding mail_trust 9d8979021e2696d7251c1210fd52d01f90adea61a302e4f4a1d7fe41321dccd7
{
    "evidence": null,
    "severity": "low"
}
http_header headers 66aa1d5671b55805ff383577b69c7cc5b70f8ac0cb29e7c86d030caeeaa529fb
[
    "nosniff"
]
http_header headers deaad91874a75a5429ef518eef962fc909fa481b977a552a429b38af731598e7
[
    "same-origin"
]
module_finding dns d07f5ca3ad98f3c189277eee8bd1fa15746bf89d3cb89038cb6fbe07be80b2e8
{
    "evidence": null,
    "severity": "low"
}
module_finding mail_trust 4612d76b0293caf6f86ff0f2ed6ed3ee5b85001b42326d61072bb64600ee3705
{
    "evidence": null,
    "severity": "high"
}
module_finding mail_trust e5a77c9d31bee4948a48c7e5f96465d60ae991d71572a5e1bf5699c1caf066fb
{
    "evidence": null,
    "severity": "low"
}
http_header headers 169c31f34701ac8b4fd49cf157571457f19837c74564edbb681eb4cff54822b4
[
    "DENY"
]
module_finding resilience a13d72220e1a5d1af403bb91cfe04d58a2d3f7ca974cebca5584aaed52d84f3a
{
    "evidence": [
        "dns105.ovh.net",
        "ns105.ovh.net"
    ],
    "severity": "medium"
}
http_header headers 82b4eb137e4ceb39df539fa73c652e252491f9014705fff17baba457fa36aeee
[
    "strict-origin-when-cross-origin"
]
module_finding dns 280ba78273e5be6a147f01e76835d8bbd412a630bd2b81785a64506a2020836b
{
    "evidence": [
        "dns105.ovh.net",
        "ns105.ovh.net"
    ],
    "severity": "low"
}
module_finding dns b108711770fefd7f319365c442db97bdf90b2600245de84c718a2770394db43c
{
    "evidence": null,
    "severity": "medium"
}
http_header headers 998dce3408962c40df12f57cccdcf882c46b8c36fd6a32871700ed4b1f285ed1
[
    "accelerometer=(), autoplay=(), camera=(), display-capture=(), encrypted-media=(), fullscreen=(self), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), midi=(), payment=(), publickey-credentials-get=(), screen-wake-lock=(), usb=()"
]
http_header headers cbee82497783f4c74c11dcd51fe98e22e45414038c8c2868858dd00273be034b
[
    "default-src 'self'; base-uri 'self'; form-action 'self'; frame-ancestors 'none'; object-src 'none'; img-src 'self' data: https:; style-src 'self'; script-src 'self'; connect-src 'self'; font-src 'self'; manifest-src 'self'; media-src 'self'; worker-src 'self'; upgrade-insecure-requests; block-all-mixed-content"
]
http_header headers e846af19205bad86e03451978bd31a50982558da543ebef7387c867419631ef9
[
    "same-origin"
]
http_header headers b20b94ee864b9af06549c2509659b6d6f3fcd40f51d9643e549b32cb792cdfb9
[
    "Apache"
]
module_finding dns fe8a94e75df7e0a503249011b3ed7913161c33e69a475d7b9653e8fe4dd69bc4
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
module_finding headers d6961aadbcc4466945c6a15063e6919cee353f2c85d1b41dd7123b22bd0ab25c
{
    "evidence": null,
    "severity": "info"
}
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 26c894e98d62e2a109d0dade0b305a0c1ad167e062d581a174db374623b18e80
[
    "max-age=63072000; includeSubDomains; preload"
]
module_finding mail_trust 9d8979021e2696d7251c1210fd52d01f90adea61a302e4f4a1d7fe41321dccd7
{
    "evidence": null,
    "severity": "low"
}
http_header headers 66aa1d5671b55805ff383577b69c7cc5b70f8ac0cb29e7c86d030caeeaa529fb
[
    "nosniff"
]
http_header headers deaad91874a75a5429ef518eef962fc909fa481b977a552a429b38af731598e7
[
    "same-origin"
]
module_finding dns d07f5ca3ad98f3c189277eee8bd1fa15746bf89d3cb89038cb6fbe07be80b2e8
{
    "evidence": null,
    "severity": "low"
}
module_finding mail_trust 4612d76b0293caf6f86ff0f2ed6ed3ee5b85001b42326d61072bb64600ee3705
{
    "evidence": null,
    "severity": "high"
}
module_finding mail_trust e5a77c9d31bee4948a48c7e5f96465d60ae991d71572a5e1bf5699c1caf066fb
{
    "evidence": null,
    "severity": "low"
}
http_header headers 169c31f34701ac8b4fd49cf157571457f19837c74564edbb681eb4cff54822b4
[
    "DENY"
]
module_finding resilience a13d72220e1a5d1af403bb91cfe04d58a2d3f7ca974cebca5584aaed52d84f3a
{
    "evidence": [
        "dns105.ovh.net",
        "ns105.ovh.net"
    ],
    "severity": "medium"
}
http_header headers 82b4eb137e4ceb39df539fa73c652e252491f9014705fff17baba457fa36aeee
[
    "strict-origin-when-cross-origin"
]
module_finding dns 280ba78273e5be6a147f01e76835d8bbd412a630bd2b81785a64506a2020836b
{
    "evidence": [
        "dns105.ovh.net",
        "ns105.ovh.net"
    ],
    "severity": "low"
}
module_finding dns b108711770fefd7f319365c442db97bdf90b2600245de84c718a2770394db43c
{
    "evidence": null,
    "severity": "medium"
}
http_header headers 998dce3408962c40df12f57cccdcf882c46b8c36fd6a32871700ed4b1f285ed1
[
    "accelerometer=(), autoplay=(), camera=(), display-capture=(), encrypted-media=(), fullscreen=(self), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), midi=(), payment=(), publickey-credentials-get=(), screen-wake-lock=(), usb=()"
]
http_header headers cbee82497783f4c74c11dcd51fe98e22e45414038c8c2868858dd00273be034b
[
    "default-src 'self'; base-uri 'self'; form-action 'self'; frame-ancestors 'none'; object-src 'none'; img-src 'self' data: https:; style-src 'self'; script-src 'self'; connect-src 'self'; font-src 'self'; manifest-src 'self'; media-src 'self'; worker-src 'self'; upgrade-insecure-requests; block-all-mixed-content"
]
http_header headers e846af19205bad86e03451978bd31a50982558da543ebef7387c867419631ef9
[
    "same-origin"
]
http_header headers b20b94ee864b9af06549c2509659b6d6f3fcd40f51d9643e549b32cb792cdfb9
[
    "Apache"
]
module_finding dns fe8a94e75df7e0a503249011b3ed7913161c33e69a475d7b9653e8fe4dd69bc4
{
    "evidence": {
        "reason": "No external validating resolver is used; DS validation is intentionally not inferred.",
        "status": "not_tested"
    },
    "severity": "info"
}
module_finding headers d6961aadbcc4466945c6a15063e6919cee353f2c85d1b41dd7123b22bd0ab25c
{
    "evidence": null,
    "severity": "info"
}
10
Partial First observation

Security signals

This angle is only partially documented by public evidence

Angle 10

Security signals

Partial First observation

This angle is only partially documented by public evidence

01

Why it matters

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

02

How to read it

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

03

What it is for

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

04

What it does not prove

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

Material available for this angle

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
1
Changes
0

Unknowns and limitations

2 items still require qualification

http_header headers 26c894e98d62e2a109d0dade0b305a0c1ad167e062d581a174db374623b18e80
[
    "max-age=63072000; includeSubDomains; preload"
]
tls_issuer tls 458ee8e291926a8313e41be3f16125d53cb4f5e15757cb9488baceb56970d405
"C = US, O = Let's Encrypt, CN = YR2"
mail_exchanger dns d62438acd8b408dda45a4d5dd0f386246dd9c32c20858b287a6dc2ef58cbc207
"mx2.mail.ovh.net"
module_finding mail_trust 9d8979021e2696d7251c1210fd52d01f90adea61a302e4f4a1d7fe41321dccd7
{
    "evidence": null,
    "severity": "low"
}
http_header headers 66aa1d5671b55805ff383577b69c7cc5b70f8ac0cb29e7c86d030caeeaa529fb
[
    "nosniff"
]
http_header headers deaad91874a75a5429ef518eef962fc909fa481b977a552a429b38af731598e7
[
    "same-origin"
]
module_finding dns d07f5ca3ad98f3c189277eee8bd1fa15746bf89d3cb89038cb6fbe07be80b2e8
{
    "evidence": null,
    "severity": "low"
}
module_finding mail_trust 4612d76b0293caf6f86ff0f2ed6ed3ee5b85001b42326d61072bb64600ee3705
{
    "evidence": null,
    "severity": "high"
}
mail_policy_flag mail_trust 13a99ae02a2e051fedb9b0ec3af7381994c9eccd9f350d862d00eda00b262a31
false
module_finding mail_trust e5a77c9d31bee4948a48c7e5f96465d60ae991d71572a5e1bf5699c1caf066fb
{
    "evidence": null,
    "severity": "low"
}
http_header headers 169c31f34701ac8b4fd49cf157571457f19837c74564edbb681eb4cff54822b4
[
    "DENY"
]
module_finding resilience a13d72220e1a5d1af403bb91cfe04d58a2d3f7ca974cebca5584aaed52d84f3a
{
    "evidence": [
        "dns105.ovh.net",
        "ns105.ovh.net"
    ],
    "severity": "medium"
}
http_header headers 82b4eb137e4ceb39df539fa73c652e252491f9014705fff17baba457fa36aeee
[
    "strict-origin-when-cross-origin"
]
mail_exchanger dns 053d5910e8d57a51bf283891e6e891b1d6692cfaa95ca2faf5d3a69c3e6c6300
"mx1.mail.ovh.net"
module_finding dns 280ba78273e5be6a147f01e76835d8bbd412a630bd2b81785a64506a2020836b
{
    "evidence": [
        "dns105.ovh.net",
        "ns105.ovh.net"
    ],
    "severity": "low"
}
mail_exchanger dns 28e7bc31967581ceed476fc91d9f075bb52b7ca82e987d568e09ef944f4f34f4
"mx3.mail.ovh.net"
module_finding dns b108711770fefd7f319365c442db97bdf90b2600245de84c718a2770394db43c
{
    "evidence": null,
    "severity": "medium"
}
dns_nameserver dns 0961c865d3699291e541caea89381e85d921514d32225d2d21e2b2da786e1c35
"ns105.ovh.net"
http_header headers 998dce3408962c40df12f57cccdcf882c46b8c36fd6a32871700ed4b1f285ed1
[
    "accelerometer=(), autoplay=(), camera=(), display-capture=(), encrypted-media=(), fullscreen=(self), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), midi=(), payment=(), publickey-credentials-get=(), screen-wake-lock=(), usb=()"
]
http_header headers cbee82497783f4c74c11dcd51fe98e22e45414038c8c2868858dd00273be034b
[
    "default-src 'self'; base-uri 'self'; form-action 'self'; frame-ancestors 'none'; object-src 'none'; img-src 'self' data: https:; style-src 'self'; script-src 'self'; connect-src 'self'; font-src 'self'; manifest-src 'self'; media-src 'self'; worker-src 'self'; upgrade-insecure-requests; block-all-mixed-content"
]
http_header headers e846af19205bad86e03451978bd31a50982558da543ebef7387c867419631ef9
[
    "same-origin"
]
mail_policy_flag mail_trust 8ce27d0dd8d99cf8ec9bc11220cb983e5e256c7d79a713d0298ebdab95a2a8b1
false
dns_address dns 8ea92001c1d6563aa207bd34e68795958ce6b7f380c9ca3fc21dbd931cc40b18
"2001:1600::aaaa:0:0:80:5b"
mail_policy_flag mail_trust 112a568b00103ffb2a6b781ed5c59115bc90b7869a6912f5b3f6f3ba525557d6
false
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
2
Changes
0
technology technology 54133f661a7f127fcda75608d34f4ccb018bc7d23d2c632ed991695790a239b1
{
    "name": "Apache",
    "version": "",
    "version_exposed": false
}
dependency_provider dependencies 4812963b2a4ee296bdb646d565d1813753193b13e85b5cc7368ec2d2f1e32bba
{
    "critical": true,
    "hosts": [
        "dns105.ovh.net",
        "mx1.mail.ovh.net",
        "mx2.mail.ovh.net",
        "mx3.mail.ovh.net",
        "ns105.ovh.net"
    ],
    "id": "ovhcloud",
    "known": true,
    "name": "OVHcloud",
    "observation_count": 5,
    "services": [
        "cloud",
        "dns",
        "hosting"
    ],
    "tracker": false
}
http_header headers 26c894e98d62e2a109d0dade0b305a0c1ad167e062d581a174db374623b18e80
[
    "max-age=63072000; includeSubDomains; preload"
]
tls_issuer tls 458ee8e291926a8313e41be3f16125d53cb4f5e15757cb9488baceb56970d405
"C = US, O = Let's Encrypt, CN = YR2"
mail_exchanger dns d62438acd8b408dda45a4d5dd0f386246dd9c32c20858b287a6dc2ef58cbc207
"mx2.mail.ovh.net"
module_finding mail_trust 9d8979021e2696d7251c1210fd52d01f90adea61a302e4f4a1d7fe41321dccd7
{
    "evidence": null,
    "severity": "low"
}
http_header headers 66aa1d5671b55805ff383577b69c7cc5b70f8ac0cb29e7c86d030caeeaa529fb
[
    "nosniff"
]
http_header headers deaad91874a75a5429ef518eef962fc909fa481b977a552a429b38af731598e7
[
    "same-origin"
]
module_finding dns d07f5ca3ad98f3c189277eee8bd1fa15746bf89d3cb89038cb6fbe07be80b2e8
{
    "evidence": null,
    "severity": "low"
}
module_finding mail_trust 4612d76b0293caf6f86ff0f2ed6ed3ee5b85001b42326d61072bb64600ee3705
{
    "evidence": null,
    "severity": "high"
}
mail_policy_flag mail_trust 13a99ae02a2e051fedb9b0ec3af7381994c9eccd9f350d862d00eda00b262a31
false
module_finding mail_trust e5a77c9d31bee4948a48c7e5f96465d60ae991d71572a5e1bf5699c1caf066fb
{
    "evidence": null,
    "severity": "low"
}
http_header headers 169c31f34701ac8b4fd49cf157571457f19837c74564edbb681eb4cff54822b4
[
    "DENY"
]
module_finding resilience a13d72220e1a5d1af403bb91cfe04d58a2d3f7ca974cebca5584aaed52d84f3a
{
    "evidence": [
        "dns105.ovh.net",
        "ns105.ovh.net"
    ],
    "severity": "medium"
}
http_header headers 82b4eb137e4ceb39df539fa73c652e252491f9014705fff17baba457fa36aeee
[
    "strict-origin-when-cross-origin"
]
mail_exchanger dns 053d5910e8d57a51bf283891e6e891b1d6692cfaa95ca2faf5d3a69c3e6c6300
"mx1.mail.ovh.net"
module_finding dns 280ba78273e5be6a147f01e76835d8bbd412a630bd2b81785a64506a2020836b
{
    "evidence": [
        "dns105.ovh.net",
        "ns105.ovh.net"
    ],
    "severity": "low"
}
mail_exchanger dns 28e7bc31967581ceed476fc91d9f075bb52b7ca82e987d568e09ef944f4f34f4
"mx3.mail.ovh.net"
module_finding dns b108711770fefd7f319365c442db97bdf90b2600245de84c718a2770394db43c
{
    "evidence": null,
    "severity": "medium"
}
dns_nameserver dns 0961c865d3699291e541caea89381e85d921514d32225d2d21e2b2da786e1c35
"ns105.ovh.net"
http_header headers 998dce3408962c40df12f57cccdcf882c46b8c36fd6a32871700ed4b1f285ed1
[
    "accelerometer=(), autoplay=(), camera=(), display-capture=(), encrypted-media=(), fullscreen=(self), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), midi=(), payment=(), publickey-credentials-get=(), screen-wake-lock=(), usb=()"
]
http_header headers cbee82497783f4c74c11dcd51fe98e22e45414038c8c2868858dd00273be034b
[
    "default-src 'self'; base-uri 'self'; form-action 'self'; frame-ancestors 'none'; object-src 'none'; img-src 'self' data: https:; style-src 'self'; script-src 'self'; connect-src 'self'; font-src 'self'; manifest-src 'self'; media-src 'self'; worker-src 'self'; upgrade-insecure-requests; block-all-mixed-content"
]
http_header headers e846af19205bad86e03451978bd31a50982558da543ebef7387c867419631ef9
[
    "same-origin"
]
mail_policy_flag mail_trust 8ce27d0dd8d99cf8ec9bc11220cb983e5e256c7d79a713d0298ebdab95a2a8b1
false

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

DNS

2
DNS server Observed

ns105.ovh.net

DNS server Observed

dns105.ovh.net

mail

3
Mail server Observed

mx3.mail.ovh.net

Mail server Observed

mx2.mail.ovh.net

Mail server Observed

mx1.mail.ovh.net

technology

1
Observed technology Observed

Apache

external resources

1
External provider or resource Corroborated

OVHcloud

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 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:34:09+00:00

#02 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": [ "dns105.ovh.net", "mx1.mail.ovh.net", "mx2.mail.ovh.net", "mx3.mail.ovh.net", "ns105.ovh.net" ], "id": "ovhcloud", "known": true, "name": "OVHcloud", "observation_count": 5, "services": [ "cloud", "dns", "hosting" ], "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": [
        "dns105.ovh.net",
        "mx1.mail.ovh.net",
        "mx2.mail.ovh.net",
        "mx3.mail.ovh.net",
        "ns105.ovh.net"
    ],
    "id": "ovhcloud",
    "known": true,
    "name": "OVHcloud",
    "observation_count": 5,
    "services": [
        "cloud",
        "dns",
        "hosting"
    ],
    "tracker": false
}

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

#04 Public TLS endpoint

Evidence: tls_issuer

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

Active non-intrusive High
Why it matters

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

What to check next

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

Possible action

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

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

Standards and reference context

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

Verify it yourself

This command reproduces the public observation without changing the target.

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

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

#05 DNS public records

Evidence: mail_exchanger

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

Passive High
Why it matters

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

What to check next

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

Possible action

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

Observation
mx2.mail.ovh.net
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 darfoufa.com
View raw data
mx2.mail.ovh.net

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

#06 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:34:09+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
[ "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:34:09+00:00

#08 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:34:09+00:00

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

#10 Mail-related public records

Evidence: module_finding

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

Active non-intrusive High
Why it matters

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

What to check next

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

Possible action

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

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

Standards and reference context

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

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

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

#12 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:34:09+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
[ "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:34:09+00:00

#14 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": [ "dns105.ovh.net", "ns105.ovh.net" ], "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": [
        "dns105.ovh.net",
        "ns105.ovh.net"
    ],
    "severity": "medium"
}

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

#15 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:34:09+00:00

#16 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
mx1.mail.ovh.net
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 darfoufa.com
View raw data
mx1.mail.ovh.net

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

#17 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": [ "dns105.ovh.net", "ns105.ovh.net" ], "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": [
        "dns105.ovh.net",
        "ns105.ovh.net"
    ],
    "severity": "low"
}

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

#18 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
mx3.mail.ovh.net
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 darfoufa.com
View raw data
mx3.mail.ovh.net

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

Standards and reference context

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

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

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

#20 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
ns105.ovh.net
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 darfoufa.com
View raw data
ns105.ovh.net

Rule 2026.09.4 · 2026-09-04T19:34:09+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
[ "accelerometer=(), autoplay=(), camera=(), display-capture=(), encrypted-media=(), fullscreen=(self), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), midi=(), payment=(), publickey-credentials-get=(), screen-wake-lock=(), usb=()" ]
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=(), encrypted-media=(), fullscreen=(self), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), midi=(), payment=(), publickey-credentials-get=(), screen-wake-lock=(), usb=()"
]

Rule 2026.09.4 · 2026-09-04T19:34:09+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
[ "default-src 'self'; base-uri 'self'; form-action 'self'; frame-ancestors 'none'; object-src 'none'; img-src 'self' data: https:; style-src 'self'; script-src 'self'; connect-src 'self'; font-src 'self'; manifest-src 'self'; media-src 'self'; worker-src 'self'; upgrade-insecure-requests; block-all-mixed-content" ]
Understand
HTTP response-header inspection
Source
Public HTTP response
Reliability
High
What this supports
Describe defensive policies declared on the observed response
What this does not prove
A header being present does not prove it is optimal or that the application has no vulnerabilities.

Standards and reference context

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

View raw data
[
    "default-src 'self'; base-uri 'self'; form-action 'self'; frame-ancestors 'none'; object-src 'none'; img-src 'self' data: https:; style-src 'self'; script-src 'self'; connect-src 'self'; font-src 'self'; manifest-src 'self'; media-src 'self'; worker-src 'self'; upgrade-insecure-requests; block-all-mixed-content"
]

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

#24 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:34:09+00:00

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

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

#26 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:34:09+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:34:09+00:00

#28 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
dns105.ovh.net
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 darfoufa.com
View raw data
dns105.ovh.net

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

#29 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:34:09+00:00

#30 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 darfoufa.com
View raw data
hardfail

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

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

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

#32 Public HTTP response

Evidence: module_finding

HTTP headers can ask the browser to enforce specific protections.

Active non-intrusive High
Why it matters

They are visible, verifiable browser-side defensive layers.

What to check next

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

Possible action

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

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

Standards and reference context

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

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

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

#33 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:mx.ovh.com -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:mx.ovh.com -all

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

#34 Public TLS endpoint

Evidence: tls_valid_to

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

Active non-intrusive High
Why it matters

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

What to check next

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

Possible action

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

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

Standards and reference context

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

View raw data
2026-11-06T17:51:10+00:00

Rule 2026.09.4 · 2026-09-04T19:34:09+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": "0bc979464c226e1ab5a6a0e21263a328dd89ff3532aeb41de88ac839889de80d",
        "display_name": "darfoufa.com",
        "slug": "darfoufa-com",
        "entity_type": "domain_subject",
        "auto_created": true,
        "primary_asset": "darfoufa.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
    }
}