Skip to main content

​
1. Required Information

So Aegister can create your organization and activate the service, provide the following details:
  • Organization details: legal name and industry.
  • Primary contacts: names and email addresses of technical and administrative contacts.
  • Domain (FQDN): the full domain name of your site (e.g., www.example.com).
  • Endpoint: the public address (IP or URL) where your web application is hosted.
  • Technical contact email: for notifications and technical communications.
  • Requested services: the services to activate (e.g., Caching, DDoS, Threat Intelligence, WAF).

​
2. DNS Update

Once Aegister configures Cloud Defender, update your domain’s DNS records:
  1. Access the DNS control panel:
    Log in to the DNS provider or hosting control panel where you manage your domain records.
  2. Point the domain to Cloud Defender:
    Replace the record for the web application with a CNAME pointing to secure.aegister.com (at the root of a domain, where a CNAME is not allowed, use your provider’s ALIAS or ANAME record).
  3. Confirmation and propagation:
    Save your changes and wait for DNS propagation, which takes 1 to 24 hours depending on your provider.

​
3. Final Verification

After DNS propagation, run these tests to confirm that Aegister Cloud Defender protects your site:
  • Browsing test:
    Visit your domain (e.g., www.example.com) to verify that the site loads correctly.
  • Traffic monitoring:
    Open the Cloud Defender page in the Cyber Console: it shows the traffic handled, the requests blocked and the detail of every single block: time, source, request and the layer that stopped it.

​
4. Lock the Origin (essential step)

Once you have confirmed the site responds correctly through Cloud Defender, configure your origin firewall, or an application level rule, to accept traffic only from Cloud Defender. Without this step the site stays reachable directly at its public IP address: anyone who knows it bypasses the whole protection, because the WAF, Threat Intelligence, DDoS mitigation and caching are all skipped. This is the step that makes the protection effective, not a later optimisation.
  1. Allow the Cloud Defender addresses: Aegister gives you the addresses to allow when your domain is activated.
  2. Deny all other inbound traffic on ports 80 and 443.
  3. Where to apply it: perimeter firewall, cloud provider security group, or a web server rule (for example allow / deny in Apache or Nginx).
Apply the rule only after verifying the site works through Cloud Defender. Enabling it before DNS has propagated will block legitimate traffic too.
If you need to keep direct access for maintenance, explicitly allow the addresses you connect from alongside the Cloud Defender addresses.

​
5. Support and Contacts

If you have questions or run into issues during the DNS update or after configuration, contact your Aegister point of contact, or write to info@aegister.com.

​
6. Conclusion

Once you update the DNS records correctly, Aegister Cloud Defender protects your website. The activated services (Caching, DDoS, Threat Intelligence, WAF) start running, protecting and optimizing your web application.
For more information, contact our support team.