scanner.dev valid

Scanner

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-24T18:31:40.394Z. Cached copy · Source on scanner.dev

# Scanner

## SCANNER

- [What is Scanner](https://docs.scanner.dev/scanner/what-and-why/readme.md): Index your security data where it lives. Full visibility, hyper-fast search, and continuous detections, without SIEM-scale costs.
- [How it Works](https://docs.scanner.dev/scanner/what-and-why/how-it-works.md)
- [How Scanner Achieves Fast Queries](https://docs.scanner.dev/scanner/what-and-why/how-it-works/how-scanner-achieves-fast-queries.md)
- [Detection Rule Engine](https://docs.scanner.dev/scanner/what-and-why/how-it-works/detection-rule-engine.md)
- [Bring Your Own Cloud (BYOC) / Self-Hosted](https://docs.scanner.dev/scanner/what-and-why/how-it-works/bring-your-own-cloud-byoc-self-hosted.md)
- [Quick Setup Overview](https://docs.scanner.dev/scanner/getting-started/quick-setup-overview.md): This guide walks you through connecting Scanner to your AWS environment and ingesting your first logs. The entire process typically takes 30-45 minutes.
- [Step 1: AWS Infrastructure Setup](https://docs.scanner.dev/scanner/getting-started/step-1-aws-infrastructure-setup.md): Before Scanner can analyze logs, you must establish a secure connection to your AWS account. This creates the IAM roles, S3 buckets, and EventBridge resources Scanner requires.
- [AWS CloudFormation](https://docs.scanner.dev/scanner/getting-started/step-1-aws-infrastructure-setup/aws-cloudformation.md): Getting started with CloudFormation
- [Terraform](https://docs.scanner.dev/scanner/getting-started/step-1-aws-infrastructure-setup/terraform.md): Getting started with Terraform
- [Manual Setup - AWS CloudShell](https://docs.scanner.dev/scanner/getting-started/step-1-aws-infrastructure-setup/manual-setup-aws-cloudshell.md)
- [Troubleshooting AWS Errors](https://docs.scanner.dev/scanner/getting-started/step-1-aws-infrastructure-setup/troubleshooting-aws-errors.md): A guide to understanding and resolving AWS configuration and permission errors that appear in the Scanner UI.
- [Step 2: Connect Your First Data Source using Scanner Collect](https://docs.scanner.dev/scanner/getting-started/step-2-connect-your-first-data-source-using-scanner-collect.md)
- [Step 3: Validate & Test](https://docs.scanner.dev/scanner/getting-started/step-3-validate-and-test.md): Once you have set up a new source you can expect to see data flowing into Scanner within a few minutes. Follow the steps below to get started exploring your data.
- [Scanner Collect: Data Ingestion](https://docs.scanner.dev/scanner/using-scanner-complete-feature-reference/data-ingestion.md): Learn what Scanner Collect is, how it delivers your SaaS and cloud logs into S3 storage you control, and how it simplifies ingestion, indexing, and detection.
- [Sources](https://docs.scanner.dev/scanner/using-scanner-complete-feature-reference/data-ingestion/sources.md)
- [1Password](https://docs.scanner.dev/scanner/using-scanner-complete-feature-reference/data-ingestion/sources/1password.md)
- [Atlassian](https://docs.scanner.dev/scanner/using-scanner-c
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=scanner.dev · GET /v1/domain/scanner.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for scanner.dev:
1. POST https://agentwebmap.com/v1/sites/scanner.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://scanner.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/scanner.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/scanner.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.