IP Intelligence Briefing: 64.23.173.53/32
Date: 2026-06-11
---
**1. Core Profile**
- Risk Score: 25 (Low Risk)
- Provider: DigitalOcean, LLC (ASN 14061)
- Geolocation: Santa Clara, CA, US (inferred via multi-signal geolocation)
- Network Role: Cloud compute instance (hosted by DigitalOcean)
- Threat Indicators: No malicious activity detected (no abuse confidence score, no DNSBL listings, no known campaigns).
---
**2. Observation History**
- Recent Activity (2026-06-11):
- Geolocation inferred as US (Santa Clara, CA) with 2500km accuracy.
- DNSSEC validation confirmed (valid).
- No threat signals, spam, or attacker associations.
- Long-Term Trends:
- No persistent malicious behavior (threat persistence days = 0).
- Ownership stable (no recent changes).
---
**3. Relationships**
- Network Affiliation:
- Part of the `DIGITALOCEAN-64-23-128-0` network (CIDR: 64.23.128.0/17).
- Linked to other DigitalOcean cloud instances.
- No Known Malicious Associations:
- No correlated IPs, certificates, or campaigns.
---
**4. Neighborhood Analysis**
- Subnet: 64.23.173.53/24
- Abuse Density: 0% (clean subnet).
- Neighbors: No active or threatening sibling IPs in the /24 range.
---
**5. Recommended Actions**
- Monitoring: Continue standard monitoring for anomalous behavior (e.g., unexpected port activity, DNS changes).
- Firewall Rules: No immediate blocking required; this IP is part of a legitimate cloud providerβs infrastructure.
- Contextual Awareness: Note the IPβs association with DigitalOcean; ensure cloud access controls align with organizational policies.
---
Conclusion:
64.23.173.53 is a low-risk IP associated with DigitalOceanβs cloud infrastructure. No malicious activity, abuse, or threat indicators were detected. No action required unless further anomalies are observed.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
π’ Ownership & Registration
| Organization | DigitalOcean, LLC |
| ASN | AS14061 |
| Network Name | DIGITALOCEAN-64-23-128-0 |
| CIDR Block | 64.23.128.0/17 |
| RIR | ARIN |
| Country | United States |
| 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 Hygiene
| Hygiene Score | 20% (Poor) |
| SPF | Not configured |
| DMARC | Not configured |
| FCrDNS | Not verified |
| DNSSEC | Valid |
| CAA | Not configured |
βοΈ Network Classification
| Infrastructure | Infrastructure / Datacenter |
| Service Purpose | Web Server |
| Network Tier | Hosting β Infrastructure provider without advanced routing |
π Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| 80 | http | tcp | β |
| 443 | https | tcp | β |
| 22 | ssh | tcp | |
| Closed Ports | 25, 3389, 8080, 8443 (3 open / 7 scanned) | ||
| Server | nginx/1.24.0 (Ubuntu) |
| HTTP Title | β |
| SSH Version | SSH-2.0-OpenSSH_9.6p1 Ubuntu-3ubuntu13.16 |
π TLS Certificate
| SANs | gs-luckybattlegrounds-phphjbtq7waoeoleonr4r-0.bloxd.io |
| Valid From | 2026-06-26T00:00:00+00:00 |
| Valid Until | 2026-09-24T23:59:59+00:00 |
| TLS Protocol | Tls13 |
| Cipher Suite | TLS_AES_256_GCM_SHA384 |
| Signature Algorithm | sha256ECDSA |
| Validity Period | 90 days |
| Serial Number | 18EF1EF2B90C9999677F7FAF327847CC |
| Thumbprint | 1881B12B5DA1246111470E1CE695F6B06E14996C |
π― Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 27% | 2 | 3 |
| routing | 13% | 1 | 1 |
| services | 19% | 2 | 2 |
| ownership | 27% | 2 | 3 |
| reputation | 22% | 1 | 3 |
| geolocation | 24% | 2 | 3 |
| Overall | 22% | 10 | 15 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
π Observation Timeline π Live
| First Seen | 2026-05-29 18:15:23 UTC |
| Last Seen | 2026-06-29 06:48:39 UTC |
| Profile Built | 2026-06-29 07:35:48 UTC |
| Data Freshness | Live |
| Signal Types | 20 |
| Total Observations | 20 |
Full dossier details are available via our API.