IPDebrief

103.174.102.42

IP Intelligence Dossier
Your IP: 216.73.216.5
{ } JSON ๐Ÿ”ง Full Actions API
๐Ÿค– Witness AIThis summary was generated by AI and may contain inaccuracies. Verify critical details independently.

# IP INTELLIGENCE BRIEFING

Target: 103.174.102.42/32

Date: 2026-07-29

Classification: Moderate Risk (Score: 50/100)

---

## EXECUTIVE SUMMARY

IP 103.174.102.42 presents a moderate risk profile with no active threat indicators. The asset appears to be a firewalled infrastructure endpoint with minimal operator activity and no known malicious associations. Geolocation data shows conflicting signals requiring validation.

---

## OWNERSHIP & NETWORK CONTEXT

---

## THREAT INDICATORS

---

## GELOCATION INCONSISTENCY ALERT

Profile geolocation indicates US/New York, while historical observation data (2026-07-29 09:57:33 UTC) shows geolocation inference pointing to India (IN) with 0.52 confidence. This discrepancy warrants investigation and may indicate:

---

## DNS & HOSTING

---

## NEIGHBORHOOD ANALYSIS

Subnet: 103.174.102.0/24

- 103.174.102.136: 30/100 (Low)

- 103.174.102.204: 40/100 (Low)

---

## OBSERVATION HISTORY

---

## RECOMMENDED ACTIONS

Current Risk Assessment: No immediate threat action required. However, the following controls are recommended:

PlatformAction
iptables`iptables -A INPUT -s 103.174.102.42 -j DROP`
nftables`nft add rule inet filter input ip saddr 103.174.102.42 drop`
nginx`deny 103.174.102.42;`
pfSenseBlock 103.174.102.42/32
Cloudflare WAFBlock IP with expression `ip.src eq 103.174.102.42`
AWS WAFAdd to allow/block list: 103.174.102.42/32

---

## ANALYST NOTES

1. Monitor Geolocation Discrepancy: The US vs India location conflict should be validated through additional passive DNS or traceroute analysis.

2. No Active Threats: The IP has no known malicious associations. Firewall rules are probabilistic recommendations and should be reviewed against other intelligence.

3. Neighborhood Clean: The /24 subnet shows minimal abuse density with only 1 active sibling.

4. Email Infrastructure: The associated domain (wehear.in) has proper SPF/DMARC configuration, suggesting legitimate email hosting use case.

---

Status: MONITOR (No immediate blocking required)

Priority: LOW

Next Review: Recommended within 7-14 days or upon threat indicator escalation

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

๐ŸŒ Geolocation

Country๐Ÿ‡ฎ๐Ÿ‡ณ India
Regionโ€”
CityNew York
Timezoneโ€”
Latitudeโ€”
Longitudeโ€”

๐Ÿข Ownership & Registration

OrganizationNOC ADMIN
ASNAS133719
Network NameIDIGITAL
CIDR Block103.174.102.0/23
RIRAPNIC
CountryIN
Abuse ContactAvailable via RDAP

๐ŸŒ DNS Intelligence

PTRserver1.wehear.in
Forward ConfirmedNo โ€” PTR hostname does not resolve back to this IP (weak signal)
Forward Hostnamesserver1.wehear.in

๐Ÿ” DNS Hygiene

Hygiene Score60% (Good)
SPFPresent
DMARCPresent
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
25%
11
routing
25%
11
services
25%
11
ownership
25%
12
reputation
0%
00
geolocation
0%
00
Overall16%45
Coverage: 4/6 dimensions ยท Data sufficiency: partial
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

๐Ÿ“… Observation Timeline ๐Ÿ”„ Live

First Seen2026-07-21 19:02:23 UTC
Last Seen2026-08-13 06:43:20 UTC
Profile Built2026-08-08 01:30:22 UTC
Data FreshnessLive
Signal Types21
Total Observations21
๐Ÿ” 21 signal types ยท 21 observations collected
This report is generated from 21+ 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.