IP abuse report2a04:52c0:106:394:3218:d72f:49fa:8738

Low Risk Tor Exit Node IPv6 The Netherlands AS60404

2a04:52c0:106:394:3218:d72f:49fa:8738 is an IPv6 address located in Amsterdam, The Netherlands. It belongs to a network operated by The Infrastructure Group B.V. (AS60404). The address is listed by 1 of the threat-intelligence sources we track and carries a confidence score of 25/100. No community reports have been filed for it yet.

Last updated Listing sources 1 Community Reports 0 How the score works
Listing sources1
Community Reports0
Distinct Reporters0
Last seen 30 minutes ago

IP Information

ISP / Organization
The Infrastructure Group B.V.
ASN
AS60404 Liteserver
ASN Domain
liteserver.nl
IP Range
2a00::/11
Regional Registry
RIPENCC
Connection Type
Tor Exit Node
Country
The Netherlands (NL)
Region / State
North Holland
City
Amsterdam
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
Amsterdam North Holland, The Netherlands
Coordinates
52.37, 4.90
Network
AS60404 The Infrastructure Group B.V.
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.

Threat Evidence

Last 30 days: how many feeds listed this address each day, and the community reports filed.

Blocklist feeds

Blacklist Matches

1

In our pool since: 2026-09-27 02:52 (1 month ago) · Last confirmed: 2026-11-20 02:47

Tor Exit Node 1
SourceScopeFirst seenConfirmed
Tor Exit Nodes (IPv6) Single address 2026-11-07 19:32 2026-11-20 03:17just now

“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 2a04:52c0:106:394:3218:d72f:49fa:8738 login attempt root / ••••••
  2. 14:02:10 globalprotect:443 2a04:52c0:106:394:3218:d72f:49fa:8738 exploit attempt CVE-2024-3400
  3. 14:02:13 owa:4443 2a04:52c0:106:394:3218:d72f:49fa:8738 password spray Exchange OWA
  4. 14:02:16 netscaler:8443 2a04:52c0:106:394:3218:d72f:49fa:8738 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

7
Added to the pool
17 days ago
2026-11-02 11:52
Removed from the pool
17 days ago · score at the time: 25/100 · carried by 1 sources
2026-11-02 10:52
Added to the pool
17 days ago
2026-11-02 09:52
Removed from the pool
1 month ago · score at the time: 60/100 · carried by 1 sources
2026-10-06 02:52
Added to the pool
1 month ago
2026-10-04 02:52
Removed from the pool
1 month ago · score at the time: 60/100 · carried by 1 sources
2026-09-29 02:52
Added to the pool
1 month ago
2026-09-27 02:52

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 2a04:52c0:106:394:3218:d72f:49fa:8738

Is 2a04:52c0:106:394:3218:d72f:49fa:8738 safe?

2a04:52c0:106:394:3218:d72f:49fa:8738 scores 25/100: weak or single-source signals (1 source). Treat it as low risk and keep logging rather than blocking on this alone.

Who owns 2a04:52c0:106:394:3218:d72f:49fa:8738?

2a04:52c0:106:394:3218:d72f:49fa:8738 is announced by AS60404 and operated by The Infrastructure Group B.V.. It sits in the 2a00::/11 block registered with RIPENCC.

Where is 2a04:52c0:106:394:3218:d72f:49fa:8738 located?

Geolocation places 2a04:52c0:106:394:3218:d72f:49fa:8738 in Amsterdam, The Netherlands. IP geolocation is approximate: it shows where the network is registered or routed, not a device's street address.

Is 2a04:52c0:106:394:3218:d72f:49fa:8738 on a blacklist?

Yes. 2a04:52c0:106:394:3218:d72f:49fa:8738 is currently listed by 1 threat sources: Tor Exit Nodes (IPv6).

How do I report abuse from 2a04:52c0:106:394:3218:d72f:49fa:8738?

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/2a04:52c0:106:394:3218:d72f:49fa:8738

Guides for this IP