IPDebrief

2800:a4:1d46:b600:70a5:5a06:9207:8f42

IP Intelligence Dossier
Your IP: 216.73.217.75

2800:a4:1d46:b600:70a5:5a06:9207:8f42 is an IPv6 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.

{ } JSON

🌍 Geolocation

Country🇺🇾 Uruguay
Location scopeApproximate network location. Distributed and anycast services can vary by observation point.
Anycast classificationUnverified (not proof of unicast)
RegionMontevideo Department
CityMontevideo
Timezone—
Latitude-34.91
Longitude-56.16

🏢 Ownership & Registration

Registered holderAdministracion Nacional de Telecomunicaciones
ASNAS6057
Network Name2800:a0:: - 2800:af:ffff:ffff:ffff:ffff:ffff:ffff
CIDR Block—
RIRARIN
Network registration countryUY
Routing operatorAS6057 - Administracion Nacional de Telecomunicaciones, UY
Abuse ContactAvailable via RDAP

🌐 DNS Intelligence

PTR RecordNo PTR
Forward ConfirmedNo — 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.

caaNot applicable
spfUnknown / lookup inconclusive
dmarcUnknown / lookup inconclusive
dnssecUnknown / lookup inconclusive
2.4.f.8.7.0.2.9.6.0.a.5.5.a.0.7.0.0.6.b.6.4.d.1.4.a.0.0.0.0.8.2.ip6.arpa
fcrDnsUnknown / lookup inconclusive

☁️ Network Classification

InfrastructureUnknown
Service PurposeFirewalled / No Services
Network TierUnknown — Insufficient routing data to classify
No specific classification

🔌 Services & Open Ports

PortServiceProtocolBanner
No open ports detected
Server—
HTTP Title—

🔐 TLS Certificate

🔒
No certificate captured; current certificate unknown
Issued by —
N/A
SANsNone
Valid From—
Valid Until—

🛡️ Public Network Snapshot

Origin ASNAS6057
Network Prefix2800:a0::/28
Route mappingFound

📅 Observation Timeline 🔄 Live

First Seen2026-11-05 21:37:53 UTC
Last Seen2026-11-08 01:55:36 UTC
Profile Built2026-11-13 08:01:38 UTC
Data FreshnessLive
Signal Types12
Total Observations13
🔍 12 signal types · 13 observations collected
This report is generated from 12+ 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.
{ } JSON API 📧 Enterprise Access

❓ Frequently Asked Questions About 2800:a4:1d46:b600:70a5:5a06:9207:8f42

Who owns the IP address 2800:a4:1d46:b600:70a5:5a06:9207:8f42?

2800:a4:1d46:b600:70a5:5a06:9207:8f42 is registered to Administracion Nacional de Telecomunicaciones. Registration is held at ARIN.

Where is 2800:a4:1d46:b600:70a5:5a06:9207:8f42 located?

Geolocation data places 2800:a4:1d46:b600:70a5:5a06:9207:8f42 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 2800:a4:1d46:b600:70a5:5a06:9207:8f42 malicious or safe?

2800:a4:1d46:b600:70a5:5a06:9207:8f42 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.

🏘️ Related IP Addresses

Browse related networks

ℹ️ 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.