39.34.166.56
IP 39.34.166.56 was assessed as Moderate Risk with a reputation score of 40. Ownership records identified the address under ASN 132165 (Munir Ahmed) within the PTCLBB-PK block 39.32.0.0/11 under APNIC. Geolocation data exhibited inconsistency, with three sources placing the host in Boston, US, while ownership data indicated a Pakistan origin; geo consensus was false. Threat indicators did not classify the IP as a known attacker, spam source, or Tor exit, but the address was listed on two DNSBLs out of eight total lists. Network analysis detected no open ports or active services, resulting in a firewalled status. DNS records lacked reverse resolution and did not contain SPF or DMARC authentication. Route stability was not confirmed over the 30-day observation period.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | Munir Ahmed |
| ASN | AS132165 |
| Network Name | PTCLBB-PK |
| CIDR Block | 39.32.0.0/11 |
| RIR | APNIC |
| Country | PK |
| Abuse Contact | Available via RDAP |
🌐 DNS Intelligence
| PTR Record | No PTR |
| Forward Confirmed | No — PTR hostname does not resolve back to this IP (weak signal) |
🔐 DNS Hygiene
| Hygiene Score | 20% (Poor) |
| SPF | Not configured |
| DMARC | Not configured |
| FCrDNS | Not verified |
| DNSSEC | Valid |
| CAA | Not configured |
☁️ 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 | AS132165 |
| Network Prefix | 39.34.166.0/24 |
| Route mapping | Found |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 17% | 2 | 3 |
| routing | 8% | 1 | 1 |
| services | 12% | 2 | 2 |
| ownership | 17% | 2 | 3 |
| reputation | 8% | 1 | 2 |
| geolocation | 8% | 1 | 1 |
| Overall | 12% | 9 | 12 |
| Data Coherence | Mostly Consistent (80%) — 1 contradiction(s) |
| Attribution | Low (35%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-07-02 16:28:35 UTC |
| Last Seen | 2026-08-24 15:55:36 UTC |
| Profile Built | 2026-08-29 09:36:49 UTC |
| Data Freshness | Live |
| Signal Types | 19 |
| Total Observations | 21 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 39.34.166.56
Who owns the IP address 39.34.166.56?
39.34.166.56 is registered to Munir Ahmed. The address falls within the 39.32.0.0/11 network block. Registration is held at APNIC.
Where is 39.34.166.56 located?
Geolocation data places 39.34.166.56 in Boston, US-MA, United States. The local time zone is America/New_York. IP geolocation is approximate and indicates the network's registered or routed location rather than a precise physical address.
Is 39.34.166.56 malicious or safe?
39.34.166.56 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.