ABUSE.MOM
THREAT REPORT

IP Threat Report
87.199.207.61

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-31 21:16:02
First seen: 2026-07-01 02:59:42
Last seen: 2026-07-31 20:58:41
165

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHRATIO_404REDIRECT_PROBEREFERERUA_CHANGED
01

Geolocation & Classification

IP Address
87.199.207.61
Type
Residential
Country
🇳🇱 Netherlands
City
Amsterdam
ISP
Servers Tech Fzco
Organization
Servers Tech Fzco
Autonomous System
AS216071 SERVERS TECH FZCO
Hit Count
1956
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Burst 6/2sAbnormally fast request rate — automated scanning+35
Danger medium hits: 10Medium-risk: admin panels, config files+60
Danger medium hits: 15Medium-risk: admin panels, config files+60
Danger medium hits: 20Medium-risk: admin panels, config files+60
Danger medium hits: 25Medium-risk: admin panels, config files+60
Danger medium hits: 30Medium-risk: admin panels, config files+60
Danger medium hits: 35Medium-risk: admin panels, config files+60
Danger medium hits: 40Medium-risk: admin panels, config files+60
Danger medium hits: 45Medium-risk: admin panels, config files+60
Danger medium hits: 5Medium-risk: admin panels, config files+50
Danger medium hits: 50Medium-risk: admin panels, config files+60
Danger medium hits: 55Medium-risk: admin panels, config files+60
Danger medium hits: 60Medium-risk: admin panels, config files+60
Foreign refererReferer from unrelated external domain+10
Probe 302→404Behavioral anomaly detected by automated analysis+20
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 815
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-07-01 02:59:42
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), Burst 6/2s (+35), Danger medium hits: 10 (+60)
2026-07-31 20:58:41
Last malicious request observed
Total score reached: 165/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Servers Tech Fzco
AS216071 · 🇳🇱 Netherlands
06

Recommendations

Actions taken & recommended

  • IP 87.199.207.61 is blocked at application level (HTTP 403)
  • Consider blocking at firewall level (iptables/CSF) to reduce server load
  • 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 87.199.207.61: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

🌊 Traffic Flood Defense

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

09

Blacklist Status (DNSBL)

This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.

✓ Clean
zen.spamhaus.org
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
bl.spamcop.net
✓ Clean
bl.blocklist.de
✓ Clean
cbl.abuseat.org
✓ Clean
dnsbl.dronebl.org
✓ Clean
psbl.surriel.com

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

10

Threat Analysis

87.199.207.61 has been assigned a threat score of 165/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

87.199.207.61 is registered in Amsterdam, Netherlands, operating on the network of Servers Tech Fzco. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. The address has been active for 30 days in our monitoring system, producing 1,956 flagged requests at a rate of ~65.2/day. This is a residential IP address, suggesting a compromised home device such as a router, smart appliance, or infected workstation participating in a botnet. The combination of 3 distinct attack vectors indicates a sophisticated, multi-pronged threat actor deploying automated tools that probe multiple attack surfaces simultaneously. With 105 flagged addresses, Netherlands represents a significant presence in our threat database. With a threat score of 165/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.

This IP is classified as residential, suggesting it may belong to a compromised home device, IoT botnet member, or an infected personal computer. Residential IPs involved in attacks often indicate malware infection without the owner's knowledge.

11

Related Threats

🇳🇱 Top threats from Netherlands

91.92.43.144 (358)91.92.43.186 (358)91.92.43.190 (358)91.92.43.157 (358)91.92.43.153 (358)View all →

🏢 Same network: AS216071

87.199.199.112 (100)89.124.110.221 (100)144.124.232.239 (100)144.124.232.204 (95)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.

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

🔍 Check Any IP Address

Share this report: