Ricerca prefisso BGP
Inserisci un prefisso (o un singolo indirizzo). Risposta dalla nostra copia giornaliera della tabella di routing globale.
206.39.0.0/16
Annunciato esattamente
- 206.39.0.0/16AS721United States Department of Defense (DoD)RPKI Nessun ROA206.39.0.0
- Registro
- ARIN · Stati Uniti · 30 mag 1995
- Blocco assegnato
- 206.36.0.0 – 206.39.255.255
Rotte che lo coprono
Nessuna rotta meno specifica lo copre.
Rotte più specifiche
- 206.39.0.0/23AS56United States Department of Defense (DoD)RPKI Nessun ROA206.39.0.0
- 206.39.10.0/24AS5180United States Department of Defense (DoD)RPKI Nessun ROA206.39.10.0
- 206.39.11.0/24AS5180United States Department of Defense (DoD)RPKI Nessun ROA206.39.11.0
- 206.39.12.0/24AS5180United States Department of Defense (DoD)RPKI Nessun ROA206.39.12.0
- 206.39.13.0/24AS5180United States Department of Defense (DoD)RPKI Nessun ROA206.39.13.0
- 206.39.14.0/24AS1556United States Department of Defense (DoD)RPKI Nessun ROA206.39.14.0
- 206.39.16.0/24AS1540Headquarters, USAISCRPKI Nessun ROA206.39.16.0
- 206.39.28.0/24AS1554United States Department of Defense (DoD)RPKI Nessun ROA206.39.28.0
- 206.39.32.0/23AS1540Headquarters, USAISCRPKI Nessun ROA206.39.32.0
- 206.39.34.0/24AS1540Headquarters, USAISCRPKI Nessun ROA206.39.34.0
- 206.39.35.0/24AS1556United States Department of Defense (DoD)RPKI Nessun ROA206.39.35.0
- 206.39.36.0/24AS1563United States Department of Defense (DoD)RPKI Nessun ROA206.39.36.0
- 206.39.38.0/24AS1562United States Department of Defense (DoD)RPKI Nessun ROA206.39.38.0
- 206.39.39.0/24AS1561United States Department of Defense (DoD)RPKI Nessun ROA206.39.39.0
- 206.39.40.0/24AS1540Headquarters, USAISCRPKI Nessun ROA206.39.40.0
- 206.39.41.0/24AS1540Headquarters, USAISCRPKI Nessun ROA206.39.41.0
- 206.39.56.0/24AS391Air Force Systems NetworkingRPKI Nessun ROA206.39.56.0
- 206.39.58.0/24AS391Air Force Systems NetworkingRPKI Nessun ROA206.39.58.0
- 206.39.60.0/24AS56United States Department of Defense (DoD)RPKI Nessun ROA206.39.60.0
- 206.39.62.0/24AS56United States Department of Defense (DoD)RPKI Nessun ROA206.39.62.0
- 206.39.63.0/24AS56United States Department of Defense (DoD)RPKI Nessun ROA206.39.63.0
- 206.39.152.0/23AS1540Headquarters, USAISCRPKI Nessun ROA206.39.152.0
- 206.39.153.0/24AS1540Headquarters, USAISCRPKI Nessun ROA206.39.153.0
- 206.39.155.0/24AS1540Headquarters, USAISCRPKI Nessun ROA206.39.155.0
- 206.39.172.0/24AS367United States Department of Defense (DoD)RPKI Nessun ROA206.39.172.0
- 206.39.200.0/24AS5133United States Department of Defense (DoD)RPKI Nessun ROA206.39.200.0
- 206.39.201.0/24AS5133United States Department of Defense (DoD)RPKI Nessun ROA206.39.201.0
- 206.39.203.0/24AS687United States Department of Defense (DoD)RPKI Nessun ROA206.39.203.0
- 206.39.244.0/24AS3474United States Department of Defense (DoD)RPKI Nessun ROA206.39.244.0
- 206.39.245.0/24AS3474United States Department of Defense (DoD)RPKI Nessun ROA206.39.245.0
- 206.39.250.0/24AS27064United States Department of Defense (DoD)RPKI Nessun ROA206.39.250.0
Questo testo non è ancora disponibile in italiano. Viene mostrato in inglese finché non sarà pubblicata una traduzione.
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 144.122.0.0/16 (Middle East Technical University, AS1967). This tool looks a prefix up in our daily copy of the global routing table and shows three things:
- Exact announcements: which AS originates exactly this prefix. More than one origin (a MOAS) is normal for anycast services and some multihomed networks, and suspicious otherwise.
- Covering routes: less-specific announcements that contain it. Traffic follows the most specific route, so a covering route matters if the more-specific one disappears.
- More-specifics: announcements inside it, which may belong to other networks (customers, or a hijack).
Each announced route is also checked against the RPKI: whether a ROA authorises its origin AS.
The table is the view from APNIC’s route collector. Most of the global table is the same from everywhere, but a route that is filtered before it reaches that collector will not appear.
Domande frequenti
Why is my /24 not listed but a /16 is?
Your addresses are announced as part of the larger block, and no one announces the /24 separately. That is the normal case for most customers of a provider.
What is a more-specific hijack?
Someone announces a longer prefix inside your space. Because routers prefer the most specific route, traffic goes to them. RPKI with a strict max length makes such announcements invalid.
Can I enter a single address?
Yes. The tool then shows the most specific announced route that contains it.
Correlati
- Validatore di rotte RPKIL'AS di origine di una rotta è autorizzato da un ROA?
- Ricerca ASNTitolare, registro e tutti i prefissi annunciati da un AS.
- Ricerca IPASN, provider, route, DNS inverso e posizione di qualsiasi indirizzo.
- Calcolatore CIDRRete, broadcast, maschere e numero di host per qualsiasi prefisso.