Skip to content

Hostname

datalegal.fr

Last fetched

datalegal.fr resolves to 108.132.87.227, announced in 108.128.0.0/13 by AMAZON-02 - Amazon.com, Inc. in IE. datalegal.fr is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · datalegal.frRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.6/10canon.whisper.security/host/datalegal.fr

Resolution chain

IPv6 resolution

No AAAA record for datalegal.fr is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for datalegal.fr. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

Subdomains

Subdomain
api.datalegal.fr
cdn.datalegal.fr
companies-assets.datalegal.fr
sitemaps.datalegal.fr
staging-cdn.datalegal.fr
staging-companies-assets.datalegal.fr
staging.datalegal.fr
support.datalegal.fr

Showing 8 of 8 subdomains (8 per page).

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Sample inbound links

Sample outbound links

Mail and authentication

Nameservers

  • ns-171.awsdns-21.com
  • ns-815.awsdns-37.net
  • ns-1455.awsdns-53.org
  • ns-1888.awsdns-44.co.uk

MX records

  • fb.mail.gandi.net
  • spool.mail.gandi.net

SPF policy

  • include: mail.zendesk.com
  • include: _mailcust.gandi.net

Threat-feed evidence

History

Related pages

Pivot from datalegal.fr into the addresses, networks and registries it depends on.

Cypher and MCP

Reproduce this hostname's resolution chain against graph.whisper.security:

MATCH (h:HOSTNAME {name: "datalegal.fr"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.