Skip to content
thenetworkery

Network report

Who holds an IP address, prefix or AS number, how it is routed (origin AS, RPKI, IRR), its reverse DNS, blocklist listings and PeeringDB record, with what to fix first.

IP address, prefix or AS number

92.55.183.0/24 ·

curl -s "https://thenetworkery.com/api/v1/network-report?query=92.55.183.0%2F24"
JSON Docs

Warning: 92.55.183.0/24 is announced by AS35566 (KARTEL-AS Kar-Tel LLC). 3 warnings

Announced as92.55.183.0/24
Origin ASAS35566 KARTEL-AS Kar-Tel LLC
HolderTNSPLUS-MNT
AllocationRIPE NCC, Kazakhstan (KZ), allocated 2008-03-14
Size256 addresses
Abuse contactripe-kartel-mobile@beeline.kz

What to fix

  1. Warning

    92.55.183.0/24 from AS35566 is RPKI not found: no ROA covers it.

    Routes without a ROA are still accepted almost everywhere, but nothing protects them from a hijack.

    Fix: Create a ROA for this prefix with origin AS35566 and a max length equal to the prefix length.

    prefix: 92.55.183.0/24
    origin: AS35566
    max-length: 24

    Open in RPKI / ROA validator Guide

  2. Warning

    No IRR route object for 92.55.183.0/24 with origin AS35566.

    Many networks build their prefix filters from IRR data; without a route object some of them drop the route.

    Fix: Create a route object in your RIR’s IRR database (or RADB):

    route: 92.55.183.0/24
    origin: AS35566

    Open in ASN & BGP prefix lookup

  3. Warning

    Reverse DNS is not delegated for 92.55.183.0/24, so its addresses have no PTR records.

    Mail receivers look up the PTR of the sending address and reject or spam-score mail without one; traceroutes and logs show bare numbers.

    Fix: Create the reverse zones (domain objects for in-addr.arpa or ip6.arpa) at your RIR, pointing at your nameservers, or ask your provider to set PTR records.

    Open in DNS lookup

Checks

Routing and RPKI 92.55.183.0/24 from AS35566 is RPKI not found: no ROA covers it.
  • Pass: Announced as 92.55.183.0/24 by AS35566.
  • Warning: 92.55.183.0/24 from AS35566 is RPKI not found: no ROA covers it.
  • Warning: No IRR route object for 92.55.183.0/24 with origin AS35566.
  • Pass: Seen by 100% of RIPE RIS peers.
Route92.55.183.0/24
Origin ASAS35566 KARTEL-AS Kar-Tel LLC No ROA
Visibility (RIS peers)319 / 319
First seen2020-02-07
Covering prefixes92.55.176.0/20, 92.55.160.0/19

Source: RIPEstat (RIPE NCC RIS, Routinator)

Open in ASN & BGP prefix lookup
Reverse DNS Reverse DNS is not delegated for 92.55.183.0/24, so its addresses have no PTR records.
  • Warning: Reverse DNS is not delegated for 92.55.183.0/24, so its addresses have no PTR records.
Reverse zones 1
ZoneNameservers
183.55.92.in-addr.arpa Not delegated
Open in DNS lookup
Registration Found at rdap.db.ripe.net.
  • Pass: Found at rdap.db.ripe.net.
NameFTTB_2DayTelecom
Handle92.55.176.0 - 92.55.191.255
Range92.55.176.0 – 92.55.191.255
CountryKZ
Statusactive
Registered2017-07-09T17:52:37Z
Last changed2017-07-09T17:52:50Z
Abuse contactripe-kartel-mobile@beeline.kz
Allocation
Registry (RIR)RIPE NCC
CountryKazakhstan (KZ)
Delegated on2008-03-14
StatusAllocated
Delegated range92.55.160.0/19 (92.55.160.0 – 92.55.191.255)

Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.

Contacts
RoleNameEmail
registrant TNSPLUS-MNT
abuse Abuse-C Role ripe-kartel-mobile@beeline.kz

Source: https://rdap.db.ripe.net/ip/92.55.183.0/24. Registration data from rdap.db.ripe.net, shown under its terms of use (terms): not for marketing or bulk collection. Personal contacts in this registry are not shown.

Open in WHOIS / RDAP lookup
PeeringDB PeeringDB did not answer: HTTP 404
  • Warning: PeeringDB did not answer: HTTP 404

About the network that announces this space, so not in the fix list.

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup