ABUSE.MOM
THREAT REPORT

IP Threat Report
217.116.53.171

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-29 11:11:35
First seen: 2026-06-22 07:56:27
Last seen: 2026-06-27 23:33:14
120

⛔ Verdict: BLOCK

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

01

Geolocation & Classification

IP Address
217.116.53.171
Type
Unknown
Country
🇷🇺 Russia
City
Tyumen
ISP
Russian company LLC
Organization
Russian company LLC
Autonomous System
Unknown
Hit Count
1762
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-22 07:56:27
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
DDoS / Flood
2026-06-27 23:33:14
Last malicious request observed
Total score reached: 120/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
06

Recommendations

Actions taken & recommended

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

⚙️ General Security

Add 217.116.53.171 to your firewall blocklist. Review logs for successful connections. Enable comprehensive logging on all public-facing services.

07

Neighbors in 217.116.53.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
bl.spamcop.net
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
cbl.abuseat.org
✓ Clean
bl.blocklist.de
✓ 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

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

📊 Threat Analysis

217.116.53.171 is registered in Tyumen, Russia, operating on the network of Russian company LLC. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. Our sensors captured 1,762 malicious requests from this address across a 5-day span, reflecting a sustained attack cadence of ~352.4 requests per day. Russia currently accounts for 102 blocked IPs in our database, making it a significant source of malicious traffic. At 120/100, this is an extremely high-risk address. All traffic should be considered hostile.

11

Related Threats

🇷🇺 Top threats from Russia

157.22.102.172 (313)178.130.54.159 (288)185.103.167.63 (265)72.56.191.6 (265)95.182.125.201 (265)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.

💡 BGP Hijacking and IP Spoofing

Border Gateway Protocol hijacking allows attackers to redirect internet traffic through their infrastructure. While less common than application-level attacks, BGP hijacks can intercept sensitive data, inject malware, or cause widespread service disruption.

🔍 Check Any IP Address

Share this report: