IP abuse report69.5.169.10
69.5.169.10 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. It has also been reported 1 time(s) by the community.
Provider notified This IP was reported to its network operator Hydra Communications Ltd · 2026-09-22 · IPDB-AR-000032 Awaiting reply Show detailsHide
- DetectedScore 100/100
- Notice sent2026-09-22 23:49
- Deliveredinfrawat.ch
- 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
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- Coordinates
- 50.11, 8.68
- Network
- AS25369 Hydra Communications Ltd
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/24252 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.
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
- Canada1
When each feed first and last carried this address, over the last 30 days.
Blacklist Matches
10In our pool since: 2026-08-28 11:17 (2 months ago) · Last confirmed: 2026-11-20 06:20
| Source | Scope | First seen | Confirmed |
|---|---|---|---|
| IPsum (4+ lists) Aggregator | Single address | 2026-11-07 19:33 | 2026-11-20 06:1821 minutes ago |
| FireHOL Level 1 Aggregator | 69.5.169.0/24 | 2026-11-18 14:47 | 2026-11-20 06:1821 minutes ago |
| Source | Scope | First seen | Confirmed |
|---|---|---|---|
| FireHOL Level 3 Aggregator | 69.5.169.0/24 | 2026-11-07 19:33 | 2026-11-20 06:1821 minutes ago |
| Source | Scope | First seen | Confirmed |
|---|---|---|---|
| FireHOL Level 2 Aggregator | 69.5.169.0/24 | 2026-11-07 19:33 | 2026-11-20 06:1821 minutes ago |
| Source | Scope | First seen | Confirmed |
|---|---|---|---|
| Data-Shield IPv4 Blocklist | Single address | 2026-11-20 04:19 | 2026-11-20 06:1921 minutes ago |
| IP-DB Sensor Network | Single address | 2026-11-10 12:49 | 2026-11-20 06:2020 minutes ago |
| Source | Scope | First seen | Confirmed |
|---|---|---|---|
| CINS Army List | Single address | 2026-11-20 04:17 | 2026-11-20 06:1723 minutes ago |
| ThreatView High Confidence | Single address | 2026-11-19 02:47 | 2026-11-20 06:1822 minutes ago |
| Malicious IP (romainmarcoux) Aggregator | Single address | 2026-11-20 04:19 | 2026-11-20 06:1821 minutes ago |
| Emerging Threats Block IPs | 69.5.169.0/24 | 2026-11-19 01:17 | 2026-11-20 06:1723 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 69.5.169.10 login attempt root / ••••••
- 14:02:10 globalprotect:443 69.5.169.10 exploit attempt CVE-2024-3400
- 14:02:13 owa:4443 69.5.169.10 password spray Exchange OWA
- 14:02:16 netscaler:8443 69.5.169.10 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.
-
Alex Registered memberReason: Port Scan
Fail2Ban report from custom-honeypot; service=RDP; application_protocol=RDP; transport=TCP; destination_port=3389; observed_at=2026-11-18T15:59:24Z; last_observed_at=2026-11-18T15:59:24Z; reported_at=2026-11-18T15:59:26Z matched_log_events=3; evidence_window_seconds=30; logged_tcp_connections=1; destination_ports_seen=3389 2026-11-18T15:59:24Z RDP/3389 activity=handshake initiated 2026-11-18T15:59:24Z RDP/3389 activity=client data bytes=19 sha256=7f10077135035453 2026-11-18T15:59:24Z RDP/3389 activity=connection accepted
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 69.5.169.10
Is 69.5.169.10 safe?
No. 69.5.169.10 scores 100/100 with strong, recent evidence of abuse (10 sources, 1 community report). Blocking it at your firewall is advisable.
Who owns 69.5.169.10?
69.5.169.10 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.10 located?
Geolocation places 69.5.169.10 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.10 on a blacklist?
Yes. 69.5.169.10 is currently listed by 10 threat sources: CINS Army List, ThreatView High Confidence, IPsum (4+ lists), Malicious IP (romainmarcoux), Data-Shield IPv4 Blocklist, IP-DB Sensor Network….
How do I report abuse from 69.5.169.10?
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.10