Dashboard›🇨🇭 Switzerland›20.203.205.96
ABUSE.MOM
THREAT REPORT

IP Threat Report
20.203.205.96

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-09-08 04:23:27
First seen: 2026-07-29 14:38:16
Last seen: 2026-08-09 04:16:54
280

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHRATIO_404REDIRECT_PROBEUA_SUS
01

Geolocation & Classification

IP Address
20.203.205.96
Type
Hosting
Country
🇨🇭 Switzerland
City
Zurich
ISP
Microsoft Corporation
Organization
Microsoft Azure Cloud (switzerlandnorth)
Autonomous System
AS8075 Microsoft Corporation
Hit Count
8831
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Burst 100/10sAbnormally fast request rate — automated scanning+35
Burst 103/10sAbnormally fast request rate — automated scanning+35
Burst 104/10sAbnormally fast request rate — automated scanning+35
Burst 105/10sAbnormally fast request rate — automated scanning+35
Burst 107/10sAbnormally fast request rate — automated scanning+35
Burst 108/10sAbnormally fast request rate — automated scanning+35
Burst 109/10sAbnormally fast request rate — automated scanning+35
Burst 110/10sAbnormally fast request rate — automated scanning+35
Burst 111/10sAbnormally fast request rate — automated scanning+35
Burst 114/10sAbnormally fast request rate — automated scanning+35
Burst 115/10sAbnormally fast request rate — automated scanning+35
Burst 117/10sAbnormally fast request rate — automated scanning+35
Burst 118/10sAbnormally fast request rate — automated scanning+35
Burst 120/10sAbnormally fast request rate — automated scanning+35
Burst 125/10sAbnormally fast request rate — automated scanning+35
Burst 126/10sAbnormally fast request rate — automated scanning+35
Burst 129/10sAbnormally fast request rate — automated scanning+35
Burst 130/10sAbnormally fast request rate — automated scanning+35
Burst 134/10sAbnormally fast request rate — automated scanning+35
Burst 136/10sAbnormally fast request rate — automated scanning+35
Burst 140/10sAbnormally fast request rate — automated scanning+35
Burst 149/10sAbnormally fast request rate — automated scanning+35
Burst 150/10sAbnormally fast request rate — automated scanning+35
Burst 153/10sAbnormally fast request rate — automated scanning+35
Burst 155/10sAbnormally fast request rate — automated scanning+35
Burst 158/10sAbnormally fast request rate — automated scanning+35
Burst 160/10sAbnormally fast request rate — automated scanning+35
Burst 163/10sAbnormally fast request rate — automated scanning+35
Burst 164/10sAbnormally fast request rate — automated scanning+35
Burst 167/10sAbnormally fast request rate — automated scanning+35
Burst 169/10sAbnormally fast request rate — automated scanning+35
Burst 174/10sAbnormally fast request rate — automated scanning+35
Burst 176/10sAbnormally fast request rate — automated scanning+35
Burst 179/10sAbnormally fast request rate — automated scanning+35
Burst 182/10sAbnormally fast request rate — automated scanning+35
Burst 184/10sAbnormally fast request rate — automated scanning+35
Burst 187/10sAbnormally fast request rate — automated scanning+35
Burst 196/10sAbnormally fast request rate — automated scanning+35
Burst 199/10sAbnormally fast request rate — automated scanning+35
Burst 200/10sAbnormally fast request rate — automated scanning+35
Burst 27/2sAbnormally fast request rate — automated scanning+35
Burst 29/2sAbnormally fast request rate — automated scanning+35
Burst 30/2sAbnormally fast request rate — automated scanning+35
Burst 33/2sAbnormally fast request rate — automated scanning+35
Burst 34/2sAbnormally fast request rate — automated scanning+35
Burst 35/2sAbnormally fast request rate — automated scanning+35
Burst 36/10sAbnormally fast request rate — automated scanning+35
Burst 36/2sAbnormally fast request rate — automated scanning+35
Burst 37/2sAbnormally fast request rate — automated scanning+35
Burst 38/2sAbnormally fast request rate — automated scanning+35
Burst 39/2sAbnormally fast request rate — automated scanning+35
Burst 40/2sAbnormally fast request rate — automated scanning+35
Burst 41/2sAbnormally fast request rate — automated scanning+35
Burst 42/2sAbnormally fast request rate — automated scanning+35
Burst 44/2sAbnormally fast request rate — automated scanning+35
Burst 45/2sAbnormally fast request rate — automated scanning+35
Burst 46/2sAbnormally fast request rate — automated scanning+35
Burst 47/2sAbnormally fast request rate — automated scanning+35
Burst 48/2sAbnormally fast request rate — automated scanning+35
Burst 49/2sAbnormally fast request rate — automated scanning+35
Burst 50/2sAbnormally fast request rate — automated scanning+35
Burst 51/2sAbnormally fast request rate — automated scanning+35
Burst 52/10sAbnormally fast request rate — automated scanning+35
Burst 52/2sAbnormally fast request rate — automated scanning+35
Burst 53/2sAbnormally fast request rate — automated scanning+35
Burst 54/2sAbnormally fast request rate — automated scanning+35
Burst 55/2sAbnormally fast request rate — automated scanning+35
Burst 56/2sAbnormally fast request rate — automated scanning+35
Burst 57/2sAbnormally fast request rate — automated scanning+35
Burst 59/2sAbnormally fast request rate — automated scanning+35
Burst 60/2sAbnormally fast request rate — automated scanning+35
Burst 61/10sAbnormally fast request rate — automated scanning+35
Burst 62/10sAbnormally fast request rate — automated scanning+35
Burst 63/2sAbnormally fast request rate — automated scanning+35
Burst 65/2sAbnormally fast request rate — automated scanning+35
Burst 67/2sAbnormally fast request rate — automated scanning+35
Burst 71/10sAbnormally fast request rate — automated scanning+35
Burst 73/10sAbnormally fast request rate — automated scanning+35
Burst 74/10sAbnormally fast request rate — automated scanning+35
Burst 76/10sAbnormally fast request rate — automated scanning+35
Burst 77/10sAbnormally fast request rate — automated scanning+35
Burst 85/10sAbnormally fast request rate — automated scanning+35
Burst 89/10sAbnormally fast request rate — automated scanning+35
Burst 91/10sAbnormally fast request rate — automated scanning+35
Burst 93/10sAbnormally fast request rate — automated scanning+35
Burst 96/10sAbnormally fast request rate — automated scanning+35
Burst 97/10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 1Medium-risk: admin panels, config files+10
Danger medium hits: 100Medium-risk: admin panels, config files+60
Danger medium hits: 104Medium-risk: admin panels, config files+60
Danger medium hits: 106Medium-risk: admin panels, config files+60
Danger medium hits: 111Medium-risk: admin panels, config files+60
Danger medium hits: 122Medium-risk: admin panels, config files+60
Danger medium hits: 128Medium-risk: admin panels, config files+60
Danger medium hits: 139Medium-risk: admin panels, config files+60
Danger medium hits: 144Medium-risk: admin panels, config files+60
Danger medium hits: 148Medium-risk: admin panels, config files+60
Danger medium hits: 151Medium-risk: admin panels, config files+60
Danger medium hits: 168Medium-risk: admin panels, config files+60
Danger medium hits: 178Medium-risk: admin panels, config files+60
Danger medium hits: 185Medium-risk: admin panels, config files+60
Danger medium hits: 187Medium-risk: admin panels, config files+60
Danger medium hits: 195Medium-risk: admin panels, config files+60
Danger medium hits: 196Medium-risk: admin panels, config files+60
Danger medium hits: 220Medium-risk: admin panels, config files+60
Danger medium hits: 222Medium-risk: admin panels, config files+60
Danger medium hits: 247Medium-risk: admin panels, config files+60
Danger medium hits: 256Medium-risk: admin panels, config files+60
Danger medium hits: 276Medium-risk: admin panels, config files+60
Danger medium hits: 278Medium-risk: admin panels, config files+60
Danger medium hits: 317Medium-risk: admin panels, config files+60
Danger medium hits: 322Medium-risk: admin panels, config files+60
Danger medium hits: 352Medium-risk: admin panels, config files+60
Danger medium hits: 360Medium-risk: admin panels, config files+60
Danger medium hits: 376Medium-risk: admin panels, config files+60
Danger medium hits: 382Medium-risk: admin panels, config files+60
Danger medium hits: 390Medium-risk: admin panels, config files+60
Danger medium hits: 415Medium-risk: admin panels, config files+60
Danger medium hits: 417Medium-risk: admin panels, config files+60
Danger medium hits: 42Medium-risk: admin panels, config files+60
Danger medium hits: 428Medium-risk: admin panels, config files+60
Danger medium hits: 52Medium-risk: admin panels, config files+60
Danger medium hits: 582Medium-risk: admin panels, config files+60
Danger medium hits: 72Medium-risk: admin panels, config files+60
Danger medium hits: 74Medium-risk: admin panels, config files+60
Danger medium hits: 84Medium-risk: admin panels, config files+60
Danger medium hits: 96Medium-risk: admin panels, config files+60
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
Danger strong hits: 10High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 12High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 14High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 16High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 17High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 18High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Danger strong hits: 25High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 28High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 29High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 3High-risk paths: shells, RCE vectors, exploits+75
Danger strong hits: 30High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 32High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 37High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 4High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 40High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 43High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 50High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 56High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 6High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 7High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 8High-risk paths: shells, RCE vectors, exploits+100
Probe 302→404Behavioral anomaly detected by automated analysis+20
UA suspiciousBehavioral anomaly detected by automated analysis+15
Σ = 7620
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-29 14:38:16
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), 404 ratio >= 60% (+25), Burst 100/10s (+35)
2026-08-09 04:16:54
Last malicious request observed
Total score reached: 280/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Microsoft Corporation
AS8075 · 🇨🇭 Switzerland
06

