
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.
Block 100.36.224.138 at the network perimeter. Implement defense-in-depth combining IP blocking with application-layer protections.
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.
100.36.224.138 has been assigned a threat score of 200/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.
IP address 100.36.224.138 has been traced to Gaithersburg, United States, operating on the network of Verizon Communications. Our threat detection systems have flagged this address based on observed malicious behavior patterns. Over a period of 7 days, this IP generated 232 malicious requests, averaging approximately 33.1 requests per day. Our records show 101 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. With a threat score of 200/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.
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.