Open CDN detection tool

cdn.steamstatic.com CDN Detection: Possible Fastly Usage

CNAME, HTTP header, and ASN signals indicate that cdn.steamstatic.com may be using Fastly, with 65% confidence. Review the evidence and latest check time.

Checked At: 11/11/2026, 20:09:04

Likely using Fastly

This result is based on public DNS, HTTP, and network signals and may update with later observations.

cdn.steamstatic.comHTTP Status 200 11/11/2026, 20:09:04

Overall Confidence

65%Evidence strength

Based on the independent evidence matched in this detection

Provider evidence strength

Current snapshot
Fastly 65%

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/11/2026, 20:09:04
12:09:04 PM
CNAME
CNAME: shared.valve.map.fastly.net
Fastly

Unknown

12:09:04 PM
HTTP
header: x-served-by
Fastly

Strong

12:10:37 PM
HTTP
header: x-served-by
Fastly

Strong

12:10:37 PM
CNAME
CNAME: shared.valve.map.fastly.net
Fastly

Unknown

12:10:38 PM
HTTP
header: x-served-by
Fastly

Strong

Show 9 more evidence items
12:10:38 PM
CNAME
CNAME: shared.valve.map.fastly.net
Fastly

Unknown

12:10:38 PM
HTTP
header: x-served-by
Fastly

Strong

12:10:38 PM
CNAME
CNAME: shared.valve.map.fastly.net
Fastly

Unknown

12:10:38 PM
HTTP
header: x-served-by
Fastly

Strong

12:10:38 PM
CNAME
CNAME: shared.valve.map.fastly.net
Fastly

Unknown

12:10:39 PM
CNAME
CNAME: shared.valve.map.fastly.net
Fastly

Unknown

12:10:39 PM
HTTP
header: x-served-by
Fastly

Strong

12:10:41 PM
CNAME
CNAME: shared.valve.map.fastly.net
Fastly

Unknown

12:10:41 PM
HTTP
header: x-served-by
Fastly

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 ChinaChina Telecom199.232.163.52/32Fastly-中国 北京市-
65%
1167ms
Central node-199.232.211.52/32Fastly--16s
65%
-
East AsiaOverseas140.248.167.52/32Fastly-中国香港特别行政区 香港-
65%
24ms
Eastern North AmericaOverseas199.232.135.52/32Fastly-美国 波士顿-
65%
21ms
North America-199.232.215.52/32Fastly-美国 洛杉矶-
65%
37ms
Southern ChinaBGP multi-line146.75.115.52/32Fastly-中国 广州市-
65%
1571ms
Southwestern ChinaChina Telecom146.75.115.52/32Fastly-中国 昆明市-
65%
2361ms
Routing prefixes and network organizations describe IP ownership, not exclusive CDN ranges. Results vary by region and time.7 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.
FastlyPrimary candidate

Confidence 65%

CNAME: shared.valve.map.fastly.net
header: x-served-by
CNAME: shared.valve.map.fastly.net
header: x-served-by
CNAME: shared.valve.map.fastly.net
header: x-served-by
CNAME: shared.valve.map.fastly.net
header: x-served-by
CNAME: shared.valve.map.fastly.net
header: x-served-by
CNAME: shared.valve.map.fastly.net
header: x-served-by
CNAME: shared.valve.map.fastly.net
header: x-served-by

Methodology and limitations

The identification result is determined by cross-referencing public DNS, HTTP response headers, and ASN signals; confidence indicates the strength of the evidence and does not represent statistical accuracy.