Open CDN detection tool

chat.deepseek.com CDN Detection: Possible Amazon CloudFront Usage

CNAME, HTTP header, and ASN signals indicate that chat.deepseek.com may be using Amazon CloudFront, with 99% confidence. Review the evidence and latest check time.

Checked At: 11/5/2026, 08:37:14

Confirmed use of Amazon CloudFront

At least two real probes from different regions and multiple independent evidence types point to this provider.

chat.deepseek.comHTTP Status 200 11/5/2026, 08:37:14

Overall Confidence

99%Evidence strength

Based on the independent evidence matched in this detection

Node Distribution

Current snapshot
Amazon CloudFront 99%

Detection Path

Complete · 5 stages

DNS Resolution
-

Complete · 6 addresses

CNAME Chain
-

Complete · 1 CNAME found

IP / ASN
-

Complete · 6 IPs, 4 ASNs

HTTP Response
-

Complete · response headers collected

Fingerprint Score
-

Complete · 4 evidence types

Evidence Timeline

Observed facts ordered by collection time

Checked At: 11/5/2026, 08:37:14
12:38:35 AM
CNAME
CNAME: d3bbv8sr76az5s.cloudfront.net
Amazon CloudFront

Unknown

12:38:35 AM
CNAME
CNAME: d3bbv8sr76az5s.cloudfront.net
Amazon CloudFront

Strong

12:38:35 AM
HTTP
header: x-amz-cf-id
Amazon CloudFront

Strong

12:38:35 AM
CNAME
CNAME: d3bbv8sr76az5s.cloudfront.net
Amazon CloudFront

Strong

12:38:35 AM
HTTP
header: x-amz-cf-id
Amazon CloudFront

Strong

Show 7 more evidence items
12:38:35 AM
CNAME
CNAME: d3bbv8sr76az5s.cloudfront.net
Amazon CloudFront

Unknown

12:38:35 AM
CNAME
CNAME: d3bbv8sr76az5s.cloudfront.net
Amazon CloudFront

Strong

12:38:35 AM
HTTP
header: x-amz-cf-id
Amazon CloudFront

Strong

12:38:35 AM
CNAME
CNAME: d3bbv8sr76az5s.cloudfront.net
Amazon CloudFront

Unknown

12:38:36 AM
CNAME
CNAME: d3bbv8sr76az5s.cloudfront.net
Amazon CloudFront

Unknown

12:38:36 AM
CNAME
CNAME: d3bbv8sr76az5s.cloudfront.net
Amazon CloudFront

Strong

12:38:36 AM
HTTP
header: x-amz-cf-id
Amazon CloudFront

Strong

Score Explanation

Evidence strength breakdown

CNAME evidence
100 / 100

CNAME target and routing-domain signals

HTTP headers
100 / 100

Response header name and value matches

This score presents evidence strength, not statistical probability. A shared ASN or cloud network cannot confirm a CDN on its own.

Node and Routing Differences

Resolution results and access signals observed by region and carrier

Collected just now
RegionCarrierResolved IPCDN ProviderASNLocationTTLConfidenceTTFB
Northern China中国电信116.205.40.114/32--中国 北京市-
0%
256ms
East AsiaOverseas3.173.21.63/32Amazon CloudFront-中国香港特别行政区 香港-
99%
21ms
North America-3.173.21.63/32Amazon CloudFront-美国 洛杉矶-
99%
35ms
Central node-3.173.21.63/32Amazon CloudFront--59s
99%
-
Southern ChinaBGP多线116.205.40.114/32--中国 广州市-
0%
178ms
Eastern North AmericaOverseas3.173.21.63/32Amazon CloudFront-美国 波士顿-
99%
281ms
Southwestern China中国电信116.205.40.114/32--中国 昆明市-
0%
376ms
Node results vary by region, carrier and time7 nodes
Detection results are inferred from public DNS and HTTP signals. Confidence reflects the strength of the matched evidence and does not imply 100% certainty.
Amazon CloudFrontPrimary candidate

Confidence 99%

CNAME: d3bbv8sr76az5s.cloudfront.net
CNAME: d3bbv8sr76az5s.cloudfront.net
header: x-amz-cf-id
CNAME: d3bbv8sr76az5s.cloudfront.net
CNAME: d3bbv8sr76az5s.cloudfront.net
header: x-amz-cf-id
CNAME: d3bbv8sr76az5s.cloudfront.net
CNAME: d3bbv8sr76az5s.cloudfront.net
header: x-amz-cf-id
CNAME: d3bbv8sr76az5s.cloudfront.net
CNAME: d3bbv8sr76az5s.cloudfront.net
header: x-amz-cf-id
View Amazon CloudFront Performance Review

Methodology and limitations

The confirmation result is based on currently published rules, multiple real Agents, multiple regions, and at least two types of independent evidence.