tech-stack-teardown
Reverse-engineer a company's sales, marketing, and outbound technology stack from public signals. This runbook checks DNS records, website source code, optional Apify technology profiling, blacklist databases, and public complaint signals. It works for one…
8 steps · start to finish.
- 1Step 1
Environment Setup
▶Create the results directory and verify local tools before inspecting any target.
mkdir -p /app/results command -v dig >/dev/null || { echo "ERROR: dig is required"; exit 1; } command -v curl >/dev/null || { echo "ERROR: curl is required"; exit 1; } command -v python3 >/dev/null || { echo "ERROR: python3 is required"; exit 1; } python3 -m pip install requests python-dotenvIf
APIFY_API_TOKENis present, record that paid profiling is available. Never write the token value to logs or output files. - 2Step 2
Resolve Inputs
▶Normalize the requested domains before scanning.
- 3Step 3
DNS and Email Infrastructure Scan
▶For each domain, collect MX, SPF, DKIM, DMARC, TXT, and CNAME records. Check common DKIM selectors such as google, selector1, selector2, s1, s2, k1, k2, mandrill, pm, smtp, and em. Also inspect…
- 4Step 4
Website Source Inspection
▶Fetch each homepage and inspect HTML, script URLs, meta tags, form handlers, and framework signatures.
- 5Step 5
Optional Apify Technology Profiling
▶When APIFY_API_TOKEN is available and no_apify is false, run the Apify Technology Profiling Engine for deeper detection. Treat this as a paid step with an estimated cost near $0.005 per domain. If…
- 6Step 6
Blacklist and Complaint Checks
▶Check each domain against major DNS-based blacklists: Spamhaus, Barracuda, SpamCop, SORBS, SURBL, and URIBL. Add public complaint searches for spam, unsolicited email, cold email, blacklist…
- 7Step 7
Report Generation
▶Generate /app/results/tech_stack_report.md with one section per company:
- 8Step 8
Iterate on Errors (max 3 rounds)
▶If any required output is missing, malformed, or lacks evidence for a claimed finding, perform up to 3 correction rounds: