WAFGOPreparing your page
DOCUMENTATION / START BUILDING

Start with a domain. Build from there.

This guide explains the DNS, origin, TLS and security setup process for WAFGO. Use the actual parameters assigned by the service team or console.

SETUP WORKFLOW

01 / Confirm your domain and origin

List your domains, origin IP addresses or hostnames, ports and protocols. Check that the origin returns the expected content for the intended Host. Record existing DNS and certificate settings for rollback.

Configuration notes

Validate with a test domain first. Do not point a production domain at an unverified target, or include keys and origin credentials in public support requests.

SETUP WORKFLOW

02 / Configure DNS

After creating the domain service configuration, use its officially assigned CNAME target. Never infer a destination from another customer or a demo. Apex CNAME/ALIAS support depends on your DNS provider.

Local verification commands
nslookup -type=CNAME wafgo.com

dig +short CNAME wafgo.com

Configuration notes

The query below only checks current resolution. Replace the domain with your actual hostname and compare the result with your assigned target after propagation.

SETUP WORKFLOW

03 / Check HTTPS and origin transport

Client-to-edge and edge-to-origin are separate connections. Both should use correct certificates and hostname verification. Check that HTTPS redirects do not create a loop.

Local verification commands
curl -I https://wafgo.com

openssl s_client -connect wafgo.com:443 \
  -servername wafgo.com -verify_return_error </dev/null

Configuration notes

Review expiration, domain matching, the complete certificate chain and origin SNI/Host. Never put private keys in frontend code or public configuration.

SETUP WORKFLOW

04 / Begin with conservative policies

Cache static assets while preserving correct isolation for logins, payments and personalized content. Validate security policies against test traffic or in observation mode before enabling blocking.

Configuration notes

Evaluate admin paths, APIs and pages separately. Keep trusted-source exceptions narrowly scoped, with an expiry and a review process.

SETUP WORKFLOW

05 / Verify, observe and iterate

Check access, status codes, caching and security events from your primary user regions. Watch for origin errors, false positives, caching leaks and certificate failures. Use your recorded rollback process when needed.

Configuration notes

Before launch, confirm alert delivery, responsible owners, operational permissions and support channels. Measure performance using your actual business workload.

Your pre-launch checklist

  • DNS destination matches the assigned service details
  • Dynamic and personalized content cannot be cached incorrectly
  • Client and origin TLS verification succeeds
  • Security policies are tested and rollback is ready
  • Critical application journeys pass end-to-end checks

Planning an automated integration?

This page covers onboarding and verification. Ask the service team for the official API documentation, including endpoints, authentication, permissions and available operations, before integrating.

Ask about API documentation
All products