170.64.133.217
170.64.133.217 is an IPv4 address operated by DIGITALOCEAN-ASN - DigitalOcean, LLC, US (AS14061), with approximate network location San Jose, United States. It belongs to datacenter or hosting infrastructure. As of November 13, 2026, IPDebrief rates it Low Risk (0/100); no anonymizing service was detected.
🏢 Ownership & Registration
| Registered holder | DigitalOcean, LLC |
| ASN | AS14061 |
| Network Name | DIGITALOCEAN-170-64-128-0 |
| CIDR Block | 170.64.128.0/17 |
| RIR | ARIN |
| Network registration country | United States |
| Routing operator | DIGITALOCEAN-ASN - DigitalOcean, LLC, US |
| Abuse Contact | Available via RDAP |
🌐 DNS Intelligence
| PTR Record | No PTR |
| Forward Confirmed | No — PTR hostname does not resolve back to this IP (weak signal) |
DNS Posture
Results describe the queried names. SPF, DMARC and CAA are domain policies, not requirements for every IP. DNSSEC here describes reverse DNS; inconclusive validation does not mean unsigned.
Not assessed: 0 conclusive IP DNS checks.
| caa | Not applicable |
| spf | Unknown / lookup inconclusive |
| dmarc | Unknown / lookup inconclusive |
| dnssec | Unknown / lookup inconclusive 217.133.64.170.in-addr.arpa |
| fcrDns | Unknown / lookup inconclusive |
☁️ Network Classification
| Infrastructure | Infrastructure / Datacenter |
| Service Purpose | Single-Service Host |
| Network Tier | Hosting — Infrastructure provider without advanced routing |
🔌 Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| 22 | ssh | tcp | Banner detected |
| Closed Ports | 25, 80, 443, 3389, 8080, 8443 (1 open / 7 scanned) | ||
| Server | — |
| HTTP Title | — |
🔐 TLS Certificate
| SANs | None |
| Valid From | — |
| Valid Until | — |
🛡️ Public Network Snapshot
| Origin ASN | AS14061 |
| Network Prefix | 170.64.128.0/18 |
| Route mapping | Found |
| Certificates in transparency logs | 0 certificates |
| HSTS | Enabled |
| CSP | Not detected |
| HTTP/2 | Enabled |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 21% | 2 | 5 |
| routing | 3% | 1 | 1 |
| services | 14% | 2 | 3 |
| ownership | 7% | 2 | 3 |
| reputation | 8% | 1 | 3 |
| geolocation | 14% | 2 | 3 |
| Overall | 11% | 10 | 18 |
| Data Coherence | Mostly Consistent (80%) — 1 contradiction(s) |
| Attribution | Very Low (20%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-07-20 00:17:04 UTC |
| Last Seen | 2026-11-10 08:26:41 UTC |
| Profile Built | 2026-11-13 05:52:35 UTC |
| Data Freshness | Live |
| Signal Types | 23 |
| Total Observations | 36 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 170.64.133.217
Who owns the IP address 170.64.133.217?
170.64.133.217 is registered to DigitalOcean, LLC. The address falls within the 170.64.128.0/17 network block. Registration is held at ARIN.
Where is 170.64.133.217 located?
Geolocation data places 170.64.133.217 in San Jose, US-CA, United States. The local time zone is America/Los_Angeles. IP geolocation is approximate, not a precise physical address. Registration country and certificate organization addresses do not establish service location.
Is 170.64.133.217 malicious or safe?
170.64.133.217 currently carries a low risk assessment, meaning no significant threat indicators have been observed. This assessment is generated from continuously collected signals and can change over time.
What ports are open on 170.64.133.217?
Responsive ports observed on 170.64.133.217 include 22. Port visibility reflects the most recent scan and may change as the host's configuration or firewall rules change.
Is 170.64.133.217 a VPN, proxy, or data center address?
170.64.133.217 is classified as cloud infrastructure and hosting infrastructure based on network ownership and behavioural analysis.