
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Directory Scan | Behavioral anomaly detected by automated analysis | +0 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Add 195.210.113.14 to your firewall blocklist. Review logs for successful connections. Enable comprehensive logging on all public-facing services.
Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.
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.
195.210.113.14 has been assigned a threat score of 75/100 (High). This score indicates high threat severity. The IP has shown clear patterns of malicious behavior that warrant immediate defensive measures.
Threat intelligence analysis has linked 195.210.113.14 to malicious activity originating from Honolulu, United States, operating on the network of GSL Networks Pty LTD. The address has been under observation since its initial detection. During its 10-day observation window, we recorded 203 hostile requests from this IP — roughly 20.3 per day on average. United States currently accounts for 111 blocked IPs in our database, making it a significant source of malicious traffic. A threat score of 75/100 places this IP in the high-risk category. Blocking at the firewall level is recommended.
IP geolocation databases provide approximate locations with varying accuracy. City-level geolocation is typically 50-80% accurate, while country-level exceeds 95%. VPNs, proxies, and mobile networks further reduce reliability, making geolocation a useful but imperfect intelligence signal.
Containerized applications face unique security challenges including vulnerable base images, excessive privileges, shared kernel attacks, and insecure orchestration configurations. Runtime security monitoring and immutable container policies mitigate these risks.