ABUSE.MOM
THREAT REPORT

IP Threat Report
172.213.0.0

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 11:31:57
First seen: 2026-03-30 10:00:08
Last seen: 2026-04-03 16:00:06
280

⛔ Verdict: BLOCK

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

UA_SUSDANGER_PATHBURSTRATIO_404REDIRECT_PROBE
01

Geolocation & Classification

IP Address
172.213.0.0
Type
Hosting
Country
🇮🇹 Italy
City
Milan
ISP
Microsoft Corporation
Organization
Microsoft Azure Cloud (italynorth)
Autonomous System
AS8075 Microsoft Corporation
Hit Count
31
02

Detection Signatures

SignatureDescriptionPointsSeverity
UA suspicious (short/empty)Behavioral anomaly detected by automated analysis+15
Danger strong hits: 9High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 286Medium-risk: admin panels, config files+60
Burst: 51 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 142 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 32 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 98 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 6High-risk paths: shells, RCE vectors, exploits+100
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Probe pattern 302->404 same pathBehavioral anomaly detected by automated analysis+20
Burst: 48 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 50 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 167 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 12High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 429Medium-risk: admin panels, config files+60
Burst: 181 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 54 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 193 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 197 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 52 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 175 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 3High-risk paths: shells, RCE vectors, exploits+75
Danger medium hits: 134Medium-risk: admin panels, config files+60
Burst: 173 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Burst: 134 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 4High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 201Medium-risk: admin panels, config files+60
Burst: 55 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 38 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 129 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 42 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 140 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 199 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 44 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 153 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 168 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 187 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 58 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 59 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 200 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 56 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 60 req / 2sAbnormally fast request rate — automated scanning+35
Danger medium hits: 176Medium-risk: admin panels, config files+60
Burst: 198 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 53 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 186 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 172 req / 10sAbnormally fast request rate — automated scanning+35
Σ = 2065
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-03-30 10:00:08
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
UA suspicious (short/empty) (+15), Danger strong hits: 9 (+100), Danger medium hits: 286 (+60)
2026-04-03 16:00:06
Last malicious request observed
Total score reached: 280/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Microsoft Corporation
AS8075 · 🇮🇹 Italy
06

Recommendations

Actions taken & recommended

  • IP 172.213.0.0 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.213.0.0/24
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🤖 Bot Detection

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

🌊 Flood / DDoS Mitigation

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

🔎 Path Enumeration Protection

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

07

Neighbors in 172.213.0.0/24

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

08

Open Ports & Services

Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.

OPEN PORTS (2)
PortServiceRiskDescription
80HTTPLowHTTP web server — standard web traffic
443HTTPSLowHTTPS web server — encrypted web traffic
DETECTED TECHNOLOGIES
microsoft:asp.netf5:nginx:1.28.1

Data source: Shodan InternetDB. Scanned independently of abuse.mom.

09

Blacklist Status (DNSBL)

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

✓ Clean
ix.dnsbl.manitu.net
✓ Clean
bl.spamcop.net
✓ Clean
dnsbl.sorbs.net
✓ Clean
zen.spamhaus.org
✓ Clean
dnsbl-1.uceprotect.net
✓ Clean
psbl.surriel.com
✓ Clean
b.barracudacentral.org
✓ Clean
truncate.gbudb.net

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

10

Threat Analysis

172.213.0.0 has been assigned a threat score of 280/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.

The following attack categories were identified:

User-Agent AnomalyRequest FloodingPath Enumeration

📊 Threat Analysis

IP address 172.213.0.0 has been traced to Milan, Italy, operating on the network of Microsoft Corporation. Our threat detection systems have flagged this address based on observed malicious behavior patterns. The address has been active for 4 days in our monitoring system, producing 31 flagged requests at a rate of ~7.8/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. The combination of 3 distinct attack vectors indicates a sophisticated, multi-pronged threat actor deploying automated tools that probe multiple attack surfaces simultaneously. Our records show 102 malicious IPs originating from Italy, positioning it as a significant contributor to global threat activity. At 280/100, this is an extremely high-risk address. All traffic should be considered hostile.

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 Italy

141.11.36.94 (305)2.57.170.51 (295)45.91.20.90 (295)4.232.88.90 (280)172.213.16.18 (280)View all →

🏢 Same network: AS8075

74.241.249.229 (340)20.151.111.128 (308)4.182.24.88 (285)20.65.61.3 (283)4.205.39.97 (283)View all →
12

Security Intelligence

💡 HTTP Header Analysis for Threat Detection

Examining HTTP headers beyond User-Agent reveals attack tools and automated scripts. Missing standard headers, unusual ordering, non-standard values, and inconsistencies with claimed client identity all serve as reliable detection signals.

💡 Watering Hole Attack Strategy

Watering hole attacks compromise websites frequently visited by target organizations. Rather than attacking targets directly, adversaries infect trusted resources, exploiting the inherent trust users place in regularly visited sites.

🔍 Check Any IP Address

Share this report: