research-missing-as

Identify organizations and countries for ASes lacking WHOIS metadata.

4|Updated Dec 30, 2025
One-click install
npx skills add https://github.com/ipverse/as-overlay --skill research-missing-as
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: research-missing-as
Source: https://github.com/ipverse/as-overlay/tree/main
Command: npx skills add https://github.com/ipverse/as-overlay --skill research-missing-as

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps contributors identify the organization and country behind autonomous systems that actively announce prefixes but lack published WHOIS metadata, enabling accurate overlay updates.

Core Features & Use Cases

  • Manual research workflow: guides researchers to gather data from BGP, RDAP, PeeringDB, RADb, and reverse DNS to identify the responsible organization.
  • Overlay preparation: outputs a ready-to-submit overlay.json entry with either a full handle/description pair or a country-only entry when appropriate.
  • Evidence-based validation: emphasizes verification against primary sources to ensure accurate country codes and naming.

Quick Start

To begin, run this skill with an ASN, for example: /research-missing-as 11636

Frequently Asked Questions about research-missing-as

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

FAQPage Schema
How do I identify the organization and country for an AS with missing WHOIS metadata?

To identify AS organizations with missing WHOIS metadata, cross-check authoritative sources like BGP, RDAP, PeeringDB, and RADb to gather evidence for the responsible entity and its country code.

What sources should I cross-check to research an autonomous system lacking published WHOIS data?

When researching an autonomous system lacking WHOIS data, cross-check authoritative sources including BGP route announcements, RDAP, PeeringDB, RADb, and reverse DNS to validate the organization and country.

How do I produce a valid overlay.json entry for an AS missing metadata?

To produce a valid overlay.json entry, compile your research findings into a structured format containing a valid ASN, countryCode, and either a handle/description pair or a country-only entry.

When should I use a country-only entry instead of a full handle and description for overlay metadata?

Use a country-only entry for overlay metadata when you can verify the country code via BGP or PeeringDB but cannot confidently identify the specific organization handle and description from authoritative sources.

Can I use BGP and PeeringDB to correct missing AS metadata in missing.json?

Yes, you can use BGP and PeeringDB to correct missing AS metadata in missing.json by cross-referencing prefix announcements and peering details to identify the announcing organization and its country.

What are the limitations of using reverse DNS to identify an AS organization?

Reverse DNS provides supplementary evidence for identifying an AS organization but may lack authoritative accuracy, requiring validation against primary sources like RDAP and RADb before generating overlay corrections.