Try for free
Try for free Log in

CloudFilt on ASP.net

For ASP.NET applications, CloudFilt is one helper class called from your controllers, plus the front end snippet in your layout.

Get the ASP.net 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×
ASP.NET application, allowed to make outbound HTTPS requests
1×
line of HTML, in your layout
1×
helper class, called from your controllers

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 your layout.

  3. Add the helper class

    Paste the back end code in Helpers › cloudFiltHelper.cs.

  4. Call it from your controllers

    At the beginning of every controller function.

  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 ASP.net, 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 helper class, cloudFiltHelper, called from your controllers: 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 ASP.net 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