2. Monitoring targets
Monitoring is intended for normal availability, response, certificate, registration, and related diagnostic checks against public HTTP or HTTPS endpoints. You may not use the Service to discover, map, enumerate, scan, exploit, or gain access to systems.
- Do not target private, local, link-local, metadata, loopback, reserved, internal-only, or otherwise restricted network resources.
- Do not use redirects, DNS changes, encoded addresses, custom headers, or credentials to evade target controls.
- Stop or adjust monitoring if a target owner withdraws permission or the checks cause harm.
- Comply with target rules, allowlists, rate limits, and applicable law.
3. Requests, content, and credentials
Custom headers and Basic Authentication must use dedicated, least-privilege credentials. Do not submit complete payment information, government identifiers, health information, highly sensitive personal information, destructive commands, malware, or secrets in fields not designed for encrypted credentials.
Accepted status codes and content markers must be used to assess a response you are authorized to receive, not to bypass access controls or conceal unauthorized activity.
4. Alerts and communications
Alert destinations must belong to you or a recipient who has agreed to receive the messages. Do not use email, SMS, webhooks, tests, or integrations for spam, marketing, harassment, fraud, emergency messaging, bulk messaging, or message amplification. Honour opt-outs promptly and do not repeatedly re-add a destination that opted out.
5. Public status pages and custom domains
Do not impersonate another organization, imply false endorsement, reserve a misleading slug, publish confidential data, misrepresent status, use deceptive analytics, or upload material that infringes intellectual property or privacy rights. Ownership verification does not transfer trademark, copyright, domain, or other rights.
6. APIs, tokens, webhooks, and automation
Keep tokens confidential, use only the scopes required, rotate suspected credentials, validate webhook signatures, and respect documented limits. Do not share an account to avoid plan limits, resell access without written permission, scrape customer data, bypass user interfaces or protections, or create recursive or high-volume automation that threatens reliability or cost.
7. Prohibited conduct
- Illegal, fraudulent, deceptive, infringing, abusive, harassing, or privacy-invasive activity.
- Phishing, malware, credential attacks, vulnerability exploitation, port scanning, denial of service, stress testing, or security testing without written authorization.
- Interference with another tenant, service provider, target, recipient, or StackResolve system.
- Reverse engineering or circumvention except to the limited extent a restriction is prohibited by law.
- Automated account, trial, monitor, verification, alert, status-page, or integration creation intended to evade controls.
- Use by or for a sanctioned party or prohibited jurisdiction where that use would violate applicable trade laws.
- Collection or publication of personal data without a lawful purpose, required notice, and appropriate authority.
8. Fair use and capacity protection
Published plan limits are maximum entitlements, not permission to generate abusive or harmful traffic. We may use reasonable technical limits for request frequency, timeout, redirect count, retries, response size, diagnostics, SMS segments, email, API calls, exports, retention, or concurrent work. We may temporarily slow, defer, suppress, or pause activity that creates unusual risk, cost, failure loops, or platform instability.
9. Enforcement
Depending on severity and urgency, StackResolve may warn you, require verification or remediation, remove content, restrict a destination or target, reduce traffic, revoke tokens, disable a feature or monitor, suspend an account, preserve evidence, report unlawful conduct, or terminate access. Immediate action may be taken to protect people, systems, data, legal rights, or Service availability.
Where appropriate, we will provide notice and a reasonable opportunity to correct the issue. You may contact support if you believe an action was mistaken.
10. Reporting abuse
Report suspected misuse to legal@uptimebasics.com. Include the relevant URL, monitor or status-page identifier, dates, explanation, supporting evidence, and a reliable contact method. Security vulnerabilities should follow the Vulnerability Disclosure Policy.