66.9.161.61 is an IPv4 address operated by SpaceX Services, Inc. (AS14593), geolocated to Caracas, Venezuela. Its reverse DNS name is customer.bgtacol1.isp.starlink.com. As of November 6, 2026, IPDebrief rates it Low Risk (25/100); no anonymizing service was detected.
IP 66.9.161.61 is associated with SpaceX Services, Inc. under netname STARLINK-907076731910684719-PM-FRNTDEU1-IPV4 (ASN 14593). The asset is geolocated to Caracas, Venezuela, though validation was limited due to ICMP blocks. Reputation metrics classify the IP as Low Risk with a score of 25. Network scanning confirmed the host is firewalled with no open ports or active services. DNS resolution returned customer.bgtacol1.isp.starlink.com, and SPF and DMARC records were present. While the threat actor profile labeled the host as "Suspicious Host" due to indicator presence, blacklist counts remained zero across general sources, with one listing recorded in the control plane. The neighborhood classification indicates a "mostly_clean" environment with low abuse density. Behavioral analysis recorded zero incidents, enumeration strikes, or WAF violations. Current recommendation is to Monitor the address with low severity.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | SpaceX Services, Inc. |
| ASN | AS14593 |
| Network Name | STARLINK-907076731910684719-PM-FRNTDEU1-IPV4 |
| CIDR Block | 66.9.161.0/26 |
| RIR | ARIN |
| Country | United States |
| Abuse Contact | Available via RDAP |
🌐 DNS Intelligence
| PTR | customer.bgtacol1.isp.starlink.com |
| Forward Confirmed | No — PTR hostname does not resolve back to this IP (weak signal) |
| Forward Hostnames | customer.bgtacol1.isp.starlink.com |
🔐 DNS Hygiene
| Hygiene Score | 60% (Good) |
| SPF | Present |
| DMARC | Present |
| FCrDNS | Not verified |
| DNSSEC | Not signed |
| CAA | Present |
☁️ 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 | AS14593 |
| Network Prefix | 66.9.161.0/24 |
| Route mapping | Found |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 35% | 2 | 2 |
| routing | 25% | 1 | 1 |
| services | 25% | 1 | 1 |
| ownership | 0% | 0 | 0 |
| reputation | 25% | 1 | 1 |
| geolocation | 25% | 1 | 1 |
| Overall | 22% | 6 | 6 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-11-04 12:04:09 UTC |
| Last Seen | 2026-11-06 02:09:08 UTC |
| Profile Built | 2026-11-06 02:13:01 UTC |
| Data Freshness | Live |
| Signal Types | 23 |
| Total Observations | 24 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 66.9.161.61
Who owns the IP address 66.9.161.61?
66.9.161.61 is registered to SpaceX Services, Inc.. The address falls within the 66.9.161.0/26 network block. Registration is held at ARIN.
Where is 66.9.161.61 located?
Geolocation data places 66.9.161.61 in Caracas, Distrito Federal, Venezuela. IP geolocation is approximate and indicates the network's registered or routed location rather than a precise physical address.
Is 66.9.161.61 malicious or safe?
66.9.161.61 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 66.9.161.61?
The reverse DNS (PTR) record for 66.9.161.61 is customer.bgtacol1.isp.starlink.com. This hostname is not forward-confirmed, so it should be treated as a weak signal.