Skip to content

Legal

Acceptable Use Policy

Rules for using SipRadar threat intelligence, API, honeypot feeds, and PBX scanner.

Last updated: 15 July 2026

Overview

This Acceptable Use Policy (AUP) supplements our Terms of Service. It defines permitted and prohibited uses of the SipRadar platform. Violations may result in suspension or termination without refund.

Permitted use

You may use SipRadar to:

  • Protect SIP and VoIP infrastructure you own or are authorized to manage.
  • Integrate threat feeds and IP reputation into firewalls, Fail2Ban, Kamailio, Asterisk ACLs, and SOC workflows.
  • Run PBX security audits against endpoints you have verified ownership of.
  • Research attack patterns using Community tier data within plan limits.
  • Provide managed security services to your customers on Active Defense or Enterprise plans within IP limits.

PBX scan requirements

On-demand and automated PBX scans are remote tests against public SIP interfaces. You must complete ownership verification (DNS TXT record or signed SIP OPTIONS probe) before scanning.

Scanning third-party systems without authorization is strictly prohibited and may violate computer misuse laws.

API and automation abuse

The following are prohibited:

  • Exceeding rate limits or circumventing plan restrictions (e.g. creating multiple free accounts to avoid paid tiers).
  • Reselling raw API output as a competing threat feed without Enterprise agreement.
  • Bulk scraping the website or API outside documented endpoints.
  • Using the Service to build competitive honeypot networks without authorization.

Honeypot and feed integrity

Do not attempt to poison, flood, or manipulate honeypot telemetry to artificially inflate or deflate reputation scores.

Do not use Community tier delayed feeds for real-time automated blocking while representing them as live protection to end customers.

Do not interfere with honeypot sensors or scanner infrastructure.

Crowdsourced scam reports

The Report a VoIP Scam form is for good-faith submissions from operators who received fraudulent SIP traffic or calls on infrastructure they manage.

False, defamatory, or malicious reports are prohibited. Do not submit competitor numbers, personal grudges, or unverified third-party claims without evidence.

SipRadar moderates all reports before publication. Approved entities appear on public scam profile pages; pending or rejected reports are not disclosed.

By submitting a report you confirm accuracy to the best of your knowledge and grant SipRadar permission to process attached SIP logs for fraud prevention and compliance workflows.

Network and content restrictions

You may not use SipRadar to:

  • Launch attacks against any network or system.
  • Distribute malware, spam, or illegal content via webhooks or integrations.
  • Harass, threaten, or violate the privacy of individuals.
  • Violate export control, sanctions, or applicable telecommunications regulations.

Account security

Keep API keys confidential. Do not embed keys in client-side code or public repositories. Rotate keys if compromise is suspected.

You are responsible for actions taken with your credentials, including by integrations you configure.

Enforcement

We may investigate suspected violations, throttle or block API access, remove content, and terminate accounts. We may report illegal activity to authorities.

Enterprise customers will be contacted before suspension where feasible, except for severe abuse or legal obligation.

Reporting abuse

Report abuse of SipRadar services by third parties to support@sipradar.net. Include relevant IPs, timestamps, and API keys if applicable.

Updates

We may update this AUP. Continued use after changes constitutes acceptance. Material changes will be communicated via email or in-product notice.

This document is provided for informational purposes and does not constitute legal advice. For legal inquiries, contact legal@sipradar.net.

Related policies