ABUSE.MOM
THREAT REPORT

IP Threat Report
172.202.30.101

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-26 05:10:17
First seen: 2026-07-20 21:15:51
Last seen: 2026-07-26 04:07:16
255

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHRATIO_404
01

Geolocation & Classification

IP Address
172.202.30.101
Type
Hosting
Country
🇺🇸 United States
City
Des Moines
ISP
Microsoft
Organization
Microsoft Azure Cloud (centralus)
Autonomous System
AS8075 Microsoft Corporation
Hit Count
6548
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Burst 14/2sAbnormally fast request rate — automated scanning+35
Burst 15/2sAbnormally fast request rate — automated scanning+35
Burst 19/2sAbnormally fast request rate — automated scanning+35
Burst 20/2sAbnormally fast request rate — automated scanning+35
Burst 21/2sAbnormally fast request rate — automated scanning+35
Burst 49/10sAbnormally fast request rate — automated scanning+35
Burst 53/10sAbnormally fast request rate — automated scanning+35
Burst 54/10sAbnormally fast request rate — automated scanning+35
Burst 55/10sAbnormally fast request rate — automated scanning+35
Burst 61/10sAbnormally fast request rate — automated scanning+35
Burst 62/10sAbnormally fast request rate — automated scanning+35
Burst 63/10sAbnormally fast request rate — automated scanning+35
Burst 65/10sAbnormally fast request rate — automated scanning+35
Burst 66/10sAbnormally fast request rate — automated scanning+35
Burst 67/10sAbnormally fast request rate — automated scanning+35
Burst 68/10sAbnormally fast request rate — automated scanning+35
Burst 69/10sAbnormally fast request rate — automated scanning+35
Burst 70/10sAbnormally fast request rate — automated scanning+35
Burst 72/10sAbnormally fast request rate — automated scanning+35
Burst 73/10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 184Medium-risk: admin panels, config files+60
Danger medium hits: 74Medium-risk: admin panels, config files+60
Danger medium hits: 84Medium-risk: admin panels, config files+60
Danger strong hits: 35High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 39High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 64High-risk paths: shells, RCE vectors, exploits+100
Σ = 1205
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-07-20 21:15:51
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio >= 60% (+25), Burst 14/2s (+35), Burst 15/2s (+35)
2026-07-26 04:07:16
Last malicious request observed
Total score reached: 255/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Microsoft
AS8075 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

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

🔎 Directory Scan Defense

IP 172.202.30.101 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

🌊 Flood / DDoS Mitigation

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

07

Neighbors in 172.202.30.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.

✓ Clean
b.barracudacentral.org
✓ Clean
psbl.surriel.com
✓ Clean
spam.dnsbl.sorbs.net

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

10

Threat Analysis

172.202.30.101 has been assigned a threat score of 255/100 (Critical). This places it in the critical threat category. Immediate blocking is strongly advised across all network perimeters.

The following attack categories were identified:

Path EnumerationRequest Flooding

📊 Threat Analysis

Our monitoring infrastructure has identified 172.202.30.101, geolocated to Des Moines, United States, operating on the network of Microsoft, as a source of suspicious network activity. During its 5-day observation window, we recorded 6,548 hostile requests from this IP — roughly 1309.6 per day on average. This address belongs to a datacenter or cloud hosting provider. Hosting IPs are frequently leveraged by threat actors who rent cheap VPS instances specifically for conducting attacks. The dual attack vectors of Path Enumeration combined with Request Flooding indicate a coordinated assault rather than opportunistic scanning. With 108 flagged addresses, United States represents a significant presence in our threat database. With a threat score of 255/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.

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 States

104.28.246.115 (350)104.28.214.122 (350)103.215.74.213 (340)103.168.66.237 (340)34.187.158.4 (340)View all →

🏢 Same network: AS8075

20.226.81.88 (280)20.48.26.146 (280)191.234.169.57 (280)52.237.113.70 (280)104.208.65.18 (280)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.

💡 False Positive Management

False positives erode trust in security systems and waste analyst resources. Effective management requires feedback loops, allowlisting mechanisms, contextual analysis, and regular tuning of detection rules based on operational experience.

🔍 Check Any IP Address

Share this report: