← All tools01 / NETWORK DIAGNOSTICS

URL / IP
Checker.

Find the address. Test the connection. Follow the route.
A little clarity for the moments when “it’s not working” isn’t enough.

View source on GitHub ↗

KNOW YOUR VANTAGE POINT

A second
point of view.

These checks run from remote servers, not your device. DNS, TCP, HTTP, and TLS use Northern Virginia. Ping and traceroute show the selected US probe’s location.

A timeout does not always mean a host is down. Firewalls can block ping or hide traceroute hops while a website works normally.

Fair-use limits

20 checks per network per hour, at least 10 seconds apart. Ping and traceroute share a stricter allowance: 5 per network per hour and a 30-second cooldown.

Site-wide: 1,000 checks per UTC day. Ping and traceroute share 100 per hour and 200 per UTC day. Failed checks can count toward these limits.

What is checked?

One validated public IP per check. HTTP sends a HEAD request to the root and does not follow redirects. TLS checks port 443, even for an HTTP target. Overview does not run ping or traceroute.

Use this for systems you own or have permission to test. No port scanning, private-network access, or continuous monitoring.

URL / IPChecker.

Check results

URL / IP
Checker.