
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Directory Scan | Behavioral anomaly detected by automated analysis | +0 | |
| DDoS / Flood | Behavioral anomaly detected by automated analysis | +0 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Add 35.237.139.35 to your firewall blocklist. Review logs for successful connections. Enable comprehensive logging on all public-facing services.
This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.
Checked: Spamhaus, SpamCop, Barracuda, SORBS, CBL, UCEProtect. Results may change over time.
35.237.139.35 has been assigned a threat score of 320/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.
The address 35.237.139.35 originates from North Charleston, United States, operating on the network of Google LLC. It was identified through automated analysis of incoming network traffic across monitored endpoints. During its 18-day observation window, we recorded 180 hostile requests from this IP — roughly 10 per day on average. United States currently accounts for 101 blocked IPs in our database, making it a significant source of malicious traffic. With a threat score of 320/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.
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.
Zero trust eliminates implicit trust based on network location. Every access request is verified regardless of source, minimizing the impact of compromised credentials or network breaches. Implementation requires strong identity verification and continuous authorization.