ABUSE.MOM
THREAT REPORT

IP Threat Report
216.228.180.161

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 05:51:01
First seen: 2026-05-24 01:28:23
Last seen: 2026-05-24 09:59:45
75

⛔ Verdict: BLOCK

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

BURSTRATIO_404UA_CHANGED
01

Geolocation & Classification

IP Address
216.228.180.161
Type
Residential
Country
🇺🇸 United States
City
Redmond
ISP
TDS TELECOM
Organization
TDS TELECOM
Autonomous System
AS4181 TDS TELECOM
Hit Count
26
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Burst 7/2sAbnormally fast request rate — automated scanning+35
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 75
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-05-24 01:28:23
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), Burst 7/2s (+35), UA changed (+25)
2026-05-24 09:59:45
Last malicious request observed
Total score reached: 75/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

TDS TELECOM
AS4181 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

  • IP 216.228.180.161 is blocked at application level (HTTP 403)
  • Consider blocking at firewall level (iptables/CSF) to reduce server load
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🔎 Directory Scan Defense

IP 216.228.180.161 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

🌊 Flood / DDoS Mitigation

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

🤖 Bot Detection

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

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

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

10

Threat Analysis

216.228.180.161 has been assigned a threat score of 75/100 (High). This score indicates high threat severity. The IP has shown clear patterns of malicious behavior that warrant immediate defensive measures.

The following attack categories were identified:

Path EnumerationRequest FloodingUser-Agent Anomaly

📊 Threat Analysis

Network traffic from 216.228.180.161, located in Redmond, United States, operating on the network of TDS TELECOM, has been classified as malicious by our automated threat scoring engine. Over a period of 1 days, this IP generated 26 malicious requests, averaging approximately 26 requests per day. This is a residential IP address, suggesting a compromised home device such as a router, smart appliance, or infected workstation participating in a botnet. With 3 different attack patterns detected, this IP exhibits behavior characteristic of advanced automated scanning frameworks. With 108 flagged addresses, United States represents a significant presence in our threat database. The score of 75/100 indicates a confirmed malicious actor. Network-level blocking is appropriate.

This IP is classified as residential, suggesting it may belong to a compromised home device, IoT botnet member, or an infected personal computer. Residential IPs involved in attacks often indicate malware infection without the owner's knowledge.

11

Related Threats

🇺🇸 Top threats from United States

104.28.246.115 (350)104.28.246.113 (340)104.28.246.116 (340)104.28.235.58 (340)104.28.246.122 (340)View all →

🏢 Same network: AS4181

135.135.151.47 (85)69.130.190.17 (70)134.215.218.19 (70)96.61.187.8 (70)208.100.174.162 (70)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.

💡 WebSocket Security Considerations

WebSocket connections bypass traditional HTTP security controls, creating opportunities for cross-site WebSocket hijacking, denial of service, and data injection. Proper origin validation, authentication, and message rate limiting are essential for secure WebSocket implementations.

🔍 Check Any IP Address

Share this report: