IPDebrief

23.129.64.203

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: 23.129.64.203

*Generated via IPDebrief analysis*

---

**Risk Profile**

- Country: US (Seattle, WA)

- Plausibility: Geo validation failed (RTT inconsistency for distance).

---

**Network & Ownership**

- 23.129.64.99 (Risk: 70)

- 23.129.64.130–133 (Risk: 66–70)

---

**Observation History**

- Open ports: HTTP (80), HTTPS (443)

- TLS Certificate: Issued to `www.mwxzshkcsdjr4b5u.com` (self-signed).

---

**Relationships & Context**

- Tor network "EMERALD-ONION-TOR1" (same subnet).

- No direct ties to known malicious organizations or campaigns.

---

**Actionable Insights**

1. Monitor Tor Exit Node Activity: While not malicious, Tor exit nodes can be used for covert traffic. Investigate unusual traffic patterns or data exfiltration risks.

2. Validate Geolocation: The RTT anomaly suggests potential spoofing. Cross-check with other geolocation sources.

3. Subnet Risk Management: The subnet contains medium-risk IPs. Prioritize monitoring for lateral movement or command-and-control activity.

---

*End of Briefing*

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

🌍 Geolocation

CountryπŸ‡ΊπŸ‡Έ United States
RegionWA
CitySeattle (Yesler Terrace)
Timezoneβ€”
Latitude37.75
Longitude-97.82

🏒 Ownership & Registration

OrganizationEmerald Onion
ASNAS396507
Network Nameβ€”
CIDR Block23.129.64.0/24
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 TierTier 3 β€” Basic operator with some routing infrastructure
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
56%
210
routing
24%
23
services
30%
23
ownership
42%
310
reputation
28%
13
geolocation
30%
23
Overall35%1232
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:50 UTC
Last Seen2026-06-26 21:06:52 UTC
Profile Built2026-06-27 16:02:46 UTC
Data FreshnessLive
Signal Types26
Total Observations66
πŸ” 26 signal types Β· 66 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.