# IP Intelligence Briefing: 46.183.216.217/32
## Executive Summary
IP address 46.183.216.217 is classified as High Risk (Risk Score: 70/100) with confirmed Tor exit node activity. The IP is associated with Latvian infrastructure (RIXHOST) and presents a medium threat severity primarily due to anonymous traffic indicators. Immediate monitoring and access control enhancements are recommended.
## Technical Profile
Ownership & Geolocation
- ASN: 52048 (RIXHOST)
- Organization: lir-lv-siadc-1-MNT
- Network: 46.183.216.0/24
- Country: Latvia (LV)
- City: Riga (56.95°N, 24.1°E)
- RIR: RIPE
Network Classification
- Role: Tor Exit Nodes
- Services: Firewalled / No Services (no open ports detected)
- DNS: PTR hostname ip-216-217.dataclub.info, domain dataclub.info
- Blacklist Status: Listed on 1 blacklist (dnsblListedCount: 1)
Risk Indicators
- Tor Exit Node: Confirmed (isTorExit: true)
- Known Attacker: No
- Spam Source: No
- Abuse Confidence Score: Not available
- Operator Score: 0.1304 (Minimal)
## Observation History
Analysis of 20 signal observations reveals:
- Recent Activity: Signals observed as recent as 2026-07-25T09:12:17
- Persistence: 0 threat persistence days (not persistently malicious)
- Threat Observations: 1 total
- Geolocation Consensus: Validated with 5 probes, 1224.9km distance from origin, 115-122ms RTT
- Subnet Context: 46.183.216.0/24 classified as "mostly_clean" with abuse density of 1, inherited risk score of 2
## Relationship Graph
- Network Relationships: 2 associations with RIXHOST
- DNS Associations: 5 associations with ip-216-217.dataclub.info
- No: Organization, hostname, or certificate relationships beyond DNS
## Neighborhood Analysis (46.183.216.0/24)
- Total Siblings: 1
- Active Siblings: 0
- Threat Siblings: 1
- Abuse Density: 0
- Classification: mostly_clean
## Recommended Actions
Access Control
- Action: Consider enhanced verification for anonymous traffic
- Reason: Tor exit indicators observed
- Severity: Medium
Monitoring
- Action: Increase logging verbosity and review recent activity from this IP
- Reason: Elevated risk score (70/100)
- Severity: High
Firewall Rules
iptables:
```bash
iptables -A INPUT -s 46.183.216.217 -j DROP
```
nftables:
```bash
nft add rule inet filter input ip saddr 46.183.216.217 drop
```
nginx:
```nginx
deny 46.183.216.217;
```
pfSense:
```
46.183.216.217/32
```
Cloudflare WAF:
```json
{
"description": "Block 46.183.216.217 — IPDebrief risk score 70",
"action": "block",
"filter": {
"expression": "ip.src eq 46.183.216.217"
}
}
```
AWS WAF:
```json
{
"Addresses": ["46.183.216.217/32"],
"Description": "IPDebrief risk 70"
}
```
## Intelligence Assessment
This IP represents a Tor exit node infrastructure in Latvia. The primary threat vector is anonymous traffic routing, which could be used for:
- Concealing attacker identities
- Bypassing geographic restrictions
- Proxying malicious traffic
The subnet shows minimal inherited risk with no active sibling threats currently detected. However, the confirmed Tor exit node status warrants defensive blocking or enhanced monitoring depending on organizational risk tolerance.
Recommendation: Block at perimeter firewall if Tor traffic is not required for legitimate operations. Implement enhanced logging for any traffic that does traverse.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | lir-lv-siadc-1-MNT |
| ASN | AS52048 |
| Network Name | RIXHOST |
| CIDR Block | 46.183.216.0/24 |
| RIR | RIPE |
| Country | LV |
| Abuse Contact | Available via RDAP |
🌐 DNS Intelligence
| PTR | ip-216-217.dataclub.info |
| Forward Confirmed | No — PTR hostname does not resolve back to this IP (weak signal) |
| Forward Hostnames | ip-216-217.dataclub.info |
🔐 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 | Web Server |
| Network Tier | Unknown — Insufficient routing data to classify |
🔌 Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| 80 | http | tcp | — |
| 443 | https | tcp | — |
| 22 | ssh | tcp | Banner detected |
| Closed Ports | 25, 3389, 8080, 8443 (3 open / 7 scanned) | ||
| Server | — |
| HTTP Title | — |
🔐 TLS Certificate
CN=www.v47lg3t3igk.net was found on this IP. This may indicate a previously hosted website, a decommissioned service, or stale infrastructure.| SANs | None |
| Valid From | 2026-07-09T00:00:00+00:00 |
| Valid Until | 2026-09-19T00:00:00+00:00 (expired) |
🛡️ Public Network Snapshot
| Origin ASN | AS52048 |
| Network Prefix | 46.183.216.0/24 |
| Route mapping | Found |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 61% | 2 | 24 |
| routing | 27% | 2 | 3 |
| services | 35% | 2 | 3 |
| ownership | 37% | 3 | 5 |
| reputation | 26% | 1 | 3 |
| geolocation | 21% | 2 | 2 |
| Overall | 35% | 12 | 40 |
| Data Coherence | Mostly Consistent (80%) — 1 contradiction(s) |
| Attribution | Low (35%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-07-17 12:38:37 UTC |
| Last Seen | 2026-09-04 18:25:07 UTC |
| Profile Built | 2026-09-05 15:07:57 UTC |
| Data Freshness | Live |
| Signal Types | 28 |
| Total Observations | 34 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 46.183.216.217
Who owns the IP address 46.183.216.217?
46.183.216.217 is registered to lir-lv-siadc-1-MNT. The address falls within the 46.183.216.0/24 network block. Registration is held at RIPE.
Where is 46.183.216.217 located?
Geolocation data places 46.183.216.217 in Boston, US-MA, United States. The local time zone is America/New_York. IP geolocation is approximate and indicates the network's registered or routed location rather than a precise physical address.
Is 46.183.216.217 malicious or safe?
46.183.216.217 currently carries a moderate risk assessment, meaning some indicators warrant caution, but the evidence is mixed. This assessment is generated from continuously collected signals and can change over time.
What is the hostname for 46.183.216.217?
The reverse DNS (PTR) record for 46.183.216.217 is ip-216-217.dataclub.info. This hostname is not forward-confirmed, so it should be treated as a weak signal.
What ports are open on 46.183.216.217?
Responsive ports observed on 46.183.216.217 include 80, 443, 22. Port visibility reflects the most recent scan and may change as the host's configuration or firewall rules change.