tls-certificate-analysis

Extract TLS certificate fields and protocol signals from HTTPS endpoints.

Updated May 27, 2026
One-click install
npx skills add https://github.com/hoanghn61/.agents --skill tls-certificate-analysis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tls-certificate-analysis
Source: https://github.com/hoanghn61/.agents/tree/main/skills/techstack-identification/tls_certificate_analysis
Command: npx skills add https://github.com/hoanghn61/.agents --skill tls-certificate-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes guesswork when you need to understand how a domain’s TLS is configured by extracting certificate details and network fingerprint signals.

Core Features & Use Cases

  • Certificate metadata extraction: Pulls issuer, Subject Alternative Names (SANs), validity window, signature algorithm, and public key details from a live TLS endpoint.
  • Issuer and hosting inference: Maps issuer patterns (e.g., Let’s Encrypt, DigiCert, AWS, Cloudflare, Google Trust Services) to technology and operational signals with confidence.
  • Protocol support checks: Determines supported TLS versions (1.0 through 1.3) to surface legacy exposure or modern-only posture.
  • Optional JARM fingerprinting: Generates a server fingerprint to aid technology identification and matching against known fingerprint patterns.

Quick Start

Ask the AI to analyze the TLS certificate and TLS protocol support for the domain example.com and return issuer, SANs, protocol versions, and any known JARM match.

Frequently Asked Questions about tls-certificate-analysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I extract TLS certificate details like issuer and SANs from a domain?

To extract TLS certificate details, establish a TLS connection and parse X.509 fields from openssl output to retrieve issuer, Subject Alternative Names (SANs), validity window, and public key information.

How can I check which TLS protocol versions a domain supports?

Check supported TLS protocol versions by running deterministic network checks against the endpoint to determine support for TLS 1.0 through 1.3, surfacing legacy exposure or modern-only posture.

What is JARM fingerprinting and when do I need it for TLS analysis?

JARM fingerprinting generates a server fingerprint to aid technology identification and matching against known patterns. It is optionally applied during TLS analysis to verify server configurations.

Can I infer a domain's hosting provider from its TLS certificate issuer?

Infer a domain's hosting provider by mapping issuer patterns from the TLS certificate, such as Let's Encrypt, DigiCert, AWS, Cloudflare, or Google Trust Services, to operational signals with confidence.

Does this TLS analysis approach validate or bypass certificate trust?

This TLS analysis approach does not validate or bypass certificate trust; it establishes a connection to parse X.509 fields and run deterministic protocol checks without modifying trust behavior.