IP Intelligence Briefing: 102.66.144.172
Date: 2026-06-13
---
**1. Risk Profile**
- Overall Risk Score: Low (25/100)
- Provider/Authority Scores: Unavailable (ownership data missing)
- Network Classification: Firewalled / No Services (no open ports or active services detected)
- Threat Indicators: None detected (no malware, spam, or known attacker associations).
---
**2. Geolocation & Ownership**
- Geolocation: No data available (country, city, ISP, or coordinates).
- Ownership:
- ASN: 328471 (HERO TELECOMS (PTY) LTD, South Africa)
- Subnet: 102.66.144.0/24 (allocated to HERO TELECOMS, 2019-04-19).
- No abuse contact or registration details provided.
---
**3. Threat History**
- Observations (Last 30 Days):
- DNSBL Listings: Listed in 1 DNSBL (confidence 0.85).
- DNSSEC Valid: Yes (valid DNSSEC for reverse lookup).
- Routing Stability: Route changes: 0 (stable).
- Geolocation Plausibility: No geo-validation data (possible spoofed IP).
- Trend: No persistent malicious activity detected.
---
**4. Network Relationships**
- Connected Entities:
- No linked hostnames, certificates, or organizations.
- No correlated IPs or campaigns.
- Subnet Abuse Density: 0% (clean subnet).
---
**5. Neighboring IPs**
- Subnet: 102.66.144.0/24 (3 IPs total).
- Neighbors:
- 102.66.144.61: Risk score 25 (same as target).
- 102.66.144.93: No risk data available.
- Abuse Density: 0% (no malicious activity in subnet).
---
**6. Actionable Recommendations**
1. Monitor & Block:
- Block the IP in firewalls (iptables/nftables) due to sparse ownership data and potential spoofing risks.
- Add to WAF rules (Cloudflare/AWS) to mitigate potential reconnaissance.
2. Investigate Ownership:
- Verify HERO TELECOMS (PTY) LTDβs compliance practices, as ownership details are incomplete.
3. Check for Spoofing:
- Validate geolocation and DNSSEC data with additional probes due to lack of geo-consensus.
4. Subnet Analysis:
- Monitor neighboring IPs (e.g., 102.66.144.61) for anomalies, as they share the same risk score.
---
Conclusion: This IP appears benign with low risk, but incomplete ownership and geolocation data raise red flags. Its firewalled status and lack of services suggest it may be a protected asset or a honeypot. Further investigation into ownership and network behavior is recommended.
Tools Used: `ipdebrief_profile`, `ipdebrief_history`, `ipdebrief_neighbors`, `ipdebrief_relationships`.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
π’ Ownership & Registration
| Organization | HERO TELECOMS (PTY) LTD |
| ASN | AS328471 |
| Network Name | ORG-HP1-AFRINIC |
| CIDR Block | 102.66.0.0/16 |
| RIR | AFRINIC |
| Country | ZA |
| Abuse Contact | β |
π 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 | |||
| Server | β |
| HTTP Title | β |
π TLS Certificate
| SANs | None |
| Valid From | β |
| Valid Until | β |
π― Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 35% | 2 | 2 |
| routing | 25% | 1 | 1 |
| services | 25% | 1 | 1 |
| ownership | 0% | 0 | 0 |
| reputation | 25% | 1 | 1 |
| geolocation | 0% | 0 | 0 |
| Overall | 18% | 5 | 5 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
π Observation Timeline π Live
| First Seen | 2026-06-06 07:26:11 UTC |
| Last Seen | 2026-06-13 10:36:50 UTC |
| Profile Built | 2026-06-13 10:44:46 UTC |
| Data Freshness | Live |
| Signal Types | 14 |
| Total Observations | 14 |
Full dossier details are available via our API.