Bot signals · Internet scanner

What is the TraceSecurity external testing scanner?

Requests from TraceSecurity external testing are known internet-scanner traffic: automated probes that map public services, monitor attack surfaces or test for vulnerabilities.

risk.is_scanner

Check an IP

Is this IP really TraceSecurity external testing?

Free. The same answer as risk.is_scanner in the lookup API.

01 · Profile

TraceSecurity external testing at a glance.

What to look for in your logs, and what the lookup API returns for its addresses.

Type
Internet scanner
robots.txt
Does not control scanning.
API flag
risk.is_scanner

A user agent alone never sets a flag. Anyone can claim to be TraceSecurity external testing; the flag follows the address the request comes from.

02 · In the response

What a match looks like.

A lookup of a TraceSecurity external testing address sets risk.is_scanner. The flags come with geolocation and network data in the same response, for API keys on every paid plan.

The response says which kind of bot an address belongs to, not which operator. A request that claims to be TraceSecurity external testing while risk.is_scanner is false should not be trusted as TraceSecurity external testing.

GET /api/lookup/{ip}?key=YOUR_API_KEY
{
  // … location and network fields …
  "risk": {
    "is_ai": false,
    "is_crawler": false,
    "is_scanner": true
  }
}

03 · Control

Block TraceSecurity external testing.

At the edge

  • robots.txt won’t help. It does not control port or vulnerability scanning, so a block has to happen before the request reaches your app.
  • Firewall, WAF or CDN. Many offer bot rules you can allow or deny by category.
  • In your app. Look up the client address and allow or deny on risk.is_scanner, alongside the user agent.
  • Never on the user agent alone. Blocking the name stops only honest clients; allowing it lets anyone in who borrows it.

04 · Questions

About TraceSecurity external testing.

What is TraceSecurity external testing?

Requests from TraceSecurity external testing are known internet-scanner traffic: automated probes that map public services, monitor attack surfaces or test for vulnerabilities.

How do I block TraceSecurity external testing?

robots.txt does not control port or vulnerability scanning. Block TraceSecurity external testing at your firewall, WAF or CDN, or look up each client address and deny requests where risk.is_scanner is true.

Can I trust a request that says it is TraceSecurity external testing?

Not on the user agent alone: any client can send a bot’s name in its user agent. A user agent alone never sets a flag. Check the address with the free bot checker or the lookup API.

Which risk flag does TraceSecurity external testing set?

Its addresses set risk.is_scanner in the lookup response. The risk flags come with every paid plan.

Recognise TraceSecurity external testing on every request.

is_ai, is_crawler and is_scanner in every lookup, on every paid plan, from 9,00 € a month (VAT included).