IP Fetch Guide
Verify your visible IP, geolocation, and Tor exit status from multiple independent sources. This guide walks verification scenarios; the CLI catalog holds every flag.
Documentation Navigation
This page is scenario-first (operational workflows, real run order, and troubleshooting). For the full autogenerated command/flag catalog, use the CLI Reference.
File Information
| Property | Value |
|---|---|
| Binary Name | ip-fetch |
| Version | 10.0.3 (build 11) |
| Build Date | Not disclosed |
| Rust Version | 1.82.0 |
| File Size | 4.5MB |
| Author | Warith Al Maawali |
| License | Proprietary |
| Category | Network & Routing |
| Description | IP Geolocation data fetcher for Kodachi OS - Fetches and displays IP address information including g... |
| JSON Data | View Raw JSON |
SHA256 Checksum
Key Features
IP Detection & Geolocation
| Feature | Description |
|---|---|
| Multi-Source Fallback | Automatically switches between multiple IP services if one fails |
| Dual Stack Support | Full IPv4 and IPv6 address detection and geolocation |
| Smart Caching | Reduces network requests while maintaining fresh data |
| Tor Verification | Confirms if your traffic is properly routed through Tor |
Why IP Fetch is Essential
| Use Case | Description |
|---|---|
| Anonymity Verification | Quickly check if your real IP is hidden |
| Network Monitoring | Track IP changes when switching between VPN/Tor |
| Authentication Gateway | Verifies Kodachi service authentication status |
| Offline Capability | Works even without internet using cached data |
TL;DR - Essential Commands
# Get your current IP with full geolocation data
ip-fetch fetch
# or simply
ip-fetch
# Get just your IP address (plain text for scripts)
ip-fetch plain-ip
# Check if your connection is using Tor
ip-fetch check-tor
# Cross-verify across multiple providers
ip-fetch verify-multi --ipv4
# Force refresh cache and get latest IP data
ip-fetch --refresh-cache
# JSON outputs
ip-fetch --json
ip-fetch --json-pretty
ip-fetch --json-human
ip-fetch --ipv4
ip-fetch --ipv6
ip-fetch --both
# DNS-based IP resolution
ip-fetch dns --ipv4
# Get plain text IPv4 address
ip-fetch plain-ip --ipv4
# Test geolocation APIs
ip-fetch geo
Understanding IP Fallback System
How Multi-Source Fallback Works
IP Fetch uses an intelligent fallback system that ensures you always get IP information:
# Primary lookup with automatic fallback
ip-fetch fetch
# Test all fallback sources
ip-fetch test-fallback --ipv4
# Verify multiple sources match
ip-fetch verify-multi
Fallback Chain:
| Priority | Source | Description |
|---|---|---|
| 1 | Kodachi Cloud | Primary - Fastest, most reliable |
| 2 | Secondary APIs | Multiple backup services |
| 3 | DNS Resolution | Uses DNS queries for IP detection |
| 4 | Cached Data | Last resort using stored information |
Tor Network Verification
# Check if connection is using Tor and show IP
ip-fetch check-tor
# Get just the IP address
ip-fetch check-tor --ip-only
# Get just the Tor status
ip-fetch check-tor --status-only # Tor status without printing IP
# Get Tor status and IP in JSON format
ip-fetch check-tor --json
# Pretty-printed JSON output
ip-fetch check-tor --json-pretty
# Colorized JSON output (like jq)
ip-fetch check-tor --json-human
Caching System
Cache Warning
Cache data may not reflect IP changes when switching VPN/Tor connections. Always use --refresh-cache after connecting to VPN/Tor to get accurate current IP information.
Random Server Selection Testing
Use this command to verify random server selection is working correctly across the available IP lookup providers.
Advanced Commands
For advanced users who need access to all available commands and options, please refer to the auto-generated command reference which includes:
| Feature | Description |
|---|---|
| Bulk Operations | Bulk IP lookup operations |
| DNS Resolution | DNS-based IP resolution |
| Server Testing | Random server selection testing |
| Cache Management | Cache management commands |
| Custom Config | Custom server configuration |
| IPv6 Operations | IPv6-specific operations |
| JSON Formatting | JSON output formatting options |
| CLI Reference | All command-line flags and parameters |
Related Tools
IP Fetch works with other Kodachi tools to report route state and help detect common exposure conditions; no toolset guarantees complete privacy:
| Tool | Integration |
|---|---|
| Tor Switch | Use ip-fetch check-tor to verify Tor connectivity after enabling torrification |
| DNS Leak | Combine with DNS leak testing for egress identity and leak-check verification |
| Routing Switch | Verify IP changes after VPN/proxy connections |
| Online Auth | Authentication required for enhanced geolocation features |
Security Notes
Important Security Practices:
| Practice | Description |
|---|---|
| IP Verification | Always verify IP changes after connecting to VPN/Tor using ip-fetch check-tor |
| Comprehensive Testing | Use test-all command to run comprehensive functionality tests |
| Auth Check | Ensure authentication via online-auth authenticate --keep-alive before using other Kodachi services |
| Quick Tor Check | Use ip-fetch check-tor --status-only to quickly verify Tor connectivity |
| Cache Management | Use ip-fetch cache or --refresh-cache if concerned about data persistence |
| Privacy Mode | Use --nohistory flag to prevent saving lookup results to history |
Performance
| Metric | Value | Description |
|---|---|---|
| Lookup Time | < 2 seconds | Typical response time |
| Memory Usage | ~20MB active, < 5MB idle | Resource consumption |
| CPU Usage | < 5% active, 0% idle | Processing overhead |
| Cache Duration | 5 minutes | Default cache lifetime |
| Network Traffic | < 5KB | Per lookup bandwidth |
Support
| Resource | Link |
|---|---|
| Website | digi77.com |
| Anonymity Verifier | kodachi.cloud |
| Discord Support | discord.gg/KEFErEx |
| GitHub | github.com/WMAL |
Scenario 1: Pre-VPN IP Baseline Documentation
Document your real IP before connecting to VPN/Tor for comparison and verification.
# Step 1: Get baseline IPv4 with full geolocation
ip-fetch --ipv4
# Expected: Your real IP with ISP, country, city details
# Step 2: Save IPv6 baseline if available
ip-fetch --ipv6 --json-pretty > baseline-ipv6.json
# Step 3: Get both IP stacks for complete baseline
ip-fetch --both --json > baseline-both.json
# Step 4: Connect to VPN
sudo routing-switch connect wireguard
# Step 5: Verify IP changed after VPN connection
ip-fetch --refresh-cache
# Expected: New IP, different country/ISP than baseline
# Step 6: Compare with baseline
ip-fetch --ipv4 --json
Cross-binary workflow: ip-fetch + routing-switch
When to run: Before every VPN/Tor connection to record baseline and routed IP signals. This verifies observed routing, not anonymity as a whole. Or Automate this with workflow-manager.
Scenario 2: Multi-Source IP Verification for Consistency
Verify your IP address across multiple services to ensure consistency and detect issues.
# Step 1: Test all IPv4 sources for consistency
ip-fetch verify-multi --ipv4
# Expected: All sources should return same IP
# Step 2: Test IPv6 multi-source verification
ip-fetch verify-multi --ipv6 --json-pretty
# Expected: Consistent IPv6 across all providers
# Step 3: Test fallback mechanism
ip-fetch test-fallback --ipv4 json
# Step 4: Test plain text fallback sources
ip-fetch test-fallback --ipv4 plain
# Step 5: Verify Tor routing if enabled
sudo tor-switch tor-status-all
# Step 6: Check if sources agree on Tor status
ip-fetch check-tor --json
Cross-binary workflow: ip-fetch + tor-switch
When to run: When suspicious of IP spoofing or inconsistent geolocation data.
Scenario 3: Tor Network Connectivity Verification (SOCKS5)
Test IP lookup through Tor SOCKS5 proxy to verify Tor network connectivity.
# Step 1: Get current IP without Tor
ip-fetch --ipv4
# Step 2: Test single random IPv4 source through Tor SOCKS5
ip-fetch tor --ipv4
# Expected: Different IP than step 1
# Step 3: Test ALL IPv4 sources through Tor SOCKS5
ip-fetch tor --ipv4 all
# Expected: All sources return Tor exit node IPs
# Step 4: Verify Tor status and get IP
ip-fetch check-tor
# Expected: IsTor: true + Tor exit IP
# Step 5: Test custom Tor port (if using non-default)
ip-fetch tor --ipv4 --socks-port 9150
# Step 6: Verify Tor daemon status
sudo tor-switch tor-status-all
# Step 7: Run DNS leak test to ensure DNS not leaking
sudo dns-leak test
# Step 8: Comprehensive test including Tor
ip-fetch test-all --include-tor --json-pretty
Cross-binary workflow: ip-fetch + tor-switch + dns-leak
When to run: After enabling Tor routing to verify Tor-facing IPs, Tor status, and DNS leak results. These checks do not prove complete anonymity.
Scenario 4: Bulk IP Geolocation for Network Analysis
Analyze multiple IP addresses efficiently using bulk lookup mode.
# Step 1: Bulk lookup of common DNS servers
ip-fetch --bulk 8.8.8.8 1.1.1.1 9.9.9.9 208.67.222.222
# Expected: Geolocation data for all IPs
# Step 2: Get JSON output for analysis
ip-fetch --bulk 8.8.8.8 1.1.1.1 9.9.9.9 --json > dns-servers.json
# Step 3: Test specific geolocation API
ip-fetch geo --ip 8.8.8.8
# Step 4: Bulk lookup without saving to history
ip-fetch --bulk --nohistory 1.1.1.1 9.9.9.9 8.8.8.8
# Step 5: Individual lookups (disable bulk mode)
ip-fetch --nobulk 1.1.1.1 9.9.9.9
# Step 6: Check network security score
sudo health-control security-score
Cross-binary workflow: ip-fetch + health-control
When to run: For network reconnaissance, VPN server selection, or DNS server analysis.
Scenario 5: Comprehensive IP/Tor/DNS Diagnostic Suite
Complete network diagnostic workflow combining IP, Tor, and DNS verification.
# Step 1: Run comprehensive test suite
ip-fetch test-all --json-pretty > diagnostics-full.json
# Step 2: Check network connectivity
sudo health-control net-check
# Step 3: Verify Tor status and IP
ip-fetch check-tor --json-pretty
# Step 4: Test Tor SOCKS5 connectivity
ip-fetch tor --ipv4 all
# Step 5: Run DNS leak detection
sudo dns-leak test
# Expected: DNS queries should match VPN/Tor location
# Step 6: Verify multi-source IP consistency
ip-fetch verify-multi --ipv4
# Step 7: Check Tor daemon status
sudo tor-switch tor-status-all
# Step 8: Verify DNS configuration
sudo dns-switch status
Cross-binary workflow: ip-fetch + dns-leak + tor-switch
When to run: For egress identity and leak-check verification or troublesho