IP abuse report185.226.197.37
185.226.197.37 is an IPv4 address located in Amsterdam, The Netherlands. It belongs to a network operated by Zenlayer Inc (AS21859). The address is listed by 3 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.
Provider notified This IP was reported to its network operator Zenlayer Inc · 2026-11-09 · IPDB-AR-007082 Acknowledged Show detailsHide
- DetectedScore 100/100
- Notice sent2026-11-09 21:33
- Deliveredinternet-census.org
- 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
##- 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…
IP Information
- ISP / Organization
- Zenlayer Inc
- ASN
- AS21859 ZEN-ECN
- ASN Domain
- zenlayer.com
- IP Range
- 185.226.197.0/24
- Regional Registry
- RIPENCC
- Connection Type
- Hosting / Datacenter
- Country
- The Netherlands (NL)
- Region / State
- North Holland
- City
- Amsterdam
- Time Zone
- Unknown
- 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- Coordinates
- 52.37, 4.90
- Network
- AS21859 Zenlayer Inc
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.197.0/2468 of the 256 addresses in 185.226.197.0/24 are listed by our sources (26.6%).
Most of the block is listed. That points to a network being run for the purpose rather than one compromised machine — consider blocking at the block level instead of the single address.
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.
What this address is listed for: feed categories count sources, community categories count reports.
Where community reports were filed from. Only the reporter's country is shown, never their address.
Top reporter countries
- Japan1
When each feed first and last carried this address, over the last 30 days.
Blacklist Matches
3In our pool since: 2026-08-28 11:17 (2 months ago) · Last confirmed: 2026-11-20 03:50
| Source | Scope | First seen | Confirmed |
|---|---|---|---|
| IPsum (4+ lists) Aggregator | Single address | 2026-11-17 05:18 | 2026-11-20 03:4821 minutes ago |
| Source | Scope | First seen | Confirmed |
|---|---|---|---|
| IP-DB Sensor Network | Single address | 2026-11-15 10:49 | 2026-11-20 03:5019 minutes ago |
| Source | Scope | First seen | Confirmed |
|---|---|---|---|
| Malicious IP (romainmarcoux) Aggregator | Single address | 2026-11-07 19:33 | 2026-11-20 03:4920 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.
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.
- 14:02:07 ssh:22 185.226.197.37 login attempt root / ••••••
- 14:02:10 globalprotect:443 185.226.197.37 exploit attempt CVE-2024-3400
- 14:02:13 owa:4443 185.226.197.37 password spray Exchange OWA
- 14:02:16 netscaler:8443 185.226.197.37 Citrix Bleed scan CVE-2023-4966
- 14:02:20 ✓ evidence logged → added to your blocklist
Community Reports 1
Report This IPWho reported this address, when, and on what grounds.
-
nak Registered memberReason: Exploited HostVulnerability ScanningWeb App Attack
Observed by PHP honeypot (static responder; no code executed). 3 requests (2 matched attack signatures) on 2026-11-07 05:00:30–05:00:32 UTC (2 s). Automated MCP endpoint discovery scanner. Attack attempts: - MCP protocol endpoint probing [2 requests]: POST /mcp body: {"jsonrpc":"2.0","id":5767614,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{"sampling":{},"elicitation":{},"roots"... -> identifies exposed Model Context Protocol servers Signatures: ai-triage
Reporters' IP addresses are never published — only the country they reported from.
Listing History
1The 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.197.37
Is 185.226.197.37 safe?
No. 185.226.197.37 scores 100/100 with strong, recent evidence of abuse (3 sources, 1 community report). Blocking it at your firewall is advisable.
Who owns 185.226.197.37?
185.226.197.37 is announced by AS21859 and operated by Zenlayer Inc. It sits in the 185.226.197.0/24 block registered with RIPENCC.
Where is 185.226.197.37 located?
Geolocation places 185.226.197.37 in Amsterdam, The Netherlands. IP geolocation is approximate: it shows where the network is registered or routed, not a device's street address.
Is 185.226.197.37 on a blacklist?
Yes. 185.226.197.37 is currently listed by 3 threat sources: IPsum (4+ lists), Malicious IP (romainmarcoux), IP-DB Sensor Network.
How do I report abuse from 185.226.197.37?
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.197.37