Ordnary

Docs Ordnary Web Services Ordnary Netway

Set up Ordnary Netway

Put Ordnary Netway in front of your server: add the application, create three DNS records, and watch the status turn Protected.

6 min readBeginner

1. Add the application

NametextRequired
How the application is listed in the console.
TypeWebsite | APIRequired
Browsers can answer a challenge, programs cannot; the type decides which profiles fit.
Public hostnamehostnameRequired
The name visitors use, such as app.example.com.
Originhostname or IPv4Required
Your own server. Must differ from the public hostname, and must not be localhost or a private address.
Security profileStandard | Strict | APIRequired
What Netway does beyond the managed firewall. See Security profiles.

Choose Protect application. The application is created with the status Awaiting DNS and its DNS & TLS tab shows the three records with their exact values.

2. Create the DNS records

  1. 1

    Verify domain ownership

    Create the first TXT record with the name and value from the console. It proves the hostname is yours.

  2. 2

    Validate the TLS certificate

    Create the second TXT record. Netway uses it to issue the certificate for your hostname.

  3. 3

    Route traffic to Netway

    Point the hostname at Netway with a CNAME to customers.netway.ordnary.com. From this moment traffic flows through Netway.

DNS records (names and values come from the console)
<ownership record name>    300  IN  TXT    "<ownership value>"
<certificate record name>  300  IN  TXT    "<certificate value>"
app.example.com.           300  IN  CNAME  customers.netway.ordnary.com.

3. Wait for Protected

  1. 1
    Awaiting DNS
  2. 2
    Hostname verified
  3. 3
    Certificate issued
  4. 4
    Protected

The console checks the records on its own and refreshes the status; Refresh on the application's page checks right away. Once both TXT records are found, the hostname is verified and the certificate issued, and with the CNAME in place the status turns Protected. This usually takes minutes once the records have propagated.

4. Lock down the origin

Netway only helps if attackers cannot reach your server directly. Keep the origin hostname out of any public DNS you advertise, and configure your server or firewall to accept HTTPS only from Netway. Your application should take the visitor's address from the X-Forwarded-For header.

Was this page helpful?
Updated 25 October 2026 Suggest an edit

Choose which cookies Ordnary may use. You can change this at any time via Cookie settings at the bottom of every page.