ABUSE.MOM
THREAT REPORT

IP Threat Report
20.63.98.227

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-22 05:43:01
First seen: 2026-03-23 12:00:07
Last seen: 2026-03-23 18:00:06
255

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404BURST
01

Geolocation & Classification

IP Address
20.63.98.227
Type
Hosting
Country
🇨🇦 Canada
City
Toronto
ISP
Microsoft Corporation
Organization
Microsoft Azure Cloud (canadacentral)
Autonomous System
AS8075 Microsoft Corporation
Hit Count
107
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger strong hits: 19High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 39Medium-risk: admin panels, config files+60
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Burst: 23 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 52 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 24 req / 2sAbnormally fast request rate — automated scanning+35
Danger strong hits: 38High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 78Medium-risk: admin panels, config files+60
Danger strong hits: 18High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 47Medium-risk: admin panels, config files+60
Burst: 57 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 36High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 94Medium-risk: admin panels, config files+60
Danger medium hits: 52Medium-risk: admin panels, config files+60
Burst: 66 req / 10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 104Medium-risk: admin panels, config files+60
Σ = 960
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-03-23 12:00:07
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger strong hits: 19 (+100), Danger medium hits: 39 (+60), 404 ratio >= 60% (+25)
2026-03-23 18:00:06
Last malicious request observed
Total score reached: 255/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Microsoft Corporation
AS8075 · 🇨🇦 Canada
06

Recommendations

Actions taken & recommended

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

🌊 Traffic Flood Defense

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

07

Neighbors in 20.63.98.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
dnsbl.sorbs.net
✓ Clean
ix.dnsbl.manitu.net
✓ Clean
bl.spamcop.net
✓ Clean
b.barracudacentral.org
✓ Clean
truncate.gbudb.net
✓ Clean
psbl.surriel.com
✓ Clean
dnsbl-1.uceprotect.net

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

10

Threat Analysis

20.63.98.227 has been assigned a threat score of 255/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.

The following attack categories were identified:

Path EnumerationRequest Flooding

📊 Threat Analysis

Threat intelligence analysis has linked 20.63.98.227 to malicious activity originating from Toronto, Canada, operating on the network of Microsoft Corporation. The address has been under observation since its initial detection. Over a period of 1 days, this IP generated 107 malicious requests, averaging approximately 107 requests per day. Classified as a hosting IP, this address likely runs on a rented server or cloud instance. Attackers prefer datacenter IPs for their high bandwidth and disposable nature. The dual attack vectors of Path Enumeration combined with Request Flooding indicate a coordinated assault rather than opportunistic scanning. Our records show 103 malicious IPs originating from Canada, positioning it as a significant contributor to global threat activity. At 255/100, this is an extremely high-risk address. All traffic should be considered hostile.

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 Canada

45.91.23.64 (305)147.15.149.40 (300)148.116.72.171 (300)89.251.0.24 (295)89.251.0.128 (295)View all →

🏢 Same network: AS8075

74.241.249.229 (340)4.182.24.88 (285)20.65.61.3 (283)4.205.39.97 (283)20.29.71.103 (283)View all →
12

Security Intelligence

💡 SQL Injection Campaigns

SQL injection remains one of the most common web attack vectors. Attackers inject malicious SQL code through input fields to extract database contents, modify data, or gain administrative access. Automated scanners test for SQLi vulnerabilities at massive scale.

💡 IP Geolocation Accuracy Limitations

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.

🔍 Check Any IP Address

Share this report: