ABUSE.MOM
THREAT REPORT

IP Threat Report
165.227.31.1

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-10-25 18:25:55
First seen: 2026-10-06 10:01:12
Last seen: 2026-10-11 01:05:48
135

⛔ Verdict: BLOCK

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

BURSTDANGER_PATH
01

Geolocation & Classification

IP Address
165.227.31.1
Type
Hosting
Country
🇺🇸 United States
City
Santa Clara
ISP
DigitalOcean, LLC
Organization
DigitalOcean, LLC
Autonomous System
AS14061 DigitalOcean, LLC
Hit Count
168
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 5/2sAbnormally fast request rate — automated scanning+35
Danger strong hits: 10High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 16High-risk paths: shells, RCE vectors, exploits+100
Σ = 235
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-10-06 10:01:12
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 5/2s (+35), Danger strong hits: 10 (+100), Danger strong hits: 16 (+100)
2026-10-11 01:05:48
Last malicious request observed
Total score reached: 135/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

DigitalOcean, LLC
AS14061 · 🇺🇸 United States

We have detected 6979 malicious IPs from this autonomous system.

View all IPs from AS14061 →
06

Recommendations

Actions taken & recommended

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

07

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

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

10

Threat Analysis

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

The following attack categories were identified:

Request Flooding

📊 Threat Analysis

IP address 165.227.31.1 has been traced to Santa Clara, United States, operating on the network of DigitalOcean, LLC. Our threat detection systems have flagged this address based on observed malicious behavior patterns. The address has been active for 4 days in our monitoring system, producing 168 flagged requests at a rate of ~42/day. The IP is classified as hosting/datacenter infrastructure, commonly associated with rented servers used for automated attack campaigns, botnet command-and-control, or vulnerability scanning at scale. The IP is engaged in request flooding, sending traffic at rates designed to exhaust server capacity. United States currently accounts for 36,292 blocked IPs in our database, making it a major source of malicious traffic. With a threat score of 135/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 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: AS14061

129.212.237.216 (308)168.144.34.140 (295)170.64.203.182 (280)159.223.199.244 (280)168.144.130.251 (280)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.

💡 TLS Certificate Misconfigurations

Expired, self-signed, or misconfigured TLS certificates create security vulnerabilities and trust issues. Certificate monitoring, automated renewal through ACME protocols, and proper certificate chain configuration prevent both security gaps and service disruptions.

🔍 Check Any IP Address

Share this report: