# Install cdncheck with Homebrew, Nix

Utility to detect various technology for a given IP address. Version 1.2.47 via Homebrew; verified 2026-08-02. Also installable with nix: nix profile install nixpkgs#cdncheck.

## Install

```sh
sudo av install brew:cdncheck
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install cdncheck
```

  Evidence: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#cdncheck
```

  Evidence: nixpkgs package indexes: pkgs/by-name/cd/cdncheck/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

## Package facts

- **Package key:** brew:cdncheck
- **Package manager:** Homebrew
- **Version:** 1.2.47
- **Source summary:** Utility to detect various technology for a given IP address
- **Homepage:** <https://projectdiscovery.io>
- **Repository:** <https://github.com/projectdiscovery/cdncheck>
- **Last updated:** 2026-08-02T06:12:46Z
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- cdncheck (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 1.2.47
## Project history and usage

cdncheck is a ProjectDiscovery tool and Go library for identifying CDN, cloud, and WAF technology associated with DNS names or IP addresses.

### Project history

The official repository describes cdncheck as both a command-line utility and a helper library. Provider data is maintained in provider.yaml and compiled into sources_data.json, making the project a compact data-and-code package for infrastructure detection.

### Adoption history

Its adoption is tied to ProjectDiscovery's security tooling ecosystem, where small composable CLIs are used in reconnaissance and asset analysis pipelines. The README documents both direct CLI use and library import via github.com/projectdiscovery/cdncheck.

### How it is used

Users run cdncheck against IP or DNS input, filter results to CDN, cloud, or WAF matches, write plain or JSONL output, and can add providers through the repository's provider data workflow.

### Why package nerds care

cdncheck is package-nerd-relevant because it packages frequently changing provider intelligence into a Go CLI/library with reproducible releases; the package value is as much the curated data as the executable.

### Timeline

- 2020: GitHub repository metadata identifies projectdiscovery/cdncheck repository creation era.
- 2020s: README documents CDN, cloud, WAF detection, provider generation, CLI flags, and library usage.

### Related projects

- cdncheck belongs to the ProjectDiscovery ecosystem of reconnaissance and security tools and is commonly adjacent to DNS, HTTP probing, and asset-enrichment workflows.

### Sources

- <https://api.github.com/repos/projectdiscovery/cdncheck>
- <https://github.com/projectdiscovery/cdncheck>
- <https://projectdiscovery.io>
- <https://github.com/projectdiscovery/cdncheck#readme>
- <https://formulae.brew.sh/api/formula/cdncheck.json>


## Security Notes

No matching local secret-handling manifest was found for cdncheck. Nucleus package metadata is still published here so future coverage has a stable package URL.


## Other Package-Manager Records

- Nix - cdncheck: normalized package name match | nixpkgs package indexes: pkgs/by-name/cd/cdncheck/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1


## Combined YAML source

View the package source record on GitHub. [combined/cdncheck.yml](https://github.com/mxcl/pkgdb/blob/main/combined/cdncheck.yml)


## Sources

- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph