IP abuse report50.72.210.174

Suspicious Residential IPv4 Canada AS6327

50.72.210.174 is an IPv4 address located in Thunder Bay, Canada. It belongs to a network operated by Shaw Communications (AS6327). The address is listed by 1 of the threat-intelligence sources we track and carries a confidence score of 50/100. No community reports have been filed for it yet.

Last updated Listing sources 1 Community Reports 0 How the score works
Provider notified This IP was reported to its network operator Rogers Communications Canada Inc. · 2026-09-23 · IPDB-AR-000104 Awaiting reply Show detailsHide
  1. DetectedScore 90/100
  2. Notice sent2026-09-23 01:08
  3. Deliveredsjrb.ca
  4. Operator response Waiting · 1 month ago

The IP-DB Abuse Desk sent an abuse notice with supporting evidence to Rogers Communications Canada Inc.'s registered abuse contact on 2026-09-23 01:08: internet.abuse@sjrb.ca

This notice covers 100 address(es) on the same network. View public record · IPDB-AR-000104 →
Listing sources1
Community Reports0
Distinct Reporters0
Last seen 35 minutes ago

IP Information

ISP / Organization
Shaw Communications
ASN
AS6327 SHAW
ASN Domain
shaw.ca
IP Range
50.64.0.0/13, 50.72.0.0/16
Regional Registry
ARIN
Connection Type
Residential
Country
Canada (CA)
Region / State
Ontario
City
Thunder Bay
Time Zone
Unknown
Abuse contact
internet.abuse@sjrb.ca The abuse mailbox this network lists with its regional registry. Report traffic from this IP here, with logs and timestamps.

City is an estimate. The country is reliable; the city varies by provider.

Approximate location

City level
Thunder Bay Ontario, Canada
Coordinates
48.38, -89.25
Network
AS6327 Shaw Communications
Open on the threat map

The point is the city centre given by IP geolocation databases, not a street address. The circle shows the area of uncertainty.

Network Neighbourhood

50.72.210.0/24

No other address in 50.72.210.0/24 is listed.

An address is not guiltier for having a few listed neighbours, which is why this stays out of the confidence score entirely while the block is mostly clean. It contributes at most 20 points, and only once a substantial share of the block is listed — that ceiling is deliberate: neighbours alone can raise an address to "low" and no further.

Threat Evidence

Last 30 days: how many feeds listed this address each day, and the community reports filed.

Blocklist feeds

Blacklist Matches

1

In our pool since: 2026-08-28 11:17 (2 months ago) · Last confirmed: 2026-11-20 05:49

Attack Source 1
SourceScopeFirst seenConfirmed
Data-Shield IPv4 Blocklist Single address 2026-11-07 19:33 2026-11-20 06:195 minutes ago

“Confirmed” is the moment the address was still on that source at its most recent fetch — the feeds are replaced wholesale on every refresh. Per-source “first seen” only began being recorded on 30 August 2026, so for listings older than that this column shows the start of record-keeping. The address-level history is the “in our pool since” value above.

IP-DB Sensor · free honeypot

Catch addresses like this on your own server

Sensor opens realistic decoy services — FortiGate, GlobalProtect, Exchange, NetScaler and more — on your server's unused ports. Every address that touches them is logged with evidence, and your firewall, fail2ban and Shield pull the same list to block it.

  • Realistic decoys for VPN gateways, mail, web panels and databases
  • Names exploit attempts by their CVE signature
  • One-command install; runs unprivileged and never touches your real services

While a Sensor reports, your daily API quota rises to 30,000 lookups.

root@web-01 — ipdb-sensor DEMO
● ipdb-sensor.serviceactive (running)
4hits
4decoys
1blocked
  1. 14:02:07 ssh:22 50.72.210.174 login attempt root / ••••••
  2. 14:02:10 globalprotect:443 50.72.210.174 exploit attempt CVE-2024-3400
  3. 14:02:13 owa:4443 50.72.210.174 password spray Exchange OWA
  4. 14:02:16 netscaler:8443 50.72.210.174 Citrix Bleed scan CVE-2023-4966
  5. 14:02:20 ✓ evidence logged → added to your blocklist
Sample output — if this address probed your server

Community Reports 0

Report This IP

No community reports yet for this IP.

Report This IP

Listing History

11
Added to the pool
14 days ago
2026-11-05 10:22
Removed from the pool
14 days ago · score at the time: 50/100 · carried by 1 sources
2026-11-05 08:52
Added to the pool
15 days ago
2026-11-05 04:22
Removed from the pool
15 days ago · score at the time: 50/100 · carried by 1 sources
2026-11-04 08:52
Added to the pool
28 days ago
2026-10-23 03:22
Removed from the pool
29 days ago · score at the time: 50/100 · carried by 1 sources
2026-10-21 09:22
Added to the pool
1 month ago
2026-10-17 15:22
Removed from the pool
1 month ago · score at the time: 50/100 · carried by 1 sources
2026-10-06 09:22
Added to the pool
2 months ago
2026-09-20 05:22
Removed from the pool
2 months ago · score at the time: 50/100 · carried by 1 sources
2026-09-19 09:22
Added to the pool
2 months ago · score at the time: 86/100 · carried by 2 sources
2026-08-28 11:17

The pool is a live picture: an address listed today leaves it when the sources drop it. This record outlives that removal — “listed on 12 August, delisted on 3 September” is truer than either a permanent accusation or a blank page. Events are kept for 400 days.

Frequently asked questions about 50.72.210.174

Is 50.72.210.174 safe?

50.72.210.174 scores 50/100 from several independent signals (1 source). Rate-limit or challenge its traffic and review your logs for it.

Who owns 50.72.210.174?

50.72.210.174 is announced by AS6327 and operated by Shaw Communications. It sits in the 50.64.0.0/13, 50.72.0.0/16 block registered with ARIN.

Where is 50.72.210.174 located?

Geolocation places 50.72.210.174 in Thunder Bay, Canada. IP geolocation is approximate: it shows where the network is registered or routed, not a device's street address.

Is 50.72.210.174 on a blacklist?

Yes. 50.72.210.174 is currently listed by 1 threat sources: Data-Shield IPv4 Blocklist.

How do I report abuse from 50.72.210.174?

Send your log lines to the network's abuse contact, internet.abuse@sjrb.ca, and file a report on IP-DB so others can see it too.

Run this check via the API

The same score and evidence are available as JSON, free with an API key.

API documentation →
curl -H "Key: YOUR_API_KEY" https://ip-db.com/api/v1/check/50.72.210.174

Guides for this IP