ABUSE.MOM
THREAT REPORT

IP Threat Report
205.169.39.80

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-09-10 08:16:36
First seen: 2026-07-19 10:09:59
Last seen: 2026-08-16 00:31:57
70

⛔ Verdict: BLOCK

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

BURSTREFERERUA_CHANGED
01

Geolocation & Classification

IP Address
205.169.39.80
Type
Hosting
Country
🇺🇸 United States
City
Santa Clara
ISP
CenturyLink Communications
Organization
Palo Alto Networks, Inc
Autonomous System
AS3356 Level 3 Parent, LLC
Hit Count
509
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 5/2sAbnormally fast request rate — automated scanning+35
Foreign refererReferer from unrelated external domain+10
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 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-07-19 10:09:59
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 5/2s (+35), Foreign referer (+10), UA changed (+25)
2026-08-16 00:31:57
Last malicious request observed
Total score reached: 70/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

CenturyLink Communications
AS3356 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

  • IP 205.169.39.80 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 205.169.39.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 205.169.39.80 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.

🤖 Bot Detection

Address UA spoofing from 205.169.39.80: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.

07

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

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

10

Threat Analysis

205.169.39.80 has been assigned a threat score of 70/100 (High). At this threat level, the IP is considered high risk. Firewall rules should be updated to deny traffic from this source.

The following attack categories were identified:

Request FloodingUser-Agent Anomaly

📊 Threat Analysis

205.169.39.80 is registered in Santa Clara, United States, operating on the network of CenturyLink Communications. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. During its 27-day observation window, we recorded 509 hostile requests from this IP — roughly 18.9 per day on average. This address belongs to a datacenter or cloud hosting provider. Hosting IPs are frequently leveraged by threat actors who rent cheap VPS instances specifically for conducting attacks. The dual attack vectors of Request Flooding combined with User-Agent Anomaly indicate a coordinated assault rather than opportunistic scanning. United States currently accounts for 153 blocked IPs in our database, making it a significant source of malicious traffic. The score of 70/100 indicates a confirmed malicious actor. Network-level blocking is appropriate.

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 United States

104.28.246.115 (350)104.28.214.122 (350)216.73.160.52 (350)34.187.158.4 (340)34.186.187.208 (340)View all →

🏢 Same network: AS3356

64.156.70.231 (135)205.169.39.57 (110)205.169.39.199 (105)205.169.39.208 (105)92.112.14.62 (85)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.

💡 Web Cache Poisoning Attacks

Cache poisoning manipulates web cache behavior to serve malicious content to other users. By identifying unkeyed inputs that influence cached responses, attackers can inject JavaScript, redirect users, or cause denial of service at scale through the cache infrastructure.

🔍 Check Any IP Address

Share this report: