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

AS7500 ·

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

Warning: AS7500 (M-ROOT-DNS) announces 4 IPv4 and 1 IPv6 prefixes. 3 warnings

AS pageAS7500
HolderM-ROOT-DNS - WIDE Project
AllocationAPNIC, Japan (JP), allocated 1997-03-03
Prefixes (IPv4 / IPv6)4 / 1
RPKI valid60% (3 / 5)
Upstreams and peers41
Peering policyOpen

What to fix

  1. Warning

    2 of 5 announced prefixes have no ROA (RPKI not found): 192.50.45.0/24, 202.13.183.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 AS7500 and a max length equal to the prefix length:

    192.50.45.0/24 AS7500 max-length /24
    202.13.183.0/24 AS7500 max-length /24

    Open in RPKI / ROA validator Guide

  2. Warning

    No abuse contact is published for AS7500.

    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 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 2 of 5 announced prefixes have no ROA (RPKI not found): 192.50.45.0/24, 202.13.183.0/24.
  • Pass: AS7500 announces 4 IPv4 and 1 IPv6 prefixes.
  • Warning: 2 of 5 announced prefixes have no ROA (RPKI not found): 192.50.45.0/24, 202.13.183.0/24.
  • Info: 3 of 5 announced prefixes are RPKI valid.
  • Pass: Every announced prefix has an IRR route object.
  • Info: 41 upstreams and peers, 2 downstream networks seen.
HolderM-ROOT-DNS - WIDE Project
IPv4 prefixes4
IPv6 prefixes1
RPKI3 valid · 2 not found
Downstream networks2
Routes to fix
PrefixRPKI
192.50.45.0/24 No ROA
202.13.183.0/24 No ROA

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

Open in ASN & BGP prefix lookup
Registration No abuse contact is published for AS7500.
  • Pass: Found at rdap.apnic.net.
  • Warning: No abuse contact is published for AS7500.
NameM-ROOT-DNS
HandleAS7500
RangeAS7500
CountryJP
Statusactive
Last changed2006-11-14T20:29:29Z
Allocation
Registry (RIR)APNIC
CountryJapan (JP)
Delegated on1997-03-03
StatusAllocated
Delegated rangeAS7500 – AS7531

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

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

Source: https://rdap.apnic.net/autnum/7500. 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 public NOC, policy or technical contact.
  • Pass: AS7500 is in PeeringDB as M-ROOT DNS Server.
  • Info: Peering policy: Open.
  • Info: Present at 41 internet exchanges with 41 ports (59G in total).
  • Warning: No public NOC, policy or technical contact.
NetworkM-ROOT DNS Server
AS numberAS7500
TypeNon-Profit, Global
Websitehttp://www.wide.ad.jp/
IRR as-setRADB::AS-M-ROOT
Prefixes (IPv4 / IPv6)6 / 2
Traffic20-100Mbps, Mostly Outbound
Peering policyOpen
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2026-11-02

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup