IPDebrief

103.4.251.20

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: 103.4.251.20/32

*Last Updated: 2026-06-17*

---

**Risk Profile**

---

**Observation History**

- Geolocation: 16 observations since June 2026, with RTT anomalies (19ms vs. expected 119ms for 5,968km).

- Network Stability: BGP route instability detected (route changes in 30 days: 0, but route stability score: 0.13).

- DNSSEC: Validated, but 2 DNSBL listings (high-risk subnets).

---

**Relationships**

- Linked to LT-CODE200-20211021 (same network handle).

- Subnet 103.4.251.0/24 has high abuse density (0.7) and 7 threat siblings.

---

**Neighborhood Analysis**

- 8 IPs with moderate risk (40).

- 1 IP with lower risk (25).

---

**Actionable Insights**

1. Monitor Subnet: The 103.4.251.0/24 subnet has a high abuse density. Investigate traffic patterns and consider blocking or monitoring this subnet.

2. Verify Geolocation: The IP’s low RTT (19ms) for its claimed location (5,968km) suggests potential spoofing or misconfigured routing.

3. DNSBL Check: The IP is listed in 2 DNSBLs, warranting further scrutiny for potential spam or malicious activity.

4. No Immediate Threat: No direct indicators of malicious activity, but the subnet’s risk profile warrants cautious monitoring.

---

Recommendation: Add 103.4.251.0/24 to watchlists for ongoing threat detection. Validate geolocation anomalies and review DNSBL associations for potential spam or phishing risks.

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

🌍 Geolocation

CountryπŸ‡ΊπŸ‡Έ United States
RegionNY
CityNew York
Timezoneβ€”
Latitude40.71
Longitude-74.01

🏒 Ownership & Registration

Organizationcode200_noc
ASNAS9009
Network Nameβ€”
CIDR Blockβ€”
RIRAPNIC
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
No specific classification

πŸ”Œ 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
33%
24
routing
13%
11
services
19%
22
ownership
30%
23
reputation
28%
13
geolocation
32%
23
Overall26%1016
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-07 23:03:27 UTC
Last Seen2026-06-22 07:15:53 UTC
Profile Built2026-06-22 07:25:55 UTC
Data FreshnessLive
Signal Types19
Total Observations20
πŸ” 19 signal types Β· 20 observations collected
This report is generated from 19+ 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.