جست‌وجوی پیشوند BGP
یک پیشوند (یا یک نشانی) وارد کنید. از نسخهٔ روزانهٔ ما از جدول جهانی مسیریابی پاسخ داده می‌شود.
65.56.0.0/14
دقیقاً اعلام‌شده
- 65.56.0.0/14AS3356Level 3 Parent, LLCRPKI بدون ROA65.56.0.0
- ثبت‌کننده
- ARIN · ایالات متحده · ۳۰ شهریور ۱۳۸۰
- بلوک واگذارشده
- 65.56.0.0 – 65.59.255.255
مسیرهای پوشاننده
هیچ مسیر کلی‌تری آن را نمی‌پوشاند.
مسیرهای جزئی‌تر
- 65.56.240.0/21AS31775Greenlight Networks, LLCRPKI معتبر65.56.240.0
- 65.57.245.0/24AS3356Level 3 Parent, LLCRPKI بدون ROA65.57.245.0
- 65.57.248.0/24AS14127Iland Internet Solutions CorporationRPKI بدون ROA65.57.248.0
- 65.57.249.0/24AS14127Iland Internet Solutions CorporationRPKI بدون ROA65.57.249.0
- 65.57.250.0/24AS14127Iland Internet Solutions CorporationRPKI بدون ROA65.57.250.0
- 65.57.251.0/24AS14127Iland Internet Solutions CorporationRPKI بدون ROA65.57.251.0
- 65.57.252.0/24AS14127Iland Internet Solutions CorporationRPKI بدون ROA65.57.252.0
- 65.57.253.0/24AS14127Iland Internet Solutions CorporationRPKI بدون ROA65.57.253.0
- 65.57.254.0/24AS14127Iland Internet Solutions CorporationRPKI بدون ROA65.57.254.0
- 65.57.255.0/24AS14127Iland Internet Solutions CorporationRPKI بدون ROA65.57.255.0
- 65.59.112.0/24AS40443CDK Global, LLCRPKI بدون ROA65.59.112.0
- 65.59.113.0/24AS10461Eze Castle Software LLCRPKI بدون ROA65.59.113.0
- 65.59.246.0/24AS11135Cross Development/Montgomery LPRPKI معتبر65.59.246.0
- 65.59.247.0/24AS11135Cross Development/Montgomery LPRPKI معتبر65.59.247.0
- 65.59.254.0/24AS23089Hotwire CommunicationsRPKI بدون ROA65.59.254.0
- 65.59.255.0/24AS23089Hotwire CommunicationsRPKI بدون ROA65.59.255.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.