HTTPS proxy, cache and protection

When you enable the proxy on an A, AAAA or CNAME record, the name resolves to NorthDNS edge nodes. Traffic reaches the edge, which forwards it to your server (origin) with HTTPS, caching and security rules applied. The origin address is not exposed in DNS.

Certificates are issued and renewed automatically for proxied names, provided the domain is delegated to NorthDNS. The SSL/TLS page lets you choose the behaviour, for example redirecting HTTP to HTTPS.

On the Edge page you can enable caching, set its lifetime and exclude paths (such as /admin). Only 200 responses to GET requests without cookies or an Authorization header are stored, never those with Set-Cookie or Cache-Control: private/no-store. You can purge the cache at any time.

• Managed WAF: blocks requests matching common attack patterns.
• Rate limit per client per minute.
• Under-attack mode: shows a browser check before the site, always or only for suspicious clients, with excluded paths.

You can set a secondary origin: if the primary does not answer, the edge tries the secondary automatically.

To block, redirect or route traffic by path, method, country, IP or headers, use proxy rules.