IP abuse report5.226.140.35

Critical Hosting / Datacenter IPv4 United Kingdom AS25369

5.226.140.35 is an IPv4 address located in London, United Kingdom. It belongs to a network operated by Hydra Communications Ltd (AS25369). 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.

Last updated Listing sources 3 Community Reports 1 How the score works
Listing sources3
Community Reports1
Distinct Reporters1
Last seen 13 minutes ago

IP Information

ISP / Organization
Hydra Communications Ltd
ASN
AS25369 BANDWIDTH-AS
ASN Domain
zare.com
IP Range
5.226.140.0/25
Regional Registry
RIPENCC
Connection Type
Hosting / Datacenter
Country
United Kingdom (GB)
Region / State
England
City
London
Time Zone
Unknown
Abuse contact
abuse@infrawat.ch 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
London England, United Kingdom
Coordinates
51.51, -0.09
Network
AS25369 Hydra Communications Ltd
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

5.226.140.0/24

108 of the 256 addresses in 5.226.140.0/24 are listed by our sources (42.2%).

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.

Examples from the same block
5.226.140.25.226.140.35.226.140.45.226.140.55.226.140.75.226.140.85.226.140.95.226.140.10

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

3

In our pool since: 2026-11-20 05:19 (43 minutes ago) · Last confirmed: 2026-11-20 05:49

Aggregated List (Low Confidence) 1
SourceScopeFirst seenConfirmed
FireHOL Level 3 Aggregator 5.226.140.0/24 2026-11-07 19:33 2026-11-20 05:4815 minutes ago
Aggregated List (Medium Confidence) 1
SourceScopeFirst seenConfirmed
FireHOL Level 2 Aggregator 5.226.140.0/24 2026-11-19 21:57 2026-11-20 05:4815 minutes ago
Attack Source 1
SourceScopeFirst seenConfirmed
IP-DB Sensor Network Single address 2026-11-20 05:19 2026-11-20 05:4913 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 5.226.140.35 login attempt root / ••••••
  2. 14:02:10 globalprotect:443 5.226.140.35 exploit attempt CVE-2024-3400
  3. 14:02:13 owa:4443 5.226.140.35 password spray Exchange OWA
  4. 14:02:16 netscaler:8443 5.226.140.35 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.

1Last 24 Hours
1Last 7 Days
1Last 30 Days
1Last 90 Days
  1. Alex Registered member
    19 hours ago 2026-11-19 10:16Reported 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-19T07:16:03Z; last_observed_at=2026-11-19T07:16:03Z; reported_at=2026-11-19T07:16:04Z matched_log_events=3; evidence_window_seconds=30; logged_tcp_connections=1; destination_ports_seen=3389 2026-11-19T07:16:03Z RDP/3389 activity=handshake initiated 2026-11-19T07:16:03Z RDP/3389 activity=client data bytes=19 sha256=c7fc4bd4bc65329a 2026-11-19T07:16:03Z RDP/3389 activity=connection accepted

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

Listing History

35
Added to the pool
41 minutes ago
2026-11-20 05:22
Removed from the pool
3 days ago · score at the time: 65/100 · carried by 1 sources
2026-11-17 02:22
Added to the pool
4 days ago
2026-11-16 02:22
Removed from the pool
5 days ago · score at the time: 90/100 · carried by 2 sources
2026-11-15 04:22
Added to the pool
5 days ago
2026-11-14 10:22
Removed from the pool
7 days ago · score at the time: 90/100 · carried by 2 sources
2026-11-13 04:22
Added to the pool
8 days ago
2026-11-11 12:22
Removed from the pool
10 days ago · score at the time: 90/100 · carried by 2 sources
2026-11-09 12:22
Added to the pool
14 days ago
2026-11-06 01:22
Removed from the pool
14 days ago · score at the time: 50/100 · carried by 1 sources
2026-11-05 20:22
Added to the pool
16 days ago
2026-11-04 04:22
Removed from the pool
16 days ago · score at the time: 65/100 · carried by 1 sources
2026-11-04 02:22
Added to the pool
17 days ago
2026-11-03 02:22
Removed from the pool
17 days ago · score at the time: 50/100 · carried by 1 sources
2026-11-02 16:22
Added to the pool
18 days ago
2026-11-01 21:22
Removed from the pool
18 days ago · score at the time: 50/100 · carried by 1 sources
2026-11-01 20:22
Added to the pool
22 days ago
2026-10-28 21:22
Removed from the pool
22 days ago · score at the time: 90/100 · carried by 2 sources
2026-10-28 20:22
Added to the pool
24 days ago
2026-10-26 16:22
Removed from the pool
24 days ago · score at the time: 50/100 · carried by 1 sources
2026-10-26 14:22
Added to the pool
25 days ago
2026-10-26 04:22
Removed from the pool
25 days ago · score at the time: 90/100 · carried by 2 sources
2026-10-26 02:22
Added to the pool
25 days ago
2026-10-26 00:22
Removed from the pool
25 days ago · score at the time: 90/100 · carried by 2 sources
2026-10-25 22:22
Added to the pool
26 days ago
2026-10-25 00:22
Removed from the pool
26 days ago · score at the time: 90/100 · carried by 2 sources
2026-10-24 23:22
Added to the pool
27 days ago
2026-10-24 04:22
Removed from the pool
27 days ago · score at the time: 90/100 · carried by 2 sources
2026-10-24 03:22
Added to the pool
27 days ago
2026-10-24 00:22
Removed from the pool
27 days ago · score at the time: 60/100 · carried by 1 sources
2026-10-23 23:22
Added to the pool
27 days ago
2026-10-23 22:22
Removed from the pool
27 days ago · score at the time: 90/100 · carried by 2 sources
2026-10-23 21:22
Added to the pool
29 days ago
2026-10-21 19:22
Removed from the pool
29 days ago · score at the time: 86/100 · carried by 2 sources
2026-10-21 17:22
Added to the pool
2 months ago · score at the time: 90/100 · carried by 3 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 5.226.140.35

Is 5.226.140.35 safe?

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

Who owns 5.226.140.35?

5.226.140.35 is announced by AS25369 and operated by Hydra Communications Ltd. It sits in the 5.226.140.0/25 block registered with RIPENCC.

Where is 5.226.140.35 located?

Geolocation places 5.226.140.35 in London, United Kingdom. IP geolocation is approximate: it shows where the network is registered or routed, not a device's street address.

Is 5.226.140.35 on a blacklist?

Yes. 5.226.140.35 is currently listed by 3 threat sources: IP-DB Sensor Network, FireHOL Level 2, FireHOL Level 3. DNS blacklists: 0 of 2 list it.

How do I report abuse from 5.226.140.35?

Send your log lines to the network's abuse contact, abuse@infrawat.ch, 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/5.226.140.35

Guides for this IP