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

AS131944 ·

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

Warning: AS131944 (KADOKAWA-NET) announces 8 IPv4 and 0 IPv6 prefixes. 4 warnings

AS pageAS131944
HolderKADOKAWA-NET - KADOKAWA DWANGO CORPORATION
AllocationAPNIC, Japan (JP), allocated 2011-08-04
Prefixes (IPv4 / IPv6)8 / 0
RPKI valid100% (8 / 8)
Upstreams and peers1
Peering policySelective

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

    No abuse contact is published for AS131944.

    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

  3. Warning

    No IRR as-set is listed.

    Peers and route servers build prefix filters from the as-set. Without one they fall back to the AS number alone, which breaks as soon as you have customers.

    Fix: Create an as-set in your RIR’s IRR database and add it to your PeeringDB record.

    Open in PeeringDB lookup

  4. Warning

    No public NOC, policy or technical contact.

    Other networks use these addresses to set up peering and to reach you during an incident.

    Fix: Add a role contact (for example noc@ or peering@ an address you monitor) with visibility Public.

    Open in PeeringDB lookup

Checks

Routing and RPKI No IPv6 prefixes announced.
  • Pass: AS131944 announces 8 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Pass: All 8 announced prefixes are RPKI valid.
  • Pass: Every announced prefix has an IRR route object.
  • Info: One upstream or peer seen (AS2497): an outage there takes the whole network off the internet.
HolderKADOKAWA-NET - KADOKAWA DWANGO CORPORATION
IPv4 prefixes8
IPv6 prefixes0
RPKI8 valid
Downstream networks1

Upstreams and peers seen to the left 1

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

Open in ASN & BGP prefix lookup
Registration No abuse contact is published for AS131944.
  • Pass: Found at rdap.apnic.net.
  • Warning: No abuse contact is published for AS131944.
NameKADOKAWA-NET
HandleAS131944
RangeAS131944
CountryJP
Statusactive
Last changed2019-03-08T01:02:56Z
Allocation
Registry (RIR)APNIC
CountryJapan (JP)
Delegated on2011-08-04
StatusAllocated
Delegated rangeAS131905 – AS131992

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

Contacts
RoleNameEmail
administrative, technical Japan Network Information Center hostmaster@nic.ad.jp
administrative, technical JP00174413

Source: https://rdap.apnic.net/autnum/131944. 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 No IRR as-set is listed.
  • Pass: AS131944 is in PeeringDB as KADOKAWA CORPORATION.
  • Info: Peering policy: Selective.
  • Info: No internet exchange ports are listed.
  • Warning: No IRR as-set is listed.
  • Warning: No public NOC, policy or technical contact.
  • Info: The record was last updated 2022-10-26.
NetworkKADOKAWA CORPORATION
AS numberAS131944
TypeContent, Asia Pacific
Websitehttps://ir.kadokawa.co.jp/global/
Prefixes (IPv4 / IPv6)10 / 0
TrafficMostly Outbound
Peering policySelective
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2022-10-26

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup