IPDebrief

2a02:2f01:6011:cf00:b942:e4fe:c73:b0b4

IP Intelligence Dossier
Your IP: 216.73.217.75

2a02:2f01:6011:cf00:b942:e4fe:c73:b0b4 is an IPv6 address announced by AS8708, with approximate network location Râmnicu Vâlcea, Romania. It belongs to a mobile network. As of November 6, 2026, IPDebrief rates it Low Risk (0/100); no anonymizing service was detected.

{ } JSON

🌍 Geolocation

Country🇷🇴 Romania
Location scopeApproximate network location. Distributed and anycast services can vary by observation point.
Anycast classificationUnverified (not proof of unicast)
RegionVâlcea County
CityRâmnicu Vâlcea
TimezoneEurope/Bucharest
Latitude45.10
Longitude24.36

🏢 Ownership & Registration

Registered holderAS8708-MNT
ASNAS8708
Network NameRO-RDS-20101118
CIDR Block—
RIRARIN
Network registration countryRO
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.

spfNot checked
dmarcNot checked
fcrDnsNot checked
dnssecNot checked
caaNot checked

☁️ Network Classification

InfrastructureMobile
Service PurposeFirewalled / No Services
Network TierUnknown — Insufficient routing data to classify
Mobile

🔌 Services & Open Ports

PortServiceProtocolBanner
No open ports detected
Closed Ports22, 25, 80, 443, 3389, 8080, 8443 (0 open / 7 scanned)
Server—
HTTP Title—

🔐 TLS Certificate

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

🛡️ Public Network Snapshot

Origin ASNAS8708
Network Prefix2a02:2f00::/28
Route mappingFound

🎯 Confidence Breakdown

Per-dimension confidence scores based on source diversity and data freshness

DimensionScoreSourcesObservations
threat
32%
13
routing
20%
11
services
20%
11
ownership
40%
23
reputation
32%
13
geolocation
20%
11
Overall27%712
Coverage: 6/6 dimensions · Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

📅 Observation Timeline 🔄 Live

First Seen2026-11-05 14:56:23 UTC
Last Seen2026-11-06 16:55:51 UTC
Profile Built2026-11-06 17:02:54 UTC
Data FreshnessLive
Signal Types16
Total Observations18
🔍 16 signal types · 18 observations collected
This report is generated from 16+ 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 2a02:2f01:6011:cf00:b942:e4fe:c73:b0b4

Who owns the IP address 2a02:2f01:6011:cf00:b942:e4fe:c73:b0b4?

2a02:2f01:6011:cf00:b942:e4fe:c73:b0b4 is registered to AS8708-MNT. Registration is held at ARIN.

Where is 2a02:2f01:6011:cf00:b942:e4fe:c73:b0b4 located?

Geolocation data places 2a02:2f01:6011:cf00:b942:e4fe:c73:b0b4 in Râmnicu Vâlcea, Vâlcea County, Romania. The local time zone is Europe/Bucharest. IP geolocation is approximate, not a precise physical address. Registration country and certificate organization addresses do not establish service location.

Is 2a02:2f01:6011:cf00:b942:e4fe:c73:b0b4 malicious or safe?

2a02:2f01:6011:cf00:b942:e4fe:c73:b0b4 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.

Is 2a02:2f01:6011:cf00:b942:e4fe:c73:b0b4 a VPN, proxy, or data center address?

2a02:2f01:6011:cf00:b942:e4fe:c73:b0b4 is classified as a mobile network based on network ownership and behavioural analysis.

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