Onboarding Process

What are the prerequisites for onboarding?

To start the POC, please provide us with the below details-

1. The Fully Qualified Domain Name (FQDN) to be onboarded. (The FQDN must have at least 6000 to 7000 hits in 4 days.)

2. The endpoint IP address associated with the FQDN.

3. Information on any custom ports the application uses, aside from ports 80 and 443.

4. The location or region where the FQDN is hosted.

5. The SSL Certificate- Either in .crt and .key format or PFX file and its password

6. DNS access for the FQDN

What domain name should I enter?

Enter the primary domain name you want to secure with Prophaze WAF. This could be your main website (e.g., example.com) or a subdomain like your API endpoint (e.g., api.example.com). (FQDN)

What is an endpoint?

An endpoint is a specific URL or Loadbalancer IP or Public IP that points to your domain. (example: 134.124.176.148) should not be a private IP or 10 series,,,private ip series.

What geographic location should I choose?

This information is used for regional security considerations, regulatory compliance purposes and latency purpose. Choose the location where your application servers are physically located. We can add other regions as well.

What is a CNAME record and how do I add it?

A CNAME record aliases your domain name to another domain name. Prophaze will provide specific instructions on adding the CNAME record to your domain name system (DNS) management console. This step routes traffic through Prophaze WAF for security inspection. You can also do this through A record changes using the IP provided by Prophaze for the root domain. (It may vary from region to region) n subdomain CNAME needs to be changed.

What alternative DNS record types can be used besides CNAME?

In some cases, an A record pointing to Prophaze WAF's IP address is an option instead of a CNAME record. This depends on your specific domain configuration.

What happens to my existing DNS records when I add the Prophaze CNAME record?

Adding the Prophaze CNAME record typically doesn't affect your existing DNS records. It simply creates an alias for your domain name that points to Prophaze WAF for security inspection before reaching your application server.

Where can I find DNS related information?

You can go on to 1. Settings page.

2. Configure applications.

3. Click on the edit (pencil) button.

4. DNS setting.

Here you will get the information like CNAME and A-record.

What happens to my existing MX records (for email) when adding a CNAME record for Prophaze WAF?

Prophaze WAF integration won't affect your MX records as they point to separate servers for email delivery. You can typically manage MX records and CNAME records independently within your DNS management console.

Do I need a valid SSL certificate for Full HTTPS?

Yes, a valid SSL/TLS certificate is crucial for secure communication with Prophaze WAF. You'll need to have an active SSL certificate installed on your web server for HTTPS functionality. Prophaze can also get an SSL certificate through Let’s Encrypt if you don't have an SSL certificate.

What is Full HTTPS?

Full HTTPS ensures all communication between your application and users is encrypted using HTTPS protocol. This is crucial for protecting sensitive data transmission.

What happens to my website traffic during the CNAME record change?

There might be a brief service interruption while your DNS propagates the CNAME record change.