ASN lookup

Find the origin networks observed for a public IP, or look up an autonomous system number and its holder. Routing observations are not subscriber identities.

Public routing and registration sources.

Public IP and ASN queries go to RIPEstat through our server. Special-use ASNs are classified locally. Results describe the source’s collected routing data.

Example report

Illustrative data. Run a lookup for live results.

Routing information found

Example report

The source returned origin or holder information for this resource. Routing context does not identify an individual subscriber or prove reachability.

Next step: Keep the queried resource and source time. Inspect each origin ASN, or use IP WHOIS for registration rather than routing.

AS13335
Queried resource
AS13335
Holder reported by RIPEstat WHOIS
Example network holder
AS name (registry)
EXAMPLE-AS
Organization
Example Network, Inc.
Regional registry
ARIN
Origin visibility at the source threshold
Observed
Source
RIPEstat / RIS
Collection window start (UTC)
2010-07-14T00:00:00Z
Collection window end (UTC)
2026-01-15T14:23:00.000Z

An IP question differs from an ASN question

  1. Choose a resource

    Enter a public address or an autonomous system number.

  2. Classify locally

    Special-use numbers receive a published category.

  3. RIPEstat view

    Address queries use network-info; numbers use as-overview.

  4. Interpret the observation

    Retain all origin ASNs, the prefix and source collection window.

Routing origin, registered holder and connectivity are different kinds of evidence.
On this page

Learn more about ASN lookup

How to use ASN lookup

Enter an autonomous system number such as AS15169, a plain decimal ASN, or a public IPv4 or IPv6 address. Select Look up to request the relevant result. An ASN lookup for an address reports the matching prefix and origin networks observed by the source. A query for a number reports that autonomous system's holder description and origin visibility. These are related views, but they answer different questions.

Read more

The ASN lookup does not accept a complete website URL, a domain name, a private IP or dotted ASN notation. For a domain, use DNS lookup to inspect the relevant A or AAAA records first, then submit the address you actually want to investigate. A domain can resolve to several addresses, so preserve which answer you selected rather than treating one result as the entire service.

What an ASN lookup identifies

An autonomous system number identifies a network within interdomain routing. It is different from an individual IP address, a domain name or a subscriber account. IANA allocates number resources to regional internet registries, which make assignments under their policies; see the IANA ASN registry. An ASN lookup helps place an address observation in network context.

Read an ASN lookup result correctly

For an IP query, read the matching BGP prefix and every origin ASN returned. The RIPEstat Network Info endpoint supplies this association from RIPE RIS information and documents an eight-hour dump basis. The ASN lookup fetch time describes when we obtained the response; it does not claim that the underlying routes were measured at that exact instant.

Read more

For a number query, the holder field is the name reported through RIPEstat's WHOIS source. Origin visibility follows the source's threshold, rather than a test of whether the whole network is online. Its AS Overview documentation explains that a transit-only network can return a negative origin status. network lookup keeps this distinction visible instead of labeling that network as down.

ASN lookup and multiple origins

A source can return more than one origin ASN for a matching prefix. The tool preserves that list. Do not silently choose the first result and describe it as the only network involved. Multiple origins deserve context from the operator, the observation period and more detailed routing evidence. A network lookup alone cannot determine whether the situation is intentional, transitional or erroneous.

The result provides a separate lookup action for each returned number. Use it to inspect the corresponding holder overview while retaining the original IP-to-prefix observation. A second network lookup answers the number question; it does not replace the earlier evidence about the specific address. Record both when the distinction matters in an operational report.

ASN lookup is different from IP registration

Use IP WHOIS lookup when the question concerns address registration and network lookup when it concerns the autonomous system view. Keep the source and time attached to each. If the answers differ, preserve the difference rather than merging the names into one unsupported identity. The mismatch may be the useful fact that tells an operator what to investigate next.

Special-use numbers in ASN lookup

Some ASN values are reserved for private use, documentation or other special purposes. This tool classifies those published ranges without sending them to RIPEstat. It does not invent a public holder. The private-use ranges include 64512–65534 and 4200000000–4294967294; documentation ranges include 64496–64511 and 65536–65551. The classification also distinguishes reserved values and the AS_TRANS transition number.

A network lookup for a private-use value can explain its category, but that value is not globally unique to one internal network. Two independent organizations can use the same private number. Likewise, an example ASN in a technical document is not evidence of a real public operator. Keep the classification beside the result when explaining it to someone else.

The form lets you stop the current wait or clear the displayed query and result. These controls do not alter routing data. A public number query uses the holder overview, while an IP query uses the network-info endpoint. Inspecting an origin number starts a new, separately sourced query; save the original address-to-prefix result first if you need both observations in a support report.

ASN lookup limitations and missing results

Routing collectors observe the routes available through their participating peers. A missing prefix or origin in one source is not a universal proof that no route exists anywhere. A timeout, rate limit or provider error is a different condition again. The network lookup reports request failures explicitly and leaves unavailable fields unset instead of converting absence into a negative security verdict.

Read more

This interface does not perform traceroute, test packet delivery, enumerate every prefix belonging to an ASN or validate route origin authorization through RPKI. Those tasks require different data and methods. A network lookup should help you choose the next appropriate investigation, not imply that one organization label certifies routing correctness, ownership, reachability or trustworthiness.

Common ASN lookup questions

Does the ASN prove which ISP I pay?

No. The visible network can be a parent organization, infrastructure supplier, VPN exit or another intermediary. An ASN lookup provides network context, not your billing relationship. Compare the observation with the service architecture you actually use and confirm uncertain relationships with the provider. A surprising name is a reason to investigate, not evidence of wrongdoing by itself.

Does a negative origin status mean an outage?

No. The status uses the source's defined observation threshold and can be negative for a transit-only network. It is not a direct availability check. Preserve the source query window when supplied and test the affected destination separately. Do not report an outage solely because an ASN lookup does not show origin visibility in this particular view.

Can I use ASN lookup as an abuse or reputation score?

The result contains no fraud score or abuse verdict. Many independent users and services can share a large network, and registration information does not establish individual conduct. Use the methodology to understand how this site separates observations from conclusions. A useful ASN lookup ends with clearly labeled evidence and a justified next step, rather than a claim that the number itself proves someone is safe or malicious.

methodology

What should I do when several origin ASNs are returned?

Preserve every returned number and the matching prefix. Multiple origins require operator and timing context; selecting the first value would discard evidence. This page alone cannot decide whether the arrangement is intentional or erroneous.

Can a private-use ASN identify one public organization?

No. Independent networks can reuse private numbers. The tool classifies published special-use ranges without inventing a global holder record. Keep that category with the value when discussing an internal routing configuration.

Is retrieval time the moment the underlying routes were measured?

No. The source has its own observation period and update basis. Fetch time says when this interface obtained the response. Preserve both kinds of context rather than describing a cached routing association as a live packet-level measurement.

Does this validate route origin authorization?

No. An observed origin association and RPKI authorization are different questions. The interface does not perform the latter check. Likewise, an ASN holder label is not a reachability result or a security guarantee.

Can I submit a domain instead of an IP or number?

Resolve the domain first with the DNS tool, then choose the relevant public address. A name can have several answers or change over time. Keep the chosen address beside the network result so the association remains clear.