domain-discovery

Domain Discovery Skill

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "domain-discovery" with this command: npx skills add transilienceai/communitytools/transilienceai-communitytools-domain-discovery

Domain Discovery Skill

Purpose

Find and validate the official company domain using web search, WHOIS lookups, and common TLD pattern testing.

Operations

  1. search_official_domain

Search for the company's official website using web search engines.

Input:

{ "company_name": "string (required)" }

Process:

  • Construct search query: "{company_name} official website"

  • Execute web search

  • Extract top domain results

  • Filter out social media, news sites, directories

Search Query Templates:

"{company_name}" official website "{company_name}" homepage site:{company_name}.com OR site:{company_name}.io

  1. check_common_tlds

Test common TLD variations for the company name.

TLD Priority Order:

.com → .io → .co → .org → .net → .ai → .dev → .app

Process:

  • Normalize company name (lowercase, remove spaces/special chars)

  • Test each TLD in priority order

  • Verify domain resolves (DNS A record exists)

  • Check if homepage contains company name

Example:

Company: "Acme Corporation" Test: acme.com, acmecorp.com, acme.io, acmecorp.io, ...

  1. whois_lookup

Query WHOIS database for domains registered to the company.

Command:

whois {domain} | grep -i "Registrant|Organization|Admin"

Fields to Extract:

  • Registrant Organization

  • Registrant Name

  • Admin Email Domain

  • Creation Date

  • Name Servers

  1. validate_domain

Verify the discovered domain belongs to the target company.

Validation Checks:

  • Homepage title contains company name

  • Meta description mentions company

  • WHOIS registrant matches company name

  • Social media links point to expected profiles

Output

{ "skill": "domain_discovery", "company": "string", "results": { "primary_domain": "string", "alternative_domains": ["array"], "validation": { "title_match": "boolean", "whois_match": "boolean", "confidence": "High|Medium|Low" }, "whois_data": { "registrant": "string", "created": "date", "nameservers": ["array"] } }, "evidence": [ { "type": "search_result", "query": "string", "result": "string" }, { "type": "whois", "field": "string", "value": "string" } ] }

Detection Patterns

Company Name Normalization

"Acme Corporation" → acme, acmecorp, acme-corp "The Widget Co." → widget, widgetco, thewidget "ABC Technologies Inc" → abc, abctech, abctechnologies

Domain Validation Signals

Signal Weight Description

Title contains company name +30 Strong validation

WHOIS registrant matches +40 Definitive ownership

Meta description mentions +20 Supporting evidence

Social links present +10 Weak validation

Error Handling

  • If no domain found via search, prompt for domain hint

  • If WHOIS fails, continue with DNS-based validation

  • If multiple candidates, return all with confidence scores

  • Never assume - always validate ownership signals

Rate Limiting

  • Web search: 10 requests/minute

  • WHOIS: 5 requests/minute

  • DNS resolution: No hard limit

Security Considerations

  • Never attempt unauthorized access

  • Only use public WHOIS data

  • Respect robots.txt on discovered domains

  • Log all queries for audit trail

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

cve-testing

No summary provided by upstream source.

Repository SourceNeeds Review
General

hackerone

No summary provided by upstream source.

Repository SourceNeeds Review
General

pentest

No summary provided by upstream source.

Repository SourceNeeds Review
General

domain-assessment

No summary provided by upstream source.

Repository SourceNeeds Review