Reporting abuse
opdns runs recursive DNS resolvers. We host no content: no websites, no email and no customer servers live on our addresses. Most reports about our addresses fall into one of these groups, and all of them go to the same place.
Write to [email protected] ([email protected] reaches the same desk).
Our addresses are 23.166.164.53, 23.166.164.35, 2602:81f:6000::53 and
2602:81f:6000::35, in the prefixes 23.166.164.0/24 and 2602:81f:6000::/48
announced by AS403104 (Our network). The
public registries list Opero’s network desk, [email protected], for these
prefixes; reports sent there reach the same people.
| You are reporting | What we do |
|---|---|
| Our resolvers used in a reflection or amplification attack against you | look at our rate-limit counters for the period, limit the affected prefix on every resolver, and answer with what we found |
| An open-resolver notice from a scanner | explain the policy below; act if the notice shows abuse |
| A client abusing our service (floods, scraping) | limit or block the source on every resolver |
| A malicious domain (phishing, malware) | review it for our security lists, and tell you who hosts it, since we do not |
| A domain we block by mistake | review the list entry; if you use opdns, you can also report it from your logs |
| Spam, phishing or content “hosted on” our address | explain that a resolver only answered a lookup, and point you to the host and registrar |
Not for this address: vulnerabilities go to [email protected] under the
security policy; data-protection requests to
[email protected]; court orders and law-enforcement requests to
[email protected] (guidelines); help with your
account to [email protected] (support).
What to include
Section titled “What to include”- the address of ours you saw, and yours (or the prefix that was hit);
- times, with the time zone, of the start and end of what you saw;
- for attacks: packet samples or flow records (source port 53 and our address), and the query names if you have them;
- for domains: the full name, and why you believe it is malicious or wrongly blocked.
We do not keep per-query records of unidentified traffic (the public resolver path), so for attacks the evidence is our aggregate counters and what you send.
How fast we answer
Section titled “How fast we answer”opdns is run by a small team, so the targets are best effort, on business days, Eastern time. Automatic protections cover the hours nobody is at the desk: every resolver limits the query rate per source and caps the size of answers over UDP, which bounds what an attacker can reflect through us.
| Report | Acknowledged | Acted on |
|---|---|---|
| Active amplification or flood involving our addresses | within 24 hours (an automatic reply at once) | within 4 hours while the desk is staffed, otherwise the next morning |
| Open-resolver notice | within 24 hours | answered with this policy; action only on evidence of abuse |
| Malicious domain | within 24 hours | reviewed within 5 business days |
| Domain we block by mistake | within 24 hours | reviewed within 2 business days |
| Legal notice | within 2 business days | per the law-enforcement guidelines and the operator-block policy |
Why our resolvers answer everyone
Section titled “Why our resolvers answer everyone”Like other public resolvers, opdns answers DNS from anyone on its shared addresses, unfiltered unless the query identifies a profile. That is intentional, so open-resolver notices about our addresses are expected. If you run a scanner, please exclude our prefixes from open-resolver notifications, or write to us with the evidence of abuse you see.
When opdns blocks a name for everyone, the operator-block policy applies, and the block is counted in our transparency report. The other legal documents are listed under Policies.