IP abuse report2a01:4020:31:0:102::3da
2a01:4020:31:0:102::3da is an IPv6 address located in Frankfurt am Main, Germany. It belongs to a network operated by Hydra Communications Ltd (AS25369). The address is listed by 2 of the threat-intelligence sources we track and carries a confidence score of 50/100. No community reports have been filed for it yet.
IP Information
- ISP / Organization
- Hydra Communications Ltd
- ASN
- AS25369 BANDWIDTH-AS
- ASN Domain
- zare.com
- IP Range
- 2a00::/11
- Regional Registry
- RIPENCC
- Connection Type
- Residential
- Country
- Germany (DE)
- Region / State
- Hesse
- City
- Frankfurt am Main
- Time Zone
- Unknown
- Abuse contact
- abuse@ripe.net 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.
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.
When each feed first and last carried this address, over the last 30 days.
Blacklist Matches
2In our pool since: 2026-11-20 06:17 (23 minutes ago) · Last confirmed: 2026-11-20 06:17
| Source | Scope | First seen | Confirmed |
|---|---|---|---|
| Blocklist.de (all) | Single address | 2026-11-20 06:17 | 2026-11-20 06:1723 minutes ago |
| Source | Scope | First seen | Confirmed |
|---|---|---|---|
| Blocklist.de Web/Apache | Single address | 2026-11-20 06:17 | 2026-11-20 06:1722 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 2a01:4020:31:0:102::3da login attempt root / ••••••
- 14:02:10 globalprotect:443 2a01:4020:31:0:102::3da exploit attempt CVE-2024-3400
- 14:02:13 owa:4443 2a01:4020:31:0:102::3da password spray Exchange OWA
- 14:02:16 netscaler:8443 2a01:4020:31:0:102::3da Citrix Bleed scan CVE-2023-4966
- 14:02:20 ✓ evidence logged → added to your blocklist
Community Reports 0
Report This IPNo community reports yet for this IP.
Report This IPListing 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 2a01:4020:31:0:102::3da
Is 2a01:4020:31:0:102::3da safe?
2a01:4020:31:0:102::3da scores 50/100 from several independent signals (2 sources). Rate-limit or challenge its traffic and review your logs for it.
Who owns 2a01:4020:31:0:102::3da?
2a01:4020:31:0:102::3da is announced by AS25369 and operated by Hydra Communications Ltd. It sits in the 2a00::/11 block registered with RIPENCC.
Where is 2a01:4020:31:0:102::3da located?
Geolocation places 2a01:4020:31:0:102::3da 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 2a01:4020:31:0:102::3da on a blacklist?
Yes. 2a01:4020:31:0:102::3da is currently listed by 2 threat sources: Blocklist.de (all), Blocklist.de Web/Apache.
How do I report abuse from 2a01:4020:31:0:102::3da?
Send your log lines to the network's abuse contact, abuse@ripe.net, 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/2a01:4020:31:0:102::3da