190.133.129.94📋 Copy

IP Intelligence Briefing: 190.133.129.94

Date: 2026-05-29

---

**1. Core Profile**

• Risk Score: 40 (Moderate Risk)
• Network Type: Residential DSL endpoint (Infrastructure Type: Residential)
• Location: Montevideo, Uruguay (UY) | Coordinates: -34.91, -56.19
• ASN: AS6057 (Administracion Nacional de Telecomunicaciones, UY)
• Ownership: Residential ISP dial-up connection (Anteldata.net.uy)
• Threat Indicators: No active malicious activity, no known campaigns, no spam, no Tor/VPN/proxy associations.

---

**2. Observation History**

• Activity Trends:

- No recent threat signals (0 threat observations in 30 days).

- DNSSEC and CAA validation issues detected (potential misconfigurations).

- Listed in 2 DNSBLs (out of 8 monitored lists), but no high-severity abuse.

• Geolocation Plausibility:

- Geo-consensus: Plausible (matches ISP-reported location).

- No RTT anomalies or probe inconsistencies.

---

**3. Network Relationships**

• Subnet: 190.133.0.0/16 (Shared with 65,536 IPs).
• Key Associations:

- DNS hostname: `r190-133-129-94.dialup.adsl.anteldata.net.uy`

- No linked organizations, certificates, or hosting infrastructure.

• Control Plane:

- BGP prefix: `190.133.128.0/20` (AS6057).

- Route stability: Unstable (route changes detected in 30 days).

---

**4. Neighborhood Analysis**

• Subnet Abuse Density: 0% (clean).
• Neighbors:

- No active or threatening IPs in the /24 subnet.

- Total siblings: 1 (itself).

---

**5. Security Recommendations**

• Firewall Actions:

- Block via:

- `iptables -A INPUT -s 190.133.129.94 -j DROP`

- `nft add rule inet filter input ip saddr 190.133.129.94 drop`

- Cloudflare/WAF rules (see tool response).

• Monitoring:

- Track DNSBL listings and network stability.

- Monitor for unexpected traffic spikes or configuration changes.

---

**6. Summary**

Verdict: Low to moderate risk residential endpoint. No immediate threat, but DNS misconfigurations and ISP dial-up associations warrant cautious monitoring. Block if unnecessary, but prioritize based on contextual relevance (e.g., internal network access).

Next Steps:

• Validate DNSSEC/CAA issues with ISP.
• Monitor for subnet-wide anomalies.
• Review DNSBL listings for potential spam/abuse patterns.

This summary was generated by AI and may contain inaccuracies. Verify critical details independently.