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.
Checking routing, RPKI, reverse DNS, blocklists and the registry. This usually takes 3 to 10 seconds.
Warning: AS7529 (NETIRD) announces 9 IPv4 and 1 IPv6 prefixes. 3 warnings
| AS page | AS7529 |
|---|---|
| Holder | NETIRD - GMO NetIRD, Inc. |
| Allocation | APNIC, Japan (JP), allocated 1997-03-03 |
| Prefixes (IPv4 / IPv6) | 9 / 1 |
| RPKI valid | 50% (5 / 10) |
| Upstreams and peers | 12 |
| Peering policy | Open |
What to fix
-
Warning
5 of 10 announced prefixes have no ROA (RPKI not found): 202.34.8.0/24, 202.34.9.0/24, 202.34.15.0/24, 202.79.4.0/22, 219.99.64.0/20.
Without a ROA, networks cannot tell your routes from a hijack.
Fix: Create a ROA for each at your RIR portal, with origin AS7529 and a max length equal to the prefix length:
202.34.8.0/24 AS7529 max-length /24 202.34.9.0/24 AS7529 max-length /24 202.34.15.0/24 AS7529 max-length /24 202.79.4.0/22 AS7529 max-length /22 219.99.64.0/20 AS7529 max-length /20
-
Warning
No abuse contact is published for AS7529.
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.
-
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.
Checks
Routing and RPKI 5 of 10 announced prefixes have no ROA (RPKI not found): 202.34.8.0/24, 202.34.9.0/24, 202.34.15.0/24, 202.79.4.0/22, 219.99.64.0/20.
- Pass: AS7529 announces 9 IPv4 and 1 IPv6 prefixes.
- Warning: 5 of 10 announced prefixes have no ROA (RPKI not found): 202.34.8.0/24, 202.34.9.0/24, 202.34.15.0/24, 202.79.4.0/22, 219.99.64.0/20.
- Info: 5 of 10 announced prefixes are RPKI valid.
- Pass: Every announced prefix has an IRR route object.
- Info: 12 upstreams and peers, 19 downstream networks seen.
| Holder | NETIRD - GMO NetIRD, Inc. |
|---|---|
| IPv4 prefixes | 9 |
| IPv6 prefixes | 1 |
| RPKI | 5 valid · 5 not found |
| Downstream networks | 19 |
| Prefix | RPKI |
|---|---|
| 202.34.8.0/24 | No ROA |
| 202.34.9.0/24 | No ROA |
| 202.34.15.0/24 | No ROA |
| 202.79.4.0/22 | No ROA |
| 219.99.64.0/20 | No ROA |
Upstreams and peers seen to the left 12
Source: RIPEstat (RIPE NCC RIS, Routinator, IRR); AS names: Team Cymru
Open in ASN & BGP prefix lookupRegistration No abuse contact is published for AS7529.
- Pass: Found at rdap.apnic.net.
- Warning: No abuse contact is published for AS7529.
| Name | NETIRD |
|---|---|
| Handle | AS7529 |
| Range | AS7529 |
| Country | JP |
| Status | active |
| Last changed | 2025-12-16T20:28:59Z |
| Registry (RIR) | APNIC |
|---|---|
| Country | Japan (JP) |
| Delegated on | 1997-03-03 |
| Status | Allocated |
| Delegated range | AS7500 – AS7531 |
Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.
| Role | Name | |
|---|---|---|
| administrative, technical | Japan Network Information Center | hostmaster@nic.ad.jp |
| administrative, technical | JP00025313 |
Source: https://rdap.apnic.net/autnum/7529. Registration data from rdap.apnic.net, shown under its terms of use (terms): not for marketing or bulk collection.
Open in WHOIS / RDAP lookupPeeringDB No public NOC, policy or technical contact.
- Pass: AS7529 is in PeeringDB as NetIRD.
- Info: Peering policy: Open.
- Info: Present at 6 internet exchanges with 6 ports (70G in total).
- Warning: No public NOC, policy or technical contact.
| Network | NetIRD |
|---|---|
| AS number | AS7529 |
| Type | NSP, Regional |
| Website | https://www.netird.ad.jp/ |
| IRR as-set | AS-NETIRD |
| Prefixes (IPv4 / IPv6) | 300 / 100 |
| Traffic | 20-50Gbps, Balanced |
| Peering policy | Open |
| Locations | Not Required |
| Ratio required | No |
| Contracts | Not Required |
| Last updated | 2024-12-27 |
Source: PeeringDB. Results are cached for an hour.
Open in PeeringDB lookup