Skip to content

Authorized traffic testing

Test how your site holds up under real load.

Run rate-limited HTTP checks and real Chromium sessions against domains you have verified. See status codes, latency, console errors and analytics tags in one report, with every unit clearly labelled as automated test traffic.

500 trial credits · No credit card required · Cancel anytime

Illustration of the AutomatedTraffic dashboard with sample data: request counts, status codes and recent test events.

Product

Everything you need to test with confidence. Nothing you need to hide.

Domain verification

Prove control with a DNS TXT record or a well-known file before a single request runs. Tokens are single-use and stored hashed.

HTTP endpoint tests

Rate-limited GET requests with status codes, error categories and latency from p50 to p99, at up to 5 requests per second.

Browser validation

Real headless Chromium on desktop, tablet and mobile profiles. Load timing, console errors and multi-page sessions.

Analytics tag checks

See whether your GA4 tag loads and which events fire, with the Measurement ID matched. Hits are intercepted by default.

Credits you can audit

The maximum cost is reserved up front, charged per completed unit and the rest released. Every movement is in a ledger.

Webhooks and API

Signed webhooks for campaign and billing events, scoped API tokens, CSV and JSON exports of every event.

How it works

From a verified domain to a report. Four steps.

Read the docs
  1. 01

    Verify your domain

    Add a hostname and publish the challenge as a TXT record or a file. It takes a couple of minutes.

  2. 02

    Configure a test

    Pick HTTP or browser, a device profile and region, then set the units, rate and duration.

  3. 03

    Run within limits

    See the estimate before launch. Pause, resume or cancel at any time; unused credits return.

  4. 04

    Read the report

    Status and error breakdowns, latency percentiles, a timeline and the full event log.

Built to be trusted

Honest by design. Bounded by code.

Every worker identifies itself, every campaign has hard limits, and reports keep test activity apart from analytics events and human visits, which are always zero. Using it for anything else breaches the Acceptable Use Policy.

SSRF protectionVerified domains onlyAppend-only ledger
  • Not a source of visitors.

    Every unit is an HTTP request or an automated browser session, and is labelled as one.

  • Not a way to inflate analytics.

    Analytics hits are intercepted by default; delivery is opt-in for tag testing only.

  • Not an ad or search click service.

    We never click ads, affiliate links or search results, and only test hosts you verified.

  • Not a tool for evading defences.

    No CAPTCHA solving, proxy rotation or attempts to bypass a WAF or bot management.

Pricing

Pay for units. Never for seats.

One credit per HTTP request and ten per automated browser session. The maximum is reserved when a campaign is created, completed units are charged and the rest returns to your balance.

Plans and credit packs
HTTP request
1credit
Automated browser session
10credits

FAQ

Questions, answered plainly.

Will this increase my visitor numbers in Google Analytics?

No, and it is not designed to. HTTP tests do not execute JavaScript. Browser sessions intercept analytics hits by default, so they never reach your property. If you opt in to delivering hits for tag testing, filter that traffic out of your reports. It is synthetic and must not be counted as audience.

What exactly is a unit?

A unit is one HTTP request (1 credit) or one automated browser session (10 credits). A browser session loads between one and five pages of your verified site. Units are never visitors.

Which sites can I test?

Only hostnames your organization has verified, through a DNS TXT record at _traffic-verify.<host> or a file at /.well-known/traffic-verify.txt. Subdomains are included only if you enable that when adding the domain.

How are credits charged?

When a campaign starts, its maximum cost is reserved from your available balance. Only completed units are consumed. Anything unused is released when the campaign finishes or is cancelled.

Can I stop a test that is running?

Yes. Every campaign can be paused, resumed and cancelled. A few requests already in flight may complete after you stop; the report counts them separately.

Do you bypass CAPTCHAs, WAFs or bot detection?

No. Our browsers identify as automated and we never attempt to evade bot management or security controls. If your firewall blocks the test, allow-list it on your side or test a staging host.

Start with a domain you own.

Create an account, confirm your email for 500 trial credits, verify a hostname and run your first test in minutes.