# 119.73.116.224 — IP Intelligence Summary 119.73.116.224 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-224.link.net.pk. As of October 6, 2026, IPDebrief rates it Moderate Risk (40/100); no anonymizing service was detected. - Canonical page: https://ipdebrief.com/119.73.116.224 - Last updated: 2026-10-06 ## Ownership - Organization: TEC-DATA CORE ENGINEERING TEAM - Network name: Naqashband - Allocated block: 119.73.112.0/20 - ASN: AS138655 (https://ipdebrief.com/asn/138655) - Regional registry: APNIC ## Location - City: Faisalabad - Region: Punjab - Country: Pakistan - Time zone: — ## Network classification - Infrastructure type: — - Datacenter / hosting: no - Residential: no - Mobile: no - Anycast: no - Tor exit node: no - VPN: no - Proxy: no ## Risk assessment - Assessment: Moderate Risk (40/100) - Blocklist listings: 0 - Suspicious activity indicators: no - Spam source: no ## Reverse DNS - static-host119-73-116-224.link.net.pk - Forward-confirmed: yes ## Analyst narrative \# IP Intelligence Briefing: 119.73.116.224 \## Executive Summary IP address 119.73.116.224 presents a **MODERATE RISK** profile (Risk Score: 40) with no active threat indicators. The IP belongs to the Naqashband network owned by TEC-DATA CORE ENGINEERING TEAM and is geolocated to Faisalabad, Pakistan. The subnet shows low abuse density (0.0), with most neighbors classified as low risk. \--- \## Infrastructure Profile | Attribute | Value | |-----------|-------| | **IP Address** | 119.73.116.224/32 | | **ASN** | 138655 | | **Organization** | TEC-DATA CORE ENGINEERING TEAM | | **Netname** | Naqashband | | **CIDR Block** | 119.73.112.0/20 | | **RIR** | APNIC | | **Country** | Pakistan (PK) | | **City/Region** | Faisalabad, Punjab | | **Coordinates** | 31.37°N, 73.03°E | \--- \## Network Classification & Services \- **Network Role:** Firewalled / No Services \- **Cloud/CDN/VPN:** No \- **Proxy/Tor/Hosting:** No \- **Open Ports:** None detected \- **TLS Certificate:** None \- **HTTP Banner:** None \- **DNS Records:** 1 PTR hostname (static-host119-73-116-224.link.net.pk) \- **Email Authentication:** No SPF or DMARC records configured \--- \## Threat Intelligence Assessment **Risk Indicators:** \- Risk Score: **40/100** (Moderate Risk) \- Abuse Confidence: Not available \- Blacklist Count: **0** \- DNSBL Listed: **2 of 8** lists \- Known Campaigns: None \- Tor Exit Node: No \- Known Attacker: No \- Spam Source: No **Control Plane Analysis:** \- Operator Score: 0.2609 (Basic) \- Route Stability: False \- RPKI State: Not available \- DNSSEC Valid: Yes \--- \## Neighborhood Analysis (119.73.116.0/24) The target IP resides in a /24 subnet containing **33 neighbor IPs**: \- **High Risk:** 0 \- **Medium Risk:** 6 IPs (Risk Score 25-40) \- **Low Risk:** 27 IPs **Notable Neighbors:** \- 119.73.116.8, 119.73.116.135, 119.73.116.149, 119.73.116.166, 119.73.116.167, 119.73.116.200 (Risk Score: 40) \- 119.73.116.33, 119.73.116.38, 119.73.116.175, 119.73.116.242 (Risk Score: 25) **Subnet Abuse Density:** 0.0 \--- \## Relationship Graph The IP has **4 relationships**: \- **Same Network:** Naqashband (2 occurrences) \- **DNS Association:** static-host119-73-116-224.link.net.pk (2 occurrences) No organizational, hostname, or certificate relationships detected beyond the immediate network and DNS associations. \--- \## Historical Observations **Total Observations:** 12 **Most Recent Signals (2026-07-27):** \- **Geolocation:** Faisalabad, Punjab, Pakistan (Confidence: 70%) \- **Operator Score:** Basic (0.2609) (Confidence: 60%) \- **Ownership:** TEC-DATA CORE ENGINEERING TEAM (Confidence: 90-95%) \- **Network Registration:** 119.73.112.0/20 via APNIC (Confidence: 90-95%) **Temporal Analysis:** \- Ownership Changes: 0 \- Threat Persistence Days: 0 \- Threat Observation Count: 0 \- Persistently Malicious: No \--- \## Recommended Actions Based on the moderate risk profile and absence of active threat indicators: **Firewall Recommendations:** \`\`\`bash \# iptables iptables -A INPUT -s 119.73.116.224 -j DROP \# nftables nft add rule inet filter input ip saddr 119.73.116.224 drop \# nginx deny 119.73.116.224; \# pfSense 119.73.116.224/32 \# Cloudflare WAF { "description": "Block 119.73.116.224 — IPDebrief risk score 40", "action": "block", "filter": {"expression": "ip.src eq 119.73.116.224"} } \# AWS WAF { "Addresses": \["119.73.116.224/32"\], "Description": "IPDebrief risk 40" } \`\`\` \--- \## Assessment & Recommendations **Current Status:** Moderate Risk **Key Findings:** 1. The IP has no known malicious indicators but is flagged on 2 DNSBL lists 2. No active services or open ports detected (firewalled configuration) 3. Subnet abuse density is minimal (0.0) 4. Ownership and geolocation are stable with no recent changes 5. No threat campaigns or correlated IPs identified **SOC Action:** \- Implement blocking rules as a precautionary measure \- Monitor for any changes in network activity \- No immediate escalation required given the absence of active threat indicators \- Consider whitelist evaluation if legitimate business traffic is expected from from the Naqashband network range. \--- \## Final Assessment The IP address 119.73.116.224 maintains a **MODERATE RISK** classification with no evidence of active malicious behavior. The absence of open services, combined with zero threat observations and minimal subnet abuse density, supports a **DEFENSIVE MONITORING** posture rather than immediate aggressive blocking. **Priority Levels:** \- **Immediate Action:** Monitor for activity changes \- **Short-term:** Evaluate whitelist requirements if business traffic exists \- **Long-term:** Maintain current filtering posture **Conclusion:** This IP represents a low-severity concern that may warrant firewall blocking as a precautionary measure based on its DNSBL presence and moderate risk score. However, the lack of active threat indicators, zero known campaigns, and stable network ownership suggest limited malicious intent. SOC teams should correlate with local traffic patterns before implementing blocking rules. \--- *Intelligence Report Generated: IPDebrief Platform* *Data Sources: MaxMind GeoIP2, APNIC RIR Database, DNSBL Aggregates, Historical Traffic Correlation* ## Nearby addresses - 119.73.116.8 (https://ipdebrief.com/119.73.116.8) - 119.73.116.32 (https://ipdebrief.com/119.73.116.32) - 119.73.116.33 (https://ipdebrief.com/119.73.116.33) - 119.73.116.38 (https://ipdebrief.com/119.73.116.38) - 119.73.116.44 (https://ipdebrief.com/119.73.116.44) - 119.73.116.48 (https://ipdebrief.com/119.73.116.48) - 119.73.116.51 (https://ipdebrief.com/119.73.116.51) - 119.73.116.58 (https://ipdebrief.com/119.73.116.58) - 119.73.116.62 (https://ipdebrief.com/119.73.116.62) - 119.73.116.75 (https://ipdebrief.com/119.73.116.75) - 119.73.116.94 (https://ipdebrief.com/119.73.116.94) - 119.73.116.102 (https://ipdebrief.com/119.73.116.102) --- Source: IPDebrief, "119.73.116.224 IP intelligence", https://ipdebrief.com/119.73.116.224, updated 2026-10-06. Assessments are probabilistic.