Get help protecting your websites.
Whether you are onboarding a domain, troubleshooting DNS, reviewing traffic or responding to an attack, DNS Protector support is here to help.
Talk to our support team
Email [email protected] or use the contact form. Include your domain, a short description of the issue and the approximate time the problem started. Do not send passwords, private keys or API tokens.
My website stopped loading after changing nameservers.
Check that the required DNS records were recreated correctly, the domain is using ns1.ddos-guard.xyz and ns2.ddos-guard.xyz, and the origin server is reachable.
How do I protect my origin IP?
Configure the protected edge path first, then restrict direct origin access with firewall rules. Avoid publishing the origin IP unnecessarily.
When should I enable Shield Mode?
Use it when abnormal automated traffic or an active attack is creating unacceptable load. It adds visitor verification and can increase friction for legitimate users.
Can I manage DNS records myself?
Yes. The platform is designed to give customers centralized control over common DNS records and domain configuration.
How does automatic SSL fit into onboarding?
After DNS and edge routing are correctly configured, SSL automation can make HTTPS provisioning and renewal part of the normal protected-domain lifecycle.
Can I automate the platform?
See the API page for the integration model.