IPDebrief

103.18.166.147

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.18.166.147/32

## Executive Summary

IP address 103.18.166.147 is a Moderate Risk (Score: 40) network endpoint located in Amritsar, Punjab, India (AS132768, IRT-APNANET4-IN). The IP exhibits minimal operational activity with no open services detected. While the address itself shows no direct threat indicators, it resides within a subnet with elevated abuse density (26.36%), requiring monitoring context. Recommended action: Implement blocking controls at perimeter firewalls with awareness of neighborhood risk.

---

## Network Profile & Ownership

AttributeValue
**IP Address**103.18.166.147/32
**Risk Score**40 (Moderate Risk)
**ASN**132768
**Organization**IRT-APNANET4-IN
**Country**India (IN)
**Region**Punjab (PB)
**City**Amritsar
**RIR**APNIC
**DNSBL Listings**2 of 8 lists

Network Classification: Provider infrastructure with no discernible infrastructure role (not cloud, CDN, VPN, proxy, or hosting). Service status indicates firewalled/no services detected.

---

## Threat Indicators Assessment

Direct Threat Signals: None detected

Control Plane: Route stability flagged as false with no route changes observed in the past 30 days. RPKI state and IRR consistency unavailable.

---

## Neighborhood Analysis (103.18.166.0/24)

Subnet Risk Profile:

High-Risk Neighbors Identified:

*Context: The subnet shows elevated abuse activity. While 103.18.166.147 itself is not directly implicated, the neighborhood risk profile warrants defensive consideration.*

---

## Service & DNS Analysis

Open Ports: None detected

HTTP/HTTPS: No services listening

Email Authentication: No SPF/DMARC records

PTR Records: None

Forward Resolution: Not confirmed

---

## Historical Observation Timeline

Total Observations: 18 signals over monitoring period

Recent Activity:

---

## Recommended Security Actions

Immediate Mitigation

The following firewall rules are recommended based on risk assessment:

iptables:

```bash

iptables -A INPUT -s 103.18.166.147 -j DROP

```

nftables:

```bash

nft add rule inet filter input ip saddr 103.18.166.147 drop

```

nginx:

```nginx

deny 103.18.166.147;

```

Cloudflare WAF:

```json

{

"description": "Block 103.18.166.147 โ€” IPDebrief risk score 40",

"action": "block",

"filter": {"expression": "ip.src eq 103.18.166.147"}

}

```

AWS WAF:

```json

{

"Addresses": ["103.18.166.147/32"],

"Description": "IPDebrief risk 40"

}

```

pfSense:

```

103.18.166.147/32

```

---

## Intelligence Assessment

The IP 103.18.166.147 presents a Moderate Risk profile with no active threat indicators. However, the subnet context (26.36% abuse density, 29 threat-sibling IPs) suggests this network segment may be utilized for malicious activity. The lack of open services and firewalled status indicate either a dormant endpoint or infrastructure not currently exposed to the public internet.

Priority: MEDIUM

Recommended Action: Block traffic at perimeter with continued monitoring. Investigate associated subnet if anomalous activity is observed.

Correlation Data: No certificate matches, no campaign correlations, no correlated IPs identified.

---

*Report generated: 2026-06-26 | Data Source: IPDebrief Intelligence Platform*

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

๐ŸŒ Geolocation

Country๐Ÿ‡ฎ๐Ÿ‡ณ India
RegionPB
CityAmritsar
Timezoneโ€”
Latitude22.00
Longitude79.00

๐Ÿข Ownership & Registration

OrganizationIRT-APNANET4-IN
ASNAS132768
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
35%
23
routing
13%
11
services
15%
22
ownership
27%
23
reputation
13%
12
geolocation
35%
23
Overall23%1014
Coverage: 6/6 dimensions ยท Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

๐Ÿ“… Observation Timeline ๐Ÿ”„ Live

First Seen2026-05-10 22:16:55 UTC
Last Seen2026-06-26 03:57:00 UTC
Profile Built2026-06-26 04:03:13 UTC
Data FreshnessLive
Signal Types18
Total Observations18
๐Ÿ” 18 signal types ยท 18 observations collected
This report is generated from 18+ 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.