analyzing-certificate-transparency-for-phishing SKILL.md skillA
analyzing-certificate-transparency-for-phishing from 26zl/cybersec-toolkit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add 26zl/cybersec-toolkit/analyzing-certificate-transparency-for-phishing@v1.0Pins v1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- 26zl/cybersec-toolkit
- Path
.claude/skills/analyzing-certificate-transparency-for-phishing/SKILL.md- Versions recorded
- 1
- Latest version
- v1.0, committed Jun 2, 2026
- Size
- 13,472 bytes
- Repository stars
- 87
- License
- MIT
Monitor Certificate Transparency logs using crt.sh and Certstream to.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Analyzing Certificate Transparency for Phishing ## Overview Certificate Transparency (CT) is an Internet security standard that creates a public, append-only log of all issued SSL/TLS certificates. Monitoring CT logs enables early detection of phishing domains that register certificates mimicking legitimate brands, unauthorized certificate issuance for owned domains, and certificate-based attack infrastructure. This skill covers querying CT logs via crt.sh, real-time monitoring with Certstream, building automated alerting for suspicious certificates, and integrating findings into threat intelligence workflows. ## When to Use - When investigating security incidents that require analyzing certificate transparency for phishing - When building detection rules or threat hunting queries for this domain - When SOC analysts need structured procedures for this analysis type - When validating security monitoring coverage for related attack techniques ## Prerequisites - Python 3.9+ with `requests`, `certstream`, `tldextract`, `Levenshtein` libraries - Access to crt.sh (https://crt.sh/) for historical CT log queries …
Read the whole file at its exact version.
How to install
mdr add 26zl/cybersec-toolkit/analyzing-certificate-transparency-for-phishing@sha256:62235436eb4b1ce6The line at the top of this page pins the label v1.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_ak6h5dcboe2qusda)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Jun 2, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (13472 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
26zl/cybersec-toolkit · 87 stars · license MIT · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ak6h5dcboe2qusda GET https://markdownregistry.com/api/v1/resolve?ref=26zl/cybersec-toolkit/analyzing-certificate-transparency-for-phishing GET https://markdownregistry.com/api/v1/blob/62235436eb4b1ce68ea7a01516acad9e9e093803f5a8756b62f5f535304ee946
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from 26zl/cybersec-toolkit
Every file in 26zl/cybersec-toolkit