Acceptable Use Policy

Because PingShift fetches URLs and connects to hosts you specify, this policy is critical — it protects you, us, and third parties. It is part of our Terms of Service.

The core rule

You may only monitor assets you own or are explicitly authorized to monitor. If you don't control the target and don't have permission from whoever does, you may not point PingShift at it.

Specifically prohibited

• Using checks to attack, probe, scan, or stress-test systems you don't control — including using short intervals as a crude load or denial-of-service tool.
• Monitoring targets to harvest data, bypass access controls, or circumvent another party's terms of service.
• Pointing checks at private, internal, or reserved network addresses, cloud metadata endpoints, or other infrastructure you are not authorized to reach. (We also block these technically.)
• Monitoring illegal content or services, or anything that violates law.
• Using status pages or alerts to harass, deceive, or distribute malware or unlawful content.
• Attempting to break, overload, or reverse-engineer PingShift itself.

Technical safeguards

PingShift independently validates every target: we resolve DNS and refuse private/reserved IP ranges and cloud metadata addresses, re-validate on each check and on every redirect hop, and cap how many monitors a single account can point at one host. These safeguards reduce abuse but do not replace your responsibility under this policy.

Enforcement

We may pause or remove offending monitors and suspend or terminate accounts that violate this policy, without notice where ongoing abuse threatens others. Report suspected abuse to abuse@pingshift.app.