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

AS36457 · 

curl -s "https://thenetworkery.com/api/v1/network-report?query=AS36457"
JSON Docs

Warning: AS36457 (DISTR-21) announces 2 IPv4 and 0 IPv6 prefixes. 4 warnings

AS pageAS36457
HolderDISTR-21 - District Photo, Inc.
AllocationARIN, United States (US), assigned 2012-02-08
Prefixes (IPv4 / IPv6)2 / 0
RPKI valid50% (1 / 2)
Upstreams and peers2

What to fix

  1. Warning

    No IPv6 prefixes announced.

    Networks without IPv6 force their users through NAT64 or leave them unreachable from IPv6-only networks.

    Fix: Get an IPv6 allocation from your RIR (usually free with your IPv4 membership) and announce it.

    Open in ASN & BGP prefix lookup

  2. Warning

    1 of 2 announced prefixes have no ROA (RPKI not found): 65.122.25.0/24.

    Without a ROA, networks cannot tell your routes from a hijack.

    Fix: Create a ROA for each at your RIR portal, with origin AS36457 and a max length equal to the prefix length:

    65.122.25.0/24 AS36457 max-length /24

    Open in RPKI / ROA validator Guide

  3. Warning

    1 of 2 announced prefixes have no IRR route object: 65.122.25.0/24.

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

    Fix: Create route (IPv4) and route6 (IPv6) objects with origin AS36457 in your RIR’s IRR database (or RADB).

    route: 65.122.25.0/24
origin: AS36457

    Open in ASN & BGP prefix lookup

  4. Warning

    PeeringDB did not answer: HTTP 404

    Fix: Try again in a minute.

    Open in PeeringDB lookup

Checks

Routing and RPKI No IPv6 prefixes announced.
  • Pass: AS36457 announces 2 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Warning: 1 of 2 announced prefixes have no ROA (RPKI not found): 65.122.25.0/24.
  • Info: 1 of 2 announced prefixes are RPKI valid.
  • Warning: 1 of 2 announced prefixes have no IRR route object: 65.122.25.0/24.
  • Info: 2 upstreams and peers, 0 downstream networks seen.
HolderDISTR-21 - District Photo, Inc.
IPv4 prefixes2
IPv6 prefixes0
RPKI1 valid · 1 not found
Without IRR route object1
Downstream networks0
Routes to fix
PrefixRPKI
65.122.25.0/24 No ROA

Upstreams and peers seen to the left 2

AS33657 Comcast AS3356 Lumen AS3356

Announced prefixes 2

50.227.81.0/24 65.122.25.0/24

Source: RIPEstat (RIPE NCC RIS, Routinator, IRR); AS names: Team Cymru

Open in ASN & BGP prefix lookup
Registration Found at rdap.arin.net.
  • Pass: Found at rdap.arin.net.
NameDISTR-21
HandleAS36457
RangeAS36457
Statusactive
Registered2012-02-08T14:35:23-05:00
Last changed2012-02-08T14:35:23-05:00
Abuse contactgdixon@districtphoto.com
Allocation
Registry (RIR)ARIN
CountryUnited States (US)
Delegated on2012-02-08
StatusAssigned
Delegated rangeAS36457

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

Contacts
RoleNameEmail
registrant District Photo, Inc.

Source: https://rdap.arin.net/registry/autnum/36457. 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

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup