IP abuse report45.144.212.158

Critical Hosting / Datacenter IPv4 The Netherlands AS51396

45.144.212.158 is an IPv4 address located in Eygelshoven, The Netherlands. It belongs to a network operated by Pfcloud UG (haftungsbeschrankt) (AS51396). 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 7 time(s) by the community.

Last updated Listing sources 6 Community Reports 7 How the score works
Listing sources6
Community Reports7
Distinct Reporters2
Last seen 19 minutes ago

IP Information

ISP / Organization
Pfcloud UG (haftungsbeschrankt)
ASN
AS51396 PFCLOUD
ASN Domain
pfcloud.io
IP Range
Unknown
Regional Registry
NONE
Connection Type
Hosting / Datacenter
Country
The Netherlands (NL)
Region / State
Limburg
City
Eygelshoven 2 sources agree
Time Zone
Europe/Amsterdam

City is an estimate. The country is reliable; the city varies by provider.

Approximate location

City level
Eygelshoven Limburg, The Netherlands
Coordinates
50.89, 6.06
Network
AS51396 Pfcloud UG (haftungsbeschrankt)
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 Operator Warning

AS51396

The autonomous system this address belongs to, AS51396 (PFCLOUD), appears on the Spamhaus ASN-DROP list. That list names operators whose networks are assessed as being run for abuse as a whole, rather than individual incidents.

Operator domainpfcloud.io
RIRRIPENCC
Listed since2026-08-30

This is a finding about the operator, not about the address, and it is not part of the confidence score: an address in this network may never have been observed attacking anything. Whether you accept traffic from the network at all is a separate decision. · Spamhaus ASN-DROP

Threat Evidence

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

Blocklist feeds Community reports

Blacklist Matches

8

In our pool since: 2026-11-10 12:18 (9 days ago) · Last confirmed: 2026-11-20 03:19

Aggregated List (High Confidence) 1
SourceScopeFirst seenConfirmed
FireHOL Level 1 Aggregator 45.144.212.0/22 2026-11-07 19:33 2026-11-20 03:1820 minutes ago
Attack Source 1
SourceScopeFirst seenConfirmed
Data-Shield IPv4 Blocklist Single address 2026-11-10 12:18 2026-11-20 03:1919 minutes ago
Hijacked Network 2
SourceScopeFirst seenConfirmed
Spamhaus DROP 45.144.212.0/24 2026-11-08 04:47 2026-11-19 09:1718 hours ago
Spamhaus DROP 45.144.212.0/22 2026-11-08 04:47 2026-11-19 09:1718 hours ago
Malicious Activity 3
SourceScopeFirst seenConfirmed
Malicious IP (romainmarcoux) Aggregator Single address 2026-11-10 12:18 2026-11-20 03:1920 minutes ago
Emerging Threats Block IPs 45.144.212.0/24 2026-11-07 19:32 2026-11-20 03:1722 minutes ago
Emerging Threats Block IPs 45.144.212.0/22 2026-11-07 19:32 2026-11-20 03:1722 minutes ago
SSH Brute Force 1
SourceScopeFirst seenConfirmed
James Brine Brute-Force Hosts Single address 2026-11-15 05:17 2026-11-20 03:1820 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.

Network Neighbourhood

45.144.212.0/24

52 of the 256 addresses in 45.144.212.0/24 are listed by our sources (20.3%).

45.144.212.045.144.212.1945.144.212.2745.144.212.4045.144.212.4945.144.212.5445.144.212.7045.144.212.75

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.

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 45.144.212.158 login attempt root / ••••••
  2. 14:02:10 globalprotect:443 45.144.212.158 exploit attempt CVE-2024-3400
  3. 14:02:13 owa:4443 45.144.212.158 password spray Exchange OWA
  4. 14:02:16 netscaler:8443 45.144.212.158 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 7

Report This IP

Who reported this address, when, and on what grounds.

