ASN profile
The network behind the space: identity, announced prefixes, transit, exchanges and space quality.
Every address and prefix lookup resolves to the autonomous system originating the space, which this report profiles in full. An ASN lookup starts here directly.
Identity
The AS number, name and description, the holding organisation, country and responsible RIR, allocation status and dates, and website. Fields the sources do not publish are n/a, not zero.
Announced space
IPv4 and IPv6 prefix counts, with a preview list. Each previewed prefix carries first and last seen dates for this AS and whether the announcement is ongoing. The preview is capped; true totals are shown beside it and the full list is paged through the API.
Space quality
The announced blocks drawn as a map, one cell per block. Two kinds of evidence feed it: reputation sampling of addresses, and active checks of whole blocks.
| Status | Meaning |
|---|---|
flagged | Anonymity services, high risk addresses or working proxies found in this block. |
mild | Infrastructure signals only. |
clean | Looked at, nothing found. |
unsampled | Not looked at. |
Each sampled block carries the number of addresses checked, the worst risk score seen, and an example address. Where the map is truncated, the true totals say so.
Unsampled is not clean.
Neighbours
Traffic relationships, split by direction:
- Upstreams. ASes carrying this network's traffic, its transit providers.
- Downstreams. ASes seen behind this network, its customers.
- Uncertain. Relationships the data cannot classify.
Each neighbour carries an observed strength value; higher means the relationship appears more strongly in routing data. The preview shows true counts, with the full list paged through the API.
Internet exchanges
Where the network peers publicly, from PeeringDB: exchange name, city, country and declared port speed. Missing exchange data is reported as unavailable, not as an empty list, and is not a finding that the network peers nowhere.
PeeringDB profile
What the network declares about itself on PeeringDB: network type, traffic volume, scope, traffic ratio, peering policy, website and IRR as-set, with the record's creation and update dates. A network with no record is marked as such. Plenty of legitimate networks skip PeeringDB, so no record is not in itself a finding.
Contacts
Abuse and general contact emails and the registered address, from the registry record and the routing databases.