How passive intelligence reveals the structure, risks, and hidden organizational clusters behind Lithuania's national domain space - and why attackers already know more about your infrastructure than you think.
Published: March 2026
We often think of a domain name as a digital front door. A simple address that leads to a website. But behind every .lt domain lies a web of infrastructure decisions, organizational relationships, and - often unintentionally - security exposures visible to anyone who knows where to look.
At Entryscope, we set out to map Lithuania's national domain space: every active .lt domain, its DNS infrastructure, IP addresses, hosting providers, and organizational affiliations. The result is a dataset spanning 211,486 apex domains (out of approximately 252,410 total registered .lt domains), almost a million subdomains, and over 103,000 unique IP addresses distributed across 80 countries and over 2,000 autonomous systems.
What we found goes beyond a simple directory. By cross-referencing domain registry data, shared infrastructure signals, and corporate cloud tenant identifiers, we uncovered hidden organizational clusters: groups of seemingly unrelated domains that share the same corporate ownership. For IT security professionals, this is the kind of lateral visibility that transforms asset discovery. For everyone else, it's a revealing look at how interconnected and exposed a national domain space truly is.
Why should domain owners care? Everything described in this report is available to anyone - including adversaries - through passive data collection. The techniques we used mirror those employed by threat actors during the reconnaissance phase of a cyberattack. Understanding what your infrastructure reveals to the outside world is the first step toward reducing your attack surface.
.lt domain space as a case study, the patterns, risks, and attack vectors described here are not Lithuania-specific. Any country's national domain space - whether .de, .nl, .pl, or any other ccTLD - is very likely affected by the same structural concentrations, the same organizational clustering dynamics, and the same categories of exposed services. The methodology is universally applicable, and the findings should be read as representative of systemic internet infrastructure risks, not as unique to Lithuania.
Our analysis covers 211,486 domains registered under Lithuania's .lt country-code top-level domain (ccTLD), representing approximately 83.8% of the total 252,410 registered .lt domains at the time of writing. For each domain, we collected:
All data was collected exclusively from passive and stealth sources: public DNS records, WHOIS databases, certificate transparency logs, and aggregated scan data from publicly available online port scan databases. No websites were visited, no active port scanning was performed against any specific target, and no authentication boundaries were tested. The analysis relies entirely on what is already publicly visible - which, as the findings show, is considerable.
This methodology mirrors how sophisticated threat actors perform initial reconnaissance. Attackers often use tools like Bbot, Amass, Subfinder (just to name a few), and various OSINT frameworks which aggregate exactly these data sources to build target profiles before launching attacks. The difference is that we do it to help organizations understand their exposure - adversaries do it to exploit it.
Of the 211,486 domains in our dataset, 207,254 are actively resolving (98%), while 4,232 returned no DNS response for A type records (while still resolving to other DNS types, such as NS and MX).
From an attacker's perspective, even non-resolving domains are valuable targets. They represent potential candidates for subdomain takeover, dangling DNS exploitation, or future re-registration. An attacker monitoring the domain registry can identify when these domains expire and re-register them to impersonate the original brand.
Lithuania's domain market is concentrated among a handful of registrars. The top two alone - Interneto vizija (iv.lt) and Hostinger - account for over 67% of all registered .lt domains:
| Registrar | Domains | Market Share |
|---|---|---|
| Interneto vizija (iv.lt) | 98,315 | 46.5% |
| Hostinger | 44,712 | 21.1% |
| Telia Lietuva | 10,235 | 4.8% |
| Bartus pro (domenai.lt) | 8,763 | 4.1% |
| KTU (domains.lt) | 6,659 | 3.1% |
The remaining 108 registrars share about 20% of the market, creating a long tail of smaller providers - including international operators like Registrar.eu, Zone.eu, and NETIM serving enterprise and international clients.
Fig. 1 - Registrar market share across 211,486 .lt domains
Security Implication: Concentration as a single point of failure. With nearly half of all .lt domains managed by a single registrar, a targeted attack against that registrar - whether through social engineering of its support staff, compromise of its management panel, exploitation of N-day or 0-day vulnerabilities, or a supply-chain attack - could have cascading effects across the national domain space. A recent (2025) incident involving the widely used text editor Notepad++ reportedly saw a highly motivated actor targeting a service provider on which Lithuanian infrastructure is highly dependent. This demonstrates that with sufficient motivation, funding, and skill, even the strongest barriers can fall.
The SOA (Start of Authority) records reveal which providers actually operate the DNS infrastructure, which is often different from the registrar. Authoritative DNS is the foundation of all domain resolution - compromising a DNS authority provider gives an attacker the ability to redirect traffic for every domain under that provider's control.
| DNS Authority (SOA) | Domains |
|---|---|
| Interneto vizija (iv.lt) | 82,507 |
| Hostinger | 45,660 |
| Cloudflare | 18,736 |
| Telia Hosting | 7,382 |
| KTU (domains.lt) | 3,387 |
| Zone.eu | 2,388 |
| Wix | 2,297 |
| BALT.NET | 1,960 |
| BAcloud | 1,804 |
Cloudflare's position is notable: while it's not a registrar in this market, it serves as the DNS authority for over 18,700 .lt domains - roughly 8.9% of the entire namespace. This reflects the global trend of DNS and CDN centralization, where domains remain "Lithuanian" in name but are operationally governed by U.S.-based infrastructure providers.
Why centralization is a national risk: If a state-sponsored actor were to target the largest DNS provider in this ecosystem, the blast radius would encompass over 82,000 domains - nearly 40% of the entire .lt namespace. The 2016 Dyn DNS attack demonstrated how a single infrastructure provider's outage can take down major portions of the internet; on a national scale, the concentration visible here presents a similar systemic risk. Additionally, given Cloudflare's history of global outages in 2025 and 2026, it is clear that the material risk is a tangible concern for the business.
Where are .lt domains actually hosted? We resolved 103,963 unique IP addresses from domain and subdomain A records, spread across 80 countries. For those IPs with geolocation data available (99,033 IPs), the distribution reveals a significant dependency on foreign infrastructure:
47.1% of all geolocated IP addresses serving .lt domains are located outside Lithuania. Nearly half of the national domain space runs on foreign infrastructure.
| Country | IPs | Share |
|---|---|---|
| Lithuania | 52,390 | 52.9% |
| United States | 25,233 | 25.5% |
| Germany | 5,705 | 5.8% |
| Netherlands | 2,281 | 2.3% |
| Poland | 2,052 | 2.1% |
| France | 1,774 | 1.8% |
| Sweden | 1,523 | 1.5% |
| Ireland | 1,406 | 1.4% |
| Finland | 1,064 | 1.1% |
| United Kingdom | 963 | 1.0% |
The U.S. share is driven largely by Cloudflare (whose anycast IPs register as U.S.-based), Amazon AWS, and Microsoft Azure. Germany and the Netherlands host a significant portion of EU-hosted infrastructure through providers like Hetzner, OVH, and DigitalOcean.
This is where the analysis moves from infrastructure inventory to organizational intelligence - and where the implications for security become most acute.
One of the fundamental challenges in attack surface management is answering a deceptively simple question: which domains belong to the same organization? Companies acquire new brands, launch campaign microsites, maintain legacy domains from mergers, and register protective variations of their primary brand. These domains are rarely documented in a single inventory, and the connections between them are scattered across multiple registration records, DNS configurations, and infrastructure decisions.
An attacker performing reconnaissance faces the same question - in reverse. If they've identified one domain belonging to a target organization, their next step is to discover every other digital asset that shares the same corporate ownership. The weakest link in that chain becomes the entry point.
By cross-referencing multiple passive data sources, we can construct organizational fingerprints that link domains to their operators:
Each signal type carries a different confidence weight. Corporate cloud identifiers and registration email addresses are strong indicators of common ownership, while shared IP addresses alone may simply indicate co-hosting. By building a graph of weighted connections and extracting transitively linked clusters, we can map organizational boundaries with high accuracy.
Applying this multi-signal clustering approach across the .lt domain space, we identified 16,132 organizational clusters encompassing 70,199 domains - roughly a third of the entire dataset:
| Cluster Metric | Value |
|---|---|
| Total clusters identified | 16,132 |
| Domains linked to an organization | 70,199 |
| Clusters with 3+ domains | 8,250 |
| Clusters with 5+ domains | 3,715 |
| Clusters with 10+ domains | 1,232 |
| Clusters with 20+ domains | 382 |
| Largest single cluster | 165 domains |
| Average cluster confidence | 97.1% |
The numbers are striking. 3,715 organizations operate five or more distinct domains under the .lt namespace. 382 organizations maintain portfolios of 20 or more domains. And the largest organizational cluster - a single entity - operates 165 distinct .lt domains.
A single organizational cluster spanning 165 domains means one breach, one compromised admin account, or one misconfigured identity policy could affect the security posture of all 165 digital properties simultaneously. An attacker who compromises any single domain in the cluster gains a roadmap to 164 additional targets.
This clustering approach mirrors established OSINT techniques used by both red teams and threat actors. The technique was documented in MITRE ATT&CK under T1596 (Search Open Technical Databases) and T1593 (Search Open Websites/Domains).
Perhaps most concerning is what clustering reveals about organizational awareness. When we identify 165 domains under a single organizational identity, it's worth asking: does that organization know about all 165? In our experience, the answer is almost always no.
These shadow IT domains - campaign sites registered by the marketing department, legacy domains from acquired companies, test environments set up by developers - are frequently the least maintained and most vulnerable assets in an organization's portfolio.
Fig. 2 - Cluster size distribution across 16,132 organizational clusters
The .lt domain space tells a story of Lithuania's digital evolution. The oldest domain (out of those still active) in our dataset - mii.lt - was registered on February 26, 1993, almost three years after Lithuania declared independence.
| Period | Domains Registered | Observation |
|---|---|---|
| 1993–2006 | 6,598 | Early internet adoption |
| 2007–2013 | 27,459 | Steady growth with EU integration |
| 2014–2019 | 47,140 | Digital economy acceleration |
| 2020–2021 (COVID era) | 26,231 | Pandemic-driven surge |
| 2022–2025 | 96,832 | Continued expansion |
| 2026 (Jan–Mar) | 7,226 | Current pace on track |
Why registration history matters to attackers: The registration date of a domain reveals its likely technology vintage. Domains registered in 2007–2013 are more likely to run legacy CMS versions with known, unpatched vulnerabilities. Attackers routinely correlate domain age with technology stacks to prioritize targets.
Fig. 3 - Currently still active .lt domain registration timeline (1993–2026)
Domain expirations are a security event. An expired domain can be re-registered by anyone - including threat actors - enabling phishing, brand impersonation, or subdomain takeover attacks if dangling DNS records persist.
Because the vast majority of .lt domains are registered on one-year terms, the entire namespace exists in a state of perpetual renewal. At any given moment, a significant share of all registered domains is approaching expiration, sitting in a grace period, or pending deletion. This creates a continuous, rolling window of opportunity for attackers who monitor expiry feeds - domain drop-catching services that track and snap up valuable domains the moment they become available.
Domains that have passed their expiration date but remain in DNS - whether in a registrar grace period or simply neglected - represent active security threats through two well-documented attack vectors:
Domain Hijacking for Brand Impersonation. When a domain expires and becomes available for re-registration, an attacker can register it and replicate the original website to phish customers, partners, or employees. Because the domain was previously associated with a legitimate organization, users and even email security systems may trust it implicitly.
Account Takeover via Password Reset. If the expired domain previously hosted employee or corporate email addresses, an attacker who re-registers the domain can set up a mail server and receive password reset emails from third-party services where employees previously registered using that email address.
With 170,169 domains in our dataset configured with MX records (indicating email capability), the attack surface for this technique is significant.
Beyond DNS and domain registration, we enriched the dataset with service-level intelligence from publicly available online port scan databases for 99,078 of the resolved IPs. The results map out what's actually listening on the internet:
56.2% of all scanned IPs run a web server, and 91% of web-serving IPs support HTTPS - a reasonably healthy encryption adoption rate. The dominant software stack:
| Software | Instances | Context |
|---|---|---|
| Cloudflare | 280,327 | CDN / reverse proxy (multiple ports per IP) |
| nginx | 20,151 | Web server / reverse proxy |
| OpenResty | 12,395 | nginx-based (often cPanel stacks) |
| Dovecot | 12,670 | IMAP mail server |
| OpenSSH | 10,299 | Remote administration |
| Exim | 6,297 | Mail transfer agent |
| cPanel | 6,267 | Hosting control panel |
| Postfix | 4,062 | Mail transfer agent |
| Apache httpd | 3,869 | Web server |
More concerning are the services that should rarely - if ever - face the public internet. The following counts have been filtered to remove false positives:
| Service | Exposed IPs | Risk Context |
|---|---|---|
| FTP (ports 21/990) | 6,858 | Credential interception possible if STARTTLS not enforced |
| Databases (MySQL, PostgreSQL, MSSQL, etc.) | 4,315 | Direct data access if misconfigured |
| RDP (Remote Desktop) | 751 | Primary ransomware initial access vector |
| SMB (File Sharing) | 198 | Lateral movement, EternalBlue-class exploits |
| VNC (Remote Desktop) | 132 | Often weak or no authentication |
| Telnet | 36 | Unencrypted legacy protocol |
The 751 IPs with exposed RDP services deserve special attention. We identified RDP services not only on the standard port 3389 (447 IPs), but also on 320 additional IPs running RDP on non-standard ports - a common practice intended to "hide" the service from automated scanners, but easily detected by modern scan databases that probe the entire port range.
RDP remains the single most exploited initial access vector for ransomware operators. According to Sophos' Active Adversary Report, compromised RDP accounts were involved in over 90% of ransomware incidents in recent years.
The 4,315 IPs with internet-facing database services represent perhaps the most direct data breach risk:
| Database | Exposed IPs |
|---|---|
| MySQL / MariaDB | 3,304 |
| PostgreSQL | 461 |
| Microsoft SQL Server | 175 |
| Redis | 153 |
| MongoDB | 126 |
| Elasticsearch | 72 |
| Memcached | 24 |
The 153 Redis and 126 MongoDB instances directly exposed to the internet is concerning - these databases are frequently deployed with no authentication by default.
Fig. 4 - Administrative services exposed to the public internet across .lt infrastructure
Across the 99,078 scanned IPs, online port scan databases identified 475,433 total vulnerability instances spanning 4,789 unique CVEs. 10.7% of all scanned IPs (10,556) have at least one known vulnerability associated with their running services.
Shared hosting concentrates risk in ways that individual domain owners rarely appreciate. Our IP-to-domain mapping reveals extreme concentration:
| IP Address | Apex Domains | Total Subdomains |
|---|---|---|
| 79.*.*.1 | 22,296 | 31,178 |
| 84.*.*.32 | 10,068 | 8,289 |
| 34.*.*.41 | 7,215 | 7,245 |
| 23.*.*.65 | 4,221 | 442 |
| 2.*.*.91 | 3,633 | 3,381 |
A single IP address - 79.*.*.1 - hosts 22,296 distinct domains and over 31,000 subdomains. A successful compromise of this server, or a DDoS attack targeting it, would affect thousands of Lithuanian businesses simultaneously.
Of the 103,963 IPs in our hosting statistics, 25,260 (24.3%) belong to Cloudflare's network, which provides a layer of DDoS protection and CDN performance - but also means a quarter of all traffic flows through a single provider's infrastructure.
The fact that the top five IPs alone host over 47,000 domains means that five successful compromises could affect approximately 22% of all .lt domains. This concentration creates a systemic risk that extends beyond individual domain owners to the national digital ecosystem as a whole.
The .lt domain space tells a coherent story about how a modern, digitally active nation builds, maintains, and occasionally neglects its online presence:
.lt domains registered on one-year terms, the namespace exists in a state of perpetual renewal churn - creating persistent opportunities for domain hijacking, brand impersonation, and account takeover via password reset abuse.The Lithuanian domain space is more interconnected - and more transparent - than most realize. The connections are there, embedded in DNS records, IP geolocation data, corporate cloud identifiers, and organizational metadata, visible to anyone with the right methodology.
The purpose of this analysis is not to alarm, but to demonstrate what passive intelligence reveals at scale. Every organization has a digital perimeter, and in most cases, that perimeter is larger, more distributed, and more exposed than anyone on the IT team fully appreciates.
Understanding your attack surface is the first step to defending it - and the window between when an exposure appears and when an attacker discovers it is narrowing every day.
Want to see your organization's external footprint?
Entryscope maps your domains, IPs, exposed services, and organizational connections - continuously. See what attackers see, before they act on it.
Request a Demo