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

110.4.91.0/24 ·

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

Warning: 110.4.91.0/24 is announced by AS9457 (DREAMX-AS-KR). 3 warnings

Announced as110.4.91.0/24
Origin ASAS9457 DREAMX-AS-KR
HolderABCLE-KR
AllocationAPNIC, South Korea (KR), allocated 2009-02-23
Size256 addresses
Abuse contacthostmaster@nic.or.kr

What to fix

  1. Warning

    110.4.91.0/24 from AS9457 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 AS9457 and a max length equal to the prefix length.

    prefix: 110.4.91.0/24
    origin: AS9457
    max-length: 24

    Open in RPKI / ROA validator Guide

  2. Warning

    No IRR route object for 110.4.91.0/24 with origin AS9457.

    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: 110.4.91.0/24
    origin: AS9457

    Open in ASN & BGP prefix lookup

  3. Warning

    Reverse DNS is not delegated for 110.4.91.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 110.4.91.0/24 from AS9457 is RPKI not found: no ROA covers it.
  • Pass: Announced as 110.4.91.0/24 by AS9457.
  • Warning: 110.4.91.0/24 from AS9457 is RPKI not found: no ROA covers it.
  • Warning: No IRR route object for 110.4.91.0/24 with origin AS9457.
  • Pass: Seen by 100% of RIPE RIS peers.
Route110.4.91.0/24
Origin ASAS9457 DREAMX-AS-KR - DREAMLINE CO. No ROA
Visibility (RIS peers)321 / 321
First seen2012-03-27
Covering prefixes110.4.88.0/22

Source: RIPEstat (RIPE NCC RIS, Routinator)

Open in ASN & BGP prefix lookup
Reverse DNS Reverse DNS is not delegated for 110.4.91.0/24, so its addresses have no PTR records.
  • Warning: Reverse DNS is not delegated for 110.4.91.0/24, so its addresses have no PTR records.
Reverse zones 1
ZoneNameservers
91.4.110.in-addr.arpa Not delegated
Open in DNS lookup
Registration Found at rdap.apnic.net.
  • Pass: Found at rdap.apnic.net.
NameABCLE-KR
Handle110.4.88.0 - 110.4.91.255
Range110.4.88.0 – 110.4.91.255
CountryKR
Statusactive
Abuse contacthostmaster@nic.or.kr
Allocation
Registry (RIR)APNIC
CountrySouth Korea (KR)
Delegated on2009-02-23
StatusAllocated
Delegated range110.4.88.0/22 (110.4.88.0 – 110.4.91.255)

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

Contacts
RoleNameEmail
technical, administrative IP Manager azcloud@abcle.co.kr
abuse IRT-KRNIC-KR hostmaster@nic.or.kr

Source: https://rdap.apnic.net/ip/110.4.91.0/24. Registration data from rdap.apnic.net, shown under its terms of use (terms): not for marketing or bulk collection.

Open in WHOIS / RDAP lookup
PeeringDB AS9457 is in PeeringDB as DREAMLINE.
  • Pass: AS9457 is in PeeringDB as DREAMLINE.
  • Info: Peering policy: Selective.
  • Info: Present at 3 internet exchanges with 6 ports (60G in total).

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

NetworkDREAMLINE (DREAMX)
AS numberAS9457
TypeCable/DSL/ISP, Asia Pacific
Websitehttp://dreamline.co.kr
IRR as-setAS-DREAMLINE
Prefixes (IPv4 / IPv6)750 / 0
Traffic300-500Gbps, Balanced
Peering policySelective
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2026-10-07
Contacts
Policyip@dreamline.co.kr
Public Relationsip@dreamline.co.kr

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup