IPDebrief

46.183.216.217

IP Intelligence Dossier
Your IP: 216.73.217.131
{ } JSON 🔧 Full Actions API
🤖 Witness AIThis summary was generated by AI and may contain inaccuracies. Verify critical details independently.

# 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

Network Classification

Risk Indicators

## Observation History

Analysis of 20 signal observations reveals:

## Relationship Graph

## Neighborhood Analysis (46.183.216.0/24)

## Recommended Actions

Access Control

Monitoring

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:

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.

🌍 Geolocation

Country🇺🇸 United States
RegionUS-MA
CityBoston
TimezoneAmerica/New_York
Latitude56.95
Longitude24.10

🏢 Ownership & Registration

Organizationlir-lv-siadc-1-MNT
ASNAS52048
Network NameRIXHOST
CIDR Block46.183.216.0/24
RIRRIPE
CountryLV
Abuse ContactAvailable via RDAP

🌐 DNS Intelligence

PTRip-216-217.dataclub.info
Forward ConfirmedNo — PTR hostname does not resolve back to this IP (weak signal)
Forward Hostnamesip-216-217.dataclub.info

🔐 DNS Hygiene

Hygiene Score20% (Poor)
SPFNot configured
DMARCNot configured
FCrDNSNot verified
DNSSECValid
CAANot configured

☁️ Network Classification

InfrastructureUnknown
Service PurposeWeb Server
Network TierUnknown — Insufficient routing data to classify
No specific classification

🔌 Services & Open Ports

PortServiceProtocolBanner
80httptcp—
443httpstcp—
22sshtcpBanner detected
Closed Ports25, 3389, 8080, 8443 (3 open / 7 scanned)
Server—
HTTP Title—

🔐 TLS Certificate

An expired certificate for CN=www.v47lg3t3igk.net was found on this IP. This may indicate a previously hosted website, a decommissioned service, or stale infrastructure.
🔒
CN=www.v47lg3t3igk.net
Issued by CN=www.kdtyz2ev7zcbypbfgt6.com
Self-signed: No
SANsNone
Valid From2026-07-09T00:00:00+00:00
Valid Until2026-09-19T00:00:00+00:00 (expired)

🛡️ Public Network Snapshot

Origin ASNAS52048
Network Prefix46.183.216.0/24
Route mappingFound

🎯 Confidence Breakdown

Per-dimension confidence scores based on source diversity and data freshness

DimensionScoreSourcesObservations
threat
61%
224
routing
27%
23
services
35%
23
ownership
37%
35
reputation
26%
13
geolocation
21%
22
Overall35%1240
Coverage: 6/6 dimensions · Data sufficiency: sufficient
Data CoherenceMostly Consistent (80%) — 1 contradiction(s)
AttributionLow (35%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid
⚠ Geo sources disagree on country: RU, US

📅 Observation Timeline 🔄 Live

First Seen2026-07-17 12:38:37 UTC
Last Seen2026-09-04 18:25:07 UTC
Profile Built2026-09-05 15:07:57 UTC
Data FreshnessLive
Signal Types28
Total Observations34
🔍 28 signal types · 34 observations collected
This report is generated from 28+ independent intelligence signals including ownership records, DNS analysis, BGP routing, TLS certificates, port scanning, threat feeds, behavioral fingerprinting, and more.
Full dossier details are available via our API.
{ } JSON API 🔧 Actions API 📧 Enterprise Access

❓ 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.

🏘️ Related IP Addresses

Browse related networks

ℹ️ About This Report

All data shown is publicly available network metadata — IP addresses do not reliably identify individuals. Assessments are probabilistic and should not be used as sole basis for access control decisions. To report an issue or request data review, contact admin@ipdebrief.com.