ABUSE.MOM
THREAT REPORT

IP Threat Report
144.126.229.56

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-09-08 04:52:00
First seen: 2026-08-04 06:09:30
Last seen: 2026-08-09 04:17:12
173

⛔ Verdict: BLOCK

This IP address has been classified as a source of malicious automated activity. Threat score: 173/100. Total malicious requests observed: 308.

BURSTDANGER_PATHMETHODUA_CHANGEDUA_SUS
01

Geolocation & Classification

IP Address
144.126.229.56
Type
Hosting
Country
🇬🇧 United Kingdom
City
Slough
ISP
DigitalOcean, LLC
Organization
DigitalOcean, LLC
Autonomous System
AS14061 DigitalOcean, LLC
Hit Count
308
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 11/10sAbnormally fast request rate — automated scanning+35
Burst 11/2sAbnormally fast request rate — automated scanning+35
Danger medium hits: 2Medium-risk: admin panels, config files+20
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
POST seenBehavioral anomaly detected by automated analysis+8
UA changedMultiple User-Agents — bot rotation technique+25
UA suspiciousBehavioral anomaly detected by automated analysis+15
Σ = 188
03

Observed Activity

Reconstructed HTTP requests from server access logs. Target domains redacted for security.

[redacted]
GET
/
200
[redacted]
GET
/page
200
Requests shown: 2 · HTTP 404: 0 · Dangerous patterns: 0

* Typical request patterns for detected signatures. Actual target domains are redacted.

04

Timeline

2026-08-04 06:09:30
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 11/10s (+35), Burst 11/2s (+35), Danger medium hits: 2 (+20)
2026-08-09 04:17:12
Last malicious request observed
Total score reached: 173/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

DigitalOcean, LLC
AS14061 · 🇬🇧 United Kingdom
06

Recommendations

Actions taken & recommended

  • IP 144.126.229.56 is blocked at application level (HTTP 403)
  • Consider blocking at firewall level (iptables/CSF) to reduce server load
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🌊 Flood / DDoS Mitigation

Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 144.126.229.56.

🤖 User-Agent Anomaly Defense

IP 144.126.229.56 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.

09

Blacklist Status (DNSBL)

This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.

✓ Clean
b.barracudacentral.org
✓ Clean
cbl.abuseat.org
✓ Clean
bl.blocklist.de
✓ Clean
zen.spamhaus.org
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
dnsbl.dronebl.org
✓ Clean
psbl.surriel.com
✓ Clean
bl.spamcop.net

Checked: Spamhaus, SpamCop, Barracuda, SORBS, CBL, UCEProtect. Results may change over time.

10

Threat Analysis

144.126.229.56 has been assigned a threat score of 173/100 (Critical). With this rating, the IP falls into the critical severity bracket — among the most dangerous addresses in our monitoring database.

The following attack categories were identified:

Request FloodingUser-Agent Anomaly

📊 Threat Analysis

144.126.229.56 is registered in Slough, United Kingdom, operating on the network of DigitalOcean, LLC. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. Over a period of 4 days, this IP generated 308 malicious requests, averaging approximately 77 requests per day. The IP is classified as hosting/datacenter infrastructure, commonly associated with rented servers used for automated attack campaigns, botnet command-and-control, or vulnerability scanning at scale. Two attack patterns were identified (Request Flooding and User-Agent Anomaly), suggesting a semi-automated campaign that targets multiple vulnerabilities. United Kingdom currently accounts for 102 blocked IPs in our database, making it a significant source of malicious traffic. A score of 173/100 places this address in the top tier of severity. Block and investigate any historical connections.

This IP belongs to a hosting or data center provider. Malicious traffic from hosting infrastructure often originates from compromised VPS instances, rented servers used for scanning campaigns, or abused free-tier cloud accounts. Hosting providers typically respond to abuse reports within 24-72 hours.

11

Related Threats

🇬🇧 Top threats from United Kingdom

45.86.203.126 (350)104.28.240.60 (340)104.28.192.67 (340)104.28.208.60 (340)194.32.120.30 (320)View all →

🏢 Same network: AS14061

142.93.195.73 (275)152.42.236.252 (273)204.48.19.26 (268)157.230.45.147 (265)152.42.180.126 (263)View all →
12

Security Intelligence

💡 DDoS Mitigation Approaches

Distributed denial of service attacks overwhelm infrastructure with traffic volume. Effective mitigation combines always-on traffic scrubbing, anycast network distribution, rate limiting, and the ability to quickly scale absorption capacity during attacks.

💡 Server-Side Request Forgery (SSRF)

SSRF attacks trick servers into making requests to internal resources that should not be publicly accessible. This can expose cloud metadata endpoints, internal APIs, and private network services, potentially leading to full infrastructure compromise.

🔍 Check Any IP Address

Share this report: