IPDebrief

23.209.170.206

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 23.209.170.206 was identified as infrastructure belonging to Akamai Technologies, Inc. (ASN 20940) within the 23.192.0.0/11 CIDR block. The address carried a Low Risk reputation score of 25 with zero blacklist entries. During the observation period from 2026-09-07 to 2026-09-17, the host presented no open ports or active services. DNS resolution returned ae23.r21.iad04.mag.netarch.akamai.com with SPF and DMARC authentication records in place.

Geolocation data indicated New York, US, but a contradiction existed between claimed location and Round-Trip Time (RTT) physics, showing a 23ms RTT against a calculated minimum of 152.5ms for the stated distance. The surrounding /24 subnet maintained a mostly clean classification with an abuse density of 0.0556, though two threat siblings were recorded. Despite the low risk classification, analysts should monitor for changes due to signal contradictions.

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.192.0.0/11
RIRARIN
CountryUnited States
Abuse ContactAvailable via RDAP

🌐 DNS Intelligence

PTRae23.r21.iad04.mag.netarch.akamai.com
Forward ConfirmedNo β€” PTR hostname does not resolve back to this IP (weak signal)
Forward Hostnamesae23.r21.iad04.mag.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
27%
23
routing
13%
11
services
19%
22
ownership
27%
23
reputation
13%
12
geolocation
33%
24
Overall22%1015
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
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-07 16:01:11 UTC
Last Seen2026-09-17 05:05:57 UTC
Profile Built2026-09-17 05:22:03 UTC
Data FreshnessLive
Signal Types23
Total Observations30
πŸ” 23 signal types Β· 30 observations collected
This report is generated from 23+ 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.