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.
Problem: AS214432 (NTT-Communications-Corporation Zhilian …) announces 148 IPv4 and 6 IPv6 prefixes. 1 problem · 3 warnings
| AS page | AS214432 |
|---|---|
| Holder | NTT-Communications-Corporation Zhilian Technology CO., LTD. |
| Allocation | RIPE NCC, United Kingdom (GB), allocated 2024-08-01 |
| Prefixes (IPv4 / IPv6) | 148 / 6 |
| RPKI valid | 90% (138 / 154) |
| Upstreams and peers | 12 |
| Peering policy | Open |
What to fix
-
Problem
9 of 154 announced prefixes are RPKI invalid: 79.182.32.0/24, 79.182.52.0/24, 79.182.75.0/24, 79.182.76.0/24, 79.182.123.0/24 (+4).
A ROA covers them but does not allow this origin or prefix length, so networks that filter (most large ones do) drop these routes.
Fix: Fix the ROAs (origin AS and max length) at your RIR, or stop announcing the routes.
-
Warning
1 of 154 announced prefixes have no ROA (RPKI not found): 61.100.38.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 AS214432 and a max length equal to the prefix length:
61.100.38.0/24 AS214432 max-length /24
-
Warning
9 of 154 announced prefixes have no IRR route object: 192.217.238.0/24, 2001:978:b01::/48, 207.152.104.0/24, 199.234.72.0/24, 207.152.105.0/24 (+4).
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 AS214432 in your RIR’s IRR database (or RADB).
route: 192.217.238.0/24 origin: AS214432 route6: 2001:978:b01::/48 origin: AS214432 route: 207.152.104.0/24 origin: AS214432
-
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 9 of 154 announced prefixes are RPKI invalid: 79.182.32.0/24, 79.182.52.0/24, 79.182.75.0/24, 79.182.76.0/24, 79.182.123.0/24 (+4).
- Pass: AS214432 announces 148 IPv4 and 6 IPv6 prefixes.
- Problem: 9 of 154 announced prefixes are RPKI invalid: 79.182.32.0/24, 79.182.52.0/24, 79.182.75.0/24, 79.182.76.0/24, 79.182.123.0/24 (+4).
- Warning: 1 of 154 announced prefixes have no ROA (RPKI not found): 61.100.38.0/24.
- Info: 138 of 154 announced prefixes are RPKI valid.
- Info: The RPKI state of 6 prefixes was not looked up (no ROA of AS214432 covers them; only the first 10 are checked).
- Warning: 9 of 154 announced prefixes have no IRR route object: 192.217.238.0/24, 2001:978:b01::/48, 207.152.104.0/24, 199.234.72.0/24, 207.152.105.0/24 (+4).
- Info: 12 upstreams and peers, 6 downstream networks seen.
| Holder | NTT-Communications-Corporation Zhilian Technology CO., LTD. |
|---|---|
| IPv4 prefixes | 148 |
| IPv6 prefixes | 6 |
| RPKI | 138 valid · 9 invalid · 1 not found · 6 not looked up |
| Without IRR route object | 9 |
| Downstream networks | 6 |
| Prefix | RPKI |
|---|---|
| 79.182.32.0/24 | RPKI invalid |
| 79.182.52.0/24 | RPKI invalid |
| 79.182.75.0/24 | RPKI invalid |
| 79.182.76.0/24 | RPKI invalid |
| 79.182.123.0/24 | RPKI invalid |
| 79.183.12.0/24 | RPKI invalid |
| 151.244.38.0/24 | RPKI invalid |
| 151.244.52.0/24 | RPKI invalid |
| 151.244.221.0/24 | RPKI invalid |
| 61.100.38.0/24 | No ROA |
Announced prefixes 154
Showing the first 100.
Source: RIPEstat (RIPE NCC RIS, Routinator, IRR); AS names: Team Cymru
Open in ASN & BGP prefix lookupRegistration Found at rdap.db.ripe.net.
- Pass: Found at rdap.db.ripe.net.
| Name | NTT-Communications-Corporation |
|---|---|
| Handle | AS214432 |
| Range | AS214432 |
| Status | active |
| Registered | 2024-08-01T13:00:17Z |
| Last changed | 2026-10-11T21:53:41Z |
| Abuse contact | report@zlidc.net |
| Registry (RIR) | RIPE NCC |
|---|---|
| Country | United Kingdom (GB) |
| Delegated on | 2024-08-01 |
| Status | Allocated |
| Delegated range | AS214432 |
Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.
| Role | Name | |
|---|---|---|
| registrant | Zhilian Technology CO., LTD. | |
| registrant | RIPE-NCC-END-MNT | |
| abuse | ZLIDC NOC | report@zlidc.net |
Source: https://rdap.db.ripe.net/autnum/214432. Registration data from rdap.db.ripe.net, shown under its terms of use (terms): not for marketing or bulk collection. Personal contacts in this registry are not shown.
Open in WHOIS / RDAP lookupPeeringDB No public NOC, policy or technical contact.
- Pass: AS214432 is in PeeringDB as Zhilian Technology CO., LTD..
- Info: Peering policy: Open.
- Info: No internet exchange ports are listed.
- Warning: No public NOC, policy or technical contact.
| Network | Zhilian Technology CO., LTD. (智联) |
|---|---|
| AS number | AS214432 |
| Type | Cable/DSL/ISP, Global |
| Website | https://zlidc.net |
| IRR as-set | AS-ZLIDC |
| Prefixes (IPv4 / IPv6) | 2000 / 2000 |
| Traffic | 100-200Gbps, Balanced |
| Peering policy | Open |
| Locations | Not Required |
| Ratio required | No |
| Contracts | Not Required |
| Last updated | 2026-07-26 |
Source: PeeringDB. Results are cached for an hour.
Open in PeeringDB lookup