119.73.116.166 is an IPv4 address operated by TEC-DATA CORE ENGINEERING TEAM (AS138655), geolocated to Faisalabad, Pakistan. Its reverse DNS name is static-host119-73-116-166.link.net.pk. As of October 13, 2026, IPDebrief rates it Moderate Risk (40/100); no anonymizing service was detected.
# IP Intelligence Briefing: 119.73.116.166
Classification: MODERATE RISK
Date: 2026-07-27
Analyst: IPDebrief Intelligence Team
---
## Executive Summary
IP address 119.73.116.166 was assessed as a MODERATE RISK endpoint with a risk score of 40. The address is assigned to TEC-DATA CORE ENGINEERING TEAM (ASN 138655) under the Naqashband network block in Faisalabad, Pakistan. No active threat indicators, blacklist listings, or malicious campaigns were observed. The IP is currently firewalled with no open services detected.
---
## Technical Profile
Ownership & Registration:
- Organization: TEC-DATA CORE ENGINEERING TEAM
- ASN: 138655 (Naqashband)
- CIDR Block: 119.73.112.0/20
- RIR: APNIC
- DNS PTR: static-host116.73.119.link.net.pk
Geolocation:
- Country: Pakistan (PK)
- Region: Punjab
- City: Faisalabad
- Coordinates: 31.37°N, 73.03°E
- Geographic validation: Plausible (consensus confirmed)
Network Classification:
- Infrastructure Type: Firewalled / No Services
- Services: No open ports detected
- Proxy/VPN/Tor: Not identified
- Residential/Hosting: Not classified
---
## Threat Assessment
Current Risk Score: 40 (Moderate)
Threat Indicators: None detected
Blacklist Count: 0
Known Campaigns: None associated
Abuse Confidence Score: Not available
Spam Source: No
Tor Exit Node: No
Control Plane Analysis:
- Route Stability: Unstable
- Operator Score: 0.2609 (Basic)
- DNSBL Listings: 2 of 8 total lists
- RPKI/Irr Consistency: Not evaluated
- BGP Prefix: 119.73.116.0/24
---
## Observation History
Eighteen signal observations recorded since deployment. Key findings:
- No ownership changes detected
- Threat persistence: 0 days
- Threat observation count: 0
- No persistently malicious behavior confirmed
- ICMP validation: Blocked (unable to validate geolocation)
Recent observations (2026-07-27) confirmed:
- Geographic data consistent with registration
- No service-level changes
- Subnet classification remained "clean" with low abuse density
---
## Neighborhood Analysis (119.73.116.0/24)
Subnet Classification: CLEAN
Abuse Density: 0
Total Siblings: 34
Active Siblings: 7
Threat Siblings: 0
Risk Distribution:
- High Risk: 0
- Medium Risk: 6
- Low Risk: 27
Notable neighbors with risk score 40: 119.73.116.8, .38, .125, .135, .149, .150, .167, .200, .224
Notable neighbors with risk score 25: .33, .38, .175, .242
---
## Relationship Graph
Eight relationships identified:
- Network Associations: 4x Naqashband (119.73.116.0/24)
- DNS Associations: 4x static-host119-73-116-166.link.net.pk
No additional organizational, certificate, or hostname relationships detected.
---
## Recommended Actions
Immediate Mitigation: Block IP at network perimeter. Recommended rules:
iptables:
```
iptables -A INPUT -s 119.73.116.166 -j DROP
```
nftables:
```
nft add rule inet filter input ip saddr 119.73.116.166 drop
```
nginx:
```
deny 119.73.116.166;
```
Cloudflare WAF:
```json
{
"description": "Block 119.73.116.166 — IPDebrief risk score 40",
"action": "block",
"filter": {
"expression": "ip.src eq 119.73.116.166"
}
}
```
AWS WAF:
```json
{
"Addresses": ["119.73.116.166/32"],
"Description": "IPDebrief risk 40"
}
```
---
## Intelligence Narrative
The IP address 119.73.116.166 presents a moderate risk profile suitable for defensive blocking. While no direct threat indicators were observed, the IP's classification as "firewalled" with no open services suggests it may be part of a compromised or misconfigured infrastructure. The absence of blacklist entries and known malicious campaigns indicates the risk may be probabilistic rather than confirmed malicious.
The subnet (119.73.116.0/24) maintains a clean classification with zero threat siblings, though six neighboring addresses carry medium risk scores. This suggests isolated rather than systemic abuse within the block.
Recommendation: Apply blocking rules at the perimeter firewall. Monitor for any service activity on the IP. If the IP begins to show open services or threat indicators, conduct deeper investigation into associated hostnames and network relationships.
---
Report Generated: IPDebrief Intelligence Platform
Data Sources: Full profile, observation history, relationship graph, neighborhood analysis
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | TEC-DATA CORE ENGINEERING TEAM |
| ASN | AS138655 |
| Network Name | Naqashband |
| CIDR Block | 119.73.112.0/20 |
| RIR | APNIC |
| Country | PK |
| Abuse Contact | Available via RDAP |
🌐 DNS Intelligence
| PTR | static-host119-73-116-166.link.net.pk |
| Forward Confirmed | Yes — FCrDNS verified |
| Forward Hostnames | static-host119-73-116-166.link.net.pk |
🔐 DNS Hygiene
| Hygiene Score | 20% (Poor) |
| SPF | 0/2 domains |
| DMARC | 0/2 domains |
| FCrDNS | Verified |
| DNSSEC | Not signed |
| CAA | Not configured |
| Domains Checked | 2 domains |
☁️ Network Classification
| Infrastructure | Unknown |
| Service Purpose | Firewalled / No Services |
| Network Tier | Unknown — Insufficient routing data to classify |
🔌 Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| No open ports detected | |||
| Closed Ports | 22, 25, 80, 443, 3389, 8080, 8443 (0 open / 7 scanned) | ||
| Server | — |
| HTTP Title | — |
🔐 TLS Certificate
| SANs | None |
| Valid From | — |
| Valid Until | — |
🛡️ Public Network Snapshot
| Origin ASN | AS138655 |
| Network Prefix | 119.73.116.0/24 |
| Route mapping | Found |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 23% | 2 | 5 |
| routing | 8% | 1 | 1 |
| services | 12% | 2 | 2 |
| ownership | 17% | 2 | 3 |
| reputation | 14% | 1 | 3 |
| geolocation | 12% | 2 | 2 |
| Overall | 14% | 10 | 16 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (70%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-07-14 09:42:41 UTC |
| Last Seen | 2026-10-13 04:32:29 UTC |
| Profile Built | 2026-10-13 04:34:06 UTC |
| Data Freshness | Live |
| Signal Types | 21 |
| Total Observations | 26 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 119.73.116.166
Who owns the IP address 119.73.116.166?
119.73.116.166 is registered to TEC-DATA CORE ENGINEERING TEAM. The address falls within the 119.73.112.0/20 network block. Registration is held at APNIC.
Where is 119.73.116.166 located?
Geolocation data places 119.73.116.166 in Faisalabad, Punjab, Pakistan. IP geolocation is approximate and indicates the network's registered or routed location rather than a precise physical address.
Is 119.73.116.166 malicious or safe?
119.73.116.166 currently carries a moderate risk assessment, meaning some indicators warrant caution, but the evidence is mixed. This assessment is generated from continuously collected signals and can change over time.
What is the hostname for 119.73.116.166?
The reverse DNS (PTR) record for 119.73.116.166 is static-host119-73-116-166.link.net.pk. This hostname is forward-confirmed, meaning it resolves back to the same address.