ABUSE.MOM
THREAT REPORT

IP Threat Report
135.136.0.113

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-29 05:47:17
First seen: 2026-06-13 23:16:55
Last seen: 2026-06-27 23:57:20
255

⛔ Verdict: BLOCK

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

01

Geolocation & Classification

IP Address
135.136.0.113
Type
Unknown
Country
🇩🇪 Germany
City
Frankfurt am Main
ISP
M247 Europe SRL
Organization
M247 Europe SRL
Autonomous System
Unknown
Hit Count
117
02

Detection Signatures

SignatureDescriptionPointsSeverity
DDoS / FloodBehavioral anomaly detected by automated analysis+0
Σ = 0
03

Observed Activity

Reconstructed HTTP requests from server access logs. Target domains redacted for security.

[redacted]
GET
/
200
Requests shown: 1 · HTTP 404: 0 · Dangerous patterns: 0

* Typical request patterns for detected signatures. Actual target domains are redacted.

04

Timeline

2026-06-13 23:16:55
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
DDoS / Flood
2026-06-27 23:57:20
Last malicious request observed
Total score reached: 255/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
06

Recommendations

Actions taken & recommended

  • IP 135.136.0.113 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 135.136.0.0/24
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

⚙️ Defensive Recommendations

Block 135.136.0.113 at the network perimeter. Implement defense-in-depth combining IP blocking with application-layer protections.

07

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

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

10

Threat Analysis

135.136.0.113 has been assigned a threat score of 255/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.

📊 Threat Analysis

IP address 135.136.0.113 has been traced to Frankfurt am Main, Germany, operating on the network of M247 Europe SRL. Our threat detection systems have flagged this address based on observed malicious behavior patterns. The address has been active for 14 days in our monitoring system, producing 117 flagged requests at a rate of ~8.4/day. With 119 flagged addresses, Germany represents a significant presence in our threat database. With a threat score of 255/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.

11

Related Threats

🇩🇪 Top threats from Germany

15.220.152.241 (320)35.246.204.221 (320)185.168.29.98 (313)77.81.65.244 (313)64.89.163.68 (308)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.

💡 Privacy-Preserving Threat Detection

Advanced techniques enable threat detection while minimizing privacy impact. Encrypted DNS, differential privacy in analytics, and federated learning for threat models allow effective security monitoring without unnecessary surveillance of legitimate user behavior.

🔍 Check Any IP Address

Share this report: