ABUSE.MOM
THREAT REPORT

IP Threat Report
216.73.216.80

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-22 04:09:20
First seen: 2026-04-15 12:00:06
Last seen: 2026-04-16 23:00:06
65

⛔ Verdict: BLOCK

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

RATIO_404BURSTREFERERDANGER_PATHREDIRECT_PROBE
01

Geolocation & Classification

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

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Burst: 5 req / 2sAbnormally fast request rate — automated scanning+35
Foreign referer seenReferer from unrelated external domain+10
Danger medium hits: 2Medium-risk: admin panels, config files+20
Probe pattern 302->404 same pathBehavioral anomaly detected by automated analysis+20
Σ = 100
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-04-15 12:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), Burst: 5 req / 2s (+35), Foreign referer seen (+10)
2026-04-16 23:00:06
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.216.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 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

🔎 Path Enumeration Protection

Block scanning from 216.73.216.80: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

🌊 Traffic Flood Defense

IP 216.73.216.80 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.

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.

⛔ LISTED
zen.spamhaus.org
✓ Clean
ix.dnsbl.manitu.net
✓ Clean
bl.spamcop.net
✓ Clean
dnsbl-1.uceprotect.net
✓ Clean
dnsbl.sorbs.net
✓ 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.216.80 has been assigned a threat score of 65/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 Flooding

📊 Threat Analysis

Our monitoring infrastructure has identified 216.73.216.80, geolocated to Columbus, United States, operating on the network of Amazon.com, as a source of suspicious network activity. Our sensors captured 2 malicious requests from this address across a 1-day span, reflecting a sustained attack cadence of ~2 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. Two attack patterns were identified (Path Enumeration and Request Flooding), suggesting a semi-automated campaign that targets multiple vulnerabilities. United States currently accounts for 180 blocked IPs in our database, making it a significant source of malicious traffic. At 65/100, this IP presents a meaningful threat. Implement rate limiting with escalation to blocking.

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.

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

🔍 Check Any IP Address

Share this report: