Autonomous system
AS209990 DIYAAELDIN-MOUSTAFA-TRADING-AS-KARMUZ
Unclassified RIPE
Summary
Karmuz
hosting netherlands small
The AS handle DIYAAELDIN-MOUSTAFA-TRADING-AS-KARMUZ is held by Karmuz.
What it's used for
- The space carries infrastructure for Karmuz, evidenced by the netname
KARMUZand reverse DNS entries pointing tono2ta.karmuz.net. - The AS announces 256 IPv4 addresses and 10 IPv6 prefixes, with 39 observed neighbours. This ratio of a small address inventory against a high neighbour count indicates a transit or peering-heavy role rather than a large access network.
- Traffic from this AS consists of web and API endpoints associated with the Karmuz platform, as indicated by the specific reverse DNS domain.
Notable
- The registrant
KARMUZ-NOC; Diyaaeldin Moustafa trading as Karmuzaligns with the AS holder and the reverse DNS domain. - The address inventory consists of a single /24 IPv4 block and multiple /47 and /48 IPv6 prefixes, all located in the Netherlands.
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
Recorded at 4 exchanges in 2 countries, largest first.
| Exchange | Location | Their address |
|---|---|---|
| The Frys Internet Exchange | Frysian, Netherlands | 2001:7f8:10f::3:3446:351 |
| Speed Internet Exchange | Dronten, Netherlands | 185.1.222.238 |
| InterIX Internet Exchange | Amsterdam, Netherlands | 2001:7f8:134::53 |
| Local Internet Exchange Düsseldorf | Düsseldorf, Germany | 185.1.155.170 |
Transit providers
17 upstream, 1 downstream and 24 adjacent networks observed; most-used upstreams first.
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-27, 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 10 prefixes
| Country | Name | Prefixes |
|---|---|---|
| NL | Netherlands | 11 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS209990- Registry name
- KARMUZ
- Registrant
- ELAUNIRA-MNT
- Abuse contact
- abuse@karmuz.net
- Registered
- 2025-12-02
- Last changed
- 2026-08-30
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- Karmuz
- Scope
- Europe
- Traffic ratio
- Mostly Outbound
- Peering policy
- Selective
- IRR as-set
AS209990:AS-KARMUZ- Present at
- 7 exchanges
- Facilities
- 2 facilities
- Website
- https://karmuz.net
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 · 20 valid, 0 with no ROA
- ROAs
- 8 authorising AS209990
- ASPA
- 4 declared providers
- IRR
- 100% registered · 20 of 20 announcements
- Route objects
- 33 naming AS209990
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: 446 networks and 1,852 prefixes, as published 2026-10-27. 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