جست‌وجوی پیشوند BGP
یک پیشوند (یا یک نشانی) وارد کنید. از نسخهٔ روزانهٔ ما از جدول جهانی مسیریابی پاسخ داده می‌شود.
205.138.0.0/15
دقیقاً اعلام‌شده
- 205.138.0.0/15AS3561CenturyLink Communications, LLCRPKI بدون ROA205.138.0.0
- ثبت‌کننده
- ARIN · ایالات متحده · ۲۶ بهمن ۱۳۷۳
- بلوک واگذارشده
- 205.138.0.0 – 205.139.255.255
مسیرهای پوشاننده
هیچ مسیر کلی‌تری آن را نمی‌پوشاند.
مسیرهای جزئی‌تر
- 205.138.24.0/21AS3561CenturyLink Communications, LLCRPKI بدون ROA205.138.24.0
- 205.138.32.0/21AS3561CenturyLink Communications, LLCRPKI بدون ROA205.138.32.0
- 205.138.40.0/21AS3561CenturyLink Communications, LLCRPKI بدون ROA205.138.40.0
- 205.138.112.0/22AS3561CenturyLink Communications, LLCRPKI بدون ROA205.138.112.0
- 205.138.116.0/22AS3561CenturyLink Communications, LLCRPKI بدون ROA205.138.116.0
- 205.138.120.0/21AS3561CenturyLink Communications, LLCRPKI بدون ROA205.138.120.0
- 205.138.144.0/20AS3561CenturyLink Communications, LLCRPKI بدون ROA205.138.144.0
- 205.138.168.0/22AS3561CenturyLink Communications, LLCRPKI بدون ROA205.138.168.0
- 205.138.172.0/22AS3561CenturyLink Communications, LLCRPKI بدون ROA205.138.172.0
- 205.138.224.0/20AS209CenturyLink Communications, LLCRPKI بدون ROA205.138.224.0
- 205.138.240.0/20AS3561CenturyLink Communications, LLCRPKI بدون ROA205.138.240.0
- 205.138.242.0/24AS13458DAVIDSON KEMPNER CAPITAL MANAGEMENT LPRPKI بدون ROA205.138.242.0
- 205.138.243.0/24AS3561CenturyLink Communications, LLCRPKI بدون ROA205.138.243.0
- 205.138.247.0/24AS396167Blackhawk Network, Inc.RPKI بدون ROA205.138.247.0
- 205.138.249.0/24AS10753Level 3 Parent, LLCRPKI بدون ROA205.138.249.0
- 205.139.16.0/20AS3561CenturyLink Communications, LLCRPKI بدون ROA205.139.16.0
- 205.139.21.0/24AS3561CenturyLink Communications, LLCRPKI بدون ROA205.139.21.0
- 205.139.32.0/19AS3561CenturyLink Communications, LLCRPKI بدون ROA205.139.32.0
- 205.139.64.0/20AS3561CenturyLink Communications, LLCRPKI بدون ROA205.139.64.0
- 205.139.68.0/24AS3561CenturyLink Communications, LLCRPKI بدون ROA205.139.68.0
- 205.139.88.0/23AS3561CenturyLink Communications, LLCRPKI بدون ROA205.139.88.0
- 205.139.96.0/20AS3561CenturyLink Communications, LLCRPKI بدون ROA205.139.96.0
- 205.139.102.0/24AS203Level 3 Parent, LLCRPKI بدون ROA205.139.102.0
- 205.139.103.0/24AS203Level 3 Parent, LLCRPKI بدون ROA205.139.103.0
- 205.139.104.0/22AS203Level 3 Parent, LLCRPKI بدون ROA205.139.104.0
- 205.139.108.0/24AS203Level 3 Parent, LLCRPKI بدون ROA205.139.108.0
- 205.139.110.0/24AS30031Mimecast North America IncRPKI بدون ROA205.139.110.0
- 205.139.111.0/24AS30031Mimecast North America IncRPKI بدون ROA205.139.111.0
- 205.139.112.0/20AS3561CenturyLink Communications, LLCRPKI بدون ROA205.139.112.0
- 205.139.128.0/19AS3561CenturyLink Communications, LLCRPKI بدون ROA205.139.128.0
- 205.139.132.0/24AS3561CenturyLink Communications, LLCRPKI بدون ROA205.139.132.0
- 205.139.142.0/24AS22013Guardian Analytics, Inc.RPKI بدون ROA205.139.142.0
- 205.139.144.0/22AS19701Yodlee Inc.RPKI بدون ROA205.139.144.0
- 205.139.154.0/24AS22013Guardian Analytics, Inc.RPKI بدون ROA205.139.154.0
- 205.139.160.0/20AS3561CenturyLink Communications, LLCRPKI بدون ROA205.139.160.0
این متن هنوز به فارسی در دسترس نیست. تا انتشار ترجمه به انگلیسی نمایش داده می‌شود.
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.
پرسش‌های پرتکرار
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.