ABUSE.MOM
THREAT REPORT

IP Threat Report
173.239.196.71

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-09-11 05:31:39
First seen: 2026-08-08 04:51:23
Last seen: 2026-08-09 04:10:03
255

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHUA_CHANGED
01

Geolocation & Classification

IP Address
173.239.196.71
Type
Hosting
Country
🇰🇿 KZ
City
Nur-sultan
ISP
F.N.S. HOLDINGS LIMITED
Organization
LogicWeb Inc
Autonomous System
AS206092 F.N.S. HOLDINGS LIMITED
Hit Count
27
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 24/10sAbnormally fast request rate — automated scanning+35
Burst 7/2sAbnormally fast request rate — automated scanning+35
Danger medium hits: 969Medium-risk: admin panels, config files+60
Danger strong hits: 372High-risk paths: shells, RCE vectors, exploits+100
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 255
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-08-08 04:51:23
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 24/10s (+35), Burst 7/2s (+35), Danger medium hits: 969 (+60)
2026-08-09 04:10:03
Last malicious request observed
Total score reached: 255/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

F.N.S. HOLDINGS LIMITED
AS206092 · 🇰🇿 KZ
06

Recommendations

Actions taken & recommended

  • IP 173.239.196.71 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 173.239.196.0/24
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🌊 Traffic Flood Defense

IP 173.239.196.71 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.

🤖 User-Agent Anomaly Defense

IP 173.239.196.71 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.

07

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

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

10

Threat Analysis

173.239.196.71 has been assigned a threat score of 255/100 (Critical). With this rating, the IP falls into the critical severity bracket — among the most dangerous addresses in our monitoring database.

The following attack categories were identified:

Request FloodingUser-Agent Anomaly

📊 Threat Analysis

Threat intelligence analysis has linked 173.239.196.71 to malicious activity originating from Nur-sultan, KZ, operating on the network of F.N.S. HOLDINGS LIMITED. The address has been under observation since its initial detection. Over a period of 1 days, this IP generated 27 malicious requests, averaging approximately 27 requests per day. Classified as a hosting IP, this address likely runs on a rented server or cloud instance. Attackers prefer datacenter IPs for their high bandwidth and disposable nature. The dual attack vectors of Request Flooding combined with User-Agent Anomaly indicate a coordinated assault rather than opportunistic scanning. KZ currently accounts for 101 blocked IPs in our database, making it a significant source of malicious traffic. 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.

This IP belongs to a hosting or data center provider. Malicious traffic from hosting infrastructure often originates from compromised VPS instances, rented servers used for scanning campaigns, or abused free-tier cloud accounts. Hosting providers typically respond to abuse reports within 24-72 hours.

11

Related Threats

🇰🇿 Top threats from KZ

173.239.196.75 (255)173.239.196.79 (255)173.239.196.73 (255)173.239.196.67 (255)89.169.36.121 (200)View all →

🏢 Same network: AS206092

173.239.196.75 (255)173.239.196.79 (255)173.239.196.73 (255)173.239.196.67 (255)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.

💡 IPv6 Scanning Challenges

The vast IPv6 address space makes traditional sequential scanning impractical. However, attackers use DNS records, certificate transparency logs, and predictable address patterns to identify active IPv6 hosts, adapting their techniques to the expanded address space.

🔍 Check Any IP Address

Share this report: