agentleFS
projectdiscoveryprojectdiscovery/tlsx/CLAUDE.md

tlsx

CLAUDE.md1.2k starsChanged 4 years agoMITView on GitHub

TLSX is a Go-based TLS data gathering and analysis toolkit focused on TLS connection testing, certificate analysis, and security assessment. It's part of the ProjectDiscovery ecosystem and supports multiple TLS connection modes, fingerprinting, and misconfiguration detection. The toolkit supports multiple TLS connection backends: Implementation in pkg/tlsx/: - auto/ - Auto-detection and fallback logic - tls/ - Standard Go crypto/tls implementation - ztls/ - ZMap zcrypto implementation with JA3 fingerprinting - openssl/ - OpenSSL binary integration

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about projectdiscovery/tlsx

The biggest 5 of 51 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 51

Talked about on GitHub and Bluesky (51 times).

On GitHub · 50

45 more on GitHub

On Bluesky · 1

The file

We split this CLAUDE.md into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Test files follow Go convention: *_test.go

    line 51

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
CLAUDE.md

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

About TLSX

TLSX is a Go-based TLS data gathering and analysis toolkit focused on TLS connection testing, certificate analysis, and security assessment. It's part of the ProjectDiscovery ecosystem and supports multiple TLS connection modes, fingerprinting, and misconfiguration detection.

Build and Development Commands

  • Build: make build or go build -v -ldflags '-s -w' -o "tlsx" cmd/tlsx/main.go
  • Test: make test or go test -v ./...
  • Tidy dependencies: make tidy or go mod tidy
  • Run single test: go test -v ./path/to/specific/package -run TestName
  • Main executable: Built as ./tlsx binary

Architecture Overview

Core Structure

  • Entry point: cmd/tlsx/main.go - CLI application entry with flag parsing
  • Runner package: internal/runner/ - Orchestrates the execution flow, handles input processing and output coordination
  • Core TLS package: pkg/tlsx/ - Contains the main TLS analysis logic and connection handling

TLS Connection Modes

The toolkit supports multiple TLS connection backends:

  • auto mode (default): Automatic fallback between connection modes for maximum compatibility
  • ctls: Uses Go's standard crypto/tls library
  • ztls: Uses ZMap's zcrypto TLS implementation for older TLS versions and advanced analysis
  • openssl: Uses external OpenSSL binary for specialized operations

Implementation in pkg/tlsx/:

  • auto/ - Auto-detection and fallback logic
  • tls/ - Standard Go crypto/tls implementation
  • ztls/ - ZMap zcrypto implementation with JA3 fingerprinting
  • openssl/ - OpenSSL binary integration

Key Components

  • Client abstraction: pkg/tlsx/clients/ - Unified interface for different TLS connection modes
  • Certificate Transparency: pkg/ctlogs/ - Streaming CT logs support for real-time certificate monitoring
  • Output handling: pkg/output/ - JSON/text output formatting and file writing
  • Fingerprinting:
    • pkg/tlsx/jarm/ - JARM TLS fingerprinting
    • pkg/tlsx/ztls/ja3/ - JA3 client fingerprinting

Testing Strategy

  • Test files follow Go convention: *_test.go
  • Unit tests in each package test specific functionality
  • Integration tests in internal/runner/runner_test.go
  • OpenSSL functionality tested in pkg/tlsx/openssl/openssl_test.go

Key Features

  • Multi-mode TLS scanning: Supports different TLS libraries for comprehensive compatibility
  • Certificate analysis: Extract SANs, CNs, detect misconfigurations (expired, self-signed, mismatched, revoked, untrusted)
  • TLS fingerprinting: JARM and JA3 fingerprint generation
  • CT logs streaming: Real-time certificate transparency log monitoring
  • Flexible input: Supports ASN, CIDR, IP, hostname, and URL inputs
  • Multiple output formats: Standard text and JSON output

Development Notes

  • Go version: Requires Go 1.25+
  • Dependencies: Heavy use of ProjectDiscovery libraries (dnsx, fastdialer, goflags, gologger)
  • External tools: Optional OpenSSL binary for specialized TLS operations
  • Concurrency: Built-in support for concurrent TLS connections with configurable limits
  • Error handling: Uses ProjectDiscovery's utils/errors for consistent error handling patterns

Package Structure

  • assets/ - Embedded data (cipher status, root certificates)
  • cmd/ - Command-line applications and utilities
  • examples/ - Usage examples including CT logs streaming
  • internal/runner/ - Core execution logic, not for external use
  • pkg/ - Public API packages for library usage

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.