Cloudflare is a global network providing security and performance enhancements for the millions of websites within its network. It provides "instant-on" SSL encryption, protection against DDoS attacks, website performance enhancements, and more.

Syngency recommends that all hosted agency websites use Cloudflare, to take full advantage of these features.

Note: So long as the DNS records are copied exactly, switching to Cloudflare won't affect your current email, FTP, or associated services at all. We will confirm the records match so there will be no disruption.

Switching is easy to do, and takes just a few minutes:

  1. Locate the DNS settings in the control panel of your current domain host (the company you originally registered your domain with).
    This could be GoDaddy, Namecheap, BlueHost, or any number of other registrars. If you're not sure who you use for this, let us know and we can help you find out.

  2. Copy or take a screenshot of all current DNS records, or share your domain control panel credentials with us. This allows us to confirm the records Cloudflare has found match your current records exactly, to avoid any disruption to your services.

  3. Contact Syngency Support via Intercom, to have Cloudflare enabled for your primary domain. You will need to provide the current DNS records as above.
    Please await verification on this before proceeding with the next steps.

  4. Find the nameserver settings for the domain you're using for your site in your domain control panel.

  5. Change the existing nameservers (typically starting with ns1 and ns2) to the following Cloudflare nameservers:

    dara.ns.cloudflare.com
    jim.ns.cloudflare.com

Changes can take up to 24 hours to propagate through the Internet. Once this is complete, Cloudflare's SSL, security, and performance features will be active for your website.

You will see the familiar "lock" icon next to your website address in your browser's location bar:

And if you click on the certificate information, you'll see the Cloudflare certificate is now active for your site:

Did this answer your question?