Skip to main content

1. Add your web app

When your organization is being set up, its home page in the Cyber Console shows a first-steps card. Its step Put your website behind Cloud Defender (Add your website) opens Protect a web app, which an Owner or Security Officer fills in:
  • Organization: the organization that owns the web app.
  • Domain: the full name visitors type (e.g., www.example.com).
  • Origin server: the public IP address or host name where the web app runs today. It must answer HTTPS on port 443.
  • Technical point of contact email: Aegister writes here to agree the DNS change.
  • Services: WAF, Threat Intelligence, DDoS and Caching. Most sites keep all four. What each layer does today is described in How it works.
Adding the web app tells Aegister, who sets it up. Its status page then shows an activation checklist with each of the steps below: Domain added, Aegister sets up the domain, Point the domain at Cloud Defender, Traffic is flowing and Lock the origin. If your home page shows no first-steps card, send the same details to your Aegister point of contact and we add the web app for you.

2. DNS Update

Wait until the activation checklist shows Aegister sets up the domain as done: pointing the domain earlier takes the site offline. Then 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.
  • Activation checklist:
    On the status page, Check now tells you whether the domain already answers through Cloud Defender. Aegister also checks it once an hour. Once it does, Point the domain at Cloud Defender turns Done.
  • 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 Threat Intelligence, the WAF rules, 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. Locking the origin is the one step only you can do, so the checklist shows it as Your step. When it is done, tell Cloud Defender: in the first hours after the domain goes live, the Overview tab of its status page shows Protection is live, whose last step, Lock the origin, has a Mark as done button for Owners and Security Officers. Marking it completes the setup of the domain.

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 the DNS records point to Cloud Defender and the origin is locked, Aegister Cloud Defender protects your website and the activated services start running. For more information, contact your Aegister point of contact.