Autonomous system
AS200833 Node-Catch FURKAN AYDINLI
Unclassified RIPE Enterprise
Summary
Node-Catch
business enterprise turkey
The AS handle NODE-CATCH is held by Node-Catch.
What it's used for
- The address space carries enterprise infrastructure, evidenced by reverse DNS entries pointing to
nodecatch.com. - The network announces 256 IPv4 addresses within a single /24 prefix (151.246.175.0/24) and maintains only 1 observed neighbour, indicating a small, self-contained business network rather than a transit or access provider.
- Traffic from this AS consists of web and API endpoints for the Node-Catch enterprise platform.
Notable
- The RDAP registrant for the announced prefix is listed as "FURKAN AYDINLI; Private Customer," which aligns with the registry holder name "Node-Catch FURKAN AYDINLI."
- The address inventory is minimal, consisting of a single contiguous /24 block with no IPv6 prefixes announced.
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.
Transit providers
1 upstream, 0 downstream and 1 adjacent networks observed; most-used upstreams first.
| AS | Network | Paths seen |
|---|---|---|
| AS40676 | Psychz Networks | 60 |
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-31, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 1 prefixes · 256 addresses IPv6 0 prefixes
| Country | Name | Prefixes |
|---|---|---|
| TR | Turkey | 1 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS200833- Registry name
- Node-Catch
- Registrant
- NODECATCH-MNT
- Abuse contact
- mtdadm@protonmail.com
- Registered
- 2026-02-19
- Last changed
- 2026-05-12
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- Node-Catch
- Network type
- Enterprise
- Scope
- Europe
- Traffic ratio
- Balanced
- Peering policy
- Open
- Website
- https://nodecatch.com
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
- 100% valid · 1 valid, 0 with no ROA
- ROAs
- 1 authorising AS200833
- ASPA
- no ASPA record
- IRR
- 100% registered · 1 of 1 announcements
- Route objects
- 2 naming AS200833
Reputation
Classification and threat
Unclassified Not in the curated lists. Most of the ~80,000 allocated ASNs are not.
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: 447 networks and 1,843 prefixes, as published 2026-11-01. 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