Docs Ordnary Web Services Ordnary Netway
How protection works
What Ordnary Netway stops at each layer, what passes through to your server, and the statuses an application can have.
Netway mitigates attacks automatically, without rules for you to write. Traffic to your hostname passes several checks at the edge before any of it reaches your server.
| Layer | Protects against | How |
|---|---|---|
| Network (layers 3 and 4) | Volumetric floods such as SYN and UDP floods. | Absorbed by the edge network's capacity, always on. |
| HTTP (layer 7) | Floods of requests aimed at your application. | Automatic HTTP DDoS mitigation, plus the profile's rate limit per IP. |
| Application | Injection, cross-site scripting and the other common web attacks. | Managed firewall rules, kept up to date for you. |
| Reputation | Addresses seen attacking elsewhere. | Known-bad clients blocked; threshold depends on the profile. |
| Bots | Scrapers and automated abuse. | Challenges on the Strict profile; verified bots pass. |
| TLS | Plain-text traffic. | Visitors always connect over HTTPS with a certificate for your hostname. |
What reaches your server
Clean requests, forwarded over HTTPS to your origin on port 443 with the original hostname. The visitor's address is in X-Forwarded-For. Everything else is stopped at the edge and never costs your server a connection.
Statuses
| Status | Meaning |
|---|---|
| Awaiting DNS | One or more of the three records is missing. The DNS & TLS tab shows which. |
| Protected | Hostname verified, certificate active, traffic flowing through Netway. |
| Action required | Something needs you: a record that disappeared, a certificate that could not be issued, an origin that does not answer. The page says what. |
The protection pipeline
An application's Overview tab shows the pipeline a request passes: Visitor, DDoS, WAF, Rate limiting, Origin. It is the order the checks run in; a request stopped at one stage never reaches the next.