IPDebrief

107.189.4.209

IP Intelligence Dossier
Your IP: 216.73.217.135
{ } JSON πŸ”§ Full Actions API
πŸ€– Witness AIThis summary was generated by AI and may contain inaccuracies. Verify critical details independently.

IP Intelligence Briefing: 107.189.4.209

Date: 2026-06-09

---

**1. Core Profile**

- Identified as a Tor exit node (high-risk category).

- Observed in 1 threat feed (Tor exit indicators).

- Registered with ARIN, abuse contact available via RDAP.

- Subnet: 107.189.4.209/24 (abuse density: 1/3).

---

**2. Observation History**

- Tor exit node activity detected on 2026-06-09.

- No significant changes in risk scores or network behavior over the past 7 days.

- BGP route stability: "Basic" (operator score: 0.26).

- No route changes in 30 days.

---

**3. Relationships**

- Multiple connections to BUYVM-LUXEMBOURG-02 (same network).

- No direct links to known malicious organizations or domains.

- DNS records: No verified PTR hostnames or domain ownership.

---

**4. Neighborhood Analysis**

- 107.189.4.12: Risk score 59 (same as target).

- 107.189.4.58: Risk score 25 (low risk).

---

**5. Recommendations**

---

Source: IPDebrief Threat Intelligence Platform.

Note: This IP is flagged for Tor exit node activity, which is a known vector for malicious traffic. Further investigation into related networks is advised.

This summary was generated by AI and may contain inaccuracies. Verify critical details independently.

🌍 Geolocation

CountryπŸ‡ΊπŸ‡Έ United States
RegionME
CityBissen
Timezoneβ€”
Latitude49.79
Longitude6.10

🏒 Ownership & Registration

OrganizationBuyVM
ASNAS53667
Network Nameβ€”
CIDR Block107.189.0.0/21
RIRARIN
Countryβ€”
Abuse ContactAvailable via RDAP

🌐 DNS Intelligence

PTR RecordNo PTR
Forward ConfirmedNo β€” PTR hostname does not resolve back to this IP (weak signal)

πŸ” DNS Hygiene

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

☁️ Network Classification

InfrastructureUnknown
Service PurposeFirewalled / No Services
Network TierUnknown β€” Insufficient routing data to classify
Tor

πŸ”Œ Services & Open Ports

PortServiceProtocolBanner
No open ports detected
Closed Ports22, 25, 80, 443, 3389, 8080, 8443 (0 open / 7 scanned)
Serverβ€”
HTTP Titleβ€”

πŸ” TLS Certificate

πŸ”’
No certificate
Issued by β€”
N/A
SANsNone
Valid Fromβ€”
Valid Untilβ€”

🎯 Confidence Breakdown

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

DimensionScoreSourcesObservations
threat
26%
24
routing
17%
23
services
12%
22
ownership
19%
34
reputation
28%
13
geolocation
19%
22
Overall20%1218
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-22 13:35:41 UTC
Last Seen2026-06-28 19:19:24 UTC
Profile Built2026-06-29 13:24:58 UTC
Data FreshnessLive
Signal Types25
Total Observations50
πŸ” 25 signal types Β· 50 observations collected
This report is generated from 25+ 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

ℹ️ 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.