IP abuse report185.226.196.12

Critical Hosting / Datacenter IPv4 United States AS21859

185.226.196.12 is an IPv4 address located in Los Angeles, United States. It belongs to a network operated by Zenlayer Inc (AS21859). The address is listed by 5 of the threat-intelligence sources we track and carries a confidence score of 100/100. It has also been reported 1 time(s) by the community.

Last updated Listing sources 5 Community Reports 1 How the score works
Provider notified This IP was reported to its network operator Zenlayer Inc · 2026-11-09 · IPDB-AR-007082 Acknowledged Show detailsHide
  1. DetectedScore 100/100
  2. Notice sent2026-11-09 21:33
  3. Deliveredinternet-census.org
  4. Operator response Acknowledged

The IP-DB Abuse Desk sent an abuse notice with supporting evidence to Zenlayer Inc's registered abuse contact on 2026-11-09 21:33: optout@internet-census.org

Acknowledged / ticket opened 2026-11-09 21:33
##- Please type your reply above this line -## Your request has been updated. To add additional comments, reply to this email. ---------------------------------------------- System, Nov 9, 2026, 14:33 AST Please find activity clarification below. **Who We Are…
This notice covers 45 address(es) on the same network. View public record · IPDB-AR-007082 →
Listing sources5
Community Reports1
Distinct Reporters1
Last seen 14 minutes ago

IP Information

ISP / Organization
Zenlayer Inc
ASN
AS21859 ZEN-ECN
ASN Domain
zenlayer.com
IP Range
185.226.196.0/24
Regional Registry
RIPENCC
Connection Type
Hosting / Datacenter
Country
United States (US)
Region / State
California
City
Los Angeles 2 sources agree
Time Zone
America/Los_Angeles
Abuse contact
optout@internet-census.org The abuse mailbox this network lists with its regional registry. Report traffic from this IP here, with logs and timestamps.

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

Approximate location

City level
Los Angeles California, United States
Coordinates
34.05, -118.24
Network
AS21859 Zenlayer Inc
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.226.196.0/24

17 of the 256 addresses in 185.226.196.0/24 are listed by our sources (6.6%).

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.226.196.7185.226.196.13185.226.196.14185.226.196.15185.226.196.17185.226.196.18185.226.196.19185.226.196.20

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

5

In our pool since: 2026-08-28 11:17 (2 months ago) · Last confirmed: 2026-11-20 03:50

Aggregated List (High Confidence) 1
SourceScopeFirst seenConfirmed
IPsum (4+ lists) Aggregator Single address 2026-11-17 05:18 2026-11-20 03:4816 minutes ago
Attack Source 3
SourceScopeFirst seenConfirmed
CZ.NIC Turris Sentinel Greylist Single address 2026-11-19 02:17 2026-11-20 03:4817 minutes ago
Data-Shield IPv4 Blocklist Single address 2026-11-07 19:33 2026-11-20 03:4915 minutes ago
IP-DB Sensor Network Single address 2026-11-15 13:48 2026-11-20 03:5014 minutes ago
Malicious Activity 1
SourceScopeFirst seenConfirmed
Malicious IP (romainmarcoux) Aggregator Single address 2026-11-07 19:33 2026-11-20 03:4916 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.226.196.12 login attempt root / ••••••
  2. 14:02:10 globalprotect:443 185.226.196.12 exploit attempt CVE-2024-3400
  3. 14:02:13 owa:4443 185.226.196.12 password spray Exchange OWA
  4. 14:02:16 netscaler:8443 185.226.196.12 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. nak Registered member
    3 days ago 2026-11-16 07:52Reported from: Japan (JP)
    Reason: Vulnerability Scanning
    Observed by PHP honeypot (static responder; no code executed). 4 requests (2 matched attack signatures) on 2026-11-16 02:15:51–02:16:00 UTC (8 s). Automated MCP protocol scanner. Attack attempts: - MCP protocol endpoint discovery [2 requests]: POST /mcp body: {"jsonrpc":"2.0","id":3303228,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{"sampling":{},"elicitation":{},"roots"... -> enumerates Model Context Protocol endpoints Signatures: ai-triage

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

Listing History

1
Added to the pool
2 months ago · score at the time: 90/100 · carried by 4 sources
2026-08-28 11:17

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.226.196.12

Is 185.226.196.12 safe?

No. 185.226.196.12 scores 100/100 with strong, recent evidence of abuse (5 sources, 1 community report). Blocking it at your firewall is advisable.

Who owns 185.226.196.12?

185.226.196.12 is announced by AS21859 and operated by Zenlayer Inc. It sits in the 185.226.196.0/24 block registered with RIPENCC.

Where is 185.226.196.12 located?

Geolocation places 185.226.196.12 in Los Angeles, United States. IP geolocation is approximate: it shows where the network is registered or routed, not a device's street address.

Is 185.226.196.12 on a blacklist?

Yes. 185.226.196.12 is currently listed by 5 threat sources: CZ.NIC Turris Sentinel Greylist, IPsum (4+ lists), Malicious IP (romainmarcoux), Data-Shield IPv4 Blocklist, IP-DB Sensor Network.

How do I report abuse from 185.226.196.12?

Send your log lines to the network's abuse contact, optout@internet-census.org, and file a report on IP-DB so others can see it too.

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.226.196.12

Guides for this IP