Your IP: 216.73.216.123
π€ Witness AIThis summary was generated by AI and may contain inaccuracies. Verify critical details independently.
IP Intelligence Briefing: 67.21.32.71
Date: 2026-06-08
---
**1. Core Profile**
- Risk Score: 25 (Low Risk)
- Ownership: H4Y Technologies LLC (ASN 397373, ARIN-regulated)
- Geolocation: Charlotte, NC, United States (35.24°N, -80.9°E)
- Network Role: Firewalled / No Services (no open ports, TLS, or HTTP services detected)
- Threat Indicators: No malicious activity, spam, or known attacker associations.
---
**2. Observation History**
- Latest Activity: Minimal risk signals (June 8, 2026).
- Ownership Stability: No changes in ownership or network configuration observed.
- Threat Persistence: No persistent malicious behavior detected.
---
**3. Relationships**
- Linked Entities:
- Subnet: `67.21.32.0/23` (HTL-33)
- Organization: H4Y Technologies LLC
- No Known Campaigns or Malware Associations.
---
**4. Neighborhood Analysis**
- Subnet: `67.21.32.0/23` (no active or malicious neighbors reported).
- Abuse Density: 0% (low risk of subnet-wide compromise).
---
**5. Additional Findings**
- DNSSEC Valid: Yes, but the IP is listed in 1 DNSBL (potential false positive or unrelated).
- Routing: Stable BGP prefix (`67.21.32.0/24`) with no recent route changes.
- Email Reputation: No SPF/DKIM records detected.
---
**6. Recommendations**
- Monitor: Track DNSBL listing for accuracy, as no malicious activity is confirmed.
- Network Segmentation: Ensure firewalled subnets (e.g., `67.21.32.0/23`) are isolated from critical assets.
- Verify Ownership: Confirm H4Y Technologies LLCβs compliance practices, given the DNSBL flag.
Conclusion: This IP poses no immediate threat. Focus on verifying the DNSBL listing and maintaining network segmentation. No urgent action required.
---
*Generated by IPDebrief threat intelligence platform.*
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
π’ Ownership & Registration
| Organization | H4Y Technologies LLC |
| ASN | AS397373 |
| Network Name | HTL-33 |
| CIDR Block | 67.21.32.0/23 |
| RIR | ARIN |
| Country | United States |
| 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 | |||
| Server | β |
| HTTP Title | β |
π TLS Certificate
No certificate
Issued by β
N/A
| SANs | None |
| Valid From | β |
| Valid Until | β |
π― Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 13% | 1 | 1 |
| routing | 13% | 1 | 1 |
| services | 13% | 1 | 1 |
| ownership | 30% | 2 | 3 |
| reputation | 0% | 0 | 0 |
| geolocation | 13% | 1 | 1 |
| Overall | 14% | 6 | 7 |
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
π Observation Timeline π Live
| First Seen | 2026-05-19 15:39:28 UTC |
| Last Seen | 2026-06-08 21:18:05 UTC |
| Profile Built | 2026-06-04 10:19:14 UTC |
| Data Freshness | Live |
| Signal Types | 9 |
| Total Observations | 9 |
π 9 signal types Β· 9 observations collected
This report is generated from 9+ independent intelligence signals including
ownership records, DNS analysis, BGP routing, TLS certificates, port scanning, threat feeds,
behavioral fingerprinting, and more.
Full dossier details are available via our API.
Full dossier details are available via our API.
βΉοΈ About This Report
All data shown is publicly available network metadata β IP addresses do not reliably identify individuals.
Assessments are probabilistic and should not be used as sole basis for access control decisions.
To report an issue or request data review, contact admin@ipdebrief.com.