← Projects

Nupy

Nupy.ru was a data platform for collecting, updating, and analyzing millions of domains in the .ru, .рф, and .su zones. I built the project solo, including domain crawling, SEO and technology detection, DNS/WHOIS tools, dataset generation, Digiseller integration, and the admin system.

Nupy.ru — Domain Services and Data Platform

Nupy.ru was a service for collecting, storing, and analyzing data about domains in the Russian .ru, .рф, and .su zones.

It kept a domain database up to date and collected technical and SEO information about websites. The service was built for SEO specialists, marketers, web studios, domain investors, and analysts who needed to check domains, find useful domain lists, or buy ready-to-use datasets.

What the Service Did

Nupy.ru included free public tools for working with domains and DNS:

  • WHOIS lookup, including domain validation, zone, status, registration availability, and WHOIS data;
  • DNS lookup for A, AAAA, MX, TXT, NS, CNAME, SOA, and reverse PTR records;
  • basic technical information about a domain and its website.

The internal system regularly imported domain lists and updated their statuses. For each domain, it could collect DNS data, registration dates, registrars, page metadata, redirects, SSL information, CMS, installed modules, web technologies, analytics systems, counters, and other available website details.

Important domain changes were saved as history, so the collected data could be used later for analysis and selections.

Datasets and Sales

Based on the collected data, the service created domain selections for specific conditions. These datasets could be used for SEO, marketing, lead research, monitoring expired domains, and website market research.

The project also included a catalog of datasets with descriptions, prices, file examples, and purchase options. Product pages and offers could be created automatically and published through Digiseller. After payment, customers received a download link for the purchased file.

Main Technical Work

  • regular import and update of large domain lists;
  • mass crawling of domains and websites;
  • parsing, normalizing, and storing technical and SEO data;
  • detection of CMS, analytics, advertising systems, online chats, and other integrations;
  • automatic creation of dataset files and product pages;
  • an admin area for datasets, domains, service requests, partner programs, and click statistics;
  • partner offers from domain registrars in the WHOIS results.

Technology

PHP, Laravel, MySQL, HTML, CSS, JavaScript, VDS

Resources

Development took about 180 hours, including work on the public tools, data collection, dataset generation, integrations, logging, and maintenance.

Financial investment was minimal. The main investment was my own development time, which I did not formally track while working on the project.

Project Status

Closed / on hold.

Nupy.ru was both a product and technical experiment. I wanted to test demand for this type of service and see whether one person could build and maintain a system that works with a large amount of constantly updated data.

The main issue was the project economy. Storing, updating, and processing a large number of domains required significant server resources. At the same time, demand was not strong enough in a competitive market. Further growth would have increased costs faster than the value of the product was confirmed.

I stopped further development and kept the project as a technical and product experiment. I may return to the idea in the future with a different business model, data-processing architecture, or clearer demand.

Key Lesson

Nupy.ru showed me that it is not enough to know that a product can be built. Before starting a data-heavy project, it is also important to estimate:

  • ongoing costs after launch;
  • infrastructure needed for stable work;
  • how costs grow with the amount of data;
  • the time and skills needed to support the service;
  • expected revenue and real demand;
  • the balance between operating costs and possible profit.

One of the lessons from Nupy.ru was that low development costs do not necessarily mean a product is inexpensive to operate. In data-heavy products, infrastructure and ongoing processing costs can become significantly more important than the initial cost of development.

The project gave me experience in building a system for large-scale data collection and analysis. More importantly, it showed that technical feasibility does not always mean a product is economically viable.