IP abuse report185.136.15.6

Suspicious Residential IPv4 Kazakhstan AS210328

185.136.15.6 is an IPv4 address located in Almaty (Bostandyk District), Kazakhstan. It belongs to a network operated by AO ALMAZ (AS210328). The address is listed by 2 of the threat-intelligence sources we track and carries a confidence score of 70/100. It has also been reported 1 time(s) by the community.

Last updated Listing sources 2 Community Reports 1 How the score works
Listing sources2
Community Reports1
Distinct Reporters1
Last seen 11 minutes ago

IP Information

ISP / Organization
AO ALMAZ
ASN
AS210328 ALMAZ
IP Range
Unknown
Regional Registry
NONE
Connection Type
Residential
Country
Kazakhstan (KZ)
Region / State
Almaty
City
Almaty (Bostandyk District)
Time Zone
Unknown

City is an estimate. The country is reliable; the city varies by provider.

Approximate location

City level
Almaty (Bostandyk District) Almaty, Kazakhstan
Coordinates
43.21, 76.90
Network
AS210328 AO ALMAZ
Open on the threat map

The point is the city centre given by IP geolocation databases, not a street address. The circle shows the area of uncertainty.

Network Neighbourhood

185.136.15.0/24

31 of the 256 addresses in 185.136.15.0/24 are listed by our sources (12.1%).

Only a small part of the block is listed, which is more consistent with an isolated incident than with the network itself.

Examples from the same block
185.136.15.2185.136.15.4185.136.15.5185.136.15.7185.136.15.9185.136.15.12185.136.15.13185.136.15.16

An address is not guiltier for having a few listed neighbours, which is why this stays out of the confidence score entirely while the block is mostly clean. It contributes at most 20 points, and only once a substantial share of the block is listed — that ceiling is deliberate: neighbours alone can raise an address to "low" and no further.

Threat Evidence

Last 30 days: how many feeds listed this address each day, and the community reports filed.

Blocklist feeds Community reports

Blacklist Matches

2

In our pool since: 2026-10-09 01:22 (1 month ago) · Last confirmed: 2026-11-20 03:49

Aggregated List (Low Confidence) 1
SourceScopeFirst seenConfirmed
FireHOL Level 3 Aggregator 185.136.15.0/24 2026-11-07 19:33 2026-11-20 03:4812 minutes ago
Attack Source 1
SourceScopeFirst seenConfirmed
Data-Shield IPv4 Blocklist Single address 2026-11-07 19:33 2026-11-20 03:4911 minutes ago

“Confirmed” is the moment the address was still on that source at its most recent fetch — the feeds are replaced wholesale on every refresh. Per-source “first seen” only began being recorded on 30 August 2026, so for listings older than that this column shows the start of record-keeping. The address-level history is the “in our pool since” value above.

IP-DB Sensor · free honeypot

Catch addresses like this on your own server

Sensor opens realistic decoy services — FortiGate, GlobalProtect, Exchange, NetScaler and more — on your server's unused ports. Every address that touches them is logged with evidence, and your firewall, fail2ban and Shield pull the same list to block it.

  • Realistic decoys for VPN gateways, mail, web panels and databases
  • Names exploit attempts by their CVE signature
  • One-command install; runs unprivileged and never touches your real services

While a Sensor reports, your daily API quota rises to 30,000 lookups.

root@web-01 — ipdb-sensor DEMO
● ipdb-sensor.serviceactive (running)
4hits
4decoys
1blocked
  1. 14:02:07 ssh:22 185.136.15.6 login attempt root / ••••••
  2. 14:02:10 globalprotect:443 185.136.15.6 exploit attempt CVE-2024-3400
  3. 14:02:13 owa:4443 185.136.15.6 password spray Exchange OWA
  4. 14:02:16 netscaler:8443 185.136.15.6 Citrix Bleed scan CVE-2023-4966
  5. 14:02:20 ✓ evidence logged → added to your blocklist
Sample output — if this address probed your server

Community Reports 1

Report This IP

Who reported this address, when, and on what grounds.

0Last 24 Hours
1Last 7 Days
1Last 30 Days
1Last 90 Days
  1. Alex Registered member
    2 days ago 2026-11-17 23:45Reported from: Canada (CA)
    Reason: Port Scan
    Fail2Ban report from custom-honeypot; service=RDP; application_protocol=RDP; transport=TCP; destination_port=3389; observed_at=2026-11-17T20:45:44Z; last_observed_at=2026-11-17T20:45:44Z; reported_at=2026-11-17T20:45:45Z matched_log_events=3; evidence_window_seconds=30; logged_tcp_connections=1; destination_ports_seen=3389 2026-11-17T20:45:44Z RDP/3389 activity=handshake initiated 2026-11-17T20:45:44Z RDP/3389 activity=client data bytes=19 sha256=c7fc4bd4bc65329a 2026-11-17T20:45:44Z RDP/3389 activity=connection accepted

Reporters' IP addresses are never published — only the country they reported from.

Listing History

1
Added to the pool
1 month ago
2026-10-09 01:22

The pool is a live picture: an address listed today leaves it when the sources drop it. This record outlives that removal — “listed on 12 August, delisted on 3 September” is truer than either a permanent accusation or a blank page. Events are kept for 400 days.

Frequently asked questions about 185.136.15.6

Is 185.136.15.6 safe?

185.136.15.6 scores 70/100 from several independent signals (2 sources, 1 community report). Rate-limit or challenge its traffic and review your logs for it.

Who owns 185.136.15.6?

185.136.15.6 is announced by AS210328 and operated by AO ALMAZ.

Where is 185.136.15.6 located?

Geolocation places 185.136.15.6 in Almaty (Bostandyk District), Kazakhstan. IP geolocation is approximate: it shows where the network is registered or routed, not a device's street address.

Is 185.136.15.6 on a blacklist?

Yes. 185.136.15.6 is currently listed by 2 threat sources: Data-Shield IPv4 Blocklist, FireHOL Level 3.

How do I report abuse from 185.136.15.6?

File a report on IP-DB with your log lines; the registry publishes no abuse mailbox for this network.

Run this check via the API

The same score and evidence are available as JSON, free with an API key.

API documentation →
curl -H "Key: YOUR_API_KEY" https://ip-db.com/api/v1/check/185.136.15.6

Guides for this IP