IP Threat Report
216.73.217.123
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| Directory Scan | Behavioral anomaly detected by automated analysis | +0 |
Observed Activity
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Timeline
Recommendations
Actions taken & recommended
- IP 216.73.217.123 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
- Ensure sensitive files (.env, .git, backups) are not accessible from the web
⚙️ Defensive Recommendations
Block 216.73.217.123 at the network perimeter. Implement defense-in-depth combining IP blocking with application-layer protections.
Neighbors in 216.73.217.0/24
Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.
Blacklist Status (DNSBL)
This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.
Checked: Spamhaus, SpamCop, Barracuda, SORBS, CBL, UCEProtect. Results may change over time.
Threat Analysis
216.73.217.123 has been assigned a threat score of 65/100 (High). At this threat level, the IP is considered high risk. Firewall rules should be updated to deny traffic from this source.
📊 Threat Analysis
Network traffic from 216.73.217.123, located in Columbus, United States, operating on the network of Amazon.com, has been classified as malicious by our automated threat scoring engine. Our sensors captured 474 malicious requests from this address across a 8-day span, reflecting a sustained attack cadence of ~59.3 requests per day. With 118 flagged addresses, United States represents a significant presence in our threat database. The score of 65/100 warrants active monitoring and rate-limiting. Full blocking is advisable for sensitive systems.
Related Threats
🇺🇸 Top threats from United States
104.28.246.115 (350)104.28.214.122 (350)103.168.66.237 (340)34.187.158.4 (340)34.186.187.208 (340)View all →Security Intelligence
💡 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.
💡 Network Flow Analysis
Analyzing network flows (NetFlow, sFlow, IPFIX) provides visibility into traffic patterns without inspecting packet contents. Flow data reveals scanning activity, data exfiltration, lateral movement, and command-and-control channels at scale.