1. Purpose
ShieldNS runs infrastructure that many organisations rely on. To keep it safe and reliable for everyone, every customer must use the Services lawfully and responsibly. This policy applies to all accounts, zones, domains and certificates on ShieldNS, and to anyone who uses them, including your own users.
2. Prohibited uses
You must not use the Services, or allow them to be used, to:
- carry out or support phishing, pharming or the impersonation of any person, brand or organisation;
- distribute malware, operate botnet command-and-control servers, or point to sites that do;
- send or support unsolicited bulk email, or host domains advertised through it;
- commit fraud, sell counterfeit goods, or run scams;
- publish or point to child sexual abuse material, which we report to the relevant authorities;
- infringe copyright, trademarks or other intellectual property rights;
- promote terrorism or violence, or incite hatred against people because of protected characteristics;
- violate sanctions or export controls, or any other applicable law.
3. Network and DNS abuse
You must not use the Services to harm networks or systems, including:
- launching or helping to launch denial-of-service attacks, including DNS amplification and reflection;
- using fast-flux techniques, domain generation algorithms or similar methods to hide malicious infrastructure;
- scanning, probing or attempting unauthorised access to systems you do not own or have permission to test;
- tunnelling data through DNS to bypass security controls, other than for your own authorised testing;
- interfering with the Services or other customers, for example by deliberately sending query floods to your own zones;
- circumventing plan limits, rate limits or security measures, or creating accounts in bulk.
4. Content monitoring
We are an infrastructure provider: we answer DNS queries and register names, and we do not host the websites or email that your records point to. We do not proactively monitor what customers publish. We act when abuse is reported to us or detected by our security systems, and we review every report we receive.
Where content is hosted elsewhere, the hosting provider is usually best placed to remove it, and we may forward reports to them as well as to you.
5. Reporting abuse
Report abuse to abuse@shieldns.com. To help us act quickly, include:
- the domain or hostname involved;
- what the abuse is, with evidence such as URLs, email headers, logs or screenshots;
- the date and time you observed it, with the time zone;
- your contact details, if you would like an update.
Report security vulnerabilities in ShieldNS itself to security@shieldns.com. For intellectual property complaints, include proof that you own the rights, or are authorised to act for the owner.
6. How we handle reports
- Acknowledge. We acknowledge reports, usually within one business day.
- Investigate. We check the evidence and the domain's configuration.
- Notify. We tell the customer what was reported and give them a reasonable time to respond and fix it, normally 48 hours.
- Act. If the abuse continues or the customer does not respond, we may disable records, suspend the zone, lock or suspend the domain, revoke certificates, or suspend the account.
For serious or ongoing harm, such as active phishing, malware or attacks, we may act immediately and notify the customer afterwards. Registries, certificate authorities and authorities may also require us to act within fixed deadlines.
7. Law enforcement
We cooperate with valid requests from courts and law enforcement, and we report illegal content where the law requires it. Our approach to disclosing customer data is described in our Privacy policy.
8. Consequences
Breaking this policy is a breach of our Terms of service. Depending on how serious it is, we may warn you, suspend part or all of the Services, or terminate your account. We do not refund fees for Services suspended or terminated because of a breach of this policy.
9. Changes
We may update this policy as threats and laws change. The current version is always on this page.