ABUSE.MOM
THREAT REPORT

IP Threat Report
216.73.216.48

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-28 00:08:41
First seen: 2026-02-21 02:50:04
Last seen: 2026-05-01 23:00:05
155

⛔ Verdict: BLOCK

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

RATIO_404REDIRECT_PROBEREFERERBURSTUA_SUSDANGER_PATH
01

Geolocation & Classification

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

Detection Signatures

SignatureDescriptionPointsSeverity
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
Burst: 7 req / 2sAbnormally fast request rate — automated scanning+35
UA suspicious (short/empty)Behavioral anomaly detected by automated analysis+15
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Danger medium hits: 3Medium-risk: admin panels, config files+30
Burst: 5 req / 2sAbnormally fast request rate — automated scanning+35
Danger medium hits: 24Medium-risk: admin panels, config files+60
Burst: 6 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 10 req / 10sAbnormally fast request rate — automated scanning+35
Σ = 315
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-02-21 02:50:04
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), Probe pattern 302->404 same path (+20), Foreign referer seen (+10)
2026-05-01 23:00:05
Last malicious request observed
Total score reached: 155/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.216.48 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.216.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.216.48 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

🌊 Traffic Flood Defense

IP 216.73.216.48 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 216.73.216.48: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.

07

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

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

10

Threat Analysis

216.73.216.48 has been assigned a threat score of 155/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:

Path EnumerationRequest FloodingUser-Agent Anomaly

📊 Threat Analysis

216.73.216.48 is registered in Columbus, United States, operating on the network of Amazon.com. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. Over a period of 69 days, this IP generated 6 malicious requests, averaging approximately 0.1 requests per 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 combination of 3 distinct attack vectors indicates a sophisticated, multi-pronged threat actor deploying automated tools that probe multiple attack surfaces simultaneously. United States currently accounts for 180 blocked IPs in our database, making it a significant source of malicious traffic. With a threat score of 155/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.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

💡 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.

💡 Digital Forensics Fundamentals

Digital forensics preserves and analyzes electronic evidence following attacks. Proper chain of custody, forensic imaging, timeline reconstruction, and artifact analysis are essential for understanding attack scope, attribution, and preventing recurrence.

🔍 Check Any IP Address

Share this report: