141.117.3.220
Reputation · trust score
A transparent 0–100 signal. Every entity starts at a neutral baseline of 65; threat-intel blocklists, exposure, reverse-DNS, routing and allocation each adjust it up or down. Higher is more trustworthy.
- Baseline (neutral) 65
- Academic allocation +6
- Long-established allocation (36y) +6
- Not on any threat blocklist +5
- Has a reverse-DNS (PTR) record +5
- Trust score 87 / 100
Experimental · trust-vectors model v1.2.1 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- iamlab-medviewer.rnet.torontomu.ca
- Forward-confirmed (FCrDNS)
- Not checked
- PTR TTL
- 10800 s
- Reverse DNS last checked
- 2026-10-09 05:59 UTC
Forward DNS records for iamlab-medviewer.rnet.torontomu.ca
| Type | Value | Priority | TTL |
|---|---|---|---|
| A | 141.117.3.220 | — | 10800s |
Reverse & forward DNS collected by the WorldIP scanner fleet — FCrDNS confirms the PTR hostname resolves back to this IP.
Domains hosted
as of 2026-10-04 UTC1
Registrable domains (like example.com) with at least one name resolving to this IP — counted once a week from issued.live's DNS snapshot.
Domain data provided by issued.live — for full details visit https://issued.live/pricing
Reverse DNS history
How this IP's reverse DNS (PTR) has changed over time, from our scans.
This IP's reverse DNS changes frequently — the timeline below shows the most recent changes.
- iamlab-medviewer.rnet.torontomu.ca — Oct 8, 2026 → present
- iamlab-medviewer.rnet.ryerson.ca — Oct 7, 2026 → Oct 8, 2026
- iamlab-medviewer.rnet.torontomu.ca — Oct 6, 2026 → Oct 7, 2026
- iamlab-medviewer.rnet.ryerson.ca — Oct 6, 2026 → Oct 6, 2026
- iamlab-medviewer.rnet.torontomu.ca — Oct 5, 2026 → Oct 6, 2026
- iamlab-medviewer.rnet.ryerson.ca — Oct 2, 2026 → Oct 5, 2026
- iamlab-medviewer.rnet.torontomu.ca — Oct 2, 2026 → Oct 2, 2026
- iamlab-medviewer.rnet.ryerson.ca — Oct 1, 2026 → Oct 2, 2026
- iamlab-medviewer.rnet.torontomu.ca — Sep 30, 2026 → Oct 1, 2026
- iamlab-medviewer.rnet.ryerson.ca — Sep 27, 2026 → Sep 30, 2026
- iamlab-medviewer.rnet.torontomu.ca — Sep 25, 2026 → Sep 27, 2026
- iamlab-medviewer.rnet.ryerson.ca — Aug 24, 2026 → Sep 25, 2026
- no PTR — Aug 19, 2026 → Aug 24, 2026
- iamlab-medviewer.rnet.torontomu.ca — Jun 15, 2026 → Aug 19, 2026
- iamlab-medviewer.rnet.ryerson.ca — Jun 12, 2026 → Jun 15, 2026
Network Allocation for 141.117.3.220
- CIDR range
- 141.117.0.0/20
- IP range (int)
- 2,373,255,168 — 2,373,259,263
- Prefix length
- /20
- Organization
- Toronto Metropolitan University
- ASN
- AS26996
- ASN name
- Toronto Metropolitan University
- Location
- Toronto, Ontario, Canada
- Coordinates
- 43.657600, -79.379800
- Accuracy radius
- 5 km
- Postal code
- M5B
- Regional Internet Registry
- ARIN
- Allocated
- 1990-06-26
- Data source(s)
- maxmind_city, maxmind_country, maxmind_asn, ipinfo_lite
- Last updated
- 2026-10-09 05:24:49
BGP Routing
Live BGP anomalies →Origin AS announcing the most-specific prefix that covers this IP, observed across our RIPE RIS collectors.
RIR Ownership History
Atom feed ⇲Allocation changes captured from regional internet registry (RIR) delegation files, re-imported every six hours, for ranges that have contained this IP.
| Date | Event | From | To |
|---|---|---|---|
| 2026-05-10 | RIR Transfer | ripe | arin |
See the full history for 141.117.0.0/16.
Frequently Asked Questions
Who owns 141.117.3.220?
141.117.3.220 is allocated to Toronto Metropolitan University (AS26996), registered in Toronto, Canada.
Where is 141.117.3.220 located?
The geolocation for 141.117.3.220 maps to Toronto, Canada based on MaxMind GeoLite2 data. Accuracy depends on the provider and may represent the ISP's regional hub rather than the exact endpoint.
What network is 141.117.3.220 on?
141.117.3.220 belongs to the 141.117.0.0/20 network block announced by AS26996. This range contains 4,096 addresses.
Does 141.117.3.220 have a reverse DNS record?
Reverse DNS (PTR) records are resolved live when you visit this page. If a PTR record exists, it appears in the Reverse DNS field above. PTR records map IP addresses back to hostnames and are commonly used for email authentication and network diagnostics.
Neighbors
Other addresses in the same /24.
