Autonomous system
AS201233 DHS
Unclassified RIPE
Summary
dhs
business turkey small
The AS handle DHS is held by YONCA DURAN.
What it's used for
- The address space carries server infrastructure, as indicated by reverse DNS entries such as
server64.tr85.dhs.com.trandserver190.tr85.dhs.com.tr. - The network announces 256 IPv4 addresses within a single /24 prefix (217.18.85.0/24) and has 1 observed neighbour, indicating a small, isolated endpoint or internal network rather than a transit or large access provider.
- Traffic from this AS consists of web or API endpoints hosted on the
dhs.com.trdomain, consistent with a small business or individual operator managing their own server estate.
Notable
- The RDAP registrant
YONCA DURANmatches the registry holder and the AS namedhs, confirming consistent ownership. - The address inventory is a single contiguous /24 block with no IPv6 prefixes, representing a minimal footprint typical of a small-scale private network.
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 |
|---|---|---|
| AS6205 | HizliNet Teknoloji A.S. | 60 |
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 0 prefixes
| Country | Name | Prefixes |
|---|---|---|
| TR | Turkey | 1 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS201233- Registry name
- dhs
- Registrant
- lir-tr-dhs-1-MNT
- Abuse contact
- abuse@dhs.com.tr
- Registered
- 2022-11-18
- Last changed
- 2026-05-18
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- dhs
- Scope
- Not Disclosed
- Traffic ratio
- Not Disclosed
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
- 2 authorising AS201233
- ASPA
- no ASPA record
- IRR
- 100% registered · 1 of 1 announcements
- Route objects
- 2 naming AS201233
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,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