IP Intelligence Briefing: 102.64.46.207
Date: 2026-06-06
---
**1. Core Profile**
- Risk Score: 70/100 (High Risk)
- Ownership: Registered to Jacobus De Beer (ASN 327991) under Megasurf Wireless Internet CC (South Africa).
- Geolocation:
- City: Vanderbijlpark, Gauteng, South Africa (ZA)
- Coordinates: Approximate (latitude -30.56, longitude 22.94)
- Timezone: Africa/Johannesburg
- Network Role: Firewalled / No Services (no open ports or TLS certs detected).
- DNS:
- PTR hostname: ms-46-207.megasurf.co.za
- SPF/DKIM: Validated (SPF: true, DMARC: true).
---
**2. Threat Indicators**
- No direct malicious activity: No indicators of spam, attacks, or known campaigns.
- DNS Security: DNSSEC valid, no CAA records.
- Blacklists: Not listed in major DNSBLs (4/8 lists checked).
---
**3. Network Context**
- Subnet: 102.64.46.0/24 (Megasurf Wireless)
- Abuse Density: 19% (moderate risk).
- Neighbors:
- High-risk neighbors: 8 IPs (avg. score 55).
- Low-risk neighbors: 24 IPs (avg. score 40).
- Notable: 102.64.46.30 (score 80), 102.64.46.56 (score 40).
---
**4. Behavioral & Historical Data**
- Observation History (30 days):
- Stable ownership (no recent changes).
- Geolocation consistency with South Africa.
- Routing stability (BGP prefix 102.64.40.0/21).
- Anomalies:
- Inconsistent geolocation coordinates across sources.
- No signs of honeypot activity or enumeration.
---
**5. Recommended Actions**
- Firewall Blocking:
```bash
iptables -A INPUT -s 102.64.46.207 -j DROP
nft add rule inet filter input ip saddr 102.64.46.207 drop
```
- Monitoring:
- Increase logging verbosity for traffic from this IP.
- Review DNS activity (ms-46-207.megasurf.co.za) for anomalies.
- Network Segmentation:
- Monitor high-risk neighbors (e.g., 102.64.46.30, 102.64.46.56).
---
**6. Summary**
The IP 102.64.46.207 is part of a South African ISP network (Megasurf) with a moderate risk score. While no direct malicious activity is detected, its association with a high-risk subnet and inconsistent geolocation data warrant closer scrutiny. Block the IP and monitor related network segments for potential lateral movement or abuse.
Threat Level: Moderate (High Risk Score + Subnet Abuse)
Next Steps: Confirm ownership, validate DNS activity, and enforce network segmentation.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
π’ Ownership & Registration
| Organization | Jacobus De Beer |
| ASN | AS327991 |
| Network Name | 102.64.46.0 - 102.64.46.255 |
| CIDR Block | 102.64.46.0/24 |
| RIR | AFRINIC |
| Country | ZA |
| Abuse Contact | β |
π DNS Intelligence
| PTR | ms-46-207.megasurf.co.za |
| Forward Confirmed | Yes β FCrDNS verified |
| Forward Hostnames | ms-46-207.megasurf.co.za |
π DNS Hygiene
| Hygiene Score | 80% (Excellent) |
| SPF | Present |
| DMARC | Present |
| FCrDNS | 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 | β |
π― Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 30% | 2 | 4 |
| routing | 19% | 1 | 2 |
| services | 15% | 2 | 2 |
| ownership | 19% | 2 | 2 |
| reputation | 28% | 1 | 3 |
| geolocation | 19% | 2 | 2 |
| Overall | 22% | 10 | 15 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (70%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
π Observation Timeline π Live
| First Seen | 2026-05-12 15:46:08 UTC |
| Last Seen | 2026-06-26 17:43:55 UTC |
| Profile Built | 2026-06-26 17:56:10 UTC |
| Data Freshness | Live |
| Signal Types | 19 |
| Total Observations | 23 |
Full dossier details are available via our API.