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

155.85.0.0/19 ·

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

Warning: 155.85.0.0/19 is announced by AS4010 (DNIC-AS-04010). 3 warnings

Announced as155.85.0.0/19
Origin ASAS4010 DNIC-AS-04010
HolderHeadquarters, USAISC
AllocationARIN, United States (US), allocated 1991-12-03
Size8,192 addresses
Abuse contactdisa.columbus.ns.mbx.arin-registrations@mail.mil

What to fix

  1. Warning

    155.85.0.0/19 from AS4010 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 AS4010 and a max length equal to the prefix length.

    prefix: 155.85.0.0/19
    origin: AS4010
    max-length: 19

    Open in RPKI / ROA validator Guide

  2. Warning

    No IRR route object for 155.85.0.0/19 with origin AS4010.

    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: 155.85.0.0/19
    origin: AS4010

    Open in ASN & BGP prefix lookup

  3. Warning

    Reverse DNS is not delegated for 155.85.0.0/19, 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 155.85.0.0/19 from AS4010 is RPKI not found: no ROA covers it.
  • Pass: Announced as 155.85.0.0/19 by AS4010.
  • Warning: 155.85.0.0/19 from AS4010 is RPKI not found: no ROA covers it.
  • Warning: No IRR route object for 155.85.0.0/19 with origin AS4010.
  • Pass: Seen by 100% of RIPE RIS peers.
Route155.85.0.0/19
Origin ASAS4010 DNIC-AS-04010 - Headquarters, USAISC No ROA
Visibility (RIS peers)320 / 320
First seen2012-05-09

Source: RIPEstat (RIPE NCC RIS, Routinator)

Open in ASN & BGP prefix lookup
Reverse DNS Reverse DNS is not delegated for 155.85.0.0/19, so its addresses have no PTR records.
  • Warning: Reverse DNS is not delegated for 155.85.0.0/19, so its addresses have no PTR records.
  • Info: Only the first 10 of 32 reverse zones were checked.
Reverse zones 32
ZoneNameservers
0.85.155.in-addr.arpa Not delegated
1.85.155.in-addr.arpa Not delegated
2.85.155.in-addr.arpa Not delegated
3.85.155.in-addr.arpa Not delegated
4.85.155.in-addr.arpa Not delegated
5.85.155.in-addr.arpa Not delegated
6.85.155.in-addr.arpa Not delegated
7.85.155.in-addr.arpa Not delegated
8.85.155.in-addr.arpa Not delegated
9.85.155.in-addr.arpa Not delegated
Open in DNS lookup
Registration Found at rdap.arin.net.
  • Pass: Found at rdap.arin.net.
NameCEEIS16
HandleNET-155-85-0-0-2
Range155.85.0.0 – 155.85.255.255
Statusactive
Registered2025-08-23T14:09:02-04:00
Last changed2025-08-23T14:09:02-04:00
Abuse contactdisa.columbus.ns.mbx.arin-registrations@mail.mil
Allocation
Registry (RIR)ARIN
CountryUnited States (US)
Delegated on1991-12-03
StatusAllocated
Delegated range155.85.0.0/16 (155.85.0.0 – 155.85.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 Headquarters, USAISC

Source: https://rdap.arin.net/registry/ip/155.85.0.0/19. 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