cloud-infra-detector

Detect cloud providers from IP, DNS, HTTP, TLS, and IaC signals.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you determine which cloud provider, PaaS, and serverless/managed services power a target by turning scattered technical signals into an actionable infrastructure summary.

Core Features & Use Cases

  • Multi-signal cloud detection: Correlates IP attribution, DNS CNAME/TXT records, HTTP headers, and TLS certificate issuer details to infer infrastructure.
  • PaaS and serverless inference with implications: Detects platforms like Vercel/Netlify/Heroku and reports underlying cloud relationships when possible.
  • IaC and repo-based hints: Uses repository contents (e.g., Terraform, CloudFormation files) to strengthen attribution.
  • Use Case: Quickly assess what stack is backing a website/app during due diligence, migration planning, incident triage, or competitive research.

Quick Start

Use the cloud-infra-detector skill to analyze a target’s IP, DNS, HTTP headers, TLS certificate, and repository IaC signals and return a ranked set of detected cloud providers, PaaS platforms, and related infrastructure summary.

Frequently Asked Questions about cloud-infra-detector

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

FAQPage Schema
How do I identify cloud infrastructure and hosting providers from DNS and HTTP signals?

Cloud infrastructure identification correlates IP attribution, DNS CNAME/TXT records, HTTP headers, and TLS certificates to infer providers. It applies deterministic matching across provider-specific patterns to output structured detections with confidence-weighted signals.

What is the best way to detect PaaS platforms like Vercel or Heroku during a technology assessment?

Detecting PaaS platforms like Vercel or Heroku uses multi-signal correlation across DNS, HTTP, and TLS data to report underlying cloud relationships. It infers managed services and serverless architecture by matching provider-specific patterns during reconnaissance.

Can I use Terraform IaC files to strengthen cloud provider attribution?

Yes, repository IaC analysis uses Terraform and CloudFormation file contents to strengthen infrastructure attribution. It combines IaC hints with IP, DNS, HTTP, and TLS signals to produce a ranked set of detected cloud providers.

Does cloud detection work with partial evidence when investigating a target website?

Cloud detection works effectively with partial evidence by turning scattered technical signals into an actionable infrastructure summary. It applies deterministic matching to available signals, weighting confidence to infer cloud providers, PaaS platforms, and serverless services.

When do I need infrastructure attribution for incident triage or migration planning?

Infrastructure attribution is needed during due diligence, migration planning, incident triage, and competitive research to determine what stack backs a website. It identifies cloud providers, PaaS, and managed services powering the target.

What signals are required to perform accurate cloud detection and infrastructure identification?

Cloud detection requires IP attribution, DNS CNAME/TXT records, HTTP headers, TLS certificate issuer details, and repository IaC contents. It correlates these signals using YAML-defined discovery metadata to output confidence-weighted technology detections.