ABUSE.MOM
THREAT REPORT

IP Threat Report
34.22.44.31

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-28 16:54:13
First seen: 2026-06-15 03:43:04
Last seen: 2026-06-21 04:35:11
195

⛔ Verdict: BLOCK

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

01

Geolocation & Classification

IP Address
34.22.44.31
Type
Unknown
Country
🇺🇸 United States
City
Salt Lake City
ISP
Google LLC
Organization
Google LLC
Autonomous System
Unknown
Hit Count
262
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-15 03:43:04
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
DDoS / Flood
2026-06-21 04:35:11
Last malicious request observed
Total score reached: 195/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
06

Recommendations

Actions taken & recommended

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

⚙️ Defensive Recommendations

Block 34.22.44.31 at the network perimeter. Implement defense-in-depth combining IP blocking with application-layer protections.

07

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

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

10

Threat Analysis

34.22.44.31 has been assigned a threat score of 195/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 34.22.44.31 originates from Salt Lake City, United States, operating on the network of Google LLC. It was identified through automated analysis of incoming network traffic across monitored endpoints. Over a period of 6 days, this IP generated 262 malicious requests, averaging approximately 43.7 requests per day. With 107 flagged addresses, United States represents a significant presence in our threat database. A score of 195/100 places this address in the top tier of severity. Block and investigate any historical connections.

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.

💡 Subnet-Level vs IP-Level Blocking

When multiple IPs in a subnet show malicious behavior, subnet blocking efficiently neutralizes the threat. However, overly broad blocking risks impacting legitimate users. Analysis of subnet ownership and historical behavior guides appropriate blocking scope.

🔍 Check Any IP Address

Share this report: