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

28.5.0.0/16 ·

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

Warning: 28.5.0.0/16 is announced by AS27064 (DNIC-ASBLK-27032-27159). 14 warnings

Announced as28.5.0.0/16
Origin ASAS27064 DNIC-ASBLK-27032-27159
HolderPrivate Customer
AllocationARIN, United States (US), allocated 1996-03-11
Size65,536 addresses

What to fix

  1. Warning

    28.5.0.0/16 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: 28.5.0.0/16
    origin: AS27064
    max-length: 16

    Open in RPKI / ROA validator Guide

  2. Warning

    28.5.6.0/23 from AS27064 is RPKI not found: no ROA covers it. 28.5.6.0/23

    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: 28.5.6.0/23
    origin: AS27064
    max-length: 23

    Open in RPKI / ROA validator Guide

  3. Warning

    28.5.8.0/23 from AS27064 is RPKI not found: no ROA covers it. 28.5.8.0/23

    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: 28.5.8.0/23
    origin: AS27064
    max-length: 23

    Open in RPKI / ROA validator Guide

  4. Warning

    28.5.10.0/23 from AS27064 is RPKI not found: no ROA covers it. 28.5.10.0/23

    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: 28.5.10.0/23
    origin: AS27064
    max-length: 23

    Open in RPKI / ROA validator Guide

  5. Warning

    28.5.12.0/23 from AS27064 is RPKI not found: no ROA covers it. 28.5.12.0/23

    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: 28.5.12.0/23
    origin: AS27064
    max-length: 23

    Open in RPKI / ROA validator Guide

  6. Warning

    28.5.14.0/23 from AS27064 is RPKI not found: no ROA covers it. 28.5.14.0/23

    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: 28.5.14.0/23
    origin: AS27064
    max-length: 23

    Open in RPKI / ROA validator Guide

  7. Warning

    28.5.16.0/23 from AS27064 is RPKI not found: no ROA covers it. 28.5.16.0/23

    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: 28.5.16.0/23
    origin: AS27064
    max-length: 23

    Open in RPKI / ROA validator Guide

  8. Warning

    28.5.18.0/23 from AS27064 is RPKI not found: no ROA covers it. 28.5.18.0/23

    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: 28.5.18.0/23
    origin: AS27064
    max-length: 23

    Open in RPKI / ROA validator Guide

  9. Warning

    28.5.20.0/23 from AS27064 is RPKI not found: no ROA covers it. 28.5.20.0/23

    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: 28.5.20.0/23
    origin: AS27064
    max-length: 23

    Open in RPKI / ROA validator Guide

  10. Warning

    28.5.22.0/23 from AS27064 is RPKI not found: no ROA covers it. 28.5.22.0/23

    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: 28.5.22.0/23
    origin: AS27064
    max-length: 23

    Open in RPKI / ROA validator Guide

  11. Warning

    28.5.24.0/23 from AS27064 is RPKI not found: no ROA covers it. 28.5.24.0/23

    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: 28.5.24.0/23
    origin: AS27064
    max-length: 23

    Open in RPKI / ROA validator Guide

  12. Warning

    No IRR route object for 28.5.0.0/16 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: 28.5.0.0/16
    origin: AS27064

    Open in ASN & BGP prefix lookup

  13. Warning

    Reverse DNS is not delegated for 28.5.0.0/16, 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

  14. Warning

    No abuse contact is published for 28.5.0.0/16.

    Other networks send reports of spam, attacks and hacked machines to the abuse contact. Without one, reports go nowhere and blocklists may list the whole range.

    Fix: Add an abuse contact to the registration: abuse-c in the RIPE database, an Abuse POC at ARIN, an abuse mailbox (IRT) at APNIC, AFRINIC or LACNIC.

    Open in WHOIS / RDAP lookup

Checks

