Security
Security and responsible crawling
TierPing fetches other people's websites on your behalf, so it has to be careful in both directions: with your account and with the sites it reads.
Your account
- Accounts store an email address, the name given at sign-up, an account ID and plan status; no company details.
- Your monitored pages and history are visible only to you (row-level security).
- All writes go through server-side checks of ownership and plan limits.
- API keys for third-party services live only on the server.
Fetching safely
- Private, internal and link-local addresses are blocked (SSRF protection), including after DNS resolution and on every redirect.
- robots.txt is respected.
- One page per check; links are never followed.
- No logins, CAPTCHA solving, residential proxies or stealth browsing.
Abuse and cost controls
Manual checks, the public checker and account actions are rate limited, each fetch has a hard cost cap, and an administrator can pause all checks globally.
Payments
Paid plans are handled by Razorpay. Card details are entered in Razorpay checkout and are never stored by TierPing; paid limits switch on only after Razorpay confirms payment to our server.
Frequently asked questions
- How does Tier Ping stop requests to private networks?
- Private, internal and link-local addresses are blocked, including after DNS resolution and on every redirect.
- Who can see my monitored pages?
- Only you. Monitored pages and history are protected by row-level security, and all changes go through server-side ownership and plan checks.
- Are there limits to prevent abuse?
- Yes. Manual checks, the public checker and account actions are rate limited, each fetch has a cost cap, and an administrator can pause all checks.
Start on the free Starter pilot: 1 monitored page, 5 checks, 5 alert emails.
Start Free