Security

Report a security problem

If you have found a vulnerability in DNS Super, tell us here. Reports sent with this form go to a private queue that only we read; they are never published, logged or forwarded by email.

What to report

Problems in DNS Super itself. Thank you for looking.

In scope

  • This website, including sign-in, the dashboard, shared reports and exports
  • The REST API and the MCP server
  • Our crawler, DNSSuperBot, and the headless browser behind rendered checks: anything that makes them reach a place they shouldn't
  • How we handle the data you send us: lookups, pasted headers, keys and account details

Out of scope

  • Findings about a domain you checked with our tools: those belong to that domain's owner
  • Denial of service, load testing or anything that degrades the service for others
  • Social engineering, phishing or physical attacks on anyone
  • Reports from automated scanners with no demonstrated impact
  • The services of other companies we use, which have their own programmes

Testing safely

  • Use your own account and your own data. Never open, change or delete anyone else's.
  • Stop as soon as you have shown the problem, and don't keep any data you saw.
  • Stay within the rate limits and free allowances; don't automate sign-ups or checks to get round them.
  • Give us a reasonable chance to fix a problem before you tell anyone else about it.

Send a report

The summary and details are all we need. Add a reply address only if you want us to be able to write back.

One line: what is affected and what an attacker could do. Up to 200 characters.

The steps to reproduce it, what you expected and what happened. Leave out passwords, keys and anyone else's personal data. Up to 4,000 characters.

Only if you want us to be able to write back. We use it for this report and nothing else.

We store the summary, the details and the reply address you give, and nothing else about you.