ABUSE.MOM
THREAT REPORT

IP Threat Report
8.230.96.173

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-29 14:01:23
First seen: 2026-06-13 11:56:57
Last seen: 2026-06-20 19:18:02
105

⛔ Verdict: BLOCK

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

01

Geolocation & Classification

IP Address
8.230.96.173
Type
Unknown
Country
🇺🇸 United States
City
Dallas
ISP
Google LLC
Organization
Google LLC
Autonomous System
Unknown
Hit Count
22
02

Detection Signatures

SignatureDescriptionPointsSeverity
DDoS / FloodBehavioral anomaly detected by automated analysis+0
Σ = 0
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-06-13 11:56:57
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
DDoS / Flood
2026-06-20 19:18:02
Last malicious request observed
Total score reached: 105/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
06

Recommendations

Actions taken & recommended

  • IP 8.230.96.173 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 8.230.96.0/24
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

⚙️ General Security

Add 8.230.96.173 to your firewall blocklist. Review logs for successful connections. Enable comprehensive logging on all public-facing services.

07

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

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

10

Threat Analysis

8.230.96.173 has been assigned a threat score of 105/100 (Critical). A score this high marks a critical threat actor. This address has demonstrated persistent, aggressive malicious behavior across multiple detection vectors.

📊 Threat Analysis

The address 8.230.96.173 originates from Dallas, United States, operating on the network of Google LLC. It was identified through automated analysis of incoming network traffic across monitored endpoints. Our sensors captured 22 malicious requests from this address across a 7-day span, reflecting a sustained attack cadence of ~3.1 requests per day. Our records show 104 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. At 105/100, this is an extremely high-risk address. All traffic should be considered hostile.

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

💡 Security Header Best Practices

HTTP security headers provide defense-in-depth with minimal implementation effort. Key headers include Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, and Permissions-Policy, each addressing specific attack vectors.

🔍 Check Any IP Address

Share this report: