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.
160.22.26.0/23 ·
Warning: 160.22.26.0/23 is announced by AS152806 (IDNIC-SINARTECH-AS-ID). 1 warning
| Announced as | 160.22.26.0/23 |
|---|---|
| Origin AS | AS152806 IDNIC-SINARTECH-AS-ID |
| Holder | IDNIC-SINARTECH-ID |
| Allocation | APNIC, Indonesia (ID), assigned 2024-05-30 |
| Size | 512 addresses |
| Abuse contact | noc@sinatech.id |
What to fix
-
Warning
Reverse DNS is not delegated for 160.22.26.0/23, so its addresses have no PTR records.
Mail receivers look up the PTR of the sending address and reject or spam-score mail without one; traceroutes and logs show bare numbers.
Fix: Create the reverse zones (domain objects for in-addr.arpa or ip6.arpa) at your RIR, pointing at your nameservers, or ask your provider to set PTR records.
Checks
Routing and RPKI Announced as 160.22.26.0/23 by AS152806.
- Pass: Announced as 160.22.26.0/23 by AS152806.
- Pass: 160.22.26.0/23 from AS152806 is RPKI valid.
- Pass: 160.22.26.0/24 from AS152806 is RPKI valid. 160.22.26.0/24
- Pass: 160.22.27.0/24 from AS152806 is RPKI valid. 160.22.27.0/24
- Pass: Seen by 100% of RIPE RIS peers.
- Info: The ROA 160.22.26.0/23 AS152806 allows announcements up to /24.
| Route | 160.22.26.0/23 |
|---|---|
| Origin AS | AS152806 IDNIC-SINARTECH-AS-ID - PT Sinar Technology Jaya RPKI valid |
| IRR route objects | RADB |
| Visibility (RIS peers) | 321 / 321 |
| First seen | 2024-07-27 |
| More-specific route | Origin AS | RPKI |
|---|---|---|
| 160.22.26.0/24 | AS152806 | RPKI valid |
| 160.22.27.0/24 | AS152806 | RPKI valid |
| ROA prefix | Max length | Origin AS |
|---|---|---|
| 160.22.26.0/23 | /23 | AS152806 |
| 160.22.26.0/23 | /24 | AS152806 |
Source: RIPEstat (RIPE NCC RIS, Routinator)
Open in ASN & BGP prefix lookupReverse DNS Reverse DNS is not delegated for 160.22.26.0/23, so its addresses have no PTR records.
- Warning: Reverse DNS is not delegated for 160.22.26.0/23, so its addresses have no PTR records.
| Zone | Nameservers |
|---|---|
| 26.22.160.in-addr.arpa | Not delegated |
| 27.22.160.in-addr.arpa | Not delegated |
Registration Found at rdap.arin.net.
- Pass: Found at rdap.arin.net.
| Name | IDNIC-SINARTECH-ID |
|---|---|
| Handle | 160.22.26.0 - 160.22.27.255 |
| Range | 160.22.26.0 – 160.22.27.255 |
| Country | ID |
| Status | active |
| Registered | 2024-06-06T01:07:04Z |
| Last changed | 2024-06-06T01:06:58Z |
| Abuse contact | noc@sinatech.id |
| Registry (RIR) | APNIC |
|---|---|
| Country | Indonesia (ID) |
| Delegated on | 2024-05-30 |
| Status | Assigned |
| Delegated range | 160.22.26.0/23 (160.22.26.0 – 160.22.27.255) |
Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.
| Role | Name | |
|---|---|---|
| abuse | IRT-SINARTECH-ID | noc@sinatech.id |
| technical, administrative | Tb Oemar Mahdy | noc@sinatech.id |
Source: https://rdap.arin.net/registry/ip/160.22.26.0/23. Registration data from rdap.arin.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: AS152806 is in PeeringDB as PT Sinar Technology Jaya.
- Info: Peering policy: Open.
- Info: Present at 8 internet exchanges with 8 ports (80G in total).
- Warning: No public NOC, policy or technical contact.
About the network that announces this space, so not in the fix list.
| Network | PT Sinar Technology Jaya (SinartechNet) |
|---|---|
| AS number | AS152806 |
| Type | Cable/DSL/ISP, Not Disclosed |
| Website | https://sinatech.id/ |
| IRR as-set | AS-SINATECH |
| Prefixes (IPv4 / IPv6) | 10000 / 10000 |
| Traffic | 20-50Gbps, Heavy Inbound |
| Peering policy | Open |
| Locations | Not Required |
| Ratio required | No |
| Contracts | Not Required |
| Last updated | 2026-10-12 |
Source: PeeringDB. Results are cached for an hour.
Open in PeeringDB lookup