ABUSE.MOM
THREAT REPORT

IP Threat Report
216.73.217.70

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 07:26:57
First seen: 2026-04-26 14:00:04
Last seen: 2026-05-01 00:00:05
65

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404REDIRECT_PROBEREFERER
01

Geolocation & Classification

IP Address
216.73.217.70
Type
Hosting
Country
🇺🇸 United States
City
Columbus
ISP
Amazon.com
Organization
Anthropic, PBC
Autonomous System
AS16509 Amazon.com, Inc.
Hit Count
11
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger medium hits: 2Medium-risk: admin panels, config files+20
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Probe pattern 302->404 same pathBehavioral anomaly detected by automated analysis+20
Foreign referer seenReferer from unrelated external domain+10
Σ = 65
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-04-26 14:00:04
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger medium hits: 2 (+20), 404 ratio 40-60% (+15), Probe pattern 302->404 same path (+20)
2026-05-01 00:00:05
Last malicious request observed
Total score reached: 65/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Amazon.com
AS16509 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

  • IP 216.73.217.70 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 216.73.217.0/24
  • 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.73.217.70 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

07

Neighbors in 216.73.217.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
ix.dnsbl.manitu.net
✓ Clean
dnsbl.sorbs.net
✓ Clean
dnsbl-1.uceprotect.net
✓ Clean
bl.spamcop.net
✓ Clean
zen.spamhaus.org
✓ Clean
b.barracudacentral.org
✓ Clean
psbl.surriel.com
✓ Clean
truncate.gbudb.net

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

10

Threat Analysis

216.73.217.70 has been assigned a threat score of 65/100 (High). This classifies it as a high-severity threat. Proactive blocking is recommended for sensitive infrastructure.

The following attack categories were identified:

Path Enumeration

📊 Threat Analysis

IP address 216.73.217.70 has been traced to Columbus, United States, operating on the network of Amazon.com. Our threat detection systems have flagged this address based on observed malicious behavior patterns. Over a period of 4 days, this IP generated 11 malicious requests, averaging approximately 2.8 requests per day. Operating from datacenter infrastructure, this IP is typical of addresses used in organized attack operations. Cloud and VPS providers are commonly exploited as launching platforms for automated scanning. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. Our records show 166 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. The score of 65/100 warrants active monitoring and rate-limiting. Full blocking is advisable for sensitive systems.

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.246.113 (340)104.28.246.116 (340)104.28.235.58 (340)104.28.246.122 (340)View all →

🏢 Same network: AS16509

15.220.152.241 (320)18.219.106.176 (315)15.220.169.114 (280)108.136.131.13 (265)54.206.58.169 (263)View all →
12

Security Intelligence

💡 Credential Stuffing at Scale

Credential stuffing uses stolen username-password pairs from data breaches to attempt logins across many websites. Since users frequently reuse passwords, these automated attacks achieve success rates of 0.1-2%, which translates to thousands of compromised accounts from millions of attempts.

💡 Supply Chain Security Challenges

Attacks targeting software supply chains compromise trusted update mechanisms to distribute malware at scale. Dependency confusion, typosquatting in package registries, and compromised build pipelines threaten even organizations with strong direct security postures.

🔍 Check Any IP Address

Share this report: