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

AS23833 · 

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

Warning: AS23833 (MARUSAN-NET) announces 1 IPv4 and 0 IPv6 prefixes. 4 warnings

AS pageAS23833
HolderMARUSAN-NET - Marusan Securities Co., LTD.
AllocationAPNIC, Japan (JP), allocated 2003-06-16
Prefixes (IPv4 / IPv6)1 / 0
RPKI valid0% (0 / 1)
Upstreams and peers1

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 1 announced prefixes have no ROA (RPKI not found): 202.61.1.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 AS23833 and a max length equal to the prefix length:

    202.61.1.0/24 AS23833 max-length /24

    Open in RPKI / ROA validator Guide

  3. Warning

    No abuse contact is published for AS23833.

    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

  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: AS23833 announces 1 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Warning: 1 of 1 announced prefixes have no ROA (RPKI not found): 202.61.1.0/24.
  • Pass: Every announced prefix has an IRR route object.
  • Info: One upstream or peer seen (AS17676): an outage there takes the whole network off the internet.
HolderMARUSAN-NET - Marusan Securities Co., LTD.
IPv4 prefixes1
IPv6 prefixes0
RPKI1 not found
Downstream networks0
Routes to fix
PrefixRPKI
202.61.1.0/24 No ROA

Upstreams and peers seen to the left 1

AS17676 SoftBank Corp.

Announced prefixes 1

202.61.1.0/24

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

Open in ASN & BGP prefix lookup
Registration No abuse contact is published for AS23833.
  • Pass: Found at rdap.apnic.net.
  • Warning: No abuse contact is published for AS23833.
NameMARUSAN-NET
HandleAS23833
RangeAS23833
CountryJP
Statusactive
Last changed2004-11-11T20:56:03Z
Allocation
Registry (RIR)APNIC
CountryJapan (JP)
Delegated on2003-06-16
StatusAllocated
Delegated rangeAS23773 – AS23836

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 YO946JP

Source: https://rdap.apnic.net/autnum/23833. 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 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