> ## Documentation Index
> Fetch the complete documentation index at: https://docs.abusix.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Network Management

> Enter and verify your networks to allow us to direct reports related to the networks you own.

[Network management](https://app.abusix.com/networks) is where you tell us which networks you are responsible for. We use public WHOIS databases (RIPE, ARIN, LACNIC, APNIC, AfriNIC) as the source of truth and refresh your data every 24 hours to keep it in sync as delegations and abuse contacts change.

Your network data serves as a reference layer across the platform:

* In [Guardian Ops](/docs/guardian-ops/introduction), it determines which network ranges and abuse contacts are available for filtering in your inbound processing rules and playbooks.
* The [reputation dashboard](https://app.abusix.com/reputation-dashboard) provides analytics for your network ranges, but only for [verified abuse contacts](#abuse-contact-verification).

Network management does not, by itself, change where abuse reports are sent or who receives them. It is about defining your scope — which networks and contacts you want to work with — so the rest of the platform can act on that.

Because we continuously resync against registry data, network ranges may reappear after deletion if they are still associated with your ASN or abuse contacts in the WHOIS records. This is by design — the network list reflects the current external source of truth rather than serving as a manually curated override.

You can import networks in three ways: by ASN, by abuse contact, or manually. Each method automatically discovers associated abuse contacts, but those contacts must be [verified](#abuse-contact-verification) before their networks are fully imported.

## Import by ASN

When you add an ASN, all associated network ranges are fetched from WHOIS databases (RIPE, ARIN, LACNIC, APNIC, AfriNIC) and imported in the background.

* Imported networks are linked to the ASN, **not** to an abuse contact
* Abuse contacts found for these networks are automatically discovered and added to your account, but remain **unverified** with 0 networks
* To import the full network list for a discovered abuse contact, you must [verify it](#abuse-contact-verification)

<Note>
  Discovered abuse contacts show 0 networks until verified. This is intentional — a single abuse contact can be responsible for hundreds of network ranges, while your imported ASN may only contain a small subset.
</Note>

## Import by Abuse Contact

When you add an abuse contact email address, a verification email is sent to that address. No networks are imported until you click the verification link.

* After verification, all networks associated with that contact are fetched from WHOIS databases and imported
* Once verified, the contact becomes independent — removing the ASN or manual network that originally discovered it will not delete the contact

## Manual Import

You can add a single network range (in CIDR notation) directly. The network is available in your account immediately.

* Only the specific CIDR you entered is added (unlike ASN import, which fetches all prefixes)
* Associated abuse contacts are automatically discovered but remain unverified, just like with ASN imports

## Abuse Contact Verification

Abuse contacts must be verified before their networks are imported. A single abuse contact can be responsible for hundreds of network ranges, so importing all of them without confirmation could flood your account with unrelated networks.

Until verified, an abuse contact shows **0 associated networks**. Once you complete verification, the contact's full set of networks is imported from WHOIS databases and the contact becomes independent of its original import source.