IP abuse report69.5.169.163

Critical Hosting / Datacenter IPv4 Germany AS25369

69.5.169.163 is an IPv4 address located in Frankfurt am Main, Germany. It belongs to a network operated by Hydra Communications Ltd (AS25369). The address is listed by 10 of the threat-intelligence sources we track and carries a confidence score of 100/100. No community reports have been filed for it yet.

Last updated Listing sources 10 Community Reports 0 How the score works
Provider notified This IP was reported to its network operator Hydra Communications Ltd · 2026-09-22 · IPDB-AR-000032 Awaiting reply Show detailsHide
  1. DetectedScore 100/100
  2. Notice sent2026-09-22 23:49
  3. Deliveredinfrawat.ch
  4. Operator response Waiting · 1 month ago

The IP-DB Abuse Desk sent an abuse notice with supporting evidence to Hydra Communications Ltd's registered abuse contact on 2026-09-22 23:49: abuse@infrawat.ch

This notice covers 100 address(es) on the same network. View public record · IPDB-AR-000032 →
Listing sources10
Community Reports0
Distinct Reporters0
Last seen 29 minutes ago

IP Information

ISP / Organization
Hydra Communications Ltd
ASN
AS25369 BANDWIDTH-AS
ASN Domain
zare.com
IP Range
69.5.169.0/24
Regional Registry
RIPENCC
Connection Type
Hosting / Datacenter
Country
Germany (DE)
Region / State
Hesse
City
Frankfurt am Main
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
Frankfurt am Main Hesse, Germany
Coordinates
50.11, 8.68
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

69.5.169.0/24

252 of the 256 addresses in 69.5.169.0/24 are listed by our sources (98.4%).

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
69.5.169.269.5.169.369.5.169.469.5.169.569.5.169.669.5.169.769.5.169.869.5.169.9

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

Blacklist Matches

10

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

Aggregated List (High Confidence) 2
SourceScopeFirst seenConfirmed
IPsum (4+ lists) Aggregator Single address 2026-11-07 19:33 2026-11-20 06:481 minute ago
FireHOL Level 1 Aggregator 69.5.169.0/24 2026-11-18 14:47 2026-11-20 06:481 minute ago
Aggregated List (Low Confidence) 1
SourceScopeFirst seenConfirmed
FireHOL Level 3 Aggregator 69.5.169.0/24 2026-11-07 19:33 2026-11-20 06:481 minute ago
Aggregated List (Medium Confidence) 1
SourceScopeFirst seenConfirmed
FireHOL Level 2 Aggregator 69.5.169.0/24 2026-11-07 19:33 2026-11-20 06:481 minute ago
Attack Source 2
SourceScopeFirst seenConfirmed
Data-Shield IPv4 Blocklist Single address 2026-11-20 00:19 2026-11-20 06:1930 minutes ago
IP-DB Sensor Network Single address 2026-11-19 21:58 2026-11-20 06:2029 minutes ago
Malicious Activity 4
SourceScopeFirst seenConfirmed
CINS Army List Single address 2026-11-20 00:17 2026-11-20 06:472 minutes ago
ThreatView High Confidence Single address 2026-11-19 02:47 2026-11-20 06:481 minute ago
Malicious IP (romainmarcoux) Aggregator Single address 2026-11-20 00:19 2026-11-20 06:481 minute ago
Emerging Threats Block IPs 69.5.169.0/24 2026-11-19 01:17 2026-11-20 06:472 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 69.5.169.163 login attempt root / ••••••
  2. 14:02:10 globalprotect:443 69.5.169.163 exploit attempt CVE-2024-3400
  3. 14:02:13 owa:4443 69.5.169.163 password spray Exchange OWA
  4. 14:02:16 netscaler:8443 69.5.169.163 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 0

Report This IP

No community reports yet for this IP.

Report This IP

Listing History

1
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 69.5.169.163

Is 69.5.169.163 safe?

No. 69.5.169.163 scores 100/100 with strong, recent evidence of abuse (10 sources). Blocking it at your firewall is advisable.

Who owns 69.5.169.163?

69.5.169.163 is announced by AS25369 and operated by Hydra Communications Ltd. It sits in the 69.5.169.0/24 block registered with RIPENCC.

Where is 69.5.169.163 located?

Geolocation places 69.5.169.163 in Frankfurt am Main, Germany. IP geolocation is approximate: it shows where the network is registered or routed, not a device's street address.

Is 69.5.169.163 on a blacklist?

Yes. 69.5.169.163 is currently listed by 10 threat sources: Data-Shield IPv4 Blocklist, IP-DB Sensor Network, CINS Army List, ThreatView High Confidence, IPsum (4+ lists), Malicious IP (romainmarcoux)….

How do I report abuse from 69.5.169.163?

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/69.5.169.163

Guides for this IP