ABUSE.MOM
THREAT REPORT

IP Threat Report
35.200.47.235

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-10-25 06:22:18
First seen: 2026-08-03 05:18:05
Last seen: 2026-08-30 00:03:36
170

⛔ Verdict: BLOCK

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

BURSTDANGER_PATH
01

Geolocation & Classification

IP Address
35.200.47.235
Type
Hosting
Country
🇯🇵 Japan
City
Tokyo
ISP
Google LLC
Organization
Google Cloud (asia-northeast1)
Autonomous System
AS396982 Google LLC
Hit Count
213
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 19/10sAbnormally fast request rate — automated scanning+35
Burst 19/2sAbnormally fast request rate — automated scanning+35
Burst 24/10sAbnormally fast request rate — automated scanning+35
Burst 24/2sAbnormally fast request rate — automated scanning+35
Danger strong hits: 10High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 24High-risk paths: shells, RCE vectors, exploits+100
Σ = 340
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-08-03 05:18:05
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 19/10s (+35), Burst 19/2s (+35), Burst 24/10s (+35)
2026-08-30 00:03:36
Last malicious request observed
Total score reached: 170/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Google LLC
AS396982 · 🇯🇵 Japan

We have detected 8222 malicious IPs from this autonomous system.

View all IPs from AS396982 →
06

Recommendations

Actions taken & recommended

  • IP 35.200.47.235 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 35.200.47.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 35.200.47.235 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.

07

Neighbors in 35.200.47.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
spam.dnsbl.sorbs.net
✓ Clean
b.barracudacentral.org
✓ Clean
psbl.surriel.com
✓ Clean
dnsbl.dronebl.org

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

10

Threat Analysis

35.200.47.235 has been assigned a threat score of 170/100 (Critical). This places it in the critical threat category. Immediate blocking is strongly advised across all network perimeters.

The following attack categories were identified:

Request Flooding

📊 Threat Analysis

Threat intelligence analysis has linked 35.200.47.235 to malicious activity originating from Tokyo, Japan, operating on the network of Google LLC. The address has been under observation since its initial detection. Over a period of 26 days, this IP generated 213 malicious requests, averaging approximately 8.2 requests per day. 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. With 1,341 flagged addresses, Japan represents a major presence in our threat database. At 170/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 Japan

103.163.220.216 (340)35.189.151.182 (320)168.110.63.243 (320)168.110.58.114 (320)129.225.172.187 (310)View all →

🏢 Same network: AS396982

34.78.110.28 (348)136.67.84.210 (340)34.74.191.44 (340)136.67.103.22 (340)35.254.195.37 (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.

💡 HTTP Header Analysis for Threat Detection

Examining HTTP headers beyond User-Agent reveals attack tools and automated scripts. Missing standard headers, unusual ordering, non-standard values, and inconsistencies with claimed client identity all serve as reliable detection signals.

🔍 Check Any IP Address

Share this report: