ABUSE.MOM
THREAT REPORT

IP Threat Report
173.230.129.37

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-30 01:50:56
First seen: 2026-07-24 17:30:46
Last seen: 2026-07-26 04:01:35
225

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHREFERERUA_CHANGED
01

Geolocation & Classification

IP Address
173.230.129.37
Type
Hosting
Country
🇺🇸 United States
City
Atlanta
ISP
Akamai Technologies, Inc.
Organization
Linode
Autonomous System
AS63949 Akamai Connected Cloud
Hit Count
48
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 31/10sAbnormally fast request rate — automated scanning+35
Burst 31/2sAbnormally fast request rate — automated scanning+35
Danger medium hits: 2Medium-risk: admin panels, config files+20
Danger strong hits: 5High-risk paths: shells, RCE vectors, exploits+100
Foreign refererReferer from unrelated external domain+10
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 225
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-24 17:30:46
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 31/10s (+35), Burst 31/2s (+35), Danger medium hits: 2 (+20)
2026-07-26 04:01:35
Last malicious request observed
Total score reached: 225/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Akamai Technologies, Inc.
AS63949 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

  • IP 173.230.129.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

🌊 Flood / DDoS Mitigation

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

🤖 User-Agent Anomaly Defense

IP 173.230.129.37 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
bl.blocklist.de
✓ Clean
zen.spamhaus.org
✓ Clean
cbl.abuseat.org
✓ Clean
dnsbl.dronebl.org
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
b.barracudacentral.org
✓ Clean
psbl.surriel.com

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

10

Threat Analysis

173.230.129.37 has been assigned a threat score of 225/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:

Request FloodingUser-Agent Anomaly

📊 Threat Analysis

Our monitoring infrastructure has identified 173.230.129.37, geolocated to Atlanta, United States, operating on the network of Akamai Technologies, Inc., as a source of suspicious network activity. Over a period of 1 days, this IP generated 48 malicious requests, averaging approximately 48 requests per day. Operating from datacenter infrastructure, this IP is typical of addresses used in organized attack operations. Cloud and VPS providers are commonly exploited as launching platforms for automated scanning. Two attack patterns were identified (Request Flooding and User-Agent Anomaly), suggesting a semi-automated campaign that targets multiple vulnerabilities. With 155 flagged addresses, United States represents a significant presence in our threat database. At 225/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 United States

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

🏢 Same network: AS63949

172.235.133.193 (240)97.107.128.157 (240)173.255.253.10 (240)69.164.214.57 (225)192.155.89.179 (225)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.

💡 Machine Learning in Threat Detection

Machine learning models analyze vast amounts of network traffic to identify attack patterns invisible to rule-based systems. Supervised models classify known attack types while unsupervised models detect anomalies that may indicate novel threats.

🔍 Check Any IP Address

Share this report: