IP abuse report200.138.46.171
200.138.46.171 is an IPv4 address located in Paris, France. It belongs to a network operated by Hydra Communications Ltd (AS25369). The address is listed by 8 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.
IP Information
- ISP / Organization
- Hydra Communications Ltd
- ASN
- AS25369 BANDWIDTH-AS
- ASN Domain
- zare.com
- IP Range
- 200.138.46.0/24
- Regional Registry
- RIPENCC
- Connection Type
- Hosting / Datacenter
- Country
- France (FR)
- Region / State
- Île-de-France
- City
-
ParisLocal databaseLondonLive service
The two sources report different cities. Neither is confirmed; the country is the reliable part.
- Time Zone
- Europe/London
- Abuse contact
- report@abuseradar.com 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
- 48.86, 2.35
- 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
200.138.46.0/24253 of the 256 addresses in 200.138.46.0/24 are listed by our sources (98.8%).
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
8In our pool since: 2026-10-09 16:22 (1 month ago) · Last confirmed: 2026-11-20 03:19
| Source | Scope | First seen | Confirmed |
|---|---|---|---|
| FireHOL Level 1 Aggregator | 200.138.46.0/24 | 2026-11-19 21:57 | 2026-11-20 03:1820 minutes ago |
| Source | Scope | First seen | Confirmed |
|---|---|---|---|
| FireHOL Level 3 Aggregator | 200.138.46.0/24 | 2026-11-07 19:33 | 2026-11-20 03:1820 minutes ago |
| Source | Scope | First seen | Confirmed |
|---|---|---|---|
| FireHOL Level 2 Aggregator | 200.138.46.0/24 | 2026-11-17 14:47 | 2026-11-20 03:1820 minutes ago |
| Source | Scope | First seen | Confirmed |
|---|---|---|---|
| CZ.NIC Turris Sentinel Greylist | Single address | 2026-11-20 02:17 | 2026-11-20 03:1721 minutes ago |
| Data-Shield IPv4 Blocklist | Single address | 2026-11-07 19:33 | 2026-11-20 03:1919 minutes ago |
| SANS ISC DShield Block List | 200.138.46.0/24 | 2026-11-19 05:17 | 2026-11-20 03:1722 minutes ago |
| Source | Scope | First seen | Confirmed |
|---|---|---|---|
| Malicious IP (romainmarcoux) Aggregator | Single address | 2026-11-07 19:33 | 2026-11-20 03:1920 minutes ago |
| Emerging Threats Block IPs | 200.138.46.0/24 | 2026-11-20 01:17 | 2026-11-20 03:1721 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 200.138.46.171 login attempt root / ••••••
- 14:02:10 globalprotect:443 200.138.46.171 exploit attempt CVE-2024-3400
- 14:02:13 owa:4443 200.138.46.171 password spray Exchange OWA
- 14:02:16 netscaler:8443 200.138.46.171 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: Vulnerability Scanning
Observed by PHP honeypot (static responder; no code executed). 1 requests on 2026-11-17 12:22:53–12:22:53 UTC (0 s). Automated LLM API reconnaissance bot. Attack attempts: - LLM API version endpoint probing: GET /api/version -> discovers LLM API version and capabilities Signatures: llm-api-probe
Reporters' IP addresses are never published — only the country they reported from.
Listing History
7The 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 200.138.46.171
Is 200.138.46.171 safe?
No. 200.138.46.171 scores 100/100 with strong, recent evidence of abuse (8 sources, 1 community report). Blocking it at your firewall is advisable.
Who owns 200.138.46.171?
200.138.46.171 is announced by AS25369 and operated by Hydra Communications Ltd. It sits in the 200.138.46.0/24 block registered with RIPENCC.
Where is 200.138.46.171 located?
Geolocation places 200.138.46.171 in Paris, France. IP geolocation is approximate: it shows where the network is registered or routed, not a device's street address.
Is 200.138.46.171 on a blacklist?
Yes. 200.138.46.171 is currently listed by 8 threat sources: CZ.NIC Turris Sentinel Greylist, Malicious IP (romainmarcoux), Data-Shield IPv4 Blocklist, SANS ISC DShield Block List, Emerging Threats Block IPs, FireHOL Level 1….
How do I report abuse from 200.138.46.171?
Send your log lines to the network's abuse contact, report@abuseradar.com, 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/200.138.46.171