Infrastructure answers, when they matter most.

digNS brings practical DNS, SSL and web infrastructure tools together in one fast, accurate and accessible workspace.

DNSSSL / TLSMulti-nodeHostingDevOps
The origin

Born from a real infrastructure crisis

The story of digNS began on the evening of Thursday, January 8, 2026, when reliable answers suddenly became hard to find.

On the evening of Thursday, January 8, 2026, international internet access in Iran was completely disrupted. Public DNS resolvers became unreliable, services hosted outside the country disappeared from reach, and even domestic websites were affected by DNS instability.

At the same time, the online DNS, SSL and network diagnostic tools technical teams relied on every day were no longer accessible. There was no single Iranian service bringing these checks together. For infrastructure and support teams responsible for keeping customer websites available, that gap had become a serious operational problem—not a minor inconvenience.

digNS started as a direct response: a dependable, accessible toolkit for seeing what is happening across DNS, certificates and web infrastructure.

Access was lost

International tools and externally hosted services became unreachable.

DNS became uncertain

Resolver and authoritative name-server answers needed independent verification.

The toolkit was missing

Critical diagnostics were scattered or unavailable when they were needed most.

How it is different

More than a collection of lookup forms

Each feature is shaped around the questions a technical team asks during a real incident.

DNS from both sides

Query a selected resolver or trace answers from TLD and authoritative name servers to expose propagation differences.

Independent name-server checks

The A record on each authoritative name server is checked separately, making mismatched configurations visible.

One connected diagnosis

DNS, IP, reachability and SSL context are brought together so users spend less time switching between tools.

Built from daily operations

The workflows come from real DevOps and hosting-support work, not a theoretical feature list.

A distributed point of view

Checks from multiple nodes help separate a local routing problem from a wider service failure.

Clear and accessible

Results help both specialists and website owners understand the next useful action.

People behind the product

Human experience, accelerated by AI

Amir Mohmad Rajabi

Founder & Developer

As a DevOps engineer and technical support specialist at a hosting and infrastructure company, maintaining the availability of a large number of websites is a daily responsibility—tens of thousands of sites facing a serious crisis and a wide range of problems at the same time. digNS was built from that experience to make diagnostics faster, clearer and more practical. AI tools carried a significant part of the implementation and coding workload, while the product logic, priorities and operational decisions were shaped by real-world experience and the support of friends and colleagues.

Built through collaboration

With gratitude

The design, architecture and feature set of digNS were shaped through the ideas and thoughtful feedback of many friends and colleagues. Special thanks to engineers Meysami, Jahantigh, Majd and Pouya—and to everyone who tested, challenged and improved the product along the way.

Help expand the digNS network

Infrastructure and hosting providers can contribute a server or its cost. Approved nodes join distributed checks, and the supporting organization is credited beside the results produced by its node.

Discuss collaboration
Let’s talk

Ideas, feedback and new tools are welcome.

If you have found a bug, need a diagnostic tool, or have an idea that can make digNS more useful, get in touch.

Email LinkedIn Telegram Instagram