Authorization & Abuse Policy
Draft v1.0 — Cedar Forge Consulting. Last updated: November 2026.
1. Why this page exists
Security scanning tools can be misused. Cedar Forge Scan is built so that misuse is structurally difficult: we scan verified, authorized targets only, and this page documents exactly what that means, how it is enforced technically, and how to report abuse.
2. Ownership verification (mandatory, no exceptions)
Before any scan can be requested, the account holder must prove control of the target's DNS by publishing a TXT record of the form cedarforge-verify=<one-time-token> at _cedarforge-verify.<domain> (or the domain apex). Our system resolves the domain's DNS and confirms the token match. A pending or failed verification blocks every scan tier, at every layer of our stack — the web API refuses, the job queue refuses, and the scan worker refuses independently.
3. Authorization attestation
For every scan, the requester must confirm: "I own or am expressly authorized to order security testing for this domain, and I accept the authorization & abuse policy." We store this attestation with the account, timestamp and target domain. If you are acting on behalf of an organisation, you must have actual authority to bind it.
4. Permanent blocklists
The following can never be scanned, regardless of verification:
- Government and military domains (any
.gov,.mil, or.gov.uk/.mil.uk/.inthostname). - Reserved and non-routable IP space: RFC 1918 private ranges, loopback, link-local, CGNAT, multicast, documentation and TEST-NET ranges, and their IPv6 equivalents.
- Any additional ranges we add to the operator blocklist over time.
Checks run against the resolved IP addresses of the target at request time and again when the scan job is claimed by the worker.
5. Rate and quota limits
- One free basic scan per verified domain per 30-day period.
- Deep scans consume prepaid credits — one credit per scan, debited atomically at request time.
- Global and per-account rate limits apply across signup, verification and scanning endpoints.
6. Egress transparency
All scanning traffic originates from our dedicated scan worker with publishable reverse DNS (scan-worker.cedarforgeconsulting.com) so that scanned parties can identify the source of legitimate, authorized scans.
7. Abuse reporting
If you believe a Cedar Forge Scan customer has scanned a system you own without authorization, contact abuse@cedarforgeconsulting.com with the target, timestamps and source IP. We treat every report as urgent: implicated accounts are suspended pending investigation, and we preserve attestation and verification records for that purpose. Note that a confirmed DNS TXT record for your domain means someone with DNS control requested the scan — check with your DNS administrators.
8. Consequences of violation
Attempting to circumvent verification, scanning without authorization, or probing our infrastructure results in immediate termination, forfeiture of credits, and — where a target reports unauthorized scanning — cooperation with law enforcement including disclosure of the recorded attestions.