IP Intelligence Briefing: 121.73.162.230
Date: 2026-06-17
---
**1. IP Profile**
- Risk Score: Moderate (55/100)
- Network Provider: TelstraClear (AS4768)
- Geolocation: Residential endpoint in Te Kuiti, Waikato Region, New Zealand (NZ).
- Network Role: Residential endpoint (not cloud, CDN, or infrastructure).
- Threat Indicators: No direct malicious activity detected.
---
**2. Observation History**
- Latest Activity: June 2026 (geo validation, DNSBL listings, subnet analysis).
- Geo Validation: Plausible NZ location with 600km accuracy radius.
- DNSSEC: Validated, but 3 DNSBL listings (potential spam/abuse risk).
- Subnet Analysis:
- 121.73.162.0/24 subnet has 41% abuse density (0.412).
- 7 high-risk neighbors (scores β₯80) and 9 medium-risk (scores 40β55).
---
**3. Relationships & Network Context**
- Network Owner: TelstraClear Technical Contact (AS4768).
- Subnet: 121.73.162.0/24 (17 total IPs, 6 malicious).
- Key Neighbors:
- 121.73.162.77, 121.73.162.99, 121.73.162.145, and 121.73.162.248 (high-risk).
- 121.73.162.50 and 121.73.162.220 (low-risk).
---
**4. Threat Assessment**
- Direct Threat: No confirmed malicious activity (no malware, phishing, or campaign indicators).
- Indirect Risk:
- Subnet has moderate abuse density (0.412).
- 3 DNSBL listings suggest potential spam or abuse.
- High-risk neighbors may indicate a compromised network segment.
---
**5. Recommended Actions**
1. Monitor Subnet: Track high-risk neighbors (e.g., 121.73.162.77, 121.73.162.99) for unusual traffic.
2. Check DNSBLs: Investigate the 3 DNSBL listings (e.g., Spamhaus, Barracuda).
3. Network Segmentation: Isolate residential endpoints to mitigate potential lateral movement.
4. Geolocation Verification: Confirm if the IP is a legitimate NZ residential user or a spoofed location.
---
Conclusion: This IP is a residential endpoint with moderate risk due to its subnetβs abuse density and DNSBL associations. While no direct threats are detected, the network context warrants closer monitoring.
Tools Used: `ipdebrief_profile`, `ipdebrief_history`, `ipdebrief_relationships`, `ipdebrief_neighbors`.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
π’ Ownership & Registration
| Organization | TelstraClear Technical Contact |
| ASN | AS4768 |
| Network Name | TCL-WGTNDSL-NZ |
| CIDR Block | 121.73.160.0/19 |
| RIR | APNIC |
| Country | NZ |
| 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 | Residential |
| Service Purpose | Web Server |
| Network Tier | End-User β Residential ISP endpoint |
π Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| 80 | http | tcp | β |
| 443 | https | tcp | β |
| 22 | ssh | tcp | |
| Closed Ports | 25, 3389, 8080, 8443 (3 open / 7 scanned) | ||
| Server | β |
| HTTP Title | β |
| SSH Version | SSH-2.0-dropbear $?????.?? ?yh??mcurve25519-sha256@libssh.org,diffie-hellman-group14-sha1,diffie-he |
π 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 | 40% | 2 | 3 |
| routing | 13% | 1 | 1 |
| services | 29% | 2 | 3 |
| ownership | 19% | 2 | 2 |
| reputation | 17% | 1 | 2 |
| geolocation | 32% | 2 | 3 |
| Overall | 25% | 10 | 14 |
| Data Coherence | Mostly Consistent (80%) β 1 contradiction(s) |
| Attribution | Low (35%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
π Observation Timeline π Live
| First Seen | 2026-05-07 23:03:36 UTC |
| Last Seen | 2026-06-22 12:01:07 UTC |
| Profile Built | 2026-06-22 12:06:39 UTC |
| Data Freshness | Live |
| Signal Types | 18 |
| Total Observations | 21 |
Full dossier details are available via our API.