Try for free
Try for free Log in

CloudFilt on Go

For Go web servers, CloudFilt comes as one function to call at the top of your handlers, plus the front end snippet in your pages.

Get the Go code Create a free account

Free up to 3,000 requests per month and per site. No credit card required.

Server code FREE

In the box

1×
Go HTTP server, allowed to make outbound HTTPS requests
1×
line of HTML, before </head>
1×
function call at the top of each handler

Fitting instructions

5 steps, from sign-up to the first verdict.

  1. Create your free account and add your website

    CloudFilt gives you a public key and a private key, free up to 3,000 requests per month.

  2. Add the front end snippet

    Paste it before the </head> tag of every page.

  3. Paste the back end code

    At the end of the file that holds your handlers, with its missing imports.

  4. Call cloudfiltInterception

    At the beginning of every function passed to handlerFunc.

  5. Watch the verdicts

    Allowed, challenged and blocked requests show up in your live journal within the minute.

    Allowed Challenge Blocked

How it works

With Go, CloudFilt runs in two places. The front end snippet, one line of HTML in your pages, loads the CloudFilt script that spots automation in the browser. The back end code is one function, cloudfiltInterception, called at the top of your handlers: it sends the IP, the URL and the user agent of the request to CloudFilt and applies the verdict before your page is built.

Real visitors go through, doubtful ones get a captcha, bad bots are blocked. The code of your dashboard already holds your keys: copy, paste, deploy. Your rules (countries, URLs, anti-flood thresholds) are then edited from the dashboard, without a new deployment.

What you get

  • Front and back end analysis
  • Code generated with your keys already filled in
  • Captcha for doubtful visitors, not a hard block
  • Search engine crawlers verified and let through

From request to verdict

Once Go is plugged in, each request is scored from the front and the back end, then allowed, challenged or blocked.

  1. Visitor

    A browser, a script or a bot sends a request to your website or API.

  2. Nearest point of presence

    The CDN WAF, or your plugin, hands the request to the closest point of presence.

  3. Signals

    IP reputation, behaviour, rate, country and your own rules, weighed in real time.

  4. Verdict

    • Allowed to your site
    • Challenge captcha first
    • Blocked never reaches you

Other integration options

All integrations