Autonomous system
AS202610 NEKO-AS NekoClaw Ltd
Hosting RIPE Network Services
Summary
NekoClaw Ltd
business enterprise uk
The AS handle NEKO-AS is held by NekoClaw Ltd.
What it's used for
- The address space carries enterprise network traffic, identified by the netname
NEKOCLAW-ENTERPRISE-NETWORKon both announced IPv4 prefixes. - The AS announces 512 IPv4 addresses across 2 prefixes and 2 IPv6 prefixes, with 3 observed routing neighbours.
- As a network services provider, the traffic consists of business and enterprise endpoints rather than residential subscriber eyeballs.
Notable
- The registrants for both IPv4 prefixes are listed as "Abuse Department; NekoClaw Ltd", which aligns with the AS holder.
- The address inventory is small and finely subdivided, consistent with an internal corporate estate or a small-scale service provider.
This description is AI-generated, best-effort context — not authoritative, and provided without any guarantee of accuracy. Source, and how to suggest an edit.
Interconnection
Peering at a glance
Internet exchanges
No exchange port on file. Many exchanges publish no participant list, so this is not proof of absence.
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-11-03, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 2 prefixes · 512 addresses IPv6 2 prefixes
| Country | Name | Prefixes |
|---|---|---|
| GB | United Kingdom | 4 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS202610- Registry name
- NEKO-AS
- Registrant
- neko-mnt
- Abuse contact
- abuse@edwardcode.ru
- Registered
- 2025-12-19
- Last changed
- 2026-10-18
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- NekoClaw Ltd
- Also known as
- nekoclaw
- Network type
- Network Services
- Scope
- Global
- Traffic ratio
- Balanced
- Peering policy
- Open
- IRR as-set
AS202610:AS-ALL- Website
- https://nekoclaw.moe
PeeringDB records are maintained by the network operator and are not independently verified. Treat them as a statement of intent rather than of fact. For the observed and recorded view, see peering, which lists the exchanges Packet Clearing House has a port on file for.
Routing security
RPKI and IRR
- RPKI
- 75% valid · 3 valid, 0 with no ROA 1 RPKI-invalid
- ROAs
- 3 authorising AS202610
- ASPA
- no ASPA record
- IRR
- 75% registered · 3 of 4 announcements
- Route objects
- 3 naming AS202610
Reputation
Classification and threat
Hosting Datacenter or cloud provider. Addresses are servers, not people.
Spamhaus DROP
Not on ASN-DROP The network as a whole is not listed.
No DROP prefixes None of its announced space is on the DROP prefix list.
Spamhaus DROP ("Don't Route Or Peer") lists space and networks run by, or hijacked for, spam and cybercrime operations: 448 networks and 1,851 prefixes, as published 2026-11-04. A short, high-confidence list, so a match is worth taking seriously, and absence from it says little on its own.
FBI IC3
No IC3 indicators Nothing from the FBI IC3 feed.
IC3 threat data is alpha. Absence of an indicator is not evidence of good behaviour, only of absence from this one feed.
Elsewhere