ABUSE.MOM
THREAT REPORT

IP Threat Report
216.208.243.113

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-09-13 02:34:21
First seen: 2026-09-06 20:50:59
Last seen: 2026-09-13 01:13:18
80

⛔ Verdict: BLOCK

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

BURSTREFERER
01

Geolocation & Classification

IP Address
216.208.243.113
Type
Mobile
Country
🇨🇦 Canada
City
Halifax
ISP
Bell Canada
Organization
Bell Mobility Inc.
Autonomous System
AS577 Bell Canada
Hit Count
247
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 30/2sAbnormally fast request rate — automated scanning+35
Burst 32/10sAbnormally fast request rate — automated scanning+35
Foreign refererReferer from unrelated external domain+10
Σ = 80
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-09-06 20:50:59
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 30/2s (+35), Burst 32/10s (+35), Foreign referer (+10)
2026-09-13 01:13:18
Last malicious request observed
Total score reached: 80/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Bell Canada
AS577 · 🇨🇦 Canada
06

Recommendations

Actions taken & recommended

  • IP 216.208.243.113 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

🌊 Traffic Flood Defense

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

09

Blacklist Status (DNSBL)

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

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

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

10

Threat Analysis

216.208.243.113 has been assigned a threat score of 80/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:

Request Flooding

📊 Threat Analysis

216.208.243.113 is registered in Halifax, Canada, operating on the network of Bell Canada. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. During its 6-day observation window, we recorded 247 hostile requests from this IP — roughly 41.2 per day on average. The address belongs to a mobile carrier network. The sustained pattern of malicious requests indicates either a compromised device or deliberate abuse. The IP is engaged in request flooding, sending traffic at rates designed to exhaust server capacity. Our records show 102 malicious IPs originating from Canada, positioning it as a significant contributor to global threat activity. A threat score of 80/100 places this IP in the high-risk category. Blocking at the firewall level is recommended.

11

Related Threats

🇨🇦 Top threats from Canada

20.151.200.44 (315)20.151.179.130 (308)20.151.111.128 (308)45.91.23.64 (305)45.91.23.164 (305)View all →

🏢 Same network: AS577

67.69.76.77 (80)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.

💡 Responsible Disclosure Ethics

Responsible disclosure balances public safety with giving vendors time to patch vulnerabilities. The security community generally supports coordinated disclosure timelines, but disagreements about appropriate timeframes and full disclosure continue to drive policy debates.

🔍 Check Any IP Address

Share this report: