Explore All Our Tools
Everything here is built for quick answers and reliable checks. From simple IP lookups to deeper DNS diagnostics, email safety checks, and gaming network tests, each tool runs fast, works on mobile, and keeps your data private. Use them to troubleshoot issues, validate changes, or just learn more about how your connection works.
Categories at a Glance
- IP & Network: See your IP and estimated location, check ASN/ISP details, confirm IPv6 support, and map time zones or currency by IP.
- Webmaster & DNS: Inspect A/AAAA, MX, TXT, CNAME, and PTR records, convert hostnames and IPs, and run batch lookups during migrations or audits.
- Email & Security: Spot blacklist issues, verify SSL status, and validate SPF/DKIM so messages arrive and pass authentication checks.
- Gaming: Measure ping and packet loss, understand NAT type, and find quick wins to stabilize online play.
How Results Are Generated
Lookups are performed server-side using standard DNS resolvers and publicly available network data. We don’t rely on client-side scripts for core detection, and we don’t log personal queries. Where possible, we show raw values (like TTLs or resolver targets) so you can verify changes against your own infrastructure.
Accuracy & Limitations
- Geolocation: City/region is approximate and can be affected by VPNs, proxies, or carrier routing.
- DNS Propagation: Record updates may take time depending on TTL and caches; check again after changes.
- Blacklist & Cert Data: Third-party lists and certificate transparency feeds update on their own schedules.
- Latency Tests: Ping and loss vary by time of day, Wi-Fi quality, and ISP peering; run multiple samples.
Common Ways People Use These Tools
- Confirm a site’s DNS before and after a migration or CDN change.
- Debug email delivery by reviewing MX, SPF, DKIM, and reverse DNS.
- Check if a VPN or proxy is masking your real location.
- Benchmark gaming routes and identify packet loss or jitter.
- Audit basic security posture (SSL validity, DNS hygiene).
Quick Tips
- Enter a bare domain (e.g.,
example.com)—nohttp://or slashes. - If you want your real IP, temporarily disable VPN/proxy and refresh.
- For DNS changes, lower TTL before edits; raise it after things stabilize.
- Repeat latency tests at different times to spot peak-hour congestion.