ABUSE.MOM
THREAT REPORT

IP Threat Report
172.71.172.104

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 08:44:21
First seen: 2026-02-28 01:00:07
Last seen: 2026-05-24 10:21:59
75

⛔ Verdict: BLOCK

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

BOT_UADANGER_PATHRATIO_404
01

Geolocation & Classification

IP Address
172.71.172.104
Type
Hosting
Country
🇩🇪 Germany
City
Frankfurt
ISP
Cloudflare, Inc.
Organization
Cloudflare WARP
Autonomous System
AS13335 Cloudflare, Inc.
Hit Count
88
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Danger medium hits: 1Medium-risk: admin panels, config files+10
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
UA bot: Go-http-clientKnown bot/crawler User-Agent detected+40
Σ = 115
03

Observed Activity

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

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

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

04

Timeline

2026-02-28 01:00:07
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), Danger medium hits: 1 (+10), Danger strong hits: 2 (+50)
2026-05-24 10:21:59
Last malicious request observed
Total score reached: 75/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Cloudflare, Inc.
AS13335 · 🇩🇪 Germany
06

Recommendations

Actions taken & recommended

  • IP 172.71.172.104 is blocked at application level (HTTP 403)
  • Consider blocking at firewall level (iptables/CSF) to reduce server load
  • Other malicious IPs detected in the same /24 subnet — consider blocking 172.71.172.0/24
  • 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 172.71.172.104: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

🤖 Bot Detection

Address UA spoofing from 172.71.172.104: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.

07

Neighbors in 172.71.172.0/24

Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.

09

Blacklist Status (DNSBL)

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

⛔ LISTED
Spamhaus ZEN

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

10

Threat Analysis

172.71.172.104 has been assigned a threat score of 75/100 (High). This score indicates high threat severity. The IP has shown clear patterns of malicious behavior that warrant immediate defensive measures.

The following attack categories were identified:

Path EnumerationUser-Agent Anomaly

📊 Threat Analysis

172.71.172.104 is registered in Frankfurt, Germany, operating on the network of Cloudflare, Inc.. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. Our sensors captured 88 malicious requests from this address across a 85-day span, reflecting a sustained attack cadence of ~1 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 (Path Enumeration and User-Agent Anomaly), suggesting a semi-automated campaign that targets multiple vulnerabilities. With 196 flagged addresses, Germany represents a significant presence in our threat database. The score of 75/100 indicates a confirmed malicious actor. Network-level blocking is appropriate.

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 Germany

15.220.152.241 (320)77.81.65.244 (313)185.168.29.98 (313)91.217.249.222 (305)212.30.36.219 (305)View all →

🏢 Same network: AS13335

104.28.246.115 (350)104.28.246.113 (340)104.28.246.116 (340)104.28.235.58 (340)104.28.246.122 (340)View all →
12

Security Intelligence

💡 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.

💡 SSH Brute Force Defense

SSH servers face constant brute force attacks targeting common usernames and weak passwords. Key-based authentication, fail2ban, non-standard ports, and IP allowlisting dramatically reduce the attack surface. Monitoring auth logs reveals active campaigns and compromised credentials.

🔍 Check Any IP Address

Share this report: