170.75.161.105
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
- Active-threat / abuse risk −12
- Not on any threat blocklist +5
- Has a reverse-DNS (PTR) record +5
- Established allocation (12y) +3
- Trust score 66 / 100
Experimental · trust-vectors model v1.2.0 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- 105.161.75.170
- Forward-confirmed (FCrDNS)
- Not checked
- PTR TTL
- 1800 s
- Reverse DNS last checked
- 2026-09-22 03:26 UTC
Reverse & forward DNS collected by the WorldIP scanner fleet — FCrDNS confirms the PTR hostname resolves back to this IP.
Network Allocation for 170.75.161.105
- CIDR range
- 170.75.160.0/20
- IP range (int)
- 2,857,082,880 — 2,857,086,975
- Prefix length
- /20
- Organization
- Cogent Communications, LLC
- ASN
- AS174
- ASN name
- Cogent Communications, LLC
- Location
- Canada
- Coordinates
- 43.631900, -79.371600
- Accuracy radius
- 1000 km
- Regional Internet Registry
- ARIN
- Allocated
- 2014-06-11
- Data source(s)
- maxmind_city, maxmind_country, maxmind_asn, ipinfo_lite
- Last updated
- 2026-07-10 00:20:23
BGP Routing
Live BGP anomalies →Origin AS announcing the most-specific prefix that covers this IP, observed across our RIPE RIS collectors.
Frequently Asked Questions
Who owns 170.75.161.105?
170.75.161.105 is allocated to Cogent Communications, LLC (AS174), registered in Canada.
Where is 170.75.161.105 located?
The geolocation for 170.75.161.105 maps to 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 170.75.161.105 on?
170.75.161.105 belongs to the 170.75.160.0/20 network block announced by AS174. This range contains 4,096 addresses.
Does 170.75.161.105 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.
