Tool
Link Health
See where a link really goes — and why it might be failing.
Best for
- Broken links, unexpected redirects, “too many redirects”
- Tracking down the final destination URL
- Validating a campaign link before sharing
What we check
- Redirect hops (each step + status code)
- Final status (200/301/404/etc.) and final URL
- Basic timing and request method used
You can type
example.com. We’ll assume https:// by default. If you enter http://, we’ll use it as-is.Next
Related tools
Common follow-ups that help narrow the root cause.
Headers Check
Audit security/caching headers with clear explain + fix links.
Open →
DNS Check
Resolve common DNS records and spot setup issues fast.
Open →
QR Studio
Create QR codes + optional short /go links for sharing.
Open →
Tip: If a provider’s status is green but your app is failing, it’s often DNS, TLS, redirects, or headers. Browse Status Pages.
What does “hop” mean?
A hop is one step in a redirect chain.
Each hop shows the URL, the status code, and the Location header (if present).
What does “too many redirects” usually mean?
It usually means a loop (A → B → A) or a misconfigured HTTP→HTTPS / www / trailing-slash policy.
Fixing it typically means making one canonical redirect path and removing conflicting rules.
Why do you use HEAD or GET?
HEAD is faster and cheaper, but some servers handle it incorrectly.
If HEAD fails or looks suspicious, the checker may fall back to GET for accuracy.
Tip the project ☕
If this helped, send a small SOL tip to support Pathping.
Powered by Solana Actions (Blink)
Opens a Blink with your amount.