IP abuse report216.126.86.69

Critical Residential IPv4 Canada AS7311

216.126.86.69 is an IPv4 address located in Toronto (Etobicoke), Canada. It belongs to a network operated by Frontier Networks Inc (AS7311). The address is listed by 6 of the threat-intelligence sources we track and carries a confidence score of 91/100. No community reports have been filed for it yet.

Last updated Listing sources 6 Community Reports 0 How the score works
Listing sources6
Community Reports0
Distinct Reporters0
Last seen 14 minutes ago

IP Information

ISP / Organization
Frontier Networks Inc
ASN
AS7311 FRONTIER
IP Range
216.126.78.0/23, 216.126.80.0/21
Regional Registry
ARIN
Connection Type
Residential
Country
Canada (CA)
Region / State
Ontario
City
Toronto (Etobicoke)
Time Zone
Unknown
Abuse contact
abuse@frontiernetworks.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
Toronto (Etobicoke) Ontario, Canada
Coordinates
43.61, -79.52
Network
AS7311 Frontier Networks Inc
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

216.126.86.0/24

9 of the 256 addresses in 216.126.86.0/24 are listed by our sources (3.5%).

Only a small part of the block is listed, which is more consistent with an isolated incident than with the network itself.

Examples from the same block
216.126.86.39216.126.86.46216.126.86.60216.126.86.62216.126.86.119216.126.86.140216.126.86.227216.126.86.245

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

6

In our pool since: 2026-11-18 20:47 (yesterday) · Last confirmed: 2026-11-20 03:50

Aggregated List (Medium Confidence) 1
SourceScopeFirst seenConfirmed
FireHOL Level 2 Aggregator Single address 2026-11-19 21:57 2026-11-20 03:4815 minutes ago
Attack Source 2
SourceScopeFirst seenConfirmed
Blocklist.de (all) Single address 2026-11-18 20:47 2026-11-20 03:4717 minutes ago
Data-Shield IPv4 Blocklist Single address 2026-11-18 20:48 2026-11-20 03:4915 minutes ago
Mail Abuse 2
SourceScopeFirst seenConfirmed
Blocklist.de Mail Single address 2026-11-18 20:47 2026-11-20 03:4717 minutes ago
Blocklist.de IMAP Single address 2026-11-18 20:48 2026-11-20 03:5014 minutes ago
Malicious Activity 1
SourceScopeFirst seenConfirmed
ThreatView High Confidence Single address 2026-11-19 02:47 2026-11-20 03:4816 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 216.126.86.69 login attempt root / ••••••
  2. 14:02:10 globalprotect:443 216.126.86.69 exploit attempt CVE-2024-3400
  3. 14:02:13 owa:4443 216.126.86.69 password spray Exchange OWA
  4. 14:02:16 netscaler:8443 216.126.86.69 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

1
Added to the pool
yesterday
2026-11-18 20:52

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 216.126.86.69

Is 216.126.86.69 safe?

No. 216.126.86.69 scores 91/100 with strong, recent evidence of abuse (6 sources). Blocking it at your firewall is advisable.

Who owns 216.126.86.69?

216.126.86.69 is announced by AS7311 and operated by Frontier Networks Inc. It sits in the 216.126.78.0/23, 216.126.80.0/21 block registered with ARIN.

Where is 216.126.86.69 located?

Geolocation places 216.126.86.69 in Toronto (Etobicoke), Canada. IP geolocation is approximate: it shows where the network is registered or routed, not a device's street address.

Is 216.126.86.69 on a blacklist?

Yes. 216.126.86.69 is currently listed by 6 threat sources: Blocklist.de (all), Blocklist.de Mail, ThreatView High Confidence, FireHOL Level 2, Data-Shield IPv4 Blocklist, Blocklist.de IMAP.

How do I report abuse from 216.126.86.69?

Send your log lines to the network's abuse contact, abuse@frontiernetworks.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/216.126.86.69

Guides for this IP