0Last 24 Hours
7Last 7 Days
7Last 30 Days
7Last 90 Days
  1. nak Registered member
    2 days ago 2026-11-17 15:41Reported from: Japan (JP)
    Reason: Vulnerability Scanning
    Ongoing activity: 3 more malicious requests on 2 day(s) since my previous report of this IP on 2026-11-16 04:37 UTC. Observed on a public web server (nginx access log); all attack requests were blocked. 8 requests between 2026-11-13 08:39 and 2026-11-17 08:08 UTC, on 5 distinct days. Automated .git directory scanner. Attack attempts: - Git repository metadata exposure [8 requests]: GET /.git/config, /.git/index, /.git/HEAD, /.git/refs/, /.git/refs/heads/ (+3 more paths) -> exposes source code and secrets via repository files Signatures: git-leak
  2. nak Registered member
    2 days ago 2026-11-17 15:40Reported from: Japan (JP)
    Reason: Vulnerability Scanning
    Ongoing activity: 2 more requests (2 matching attack signatures) on 2 day(s) since my previous report of this IP on 2026-11-16 04:36 UTC. Observed by PHP honeypot (static responder; no code executed). 10 requests between 2026-11-13 08:39 and 2026-11-17 06:34 UTC, on 5 distinct days. Automated sensitive file scanner. Attack attempts: - Environment file reconnaissance [2 requests]: GET /.env -> discovers exposed configuration files containing secrets - Git repository directory enumeration [8 requests]: GET /.git/config, /.git/index, /.git/HEAD, /.git/refs/, /.git/refs/heads/ (+3 more paths) -> maps repository structure to enable source code extraction Signatures: env-leak, git-leak
  3. Alex Registered member
    3 days ago 2026-11-17 00:42Reported from: Canada (CA)
    Reason: Web App AttackVulnerability Scanning
    Fail2Ban report from nginx-bot-trap; service=HTTP; application_protocol=HTTP; observed_at=2026-11-16T21:42:20Z; last_observed_at=2026-11-16T21:42:21Z; reported_at=2026-11-16T21:42:23Z matched_log_events=2; evidence_window_seconds=3600 2026-11-16T21:42:21Z activity=bot-trap request method=GET nginx_status=444 probe_target=/.env 2026-11-16T21:42:20Z activity=bot-trap request method=GET nginx_status=444 probe_target=/.env
  4. nak Registered member
    3 days ago 2026-11-16 07:37Reported from: Japan (JP)
    Reason: Vulnerability Scanning
    Ongoing activity: 2 more malicious requests on 2 day(s) since my previous report of this IP on 2026-11-13 23:12 UTC. Observed on a public web server (nginx access log); all attack requests were blocked. 4 requests between 2026-11-13 08:39 and 2026-11-15 01:07 UTC, on 3 distinct days. Automated .git repository scanner. Attack attempts: - Git repository metadata exposure [4 requests]: GET /.git/config, /.git/index, /.git/HEAD, /.git/refs/ -> exposes source code and secrets via repository metadata Signatures: git-leak
  5. nak Registered member
    3 days ago 2026-11-16 07:36Reported from: Japan (JP)
    Reason: Vulnerability Scanning
    Ongoing activity: 2 more requests (2 matching attack signatures) on 2 day(s) since my previous report of this IP on 2026-11-13 23:12 UTC. Observed by PHP honeypot (static responder; no code executed). 4 requests between 2026-11-13 08:39 and 2026-11-15 00:26 UTC, on 3 distinct days. Automated .git repository scanner. Attack attempts: - Git repository metadata exposure [4 requests]: GET /.git/config, /.git/index, /.git/HEAD, /.git/refs/ -> exposes source code, secrets, and repository structure Signatures: git-leak
  6. nak Registered member
    6 days ago 2026-11-14 02:12Reported from: Japan (JP)
    Reason: Vulnerability Scanning
    Observed on a public web server (nginx access log); all attack requests were blocked. 1 requests on 2026-11-13 08:39:31–08:39:31 UTC (0 s). Automated source code scanner. Attack attempts: - Git repository metadata probing: GET /.git/config -> exposes repository configuration and commit history Signatures: git-leak
  7. nak Registered member
    6 days ago 2026-11-14 02:12Reported from: Japan (JP)
    Reason: Vulnerability Scanning
    Observed by PHP honeypot (static responder; no code executed). 1 requests on 2026-11-13 08:39:18–08:39:18 UTC (0 s). Automated .git secret scanner. Attack attempts: - Git repository metadata probing: GET /.git/config -> exposes repository configuration and internal metadata Signatures: git-leak

Reporters' IP addresses are never published — only the country they reported from.

Listing History

1
Added to the pool
9 days ago
2026-11-10 12:22

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 45.144.212.158

Is 45.144.212.158 safe?

No. 45.144.212.158 scores 100/100 with strong, recent evidence of abuse (6 sources, 7 community reports). Blocking it at your firewall is advisable.

Who owns 45.144.212.158?

45.144.212.158 is announced by AS51396 and operated by Pfcloud UG (haftungsbeschrankt).

Where is 45.144.212.158 located?

Geolocation places 45.144.212.158 in Eygelshoven, The Netherlands. IP geolocation is approximate: it shows where the network is registered or routed, not a device's street address.

Is 45.144.212.158 on a blacklist?

Yes. 45.144.212.158 is currently listed by 6 threat sources: James Brine Brute-Force Hosts, Malicious IP (romainmarcoux), Data-Shield IPv4 Blocklist, Spamhaus DROP, Emerging Threats Block IPs, FireHOL Level 1.

How do I report abuse from 45.144.212.158?

File a report on IP-DB with your log lines; the registry publishes no abuse mailbox for this network.

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

Guides for this IP