ABUSE.MOM
THREAT REPORT

IP Threat Report
35.209.101.52

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-22 00:56:42
First seen: 2026-05-04 09:00:06
Last seen: 2026-05-04 10:00:07
80

⛔ Verdict: BLOCK

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

BURSTREFERERRATIO_404
01

Geolocation & Classification

IP Address
35.209.101.52
Type
Hosting
Country
🇺🇸 United States
City
Council Bluffs
ISP
Google LLC
Organization
Google Cloud (us-central1)
Autonomous System
AS15169 Google LLC
Hit Count
2
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst: 9 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 12 req / 10sAbnormally fast request rate — automated scanning+35
Foreign referer seenReferer from unrelated external domain+10
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Burst: 5 req / 2sAbnormally fast request rate — automated scanning+35
Σ = 130
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-04 09:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst: 9 req / 2s (+35), Burst: 12 req / 10s (+35), Foreign referer seen (+10)
2026-05-04 10:00:07
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 35.209.101.52 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 35.209.101.52.

🔎 Directory Scan Defense

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

09

Blacklist Status (DNSBL)

This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.

✓ Clean
ix.dnsbl.manitu.net
✓ Clean
dnsbl.sorbs.net
✓ Clean
bl.spamcop.net
✓ Clean
zen.spamhaus.org
✓ Clean
b.barracudacentral.org
✓ Clean
truncate.gbudb.net
✓ Clean
psbl.surriel.com
✓ Clean
dnsbl-1.uceprotect.net

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

10

Threat Analysis

35.209.101.52 has been assigned a threat score of 80/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 FloodingPath Enumeration

📊 Threat Analysis

35.209.101.52 is registered in Council Bluffs, United States, operating on the network of Google LLC. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. During its 1-day observation window, we recorded 2 hostile requests from this IP — roughly 2 per day on average. Classified as a hosting IP, this address likely runs on a rented server or cloud instance. Attackers prefer datacenter IPs for their high bandwidth and disposable nature. The dual attack vectors of Request Flooding combined with Path Enumeration indicate a coordinated assault rather than opportunistic scanning. With 201 flagged addresses, United States represents a significant presence in our threat database. At 80/100, this IP warrants immediate defensive action.

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.

💡 IPv6 Scanning Challenges

The vast IPv6 address space makes traditional sequential scanning impractical. However, attackers use DNS records, certificate transparency logs, and predictable address patterns to identify active IPv6 hosts, adapting their techniques to the expanded address space.

🔍 Check Any IP Address

Share this report: