The Digital Data Journey

Understanding the physical and jurisdictional path of your data is essential for effective risk management. The Juri analysis tracks the complete data journey to identify all points where legal jurisdictions may impact your data.

1

Domain Analysis

When you enter a domain, IP address, or .onion address, Juri begins by determining what type of entity we're analyzing:

  • Standard domain names (example.com)
  • IPv4 addresses (93.184.216.34)
  • IPv6 addresses (2606:2800:220:1:248:1893:25c8:1946)
  • Onion addresses (facebookwkhpilnemxj7asaniu7vnjjbiltxjqhye3mhbshg7kx5tfyd.onion)
2

TLD & Domain Jurisdiction

For domain names, Juri extracts the Top-Level Domain (TLD) and maps it to its controlling jurisdiction:

  • Generic TLDs (.com, .org, .net) → US jurisdiction
  • Country code TLDs (.uk, .de, .jp) → Respective countries
  • Compound TLDs (.co.uk, .gov.uk) → Special handling
  • New gTLDs (.app, .dev, .blog) → Jurisdictional analysis
3

IP Geolocation Analysis

Juri identifies the physical location of servers by:

  • Direct IP geolocation for IP address inputs
  • DNS resolution for domains to find their IP addresses
  • Special handling for CDNs and distributed hosting
  • Tor network analysis for .onion addresses

This determines the hosting jurisdiction - the country where the servers physically reside.

4

Corporate Ownership Analysis

Juri identifies the legal entities that control the infrastructure:

  • WHOIS database lookups (with privacy protection detection)
  • Autonomous System Number (ASN) analysis
  • Corporate registration database cross-references
  • Historical acquisition data

This determines the corporate jurisdiction - the country whose laws apply to the controlling entity.

6

Embargo & Sanction Analysis

Juri identifies relevant international restrictions:

  • Country-specific embargoes affecting data flows
  • Technology export control implications
  • Sanctions that impact service provision
  • Counter-sanction considerations
7

Risk Score Calculation

Finally, Juri calculates the GLARS (Geo-Legal Access Risk Score) by:

  • Analyzing the complete jurisdictional profile
  • Weighting factors based on severity and likelihood
  • Calculating component risk scores
  • Producing a comprehensive assessment

Data Flow Complexity

The digital data journey is often more complex than it appears. A single website can involve:

  • Content hosted across multiple CDN providers
  • API calls to services in various jurisdictions
  • Database storage in different locations than web servers
  • Corporate entities with complex multinational structures

Juri untangles this complexity by focusing on the primary hosting and corporate jurisdictions while highlighting supplementary risk factors introduced by distributed architectures.