200.40.75.11 is an IPv4 address operated by AS6057 - Administracion Nacional de Telecomunicaciones, UY (AS6057), with approximate network location Montevideo, Uruguay. As of November 13, 2026, IPDebrief rates it Low Risk (0/100); no anonymizing service was detected.
Witness AI IP Assessment (AI-generated)
AI-generated assessment. Verify critical details independently.
The host 200.40.75.11 was observed within the 200.40.0.0/17 block allocated to Administracion Nacional de Telecomunicaciones (AS6057) in Uruguay. The IP was geolocated to Montevideo, Uruguay, though this represents an approximate network location that may conflict with actual server positions if the address participates in an anycast deployment. The address is currently assigned to a routing operator and identified as having a "Firewalled / No Services" network role, with no confirmed cloud, CDN, proxy, VPN, or hosting attributes. DNS hygiene assessments yielded no results, returning an unknown status for CAA and DNSSEC checks and not checking SPF and DMARC records; these missing evaluations do not establish poor IP hygiene. TLS probes returned no endpoints or certificate findings, indicating either the absence of TLS termination at this host or a lack of probing data. The assigned risk score is zero. Due to the limited service observations and unverified anycast status, monitoring or corroboration is recommended rather than assuming the host is benign solely based on the current risk assessment.
🏢 Ownership & Registration
| Registered holder | Administracion Nacional de Telecomunicaciones |
| ASN | AS6057 |
| Network Name | 200.40.0.0 - 200.40.127.255 |
| CIDR Block | 200.40.0.0/17 |
| RIR | LACNIC |
| Network registration country | UY |
| Routing operator | AS6057 - Administracion Nacional de Telecomunicaciones, UY |
| 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 Posture
Results describe the queried names. SPF, DMARC and CAA are domain policies, not requirements for every IP. DNSSEC here describes reverse DNS; inconclusive validation does not mean unsigned.
Not assessed: 0 conclusive IP DNS checks.
| caa | Unknown / lookup inconclusive net.uy |
| spf | Not checked |
| dmarc | Not checked |
| dnssec | Unknown / lookup inconclusive 11.75.40.200.in-addr.arpa |
| fcrDns | Not checked |
☁️ 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 | — |
🛡️ Public Network Snapshot
| Origin ASN | AS6057 |
| Network Prefix | 200.40.64.0/20 |
| Route mapping | Found |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 25% | 1 | 1 |
| routing | 25% | 1 | 1 |
| services | 25% | 1 | 1 |
| ownership | 25% | 1 | 2 |
| reputation | 0% | 0 | 0 |
| geolocation | 25% | 1 | 1 |
| Overall | 20% | 5 | 6 |
| Data Coherence | Consistent (100%) |
| Attribution | Low (35%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Recent
| First Seen | 2026-11-10 22:34:42 UTC |
| Last Seen | 2026-11-14 12:48:19 UTC |
| Profile Built | 2026-11-13 09:17:16 UTC |
| Data Freshness | Recent |
| Signal Types | 16 |
| Total Observations | 16 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 200.40.75.11
Who owns the IP address 200.40.75.11?
200.40.75.11 is registered to Administracion Nacional de Telecomunicaciones. The address falls within the 200.40.0.0/17 network block. Registration is held at LACNIC.
Where is 200.40.75.11 located?
Geolocation data places 200.40.75.11 in Montevideo, Montevideo Department, Uruguay. IP geolocation is approximate, not a precise physical address. Registration country and certificate organization addresses do not establish service location.
Is 200.40.75.11 malicious or safe?
200.40.75.11 currently carries a low risk assessment, meaning no significant threat indicators have been observed. This assessment is generated from continuously collected signals and can change over time.