ABUSE.MOM
THREAT REPORT

IP Threat Report
72.56.98.37

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-10-25 20:31:12
First seen: 2026-10-23 11:20:03
Last seen: 2026-10-25 04:06:13
115

⛔ Verdict: BLOCK

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

BURSTRATIO_404REDIRECT_PROBEREFERER
01

Geolocation & Classification

IP Address
72.56.98.37
Type
Hosting
Country
🇳🇱 Netherlands
City
Amsterdam
ISP
Timeweb, LLP
Organization
Timeweb, LLP
Autonomous System
AS210976 Timeweb, LLP
Hit Count
46
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Burst 21/2sAbnormally fast request rate — automated scanning+35
Burst 42/10sAbnormally fast request rate — automated scanning+35
Foreign refererReferer from unrelated external domain+10
Probe 302→404Behavioral anomaly detected by automated analysis+20
Σ = 115
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-10-23 11:20:03
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), Burst 21/2s (+35), Burst 42/10s (+35)
2026-10-25 04:06:13
Last malicious request observed
Total score reached: 115/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Timeweb, LLP
AS210976 · 🇳🇱 Netherlands

We have detected 24 malicious IPs from this autonomous system.

View all IPs from AS210976 →
06

Recommendations

Actions taken & recommended

  • IP 72.56.98.37 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

🔎 Path Enumeration Protection

Block scanning from 72.56.98.37: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

🌊 Flood / DDoS Mitigation

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

09

Blacklist Status (DNSBL)

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

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

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

10

Threat Analysis

72.56.98.37 has been assigned a threat score of 115/100 (Critical). This is a critical-level threat. Systems administrators should treat this IP as hostile and block all inbound connections without exception.

The following attack categories were identified:

Path EnumerationRequest Flooding

📊 Threat Analysis

Our monitoring infrastructure has identified 72.56.98.37, geolocated to Amsterdam, Netherlands, operating on the network of Timeweb, LLP, as a source of suspicious network activity. The address has been active for 1 days in our monitoring system, producing 46 flagged requests at a rate of ~46/day. Classified as a hosting IP, this address likely runs on a rented server or cloud instance. Attackers prefer datacenter IPs for their high bandwidth and disposable nature. The dual attack vectors of Path Enumeration combined with Request Flooding indicate a coordinated assault rather than opportunistic scanning. Netherlands currently accounts for 2,853 blocked IPs in our database, making it a major source of malicious traffic. A score of 115/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 Netherlands

91.92.43.144 (358)91.92.43.186 (358)91.92.43.190 (358)91.92.43.157 (358)91.92.43.153 (358)View all →

🏢 Same network: AS210976

147.45.135.191 (180)147.45.240.150 (180)95.140.153.172 (140)89.19.214.195 (138)72.56.114.176 (115)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.

💡 Passive DNS for Threat Hunting

Passive DNS databases record historical DNS resolution data, enabling analysts to track domain changes, identify related infrastructure, and discover malicious domains sharing hosting with known threats. This historical context is invaluable for threat investigation.

🔍 Check Any IP Address

Share this report: