IPDebrief

2.17.101.16

IP Intelligence Dossier
Your IP: 216.73.217.34
{ } JSON ๐Ÿ”ง Full Actions API
๐Ÿค– Witness AIThis summary was generated by AI and may contain inaccuracies. Verify critical details independently.

IP address 2.17.101.16 was classified as Low Risk with a reputation score of zero. Ownership records linked the address to AS20940 (Akamai Technologies) under the AKAMAI-PA organization within the RIPE RIR. The network role was identified as a Content Delivery Network (CDN) node. Threat intelligence feeds returned no indicators, with zero blacklist entries and no known association with attacker campaigns. DNS resolution pointed to Akamai infrastructure hostnames. Geolocation data placed the resource in the Netherlands, though consensus was not reached due to conflicting country reports. Service scans detected no open ports, classifying the endpoint as firewalled with no services exposed. The surrounding subnet 2.17.101.0/24 showed zero abuse density. Due to signal contradictions regarding geolocation, the recommendation was to monitor, but the overall severity remained low.

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

๐ŸŒ Geolocation

Country๐Ÿ‡ณ๐Ÿ‡ฑ Netherlands
RegionUS-NY
CityNew York
TimezoneEurope/Amsterdam
Latitude52.13
Longitude5.29

๐Ÿข Ownership & Registration

OrganizationAKAM1-RIPE-MNT
ASNAS20940
Network NameAKAMAI-PA
CIDR Block2.17.96.0/20
RIRRIPE
CountryEU
Abuse ContactAvailable via RDAP

๐ŸŒ DNS Intelligence

PTRlo1.r07.spine02.iad05.fab.netarch.akamai.com
Forward ConfirmedNo โ€” PTR hostname does not resolve back to this IP (weak signal)
Forward Hostnameslo1.r07.spine02.iad05.fab.netarch.akamai.com

๐Ÿ” DNS Hygiene

Hygiene Score40% (Fair)
SPFPresent
DMARCPresent
FCrDNSNot verified
DNSSECNot signed
CAANot configured

โ˜๏ธ Network Classification

InfrastructureInfrastructure / Datacenter
Service PurposeFirewalled / No Services
Network TierHosting โ€” Infrastructure provider without advanced routing
CDN

๐Ÿ”Œ 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
Issued by โ€”
N/A
SANsNone
Valid Fromโ€”
Valid Untilโ€”

๐ŸŽฏ Confidence Breakdown

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

DimensionScoreSourcesObservations
threat
33%
24
routing
13%
11
services
19%
22
ownership
27%
23
reputation
13%
12
geolocation
27%
23
Overall22%1015
Coverage: 5/6 dimensions ยท Data sufficiency: partial
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

๐Ÿ“… Observation Timeline ๐Ÿ”„ Live

First Seen2026-08-29 04:54:39 UTC
Last Seen2026-09-18 22:11:10 UTC
Profile Built2026-09-18 22:18:20 UTC
Data FreshnessLive
Signal Types22
Total Observations30
๐Ÿ” 22 signal types ยท 30 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 ๐Ÿ”ง Actions API ๐Ÿ“ง Enterprise Access

โ„น๏ธ 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.