IPDebrief

80.56.164.70

IP Intelligence Dossier
Your IP: 216.73.217.75

80.56.164.70 is an IPv4 address operated by TNF-AS - Vodafone Libertel B.V., NL (AS33915), with approximate network location New York, Netherlands. Its reverse DNS name is f164070.upc-f.chello.nl. As of November 13, 2026, IPDebrief rates it Low Risk (0/100); no anonymizing service was detected.

{ } JSON

🌍 Geolocation

Country🇺🇸 Netherlands
Location scopeApproximate network location. Distributed and anycast services can vary by observation point.
Anycast classificationUnverified (not proof of unicast)
RegionNorth Holland
CityNew York
Timezone—
Latitude52.23
Longitude5.15

🏢 Ownership & Registration

Registered holderZIGGO-SERVICES-MNT
ASNAS33915
Network NameUPC-NL
CIDR Block80.56.158.0/23
RIRRIPE
Network registration countryNL
Routing operatorTNF-AS - Vodafone Libertel B.V., NL
Abuse ContactAvailable via RDAP

🌐 DNS Intelligence

PTRf164070.upc-f.chello.nl
Forward ConfirmedYes — FCrDNS verified
Forward Hostnamesf164070.upc-f.chello.nl

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.

Partial coverage: 1 conclusive IP DNS checks.

caaPresent / verified
chello.nl
spfNot found at queried name
f164070.upc-f.chello.nl
dmarcNot found at queried name
_dmarc.f164070.upc-f.chello.nl
dnssecUnknown / lookup inconclusive
70.164.56.80.in-addr.arpa
fcrDnsPresent / verified
f164070.upc-f.chello.nl

☁️ Network Classification

InfrastructureUnknown
Service PurposeFirewalled / No Services
Network TierTier 3 — Basic operator with some routing infrastructure
No specific classification

🔌 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 ASNAS33915
Network Prefix80.56.0.0/16
Route mappingFound

🎯 Confidence Breakdown

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

DimensionScoreSourcesObservations
threat
25%
11
routing
25%
11
services
35%
22
ownership
0%
00
reputation
0%
00
geolocation
25%
11
Overall18%55
Coverage: 4/6 dimensions · Data sufficiency: partial
Data CoherenceConsistent (100%)
AttributionLow (40%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

📅 Observation Timeline 🔄 Live

First Seen2026-07-13 15:25:18 UTC
Last Seen2026-11-13 18:33:42 UTC
Profile Built2026-11-13 18:46:04 UTC
Data FreshnessLive
Signal Types22
Total Observations33
🔍 22 signal types · 33 observations collected
This report is generated from 22+ 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 80.56.164.70

Who owns the IP address 80.56.164.70?

80.56.164.70 is registered to ZIGGO-SERVICES-MNT. The address falls within the 80.56.158.0/23 network block. Registration is held at RIPE.

Where is 80.56.164.70 located?

Geolocation data places 80.56.164.70 in New York, North Holland, Netherlands. IP geolocation is approximate, not a precise physical address. Registration country and certificate organization addresses do not establish service location.

Is 80.56.164.70 malicious or safe?

80.56.164.70 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.

What is the hostname for 80.56.164.70?

The reverse DNS (PTR) record for 80.56.164.70 is f164070.upc-f.chello.nl. This hostname is forward-confirmed, meaning it resolves back to the same address.

🏘️ Related IP Addresses

Nearby addresses in 80.56.158.0/23

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.