IPDebrief

45.61.184.51

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

IP Intelligence Briefing: 45.61.184.51

Date: 2026-06-15

---

**1. Core Profile**

- Tor Exit Node (confirmed via multiple sources).

- DNSSEC validation and BGP route stability appear normal.

---

**2. Observation History**

- Consistent low-risk profile (avg. score ~30).

- Geo validation anomalies: RTT (47ms) contradicts 7,555km distance, suggesting potential IP spoofing or misconfigured geolocation.

- No spikes in threat indicators or DNS anomalies.

---

**3. Relationships & Network Context**

- Linked to PONYNET-15 (same /22 subnet).

- 3 active IPs; 2 flagged as medium-risk, 1 low-risk.

- Subnet abuse density: 0% (mostly clean).

---

**4. Threat & Security Context**

- Tor exit nodes are often used for anonymizing malicious traffic. Monitor for C2 activity or data exfiltration.

- Open port 22 with SSH banner. Ensure no weak credentials or brute-force attempts are detected.

- No DNS records or TLS certs found. Potential for hidden services or misconfigured infrastructure.

---

**5. Recommendations**

1. Monitor Tor Traffic: Investigate outbound connections from this IP for suspicious payloads or C2 domains.

2. Validate Geolocation: Verify the IP’s true location, as geo validation discrepancies may indicate spoofing.

3. Secure SSH: Enforce strong SSH configurations (e.g., key-based auth, rate limiting) to prevent unauthorized access.

4. Track Neighbors: Monitor the 45.61.184.0/24 subnet for emerging threats, as two neighbors show medium risk.

---

Summary: While the IP itself is not overtly malicious, its association with Tor exit nodes and geolocation inconsistencies warrant closer scrutiny. Focus on traffic patterns and network perimeter defenses.

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

🌍 Geolocation

CountryπŸ‡ΊπŸ‡Έ United States
RegionFL
CityMiami
Timezoneβ€”
Latitude25.78
Longitude-80.18

🏒 Ownership & Registration

OrganizationFranTech Solutions
ASNAS53667
Network Nameβ€”
CIDR Block45.61.184.0/22
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 PurposeSingle-Service Host
Network TierTier 3 β€” Basic operator with some routing infrastructure
No specific classification

πŸ”Œ Services & Open Ports

PortServiceProtocolBanner
22sshtcp
Closed Ports25, 80, 443, 3389, 8080, 8443 (1 open / 7 scanned)
Serverβ€”
HTTP Titleβ€”
SSH VersionSSH-2.0-OpenSSH_8.9p1 Ubuntu-3

πŸ” 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
40%
25
routing
17%
23
services
12%
22
ownership
30%
37
reputation
28%
13
geolocation
27%
23
Overall26%1223
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
Data CoherenceMostly Consistent (80%) β€” 1 contradiction(s)
AttributionLow (35%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid
⚠ Claimed geolocation contradicts RTT physics measurement

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-22 13:35:45 UTC
Last Seen2026-06-28 19:29:01 UTC
Profile Built2026-06-29 07:33:24 UTC
Data FreshnessLive
Signal Types26
Total Observations53
πŸ” 26 signal types Β· 53 observations collected
This report is generated from 26+ 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.