Fair Usage Policy

1. Why Usage Limits Exist

Usage limits help SiteSecura:

• Maintain infrastructure stability and avoid network congestion;
• Prevent automated abuse, scraping, and denial-of-service traffic;
• Protect shared scanning workers and task execution queues;
• Reduce excessive resource consumption on third-party target hosts;
• Protect other customers from noisy-neighbor resource exhaustion;
• Maintain reasonable and consistent service availability; and
• Enforce subscription-plan entitlements fairly.

Limits apply to scans, registered websites, monitored domains, API requests, report exports, AI-assisted explanations, team member seats, and historical data storage.

2. Plan-Based Usage Limits

Account resource limits are determined authoritatively by your active subscription plan. The current production quota matrix is outlined below:

Plan scan quotas reset automatically at the beginning of each calendar month (00:00 UTC). Unused scan allowances do not roll over to subsequent months.

3. Anonymous Public Usage

Unauthenticated visitors using the homepage scanner are subject to automated safeguards to prevent proxy abuse:

• IP-Based Daily Limits: A maximum of 3 free scans per 24-hour window per client IP;
• Minimum Scan Intervals: Cooldown periods between consecutive requests to the same target domain;
• Automated Abuse Detection: Rapid sequential requests from the same network subnet will trigger temporary rate limits; and
• Public Scan Mode: Scans run without permanent account history association.

Anonymous usage thresholds may be calibrated dynamically based on real-time infrastructure capacity and global threat activity.

4. Technical Rate Limiting

SiteSecura implements layered rate limiting across public entry points, authenticated APIs, and task dispatcher queues. Technical controls include:

• Burst Rate Limiting: A maximum of 20 scan requests per minute for authenticated users;
• API Concurrency Protections: Limits on simultaneous long-running Deep Scans to maintain worker queue health;
• Report Generation Caps: Throttles on rapid bulk PDF generation to prevent worker exhaustion; and
• AI Feature Rate Limits: Up to 20 AI Security Advisor requests per minute per user.

When a rate limit is exceeded, the server returns an HTTP 429 Too Many Requests status code with a Retry-After indicator. Users and automated clients must honor rate-limit headers.

5. Prohibited Usage

You must not use SiteSecura to:

• Conduct scans against domains you do not own or lack verifiable authorization to assess;
• Conduct broad, untargeted, or Internet-wide automated reconnaissance;
• Automate excessive scan submissions using headless bots, scrapers, or scripts;
• Circumvent plan scan quotas or rate-limit thresholds;
• Register multiple free accounts or use burner email addresses to bypass subscription limits;
• Rotate proxy IP addresses or spoof user agents to evade abuse controls;
• Use SiteSecura as an intermediary proxy for scanning private networks or cloud metadata;
• Deliberately trigger resource exhaustion or denial-of-service conditions; or
• Exploit platform implementation nuances to obtain unentitled feature access.

Violations of these prohibitions may lead to immediate IP blacklisting and account termination. For full guidelines, review our Authorized Scanning Policy.

6. Fair Resource Use

SiteSecura monitors aggregate resource consumption to identify anomalous or abusive activity. We reserve the right to apply temporary restrictions where reasonably necessary to protect platform integrity. Temporary restrictions may include request throttling, temporary scan delays, or temporary account locks pending review.

Where reasonably practicable, legitimate customers will receive in-app alerts or email notifications if unusual patterns trigger temporary restrictions.

7. API and Automation

Where API access is provided, API usage is subject to the applicable plan limits, documentation, and authentication requirements. Automated scripts and CI/CD pipelines must:

• Implement exponential backoff when handling HTTP 429 or 503 responses;
• Include appropriate user-agent identifiers; and
• Never use the API to circumvent account-level or website-level plan restrictions.

8. Excessive Usage Reviews

SiteSecura may review accounts generating unusually high operational overhead. High resource consumption does not automatically imply malicious intent; we evaluate:

• Request volume and scan scheduling intervals;
• Concurrent scan concurrency against single target hosts;
• High error rates or repeated scans against unreachable targets; and
• Impact on shared system queues and downstream network bandwidth.

Where appropriate, our technical support team will contact the customer to explore plan adjustments or scheduling optimizations before taking restrictive measures, unless immediate action is necessary to protect the platform.

9. Changes to Limits

SiteSecura may adjust usage allowances, rate limits, and plan features as our infrastructure expands, security requirements adapt, and scanner capabilities evolve.

Where a modification materially affects an active paid subscription, advance notice will be communicated in accordance with our Terms of Service.

10. Inquiries and Contact

If you have questions regarding plan allowances, quota increases, or fair usage policies: