216.73.163.30 is an IPv4 address operated by Prefixx, Inc. (AS206092), geolocated to San Francisco, United States. As of September 5, 2026, IPDebrief rates it Low Risk (25/100); no anonymizing service was detected.
# IP Intelligence Briefing: 216.73.163.30/32
Classification: LOW RISK
Date: July 2026
Analyst: IPDebrief Intelligence Team
---
## Executive Summary
IP 216.73.163.30 is classified as Low Risk with a risk score of 25. The address belongs to Prefixx, Inc. (ASN 206092) and operates within the PFX-EXPRESSVPN network block (216.73.160.0/22). Current threat indicators indicate no active malicious activity, with the IP showing a clean classification and zero blacklist listings. However, geolocation validation anomalies and minimal service exposure warrant continued monitoring.
---
## Ownership and Network Context
- Organization: Prefixx, Inc.
- Network Name: PFX-EXPRESSVPN
- ASN: 206092
- CIDR Block: 216.73.160.0/22
- Location: San Francisco, California, US
- Registration: ARIN (Registration date not available in dataset)
The IP operates under the PFX-EXPRESSVPN network infrastructure, which is associated with ExpressVPN services. Network classification flags indicate the IP is firewalled with no active services exposed.
---
## Threat Assessment
Current Risk Profile:
- Risk Score: 25 (Low Risk)
- Abuse Confidence Score: Not applicable
- Blacklist Count: 0
- Threat Feeds: No detections
Malicious Activity Indicators:
- Not a Tor exit node
- Not a known attacker
- Not identified as a spam source
- No known campaign associations
- Zero threat observation count in persistence metrics
Control Plane Data:
- BGP Prefix: 216.73.163.0/24
- Route Stability: False (route changes detected)
- DNSBL Listings: 1 of 8 total lists
- RPKI State: Not validated
- IRR Consistency: Not applicable
---
## Technical Observations
DNS Resolution:
- PTR Hostnames: None
- Forward Resolution Count: 0
- DNSSEC Valid: Yes
- Forward Confirmed: False
Services:
- Open Ports: None detected
- TLS Certificate: None
- HTTP Title: None
- Server Banner: None
- Service Purpose: Firewalled / No Services
Network Traceroute:
- Hop Count: 11
- Transit Networks: Comcast
- First Hop RTT: 0.2ms
- Last Hop RTT: 89.1ms
- Timed Out Hops: 2
---
## Neighborhood Analysis (216.73.163.0/24)
Subnet Statistics:
- Total Siblings: 82
- Active Siblings: 26
- Abuse Density: 0.0244 (Low)
- Threat Siblings: 2
Risk Distribution:
- High Risk: 0
- Medium Risk: 1
- Low Risk: 80
Notable Neighbor:
- 216.73.163.2: Risk Score 60, Authority Score 50 (Elevated)
The subnet exhibits minimal abuse density with a single medium-risk neighbor. The target IP does not inherit significant risk from adjacent addresses.
---
## Historical Trend Analysis
Observation Count: 19 total signals observed
Most Recent Activity: July 28, 2026
Key Historical Indicators:
- Classification: Clean
- Abuse Density: 0.0244 (consistent)
- Inherited Risk: 0
- Ownership Changes: 0 (stable)
- Threat Persistence: 0 days
- Campaign Likelihood: None
Geolocation Anomaly:
Multiple historical probes indicate geolocation validation failures. Claims show San Francisco coordinates (37.2379, -121.7946) with an 8,865.6km distance from probe origin, resulting in RTT violations (83ms observed vs. 177.3ms minimum possible). This suggests either misconfigured geolocation data or proxy usage patterns.
---
## Relationships
Network Associations:
- 4 relationships identified, all categorized as "Same Network"
- Target: PFX-EXPRESSVPN (network-level association)
- No external hostname, organization, or certificate relationships detected
---
## Recommended Actions
For SOC Analysts:
1. Monitor: Continue standard monitoring due to VPN network classification and geolocation anomalies
2. Investigate: Review traffic patterns if connections originate from unexpected geographic locations
3. Block: No immediate blocking required; risk score remains low (25)
4. Alert: Trigger alerts only if risk score increases above 50 or threat indicators emerge
Firewall/IDS Rules:
- No specific blocking rules recommended at this time
- Standard VPN traffic rules applicable
---
## Conclusion
IP 216.73.163.30 presents a low-risk threat profile with no current malicious indicators. The address operates within a VPN service infrastructure (PFX-EXPRESSVPN) and exhibits stable ownership with minimal neighborhood risk. Primary concerns are geolocation validation anomalies and the absence of service exposure, which may indicate proper firewalling but also potential misconfiguration. No immediate action required beyond routine monitoring.
Threat Level: LOW
Action Required: Monitor
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | Prefixx, Inc. |
| ASN | AS206092 |
| Network Name | PFX-EXPRESSVPN |
| CIDR Block | 216.73.160.0/22 |
| 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 | 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 | AS206092 |
| Network Prefix | 216.73.163.0/24 |
| Route mapping | Found |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 25% | 2 | 4 |
| routing | 8% | 1 | 1 |
| services | 12% | 2 | 2 |
| ownership | 17% | 2 | 3 |
| reputation | 22% | 1 | 3 |
| geolocation | 17% | 2 | 3 |
| Overall | 17% | 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-17 11:04:37 UTC |
| Last Seen | 2026-10-07 09:52:02 UTC |
| Profile Built | 2026-09-05 00:35:47 UTC |
| Data Freshness | Live |
| Signal Types | 22 |
| Total Observations | 26 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 216.73.163.30
Who owns the IP address 216.73.163.30?
216.73.163.30 is registered to Prefixx, Inc.. The address falls within the 216.73.160.0/22 network block. Registration is held at ARIN.
Where is 216.73.163.30 located?
Geolocation data places 216.73.163.30 in San Francisco, California, United States. IP geolocation is approximate and indicates the network's registered or routed location rather than a precise physical address.
Is 216.73.163.30 malicious or safe?
216.73.163.30 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.