IPDebrief

23.40.64.116

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.

The profile classified 23.40.64.116 as a CDN node within Akamai Technologies, Inc. infrastructure (AS20940). Observations indicated a Low Risk reputation with a risk score of 25 and zero blacklist entries. Direct threat indicators were absent, with no classification as a known attacker, spam source, or Tor exit node. Geolocation data listed New York, US, yet validation measurements contradicted this location, showing an RTT of 24ms against a calculated minimum of 152.5ms for the reported distance. Behavioral analysis recorded zero honeypot hits or WAF violations. While the immediate subnet classification remained mostly clean with five threat siblings among 46 active peers, the overall data confidence remained very low due to signal contradictions. The recommendation was to monitor the endpoint as severity remained low but contradictions persisted.

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

🌍 Geolocation

CountryπŸ‡ΊπŸ‡Έ United States
RegionUS-NY
CityNew York
Timezoneβ€”
Latitudeβ€”
Longitudeβ€”

🏒 Ownership & Registration

OrganizationAkamai Technologies, Inc.
ASNAS20940
Network NameAKAMAI
CIDR Block23.32.0.0/11
RIRARIN
CountryUnited States
Abuse ContactAvailable via RDAP

🌐 DNS Intelligence

PTRlo1.r05.spine03.iad03.fab.netarch.akamai.com
Forward ConfirmedNo β€” PTR hostname does not resolve back to this IP (weak signal)
Forward Hostnameslo1.r05.spine03.iad03.fab.netarch.akamai.com

πŸ” DNS Hygiene

Hygiene Score40% (Fair)
SPF2/2 domains
DMARC2/2 domains
FCrDNSNot verified
DNSSECNot signed
CAANot configured
Domains Checked2 domains

☁️ 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
37%
26
routing
13%
11
services
19%
22
ownership
27%
23
reputation
22%
14
geolocation
37%
26
Overall26%1022
Coverage: 5/6 dimensions Β· Data sufficiency: partial
Data CoherenceMostly Consistent (80%) β€” 1 contradiction(s)
AttributionLow (35%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid
⚠ Claimed geolocation contradicts RTT physics measurement

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-09-05 12:02:54 UTC
Last Seen2026-09-25 12:28:11 UTC
Profile Built2026-09-25 12:42:43 UTC
Data FreshnessLive
Signal Types24
Total Observations43
πŸ” 24 signal types Β· 43 observations collected
This report is generated from 24+ 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.