Recommendations

Actions taken & recommended

  • IP 20.203.205.96 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 20.203.205.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 20.203.205.96 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

🌊 Traffic Flood Defense

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

07

Neighbors in 20.203.205.0/24

Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.

20.203.205.107
Score: 280 · Hits: 854
09

Blacklist Status (DNSBL)

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

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

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

10

Threat Analysis

20.203.205.96 has been assigned a threat score of 280/100 (Critical). This is a critical-level threat. Systems administrators should treat this IP as hostile and block all inbound connections without exception.

The following attack categories were identified:

Path EnumerationRequest FloodingUser-Agent Anomaly

📊 Threat Analysis

The address 20.203.205.96 originates from Zurich, Switzerland, operating on the network of Microsoft Corporation. It was identified through automated analysis of incoming network traffic across monitored endpoints. Over a period of 10 days, this IP generated 8,831 malicious requests, averaging approximately 883.1 requests per day. This address belongs to a datacenter or cloud hosting provider. Hosting IPs are frequently leveraged by threat actors who rent cheap VPS instances specifically for conducting attacks. The combination of 3 distinct attack vectors indicates a sophisticated, multi-pronged threat actor deploying automated tools that probe multiple attack surfaces simultaneously. Our records show 112 malicious IPs originating from Switzerland, positioning it as a significant contributor to global threat activity. A score of 280/100 places this address in the top tier of severity. Block and investigate any historical connections.

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 Switzerland

34.65.117.95 (298)34.65.167.1 (288)20.203.149.15 (280)20.250.28.140 (280)20.250.9.235 (280)View all →

🏢 Same network: AS8075

68.155.155.199 (320)20.127.136.245 (318)20.151.200.44 (315)51.103.130.248 (280)20.203.205.107 (280)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.

💡 DNS Sinkholing for Malware Defense

DNS sinkholing redirects queries for known malicious domains to controlled IP addresses. This technique blocks malware communication, prevents data exfiltration, and identifies compromised internal hosts attempting to contact command-and-control servers.

🔍 Check Any IP Address

Share this report:
AboutDisclaimerTermsAbuse Reports Tracker
Report generated 08.09.2026 04:23
Behave or get exposed