Routing and RPKI 28.5.0.0/16 from AS27064 is RPKI not found: no ROA covers it.
  • Pass: Announced as 28.5.0.0/16 by AS27064.
  • Warning: 28.5.0.0/16 from AS27064 is RPKI not found: no ROA covers it.
  • Warning: 28.5.6.0/23 from AS27064 is RPKI not found: no ROA covers it. 28.5.6.0/23
  • Warning: 28.5.8.0/23 from AS27064 is RPKI not found: no ROA covers it. 28.5.8.0/23
  • Warning: 28.5.10.0/23 from AS27064 is RPKI not found: no ROA covers it. 28.5.10.0/23
  • Warning: 28.5.12.0/23 from AS27064 is RPKI not found: no ROA covers it. 28.5.12.0/23
  • Warning: 28.5.14.0/23 from AS27064 is RPKI not found: no ROA covers it. 28.5.14.0/23
  • Warning: 28.5.16.0/23 from AS27064 is RPKI not found: no ROA covers it. 28.5.16.0/23
  • Warning: 28.5.18.0/23 from AS27064 is RPKI not found: no ROA covers it. 28.5.18.0/23
  • Warning: 28.5.20.0/23 from AS27064 is RPKI not found: no ROA covers it. 28.5.20.0/23
  • Warning: 28.5.22.0/23 from AS27064 is RPKI not found: no ROA covers it. 28.5.22.0/23
  • Warning: 28.5.24.0/23 from AS27064 is RPKI not found: no ROA covers it. 28.5.24.0/23
  • Warning: No IRR route object for 28.5.0.0/16 with origin AS27064.
  • Pass: Seen by 98% of RIPE RIS peers.
Route28.5.0.0/16
Origin ASAS27064 DNIC-ASBLK-27032-27159 - United States Department of Defense (DoD) No ROA
Visibility (RIS peers)313 / 320
First seen2026-09-15
Covering prefixes28.0.0.0/8
More-specific routes 23
More-specific routeOrigin ASRPKI
28.5.6.0/23 AS27064 No ROA
28.5.8.0/23 AS27064 No ROA
28.5.10.0/23 AS27064 No ROA
28.5.12.0/23 AS27064 No ROA
28.5.14.0/23 AS27064 No ROA
28.5.16.0/23 AS27064 No ROA
28.5.18.0/23 AS27064 No ROA
28.5.20.0/23 AS27064 No ROA
28.5.22.0/23 AS27064 No ROA
28.5.24.0/23 AS27064 No ROA
28.5.26.0/23 AS27064
28.5.28.0/23 AS27064
28.5.66.0/23 AS27064
28.5.68.0/23 AS27064
28.5.130.0/23 AS27064
28.5.132.0/23 AS27064
28.5.144.0/23 AS27064
28.5.0.0/24 AS27064
28.5.1.0/24 AS27064
28.5.3.0/24 AS27064
28.5.5.0/24 AS27064
28.5.56.0/24 AS27064
28.5.132.0/24 AS27064

Source: RIPEstat (RIPE NCC RIS, Routinator)

Open in ASN & BGP prefix lookup
Reverse DNS Reverse DNS is not delegated for 28.5.0.0/16, so its addresses have no PTR records.
  • Warning: Reverse DNS is not delegated for 28.5.0.0/16, so its addresses have no PTR records.
Reverse zones 1
ZoneNameservers
5.28.in-addr.arpa Not delegated
Open in DNS lookup
Registration No abuse contact is published for 28.5.0.0/16.
  • Pass: Found at rdap.arin.net.
  • Warning: No abuse contact is published for 28.5.0.0/16.
NameDISA-DODNET-MDA-IPV4-1
HandleNET-28-5-0-0-1
Range28.5.0.0 – 28.5.255.255
Statusactive
Registered2026-02-05T12:31:39-05:00
Last changed2026-02-05T12:31:39-05:00
Allocation
Registry (RIR)ARIN
CountryUnited States (US)
Delegated on1996-03-11
StatusAllocated
Delegated range28.0.0.0/8 (28.0.0.0 – 28.255.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 Private Customer

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