ABUSE.MOM
THREAT REPORT

IP Threat Report
34.1.24.16

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 05:03:49
First seen: 2026-05-22 02:40:49
Last seen: 2026-05-24 10:10:34
80

⛔ Verdict: BLOCK

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

BURSTREFERER
01

Geolocation & Classification

IP Address
34.1.24.16
Type
Hosting
Country
🇺🇸 United States
City
Columbus
ISP
Google LLC
Organization
Google Cloud (us-east5)
Autonomous System
AS15169 Google LLC
Hit Count
84
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 10/10sAbnormally fast request rate — automated scanning+35
Burst 9/2sAbnormally fast request rate — automated scanning+35
Foreign refererReferer from unrelated external domain+10
Σ = 80
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-05-22 02:40:49
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 10/10s (+35), Burst 9/2s (+35), Foreign referer (+10)
2026-05-24 10:10:34
Last malicious request observed
Total score reached: 80/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Google LLC
AS15169 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

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

🌊 Traffic Flood Defense

IP 34.1.24.16 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.

07

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

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

10

Threat Analysis

34.1.24.16 has been assigned a threat score of 80/100 (Critical). This is a critical-level threat. Systems administrators should treat this IP as hostile and block all inbound connections without exception.

The following attack categories were identified:

Request Flooding

📊 Threat Analysis

Threat intelligence analysis has linked 34.1.24.16 to malicious activity originating from Columbus, United States, operating on the network of Google LLC. The address has been under observation since its initial detection. During its 2-day observation window, we recorded 84 hostile requests from this IP — roughly 42 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 IP is engaged in request flooding, sending traffic at rates designed to exhaust server capacity. United States currently accounts for 206 blocked IPs in our database, making it a significant source of malicious traffic. The score of 80/100 indicates a confirmed malicious actor. Network-level blocking is appropriate.

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.246.113 (340)104.28.246.116 (340)104.28.235.58 (340)104.28.246.122 (340)View all →

🏢 Same network: AS15169

66.249.82.32 (205)74.125.217.40 (175)192.178.11.96 (170)35.212.230.168 (170)209.85.238.2 (165)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.

💡 Subdomain Takeover Vulnerabilities

Subdomain takeover occurs when DNS records point to decommissioned services. Attackers claim the abandoned resource and serve content under the trusted domain, enabling cookie theft, phishing, and reputation damage.

🔍 Check Any IP Address

Share this report: