certgraph
v0.1.0 open-sourceThe section your link pointed to isn't on certgraph's page any more, so we've brought you to the top.
An open source intelligenceopen source intelligenceOpen-source intelligence, collecting and analyzing information from publicly available sources. Investigators use it to learn about people, infrastructure or threats. tool to crawl the graph of certificate Alternate Names - lanrat/certgraph
Summary
certgraph is an open-source command-line tool that crawls SSLSSLA cryptographic protocol for encrypting network connections, now deprecated in favor of TLS but whose name persists colloquially. Cyber tools reference it when handling HTTPS or other encrypted-channel inspection and termination. certificates, building a directed graph where domains are nodes and a certificate's Subject Alternative Names become edges to other domains. It defaults to pulling certificates directly over TCPTCPA network protocol that delivers a reliable, ordered stream of bytes between two endpoints. It detects lost data and retransmits it. but can also query certificate transparency logs through drivers like crt.sh, Censys, SMTPSMTPThe application-layer protocol used to send email between servers and from clients to servers; cyber tools use it to relay alerts, phishing simulations, or exfiltrated data over standard mail infrastructure., or HTTP/TLS, and it can serve the resulting graph through an embedded web UI. It sits in the reconnaissance space, aimed at people doing hostname enumeration for OSINTOSINTOpen-source intelligence, collecting and analyzing information from publicly available sources. Investigators use it to learn about people, infrastructure or threats. or bug bounty work, using certificate reuse to surface related domains and trust chains rather than brute-forcing DNS. First committed in 2016 and maintained by 4 contributors, it has had 6 releases in the tracked window but only 3 commits in the past year, with the last release 361 days ago, suggesting slow, low-activity maintenance rather than active development.
An open source intelligence tool to crawl the graph of certificate Alternate Names - lanrat/certgraph
How certgraph helps
Which other domains share infrastructure or ownership hints with a domain I'm investigating?
crawls the Subject Alternative Names on its certificate and follows each one as an edge to a new domain, repeating up to a bounded depth so related hostnames surface without guessing names
What hidden subdomains exist for a target that DNS brute-forcing would miss?
pulls certificates either live over TCP or from certificate transparency logs and adds every SAN entry as a new node, catching names that were only ever issued a certificate
Is a domain still actively tied to the infrastructure that issued its certificate?
checks DNS records for each discovered domain and reports registration status, distinguishing live hosts from ones that only appear in historical certificate data
How are two domains related through the certificates they've used?
assembles the crawl into a graph and can print or serve the adjacency list, showing the chain of shared certificates that connects one domain to another
Which of the domains found are worth ignoring because they sit behind shared hosting rather than the target's own infrastructure?
flags domains whose certificates come from content delivery networks so they can be distinguished from infrastructure the target actually controls
Which discovered domains are still worth chasing versus dead ends?
can restrict traversal with a regex filter and cap the number of unique apex domains pulled from a single certificate, keeping the graph focused on names that match the investigation
Languages
Command line
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for certgraph, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail certgraph puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Releases
1 entry
No entries match these filters.
- August 20251
Project health
Issue, contributor and maintainer activity in lanrat/certgraph, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 0 −1 vs prior 12 months
- Maintainers 0 +0 joined · −1 left, last 12 months
- Bus factor 0 committers behind half the commits
- Community-filed not measured of issues opened, last 12 months
- Median time to close not measured issues closed, last 12 months
- Open backlog 2 of 11 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 2
- Contributors / month 0
- Commits / month 0
- Stars 382
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Libraries its release ships
What its latest release locks, checked against known advisories.None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.
Choose a badge style and copy the code →