Founder and maintainer

Tudor Uzun

Also known as Theodore Uzun

Founder and Senior Software Engineer, IP Trackers

Founder and senior software engineer behind IP Trackers, focused on practical IP, DNS, ASN, WHOIS, port, proxy, and VPN diagnostic workflows.

93 published guides
Writing since 2026
Tested on 5 OS platforms

Explore selected work How the tools are tested Hire me

The tools and UI systems on this site are built and maintained by hand, and I take on freelance React, Next.js, and full-stack builds.

LinkedIn Medium

Founder-built and actively maintained

About Tudor

Tudor builds IP Trackers at the intersection of product engineering and network diagnostics. His work turns public signals such as IP address, ASN owner, reverse DNS, resolver path, blacklist status, and browser leak behavior into workflows that users, developers, and support teams can follow.

He also reviews tool-result pages and technical guides for overclaiming. IP geolocation is not GPS, an ASN does not identify a person, and a VPN check is incomplete until DNS, WebRTC, and IPv6 behavior are considered. Those boundaries shape how IP Trackers explains every result.

Build the workflow

Start with a tool that answers a concrete network question and makes its inputs visible.

Test related signals

Compare IP, DNS, ASN, browser, and routing evidence before drawing a conclusion.

Explain the limits

Separate facts from estimates and tell readers what a result cannot prove.

Credentials

Designed and developed IP Trackers from scratch, including the Next.js frontend, API routes, diagnostic tool pages, and reusable UI systems
Builds and maintains the IP, ASN, DNS, WHOIS, blacklist, proxy, and VPN leak workflows used across the site
Owns the product experience, technical SEO, schema markup, performance tuning, and internal linking structure
Reviews tool outputs and supporting articles for technical consistency before publication
Tests diagnostic workflows across Windows, macOS, Linux, iOS, and Android

Areas of expertise

Frontend architectureReact and Next.js developmentTypeScript application developmentTechnical SEO and schema markupPerformance-focused UI engineeringIP geolocation accuracyDNS and reverse DNS diagnosticsVPN and proxy detection

Selected work

Tools and diagnostics Tudor maintains

Each workflow pairs a practical network question with the context needed to interpret the result responsibly.

Browse all tools

Live lookup

Public IP lookup

Shows the public IP, provider, location estimate, and routing context visible to the internet.

Open workflow Connectivity tool

Open port checker

Tests whether selected TCP ports on a public connection are reachable from outside the network.

Open workflow Network directory

ASN directory

Connects autonomous system numbers with network operators, announced ranges, and routing context.

Open workflow Diagnostic guide

DNS leak test guide

Explains resolver-aware checks and how VPN, browser, and system DNS paths can differ.

Open workflow

Also maintained

WebRTC leak test IPv6 leak test WHOIS and RDAP lookup Proxy and VPN check IP blacklist check

Review standard

Evidence first, limits included

A useful diagnostic page should show where a result comes from, which related signals support it, and where certainty ends.

Read the full methodology

01
Observe
Start with data the browser or public endpoint can actually see.
02
Cross-check
Compare related IP, DNS, ASN, routing, and leak-test signals.
03
Explain
Separate measured facts, estimates, and practical next steps.

Selected reading

Cornerstone technical guides

Deeper explanations for common routing, address, and ownership questions that appear in the tools.

Browse all guides

June 3, 20269 min read

CGNAT Port Forwarding Not Working? Fix It in 2026

Carrier-grade NAT prevents inbound connections before they reach your router. Check WAN vs public IP and fix it with public IPv4, IPv6, or a reverse tunnel.

Read guide