Skip to content
Log inDashboard

Acceptable use policy

This policy is sections 3 and 4 of the terms of service; the rest of the terms apply too.

You may not use the service, directly or through software you run, to:

  1. Send attack traffic. No reflection or amplification attacks, query floods, spoofed-source traffic, or use of our resolvers as a component of a denial-of-service attack against anyone, including us.
  2. Resell or wrap the hosted service. You may not sell, sublicense or bundle access to opdns resolvers, or offer them as part of a paid product or managed service, without a written agreement with us. This includes pointing customers’ networks at your profiles and charging for it. Businesses using opdns for their own staff and devices are fine within plan limits.
  3. Evade lawful blocks that we are legally required to apply in your jurisdiction, for example by deliberately routing to another PoP.
  4. Break our systems. No probing, scanning or load testing beyond the rate limits without our written permission. The exception is research that follows our security policy.
  5. Break the law. No distribution of child sexual abuse material, malware command and control, phishing, or any other unlawful activity.
  6. Automate against the dashboard or API in ways that exceed published API rate limits or that impersonate other users.

We may rate-limit, block sources, suspend profiles or close accounts that break these rules (terms, section 7). Automated mitigation (rate limits, source blocks) may act before any human review.

4. The public resolver path and rate limits

Section titled “4. The public resolver path and rate limits”

Plain DNS sent to our IPv4 addresses from an address that is not linked to a profile is answered without filtering and without logging. Anyone may use it, under these terms and the following limits:

  • Every source address (IPv4 /32, IPv6 /64) has a per-second query budget. Current defaults, which may change without notice: 50 queries/s on plain DNS, 200 on encrypted transports, 500 for identified profiles, each with a burst of twice the rate. Over-limit UDP queries are dropped, and every second one is answered with a truncated response so a real client can retry over TCP.
  • UDP answers larger than 1232 bytes are truncated.
  • Sources that abuse the service may be blocked on every PoP at once. See our abuse desk process.
  • The public path has no account, no support entitlement and no filtering. We may change or withdraw it.

A query that names an unknown, deleted or malformed profile id is treated as carrying no profile: it is answered on the public path, unfiltered and not logged. Check that each device uses your profile’s exact address.