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

201.50.36.0/24 ·

curl -s "https://thenetworkery.com/api/v1/network-report?query=201.50.36.0%2F24"
JSON Docs

Warning: 201.50.36.0/24 is announced by AS9312 (XTOM). 1 warning

Announced as201.50.36.0/24
Origin ASAS9312 XTOM
HolderOwl Limited
AllocationRIPE NCC, United Arab Emirates (AE), allocated 2025-03-06
Size256 addresses
Abuse contactabuse@owl.net

What to fix

  1. Warning

    Reverse DNS is not delegated for 201.50.36.0/24, 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.

    Open in DNS lookup

Checks

Routing and RPKI Announced as 201.50.36.0/24 by AS9312.
  • Pass: Announced as 201.50.36.0/24 by AS9312.
  • Pass: 201.50.36.0/24 from AS9312 is RPKI valid.
  • Pass: Seen by 100% of RIPE RIS peers.
  • Info: The ROA 201.50.32.0/19 AS3214 allows announcements up to /24.
Route201.50.36.0/24
Origin ASAS9312 XTOM - xTom RPKI valid
IRR route objectsALTDB, RADB, RIPE
Visibility (RIS peers)317 / 318
First seen2026-06-27
ROAs covering this prefix
ROA prefixMax lengthOrigin AS
201.50.32.0/19 /24 AS3214
201.50.32.0/19 /24 AS3258
201.50.32.0/19 /24 AS4785
201.50.32.0/19 /24 AS6233
201.50.32.0/19 /24 AS8888
201.50.32.0/19 /24 AS9312

Source: RIPEstat (RIPE NCC RIS, Routinator)

Open in ASN & BGP prefix lookup
Reverse DNS Reverse DNS is not delegated for 201.50.36.0/24, so its addresses have no PTR records.
  • Warning: Reverse DNS is not delegated for 201.50.36.0/24, so its addresses have no PTR records.
Reverse zones 1
ZoneNameservers
36.50.201.in-addr.arpa Not delegated
Open in DNS lookup
Registration Found at rdap.lacnic.net.
  • Pass: Found at rdap.lacnic.net.
NameOWL-IPV4
Handle201.50.36.0 - 201.50.36.255
Range201.50.36.0 – 201.50.36.255
CountryHK
Statusactive
Registered2026-06-25T15:20:50Z
Last changed2026-07-15T04:41:36Z
Abuse contactabuse@owl.net
Allocation
Registry (RIR)RIPE NCC
CountryUnited Arab Emirates (AE)
Delegated on2025-03-06
StatusAllocated
Delegated range201.50.0.0/18 (201.50.0.0 – 201.50.63.255)

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

Contacts
RoleNameEmail
registrant Owl Limited
registrant owl
administrative, technical Owl Limited NOC abuse@owl.net
abuse Owl Limited NOC abuse@owl.net

Source: https://rdap.lacnic.net/rdap/ip/201.50.36.0/24. Registration data from rdap.lacnic.net, shown under its terms of use (terms): not for marketing or bulk collection.

Open in WHOIS / RDAP lookup
PeeringDB AS9312 is in PeeringDB as xTom Hong Kong.
  • Pass: AS9312 is in PeeringDB as xTom Hong Kong.
  • Info: Peering policy: Open.
  • Info: Present at 1 internet exchanges with 1 ports (10G in total).

About the network that announces this space, so not in the fix list.

NetworkxTom Hong Kong (xTom)
AS numberAS9312
TypeCable/DSL/ISP, Global
Websitehttps://xtom.com/
IRR as-setRADB::AS-XTOM
Prefixes (IPv4 / IPv6)1000 / 1000
Traffic50-100Gbps, Balanced
Peering policyOpen
Policy URLhttps://peering.xtom.com/
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Looking glasshttps://xtom.com/looking-glass/
Last updated2026-11-02
Contacts
Abuseabuse@xtom.com
NOCnoc@xtom.com
Salessales@xtom.com
Technicalsupport@xtom.com
Maintenancenoc@xtom.com
Policypeering@xtom.com

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup