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

130.22.89.0/24 ·

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

Warning: 130.22.89.0/24 is announced by AS27064 (DNIC-ASBLK-27032-27159). 3 warnings

Announced as130.22.89.0/24
Origin ASAS27064 DNIC-ASBLK-27032-27159
HolderDoD Network Information Center
AllocationARIN, United States (US), allocated 1988-04-28
Size256 addresses
Abuse contactdisa.columbus.ns.mbx.arin-registrations@mail.mil

What to fix

  1. Warning

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

    prefix: 130.22.89.0/24
    origin: AS27064
    max-length: 24

    Open in RPKI / ROA validator Guide

  2. Warning

    No IRR route object for 130.22.89.0/24 with origin AS27064.

    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: 130.22.89.0/24
    origin: AS27064

    Open in ASN & BGP prefix lookup

  3. Warning

    Reverse DNS is not delegated for 130.22.89.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 130.22.89.0/24 from AS27064 is RPKI not found: no ROA covers it.
  • Pass: Announced as 130.22.89.0/24 by AS27064.
  • Warning: 130.22.89.0/24 from AS27064 is RPKI not found: no ROA covers it.
  • Warning: No IRR route object for 130.22.89.0/24 with origin AS27064.
  • Pass: Seen by 100% of RIPE RIS peers.
Route130.22.89.0/24
Origin ASAS27064 DNIC-ASBLK-27032-27159 - United States Department of Defense (DoD) No ROA
Visibility (RIS peers)318 / 319
First seen2025-05-10
Covering prefixes130.22.0.0/16

Source: RIPEstat (RIPE NCC RIS, Routinator)

Open in ASN & BGP prefix lookup
Reverse DNS Reverse DNS is not delegated for 130.22.89.0/24, so its addresses have no PTR records.
  • Warning: Reverse DNS is not delegated for 130.22.89.0/24, so its addresses have no PTR records.
Reverse zones 1
ZoneNameservers
89.22.130.in-addr.arpa Not delegated
Open in DNS lookup
Registration Found at rdap.arin.net.
  • Pass: Found at rdap.arin.net.
NameSCWAN3
HandleNET-130-22-0-0-2
Range130.22.0.0 – 130.22.255.255
Statusactive
Registered2025-08-27T16:01:17-04:00
Last changed2025-08-27T16:01:17-04:00
Abuse contactdisa.columbus.ns.mbx.arin-registrations@mail.mil
Allocation
Registry (RIR)ARIN
CountryUnited States (US)
Delegated on1988-04-28
StatusAllocated
Delegated range130.22.0.0/16 (130.22.0.0 – 130.22.255.255)

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

Contacts
RoleNameEmail
registrant DoD Network Information Center

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

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