[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77VX6YYTZKP9M5T0P8NRPEZ":3,"skill-same:01M77VX6YYTZKP9M5T0P8NRPEZ":52},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M77VX6YYTZKP9M5T0P8NRPEZ","recon-a-domain-passively",null,"End-to-end passive reconnaissance for a domain, website or IP — builds an asset inventory covering registration, DNS, subdomains, infrastructure, tech stack, history and ownership without sending a single packet to the target. Use when asked to research or profile a domain or website, map what an organisation runs, or investigate a suspicious site without alerting its operator. Applies to vendor and third-party risk assessment, attack-surface review, M&A technical diligence, phishing and fraud-site investigation, and pre-engagement scoping. Reference at useosint.com\u002Fskills\u002Frecon-a-domain-passively.","Reihantt6\u002Fsns-myagent","Reihantt6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F219822095?v=4","01M77KK94PV8B7C2D9XWXNS8DJ","Mohamad Reihan tegar prasetya","01M77KK958QFMTHYXGXFV7KZ79",2,"MIT","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Frecon-a-domain-passively\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: \"End-to-end passive reconnaissance for a domain, website or IP — builds an asset inventory covering registration, DNS, subdomains, infrastructure, tech stack, history and ownership without sending a single packet to the target. Use when asked to research or profile a domain or website, map what an organisation runs, or investigate a suspicious site without alerting its operator. Applies to vendor and third-party risk assessment, attack-surface review, M&A technical diligence, phishing and fraud-site investigation, and pre-engagement scoping. Reference at useosint.com\u002Fskills\u002Frecon-a-domain-passively.\"\n---\n# Recon a domain passively\n\nTurn one domain into a defensible map of an organization's internet-facing estate\nplus the owner behind it. The techniques live in other skills; what this workflow\ncontributes is the **order**, the **inventory**, and the **stopping rule**. Two\nfailure modes to avoid from the start: enumerating for hours and producing 400\nhostnames with no attribution, dates or priority, which is not a map; and drifting\nactive without noticing, because one probe \"just to check if it's up\" ends the\npassive claim. Decide the passive boundary before step 2, not during it.\n\n## Ordering logic\n\nEach stage feeds the next, and the sequence is cheapest-and-quietest first:\n\n| Order | Stage | Why here |\n|---|---|---|\n| 1 | Registration and DNS | Defines the perimeter. Without the apex set and the registrant you do not know what is in scope |\n| 2 | Name expansion | Archival sources only. Costs nothing, touches nothing, produces the candidate list everything else consumes |\n| 3 | Resolution and inventory | Converts names to addresses, which is what infrastructure lookups take as input |\n| 4 | Infrastructure and services | Needs stage 3's addresses. Third-party scan data only |\n| 5 | Content, history, code, tech stack | Needs hostnames and org names from earlier stages as search terms, and reuses artifacts already collected |\n| 6 | Owner attribution | The registrant, tenant and organization names surfaced above are the input |\n\nRun stages 1–5 as a loop, not a line. Every stage produces new selectors that\nbelong back at stage 1 or 2. Stop looping when the stopping rule in step 7 is met.\n\n## Step 1 — Authorized scope\n\nState in writing: the subject (which domains and netblocks, and which adjacent ones\nare explicitly excluded), the objective, the jurisdictions involved, and the\npassive boundary — specifically whether DNS resolution, wordlist brute-forcing and\nany HTTP contact with the target are permitted. Read\n[..\u002F..\u002FETHICS.md](..\u002F..\u002FETHICS.md). If being noticed matters, set up attribution\nhygiene with `investigate-without-getting-made` before querying anything.\n\n**Done when** subject, objective, out-of-bounds list, jurisdiction and passive\nboundary are written down, and you know which of the three grey activities you may\nperform.\n\n## Step 2 — Registration and DNS baseline\n\nRun `who-owns-this-domain` on every in-scope apex. You want registrar, dates and\nstatus, nameservers, the full record set, and the mail and SaaS fingerprints TXT, MX,\nDKIM and CAA give up. Where registration is redacted, pull historical WHOIS in the\nsame pass.\n\n**Done when** every apex has a registration record with a retrieval timestamp,\na complete record set, and a list of named third-party vendors extracted from its\nDNS.\n\n## Step 3 — Expand the name space\n\nRun `find-hidden-subdomains`. Certificate Transparency and passive DNS first, because\nthey are free, historical and invisible. Feed it the organization names from step 2 as\nwell as the domains — a certificate-subject search finds sibling and acquired domains\nnobody put in the brief.\n\n**Done when** you have a deduplicated candidate hostname list with the source and\nfirst-seen date recorded per name, and any newly discovered apex domains have been\npushed back through step 2.\n\n## Step 4 — Resolve and start the inventory\n\nClassify each candidate: resolves to an address, resolves to a third-party CNAME, or\ndoes not resolve. Build the inventory now rather than at the end — retrofitting\nprovenance onto a list you already collected is how findings lose their timestamps.\nThe schema and per-row fields are in\n[reference\u002Fasset-inventory.md](reference\u002Fasset-inventory.md).\n\n**Done when** every candidate is in one of the three buckets with a resolution\ntimestamp, every resolving host has an IP and an ASN, and every third-party CNAME\nis attributed to a named vendor.\n\n## Step 5 — Infrastructure and services\n\nRun `find-exposed-servers` over the addresses and netblocks from step 4. Query scan\nplatforms only — no port scanning, no service probing. Use the certificate and\nfavicon pivots to catch hosts that share the target's infrastructure without sharing\nits DNS, and note anything that looks unintentionally exposed.\n\n**Done when** each in-scope IP has its observed ports and services with scan\ndates, each netblock has an owner from its RIR record, and any infrastructure\nfound only through cert or favicon pivots has been added to the inventory and\nattribution-graded.\n\n## Step 6 — Content, history, code and tech stack\n\nThree sources, in this order:\n\n- `read-deleted-pages` for the estate as it used to be: retired hostnames, old\n  staff pages, exposed paths, pre-CDN infrastructure references.\n- `google-like-a-spy` for what is indexed now on the hosts you found — documents,\n  directory listings, configs, forgotten portals.\n- `secrets-in-git-history` for the org names, GitHub organization slugs, cloud\n  tenant labels and project IDs surfaced in steps 2 to 5.\n\nIf imagery matters — a logo reused across a network of sites, a stock photo posing as\nan office — run `find-the-original-image`. Shared images tie sites together when DNS\nand registration do not.\n\nThen assemble the tech stack from what you now hold: headers and cookies in archived\ncopies and scan records, certificate issuers, CNAME targets, JavaScript and asset\npaths, CSP directives, favicon hashes, and the SaaS fingerprints from step 2. Where\nyou need a live page, read a third-party scan of it instead of fetching it.\n\n**Done when** archived and indexed content is reviewed for the top-priority\nhostnames, code exposure is documented or ruled out, new hostnames have gone back\nthrough step 4, and the stack is documented per host with the artifact each\nconclusion rests on and versions marked claimed rather than verified.\n\n## Step 7 — Decide whether the map is done\n\nCompleteness is a judgement, so make it against criteria:\n\n- Two consecutive new sources produced no new assets. Saturation, not exhaustion, is\n  the signal.\n- Every discovered name is resolved or classified, and every resolving host has an\n  owner and an attribution grade.\n- Naming conventions have no unexplained gaps: if `web01` and `web03` are in the\n  inventory, you have accounted for `web02`.\n- Every named vendor and tenant from step 2 has yielded assets or been ruled out.\n- The objective from step 1 can be answered from the inventory.\n\nA failing criterion tells you exactly which stage to re-enter.\n\n**Done when** all five pass, or the remaining gaps are written up as stated\nlimitations rather than left implicit.\n\n## Step 8 — Hand off the owner\n\nIf the registrant, certificate subject, RIR reassignment or tenant label resolves\nto a legal entity rather than an individual, the domain work is finished and a\ncorporate investigation starts: hand the entity name and jurisdiction to\n`x-ray-a-company`, take registry and beneficial-ownership questions to\n`who-really-owns-it`, and send recovered emails to `what-an-email-reveals`. Do not\nattempt corporate structure from DNS artifacts — DNS shows operators, not\nshareholders.\n\n**Done when** every owner-side selector is routed to the right skill or recorded as\na dead end with the reason.\n\n## Step 9 — Report\n\nRun `write-the-intel-brief`. Lead with the asset inventory, then the attribution\nchain, then anything that appears unintentionally exposed, then the limitations\nfrom step 7. **Done when** every claim traces to an inventory row with a source and\ntimestamp, and every finding carries a confidence grade.\n\n## Where this goes wrong\n\n- **Scope creep through pivots.** Enumeration produces sibling domains endlessly and\n  each looks like the next target. If it is not in the step 1 subject list it is a\n  finding to report, not a workstream to start.\n- **Silent drift into active.** Resolution, brute-forcing and HTTP probing sit on a\n  spectrum, and tools blur it — passive collectors have active modes one flag away,\n  and one careless flag ends the passive claim for the engagement.\n- **Inventory without attribution.** Shared hosting, CDN addresses and bundled certs\n  attach assets to your target that are not the target's, and an ungraded inventory\n  row is a liability. Relatedly, a vulnerable SaaS tenant the target merely uses is\n  a supply-chain finding and must be phrased as one.\n- **Stale data presented as current.** Archives, CT and scan records are all\n  historical, and undated findings are not findings.\n- **Stopping at the first quiet moment.** No new results usually means one source\n  saturated, not the estate mapped — which is what step 7 catches.\n- **Over-collection.** Staff names from archived pages and SNMP contacts are personal\n  data. Collect what the objective needs, nothing more.\n\n## Confidence grading\n\nGrade the **inventory** and the **attribution** separately. A host can be a\nconfirmed live service and an unconfirmed asset of your target at once, and\nconflating the two is the most common reporting error in domain recon.\n\n- **Confirmed asset** — under a domain whose registration you verified, or on a\n  netblock reassigned to the target by name, or serving a certificate the target\n  demonstrably controls, and corroborated by a second independent source.\n- **Probable asset** — one strong infrastructure fingerprint (shared DKIM key,\n  same mail tenant label, same provider-assigned nameserver pair, distinctive\n  favicon or body string) with nothing contradicting it.\n- **Unconfirmed** — shared-hosting or CDN addresses, bundled-certificate names,\n  `org:`-only attribution, or an aggregator result whose underlying record you\n  have not seen.\n\nPer-technique criteria in the technique skills override these where more specific.\n\n## Worked example\n\nEngagement: a client is acquiring `meridian-freight.test` and wants its\ninternet-facing estate before signing. Scope: the apex plus any domain the\nregistrant demonstrably controls. Boundary: resolution allowed, no brute-forcing,\nno HTTP contact.\n\nStep 2: five-year-old registration, registrant redacted but country `NL`, a\nMicrosoft 365 tenant, and TXT tokens for a support desk, an identity provider and\na GitHub organization. That GitHub org name is the highest-value item in the entire\nrecord set and it cost one lookup.\n\nStep 3 returns 74 candidates, and a certificate-subject search surfaces\n`meridian-logistics-group.test`, which is not in the brief. Back through step 2:\nsame M365 tenant label in its MX, so same operator. Included, client notified.\n\nStep 4: 31 resolve, nine of those to third-party CNAMEs — relationships, not\nassets. `uat-portal` sits in a small Dutch hosting netblock distinct from\neverything else, which makes it the lead of the engagement.\n\nStep 5: that UAT host had 443 and 3306 observed open five weeks earlier. Also\neleven hosts sharing a favicon hash, which looked like a hidden estate until the\nhash turned out to belong to a stock CMS theme — the dead end, and exactly the\nkind that inflates a report if you skip the check.\n\nStep 6: a public repo in the GitHub org holds a CI config naming two internal\nhostnames absent from DNS. They do not resolve; they still matter, because the\nacquirer inherits those systems.\n\nStep 7: third consecutive source adds nothing, `web02` accounted for, every vendor\nchased. Complete, with one stated gap — the apex wildcard cert means subdomains\nissued after it are invisible to CT. Step 8: Dutch registrant country plus the\nsibling domain plus the group name in the cert subject point at a holding\nstructure, so it goes to `x-ray-a-company`.\n\n## Pivots out\n\n| Selector | Goes to |\n|---|---|\n| Legal entity, group name, jurisdiction | `x-ray-a-company`, `who-really-owns-it` |\n| Emails and phone numbers | `what-an-email-reveals`, `whose-number-is-this` |\n| Named employees from archives or metadata | `find-anyone` |\n| Developer handles from repositories | `hunt-a-handle` |\n| Documents pulled from the estate | `secrets-in-file-metadata` |\n| Breach exposure for the domain's mailboxes | `what-leaked-about-you` |\n| The whole asset and entity set, for structure | `graph-the-network` |\n\n## Legal and ToS notes\n\nPassive collection from third-party datasets is lawful research in most\njurisdictions; the boundary is traffic to the target and access to non-public\nsystems. Registrant data recovered from historical WHOIS is personal data under\nGDPR even though it was once public, so you need a lawful basis and must minimize.\nScan-platform and archive terms restrict bulk redistribution — cite findings, do\nnot republish datasets. A discovered exposure authorizes a report to the operator\nor the relevant CERT and nothing else. And in due diligence, confirm you hold the\nclient's written authority for the scope you are running: \"our client is buying\nthem\" is not authorization from the target.\n","# Recon a domain passively\n\nTurn one domain into a defensible map of an organization's internet-facing estate\nplus the owner behind it. The techniques live in other skills; what this workflow\ncontributes is the **order**, the **inventory**, and the **stopping rule**. Two\nfailure modes to avoid from the start: enumerating for hours and producing 400\nhostnames with no attribution, dates or priority, which is not a map; and drifting\nactive without noticing, because one probe \"just to check if it's up\" ends the\npassive claim. Decide the passive boundary before step 2, not during it.\n\n## Ordering logic\n\nEach stage feeds the next, and the sequence is cheapest-and-quietest first:\n\n| Order | Stage | Why here |\n|---|---|---|\n| 1 | Registration and DNS | Defines the perimeter. Without the apex set and the registrant you do not know what is in scope |\n| 2 | Name expansion | Archival sources only. Costs nothing, touches nothing, produces the candidate list everything else consumes |\n| 3 | Resolution and inventory | Converts names to addresses, which is what infrastructure lookups take as input |\n| 4 | Infrastructure and services | Needs stage 3's addresses. Third-party scan data only |\n| 5 | Content, history, code, tech stack | Needs hostnames and org names from earlier stages as search terms, and reuses artifacts already collected |\n| 6 | Owner attribution | The registrant, tenant and organization names surfaced above are the input |\n\nRun stages 1–5 as a loop, not a line. Every stage produces new selectors that\nbelong back at stage 1 or 2. Stop looping when the stopping rule in step 7 is met.\n\n## Step 1 — Authorized scope\n\nState in writing: the subject (which domains and netblocks, and which adjacent ones\nare explicitly excluded), the objective, the jurisdictions involved, and the\npassive boundary — specifically whether DNS resolution, wordlist brute-forcing and\nany HTTP contact with the target are permitted. Read\n[..\u002F..\u002FETHICS.md](..\u002F..\u002FETHICS.md). If being noticed matters, set up attribution\nhygiene with `investigate-without-getting-made` before querying anything.\n\n**Done when** subject, objective, out-of-bounds list, jurisdiction and passive\nboundary are written down, and you know which of the three grey activities you may\nperform.\n\n## Step 2 — Registration and DNS baseline\n\nRun `who-owns-this-domain` on every in-scope apex. You want registrar, dates and\nstatus, nameservers, the full record set, and the mail and SaaS fingerprints TXT, MX,\nDKIM and CAA give up. Where registration is redacted, pull historical WHOIS in the\nsame pass.\n\n**Done when** every apex has a registration record with a retrieval timestamp,\na complete record set, and a list of named third-party vendors extracted from its\nDNS.\n\n## Step 3 — Expand the name space\n\nRun `find-hidden-subdomains`. Certificate Transparency and passive DNS first, because\nthey are free, historical and invisible. Feed it the organization names from step 2 as\nwell as the domains — a certificate-subject search finds sibling and acquired domains\nnobody put in the brief.\n\n**Done when** you have a deduplicated candidate hostname list with the source and\nfirst-seen date recorded per name, and any newly discovered apex domains have been\npushed back through step 2.\n\n## Step 4 — Resolve and start the inventory\n\nClassify each candidate: resolves to an address, resolves to a third-party CNAME, or\ndoes not resolve. Build the inventory now rather than at the end — retrofitting\nprovenance onto a list you already collected is how findings lose their timestamps.\nThe schema and per-row fields are in\n[reference\u002Fasset-inventory.md](reference\u002Fasset-inventory.md).\n\n**Done when** every candidate is in one of the three buckets with a resolution\ntimestamp, every resolving host has an IP and an ASN, and every third-party CNAME\nis attributed to a named vendor.\n\n## Step 5 — Infrastructure and services\n\nRun `find-exposed-servers` over the addresses and netblocks from step 4. Query scan\nplatforms only — no port scanning, no service probing. Use the certificate and\nfavicon pivots to catch hosts that share the target's infrastructure without sharing\nits DNS, and note anything that looks unintentionally exposed.\n\n**Done when** each in-scope IP has its observed ports and services with scan\ndates, each netblock has an owner from its RIR record, and any infrastructure\nfound only through cert or favicon pivots has been added to the inventory and\nattribution-graded.\n\n## Step 6 — Content, history, code and tech stack\n\nThree sources, in this order:\n\n- `read-deleted-pages` for the estate as it used to be: retired hostnames, old\n  staff pages, exposed paths, pre-CDN infrastructure references.\n- `google-like-a-spy` for what is indexed now on the hosts you found — documents,\n  directory listings, configs, forgotten portals.\n- `secrets-in-git-history` for the org names, GitHub organization slugs, cloud\n  tenant labels and project IDs surfaced in steps 2 to 5.\n\nIf imagery matters — a logo reused across a network of sites, a stock photo posing as\nan office — run `find-the-original-image`. Shared images tie sites together when DNS\nand registration do not.\n\nThen assemble the tech stack from what you now hold: headers and cookies in archived\ncopies and scan records, certificate issuers, CNAME targets, JavaScript and asset\npaths, CSP directives, favicon hashes, and the SaaS fingerprints from step 2. Where\nyou need a live page, read a third-party scan of it instead of fetching it.\n\n**Done when** archived and indexed content is reviewed for the top-priority\nhostnames, code exposure is documented or ruled out, new hostnames have gone back\nthrough step 4, and the stack is documented per host with the artifact each\nconclusion rests on and versions marked claimed rather than verified.\n\n## Step 7 — Decide whether the map is done\n\nCompleteness is a judgement, so make it against criteria:\n\n- Two consecutive new sources produced no new assets. Saturation, not exhaustion, is\n  the signal.\n- Every discovered name is resolved or classified, and every resolving host has an\n  owner and an attribution grade.\n- Naming conventions have no unexplained gaps: if `web01` and `web03` are in the\n  inventory, you have accounted for `web02`.\n- Every named vendor and tenant from step 2 has yielded assets or been ruled out.\n- The objective from step 1 can be answered from the inventory.\n\nA failing criterion tells you exactly which stage to re-enter.\n\n**Done when** all five pass, or the remaining gaps are written up as stated\nlimitations rather than left implicit.\n\n## Step 8 — Hand off the owner\n\nIf the registrant, certificate subject, RIR reassignment or tenant label resolves\nto a legal entity rather than an individual, the domain work is finished and a\ncorporate investigation starts: hand the entity name and jurisdiction to\n`x-ray-a-company`, take registry and beneficial-ownership questions to\n`who-really-owns-it`, and send recovered emails to `what-an-email-reveals`. Do not\nattempt corporate structure from DNS artifacts — DNS shows operators, not\nshareholders.\n\n**Done when** every owner-side selector is routed to the right skill or recorded as\na dead end with the reason.\n\n## Step 9 — Report\n\nRun `write-the-intel-brief`. Lead with the asset inventory, then the attribution\nchain, then anything that appears unintentionally exposed, then the limitations\nfrom step 7. **Done when** every claim traces to an inventory row with a source and\ntimestamp, and every finding carries a confidence grade.\n\n## Where this goes wrong\n\n- **Scope creep through pivots.** Enumeration produces sibling domains endlessly and\n  each looks like the next target. If it is not in the step 1 subject list it is a\n  finding to report, not a workstream to start.\n- **Silent drift into active.** Resolution, brute-forcing and HTTP probing sit on a\n  spectrum, and tools blur it — passive collectors have active modes one flag away,\n  and one careless flag ends the passive claim for the engagement.\n- **Inventory without attribution.** Shared hosting, CDN addresses and bundled certs\n  attach assets to your target that are not the target's, and an ungraded inventory\n  row is a liability. Relatedly, a vulnerable SaaS tenant the target merely uses is\n  a supply-chain finding and must be phrased as one.\n- **Stale data presented as current.** Archives, CT and scan records are all\n  historical, and undated findings are not findings.\n- **Stopping at the first quiet moment.** No new results usually means one source\n  saturated, not the estate mapped — which is what step 7 catches.\n- **Over-collection.** Staff names from archived pages and SNMP contacts are personal\n  data. Collect what the objective needs, nothing more.\n\n## Confidence grading\n\nGrade the **inventory** and the **attribution** separately. A host can be a\nconfirmed live service and an unconfirmed asset of your target at once, and\nconflating the two is the most common reporting error in domain recon.\n\n- **Confirmed asset** — under a domain whose registration you verified, or on a\n  netblock reassigned to the target by name, or serving a certificate the target\n  demonstrably controls, and corroborated by a second independent source.\n- **Probable asset** — one strong infrastructure fingerprint (shared DKIM key,\n  same mail tenant label, same provider-assigned nameserver pair, distinctive\n  favicon or body string) with nothing contradicting it.\n- **Unconfirmed** — shared-hosting or CDN addresses, bundled-certificate names,\n  `org:`-only attribution, or an aggregator result whose underlying record you\n  have not seen.\n\nPer-technique criteria in the technique skills override these where more specific.\n\n## Worked example\n\nEngagement: a client is acquiring `meridian-freight.test` and wants its\ninternet-facing estate before signing. Scope: the apex plus any domain the\nregistrant demonstrably controls. Boundary: resolution allowed, no brute-forcing,\nno HTTP contact.\n\nStep 2: five-year-old registration, registrant redacted but country `NL`, a\nMicrosoft 365 tenant, and TXT tokens for a support desk, an identity provider and\na GitHub organization. That GitHub org name is the highest-value item in the entire\nrecord set and it cost one lookup.\n\nStep 3 returns 74 candidates, and a certificate-subject search surfaces\n`meridian-logistics-group.test`, which is not in the brief. Back through step 2:\nsame M365 tenant label in its MX, so same operator. Included, client notified.\n\nStep 4: 31 resolve, nine of those to third-party CNAMEs — relationships, not\nassets. `uat-portal` sits in a small Dutch hosting netblock distinct from\neverything else, which makes it the lead of the engagement.\n\nStep 5: that UAT host had 443 and 3306 observed open five weeks earlier. Also\neleven hosts sharing a favicon hash, which looked like a hidden estate until the\nhash turned out to belong to a stock CMS theme — the dead end, and exactly the\nkind that inflates a report if you skip the check.\n\nStep 6: a public repo in the GitHub org holds a CI config naming two internal\nhostnames absent from DNS. They do not resolve; they still matter, because the\nacquirer inherits those systems.\n\nStep 7: third consecutive source adds nothing, `web02` accounted for, every vendor\nchased. Complete, with one stated gap — the apex wildcard cert means subdomains\nissued after it are invisible to CT. Step 8: Dutch registrant country plus the\nsibling domain plus the group name in the cert subject point at a holding\nstructure, so it goes to `x-ray-a-company`.\n\n## Pivots out\n\n| Selector | Goes to |\n|---|---|\n| Legal entity, group name, jurisdiction | `x-ray-a-company`, `who-really-owns-it` |\n| Emails and phone numbers | `what-an-email-reveals`, `whose-number-is-this` |\n| Named employees from archives or metadata | `find-anyone` |\n| Developer handles from repositories | `hunt-a-handle` |\n| Documents pulled from the estate | `secrets-in-file-metadata` |\n| Breach exposure for the domain's mailboxes | `what-leaked-about-you` |\n| The whole asset and entity set, for structure | `graph-the-network` |\n\n## Legal and ToS notes\n\nPassive collection from third-party datasets is lawful research in most\njurisdictions; the boundary is traffic to the target and access to non-public\nsystems. Registrant data recovered from historical WHOIS is personal data under\nGDPR even though it was once public, so you need a lawful basis and must minimize.\nScan-platform and archive terms restrict bulk redistribution — cite findings, do\nnot republish datasets. A discovered exposure authorizes a report to the operator\nor the relevant CERT and nothing else. And in due diligence, confirm you hold the\nclient's written authority for the scope you are running: \"our client is buying\nthem\" is not authorization from the target.\n",{"description":7},"main","58843b159d7a4050d6b785a98b908cce505c0b92","agent\u002Fskills\u002Frecon-a-domain-passively",0,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent","https:\u002F\u002Fgithub.com\u002FReihantt6","reihsns.web.id","2026-08-19 20:08:18",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Reihantt6\u002Fsns-myagent --skill recon-a-domain-passively",{"tool":38,"command":39},"bunx","bunx skills add Reihantt6\u002Fsns-myagent --skill recon-a-domain-passively",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Reihantt6\u002Fsns-myagent --skill recon-a-domain-passively","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Frecon-a-domain-passively\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"reference\u002Fasset-inventory.md","REFERENCE","参考文档",6875,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Frecon-a-domain-passively\u002Freference\u002Fasset-inventory.md",[53,60,67,74,81,88],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M77XDCYZ407XYMF2T4P6F7VT","youtube-transcript","Extract transcripts from YouTube videos. Use when the user asks for a transcript, subtitles, or captions of a YouTube video and provides a YouTube URL (youtube.com\u002Fwatch?v=, youtu.be\u002F, or similar). Supports output with or without timestamps.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-transcript\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M77XD7PBC98J6MXGJJ2TJ8DX","youtube-thumbnail-design","YouTube thumbnail design with specific dimensions, contrast rules, and mobile preview optimization. Covers safe zones, text placement, face expression psychology, and A\u002FB testing. Use for: YouTube thumbnails, video cover images, click-through optimization. Triggers: youtube thumbnail, thumbnail design, video thumbnail, click through rate, ctr optimization, youtube cover, video cover image, thumbnail maker, thumbnail tips, youtube design, video preview image","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-thumbnail-design\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M77XD2541C8HXJ6RHYZP4NGJ","youtube-short-maker","Make YouTube Shorts that hold attention with Pexo — vertical 9:16, fast-paced, hook in the first 3 seconds. Describe your topic and Pexo writes the script, generates the shots, picks the models, and assembles a finished Short with music and captions. Use for YouTube Shorts: \"youtube short\", \"make a youtube short\", \"shorts video\", \"short-form video\". NOT for long-form or landscape video.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-short-maker\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M77XCXKVSYK7KTZ3PQBVVGFD","xcode-project-setup","Safely modifies Xcode projects (.pbxproj) to add Swift Packages and link files. Use this skill whenever an iOS project needs dependencies installed (e.g. Firebase, Alamofire).","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fxcode-project-setup\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M77XCR1DV8ZQK2NHWKVY4EWX","x402","Set up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key. Two setups it works out up front — \"just use it\" (set up a wallet so you or Claude Code can run cloud browser tasks paid from the wallet — Claude writes and runs throwaway scripts, nothing touches your codebase) or \"build it in\" (install the SDK and write the key + code into your project). Walks through wallet setup, funding, .env, and a ~$1 test run. Use when the user asks about x402, pay-per-use, USDC payments, or wants Browser Use Cloud without an API key. For the free-tier signup (reverse-CAPTCHA → API key), use `browser-use cloud signup` or the `cloud` skill instead.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fx402\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M77XCMD3R3ZBZQQSW6E0793B","x-twitter-scraper","Build GitHub Copilot workflows with Xquik X API SDKs, REST endpoints, hosted Apify Actor runs, MCP tools, TweetClaw OpenClaw plugin installs, signed webhooks, tweet search, user lookup, follower exports, media actions, and agent automation.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fx-twitter-scraper\u002FSKILL.md",[],[]]