Traffic transparency

Asset Intelligence traffic

Kantoku helps organizations observe internet-facing assets they own, control, or are authorized to monitor.
Use this page to identify Kantoku collection traffic and report activity that appears unexpected.

Collector identity

How requests are identified

Collector-owned HTTP requests use this user agent. Browser-based collection keeps the standard Chromium identity and adds the same Kantoku Asset Intelligence identifier.
Kantoku/1.0 (+https://kantoku.io/abuse)
Current source addressesapi.kantoku.io/v1/source-ips

01 · Customer scope

Why you may see this traffic

A Kantoku customer may have configured your domain, IP address, or a related web surface as part of its authorized Asset Intelligence scope.
Traffic can include requests to public pages and common metadata files, rendered browser visits, and targeted checks of internet-facing services selected by the customer. Collection scope and cadence depend on the customer's configuration.

02 · Required use

Authorization is required

Kantoku customers must own, control, or have authorization to monitor the assets they configure. The service is not intended for scanning unrelated internet assets or for unauthorized security testing.
Website and network operators remain free to block or rate-limit requests using their normal access controls. If you believe the traffic is outside an authorized scope, please report it so we can investigate.

Unexpected activity

Report unexpected traffic

Send us enough context to identify the request and investigate the customer scope. Do not include credentials or other secrets.

abuse@kantoku.io

Include in your report

  • Source IP address
  • UTC timestamp
  • Destination hostname or IP
  • Requested path or port
  • Complete user agent or log excerpt