ABUSE.MOM
THREAT REPORT

IP Threat Report
65.21.113.196

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-26 05:20:58
First seen: 2026-06-03 19:38:50
Last seen: 2026-07-12 00:56:15
70

⛔ Verdict: BLOCK

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

BURSTRATIO_404REDIRECT_PROBE
01

Geolocation & Classification

IP Address
65.21.113.196
Type
Unknown
Country
🇫🇮 Finland
City
Helsinki
ISP
Hetzner Online GmbH
Organization
Hetzner Online GmbH
Autonomous System
Unknown
Hit Count
242
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Burst 5/2sAbnormally fast request rate — automated scanning+35
DDoS / FloodBehavioral anomaly detected by automated analysis+0
Directory ScanBehavioral anomaly detected by automated analysis+0
Probe 302→404Behavioral anomaly detected by automated analysis+20
Σ = 70
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-06-03 19:38:50
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), Burst 5/2s (+35), DDoS / Flood
2026-07-12 00:56:15
Last malicious request observed
Total score reached: 70/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
06

Recommendations

Actions taken & recommended

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

🔎 Path Enumeration Protection

Block scanning from 65.21.113.196: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

🌊 Flood / DDoS Mitigation

Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 65.21.113.196.

07

Neighbors in 65.21.113.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
bl.blocklist.de
✓ Clean
cbl.abuseat.org

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

10

Threat Analysis

65.21.113.196 has been assigned a threat score of 70/100 (High). This classifies it as a high-severity threat. Proactive blocking is recommended for sensitive infrastructure.

The following attack categories were identified:

Path EnumerationRequest Flooding

📊 Threat Analysis

Network traffic from 65.21.113.196, located in Helsinki, Finland, operating on the network of Hetzner Online GmbH, has been classified as malicious by our automated threat scoring engine. The address has been active for 38 days in our monitoring system, producing 242 flagged requests at a rate of ~6.4/day. Two attack patterns were identified (Path Enumeration and Request Flooding), suggesting a semi-automated campaign that targets multiple vulnerabilities. With 109 flagged addresses, Finland represents a significant presence in our threat database. At 70/100, this IP warrants immediate defensive action.

11

Related Threats

🇫🇮 Top threats from Finland

193.148.56.79 (328)193.148.56.148 (328)193.148.56.61 (328)193.148.57.33 (313)34.88.133.99 (295)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/2 and HTTP/3 Security Implications

Modern HTTP protocols introduce new attack surfaces including stream multiplexing abuse, header compression attacks (HPACK bombing), and rapid reset attacks. Security tools must evolve to handle these protocol-specific threats effectively.

🔍 Check Any IP Address

Share this report: