IPDebrief

102.129.200.117

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

*Generated via IPDebrief Threat Intelligence Platform*

---

**1. Core Profile**

- ASN: 208949

- Organization: IPXO Incident Response Team

- CIDR Block: 102.129.200.0/24

- Country: United States (US)

- Geo Plausibility: False (RTT inconsistency with distance)

- No malicious indicators, abuse confidence, or campaign associations.

- Not listed in DNSBLs or spam sources.

---

**2. Network Behavior**

- Firewalled / No Services (no open ports, TLS, or HTTP activity).

- Subnet: 102.129.200.0/24 (abuse density: 0.5, classified as "mostly_clean").

- BGP Prefix: 102.129.200.0/24

- RPKI State: Unknown

- DNSSEC: Valid

- CAA Records: Present

- Route Stability: Unstable (route changes in last 30 days).

---

**3. Observation History**

- Multi-signal geolocation inferred (confidence: 28%) with 3,750km accuracy.

- DNS listings (2/8 total) with "high" severity.

- Network operator score: 0.2174 (Minimal risk).

- No persistent malicious activity (threat observation count: 1).

---

**4. Neighborhood Analysis**

- 102.129.200.101: Risk score 50 (same subnet, moderate risk).

---

**5. Recommended Actions**

- iptables: `iptables -A INPUT -s 102.129.200.117 -j DROP`

- Cloudflare WAF: Block IP with description "IPDebrief risk 50".

- AWS WAF: Add `102.129.200.117/32` to IP set.

- Watch for unexpected DNS activity or subnet-wide changes.

- Validate geolocation consistency (RTT vs. distance).

---

**6. Summary**

The IP 102.129.200.117 is owned by the IPXO Incident Response Team and exhibits moderate risk. While no direct malicious indicators are present, its geolocation inconsistency and subnet abuse density suggest potential scrutiny. Monitor for anomalous behavior, especially given the unstable BGP route and minimal network operator score. Use the provided firewall rules to block the IP if it becomes a concern.

*Generated by IPDebrief – Threat Intelligence for SOC Teams*

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

🌍 Geolocation

CountryπŸ‡ΊπŸ‡Έ United States
RegionIL
CityChicago
Timezoneβ€”
Latitude-29.00
Longitude24.00

🏒 Ownership & Registration

OrganizationIPXO Incident Response Team
ASNAS208949
Network Name102.129.200.0 - 102.129.200.255
CIDR Block102.129.200.0/24
RIRAFRINIC
CountryUS
Abuse Contactβ€”

🌐 DNS Intelligence

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

πŸ” DNS Hygiene

Hygiene Score40% (Fair)
SPFNot configured
DMARCNot configured
FCrDNSNot verified
DNSSECValid
CAAPresent

☁️ Network Classification

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

πŸ”Œ Services & Open Ports

PortServiceProtocolBanner
No open ports detected
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
30%
24
routing
22%
33
services
11%
12
ownership
15%
22
reputation
21%
13
geolocation
30%
23
Overall21%1117
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 πŸ”„ Recent

First Seen2026-05-07 23:03:24 UTC
Last Seen2026-06-26 14:30:44 UTC
Profile Built2026-06-27 07:11:33 UTC
Data FreshnessRecent
Signal Types23
Total Observations24
πŸ” 23 signal types Β· 24 observations collected
This report is generated from 23+ 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.