23.94.155.93
Intelligence Briefing: 23.94.155.93/32
Observations classified the IP address 23.94.155.93 as Low Risk with a risk score of 25. Ownership records identified the address as belonging to a Private Customer under ASN 262287 within the 23.94.155.0/24 block, geolocated to Miami, Florida, US.
Network analysis indicated the host was firewalled with no open ports or active services. DNS records resolved the address to 23-94-155-93-host.colocrossing.com. Email authentication checks confirmed the presence of SPF and DMARC records.
Geolocation validation highlighted a contradiction between the claimed Miami location and physics-based RTT measurements, which recorded a 55ms latency inconsistent with the 7557km distance. Control plane data flagged one DNSBL listing out of eight lists checked. Behavioral analysis recorded zero honeypot hits, enumeration strikes, or WAF violations.
Although threat indicators lists were empty, the profile was tagged as a Suspicious Host with minimal operator stability. The neighborhood classification remained clean with zero threat siblings. Due to signal contradictions and geolocation anomalies, the assessment recommended monitoring the address for changes.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | Private Customer |
| ASN | AS262287 |
| Network Name | MIAMI-FL-USA-23-94-155-0-24 |
| CIDR Block | 23.94.155.0/24 |
| RIR | ARIN |
| Country | United States |
| Abuse Contact | — |
🌐 DNS Intelligence
| PTR | 23-94-155-93-host.colocrossing.com |
| Forward Confirmed | No — PTR hostname does not resolve back to this IP (weak signal) |
| Forward Hostnames | 23-94-155-93-host.colocrossing.com |
🔐 DNS Hygiene
| Hygiene Score | 60% (Good) |
| SPF | Present |
| DMARC | Present |
| FCrDNS | Not verified |
| DNSSEC | Valid |
| CAA | Not configured |
☁️ Network Classification
| Infrastructure | Unknown |
| Service Purpose | Firewalled / No Services |
| Network Tier | Unknown — Insufficient routing data to classify |
🔌 Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| No open ports detected | |||
| Closed Ports | 22, 25, 80, 443, 3389, 8080, 8443 (0 open / 7 scanned) | ||
| Server | — |
| HTTP Title | — |
🔐 TLS Certificate
| SANs | None |
| Valid From | — |
| Valid Until | — |
🛡️ Public Network Snapshot
| Origin ASN | AS262287 |
| Network Prefix | 23.94.155.0/24 |
| Route mapping | Found |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 39% | 2 | 5 |
| routing | 8% | 1 | 1 |
| services | 12% | 2 | 2 |
| ownership | 12% | 2 | 2 |
| reputation | 8% | 1 | 2 |
| geolocation | 28% | 2 | 4 |
| Overall | 18% | 10 | 16 |
| Data Coherence | Mostly Consistent (80%) — 1 contradiction(s) |
| Attribution | Low (35%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-07-03 23:05:39 UTC |
| Last Seen | 2026-09-13 13:27:52 UTC |
| Profile Built | 2026-09-13 13:34:11 UTC |
| Data Freshness | Live |
| Signal Types | 22 |
| Total Observations | 28 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 23.94.155.93
Who owns the IP address 23.94.155.93?
23.94.155.93 is registered to Private Customer. The address falls within the 23.94.155.0/24 network block. Registration is held at ARIN.
Where is 23.94.155.93 located?
Geolocation data places 23.94.155.93 in Miami, Florida, United States. IP geolocation is approximate and indicates the network's registered or routed location rather than a precise physical address.
Is 23.94.155.93 malicious or safe?
23.94.155.93 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 is the hostname for 23.94.155.93?
The reverse DNS (PTR) record for 23.94.155.93 is 23-94-155-93-host.colocrossing.com. This hostname is not forward-confirmed, so it should be treated as a weak signal.