fastly.net CDN Detection: Possible Fastly Usage

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

Checked At: 10/2/2026, 06:57:11

Likely using Fastly

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

fastly.netHTTP Status 200 10/2/2026, 06:57:11

Overall Confidence

65%Evidence strength

Based on the independent evidence matched in this detection

Node Distribution

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: 10/2/2026, 06:57:11

10:57:11 PM

CNAME

CNAME: prod.www-fastly-com.map.fastly.net

Fastly

Unknown

10:57:11 PM

HTTP

header: x-served-by

Fastly

Strong

10:57:24 PM

HTTP

header: x-served-by

Fastly

Strong

10:57:24 PM

HTTP

header: x-served-by

Fastly

Strong

10:57:24 PM

CNAME

CNAME: prod.www-fastly-com.map.fastly.net

Fastly

Unknown

Show 8 more evidence items

10:57:25 PM

HTTP

header: x-served-by

Fastly

Strong

10:57:25 PM

CNAME

CNAME: prod.www-fastly-com.map.fastly.net

Fastly

Unknown

10:57:25 PM

HTTP

header: x-served-by

Fastly

Strong

10:57:25 PM

CNAME

CNAME: prod.www-fastly-com.map.fastly.net

Fastly

Unknown

10:57:28 PM

HTTP

header: x-served-by

Fastly

Strong

10:57:28 PM

CNAME

CNAME: prod.www-fastly-com.map.fastly.net

Fastly

Unknown

10:57:30 PM

CNAME

CNAME: prod.www-fastly-com.map.fastly.net

Fastly

Unknown

10:57:30 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

Region	Carrier	Resolved IP	CDN Provider	ASN	Location	TTL	Confidence	TTFB
Northern China	中国电信	146.75.113.57/32	Fastly	-	中国北京市	-	65%	1847ms
Central node	-	151.101.129.57/32	Fastly	-	-	963s	65%	-
East Asia	Overseas	151.101.77.57/32	Fastly	-	中国香港特别行政区香港	-	65%	189ms
Western North America	Overseas	151.101.129.57/32	Fastly	-	美国圣何塞	-	65%	595ms
Eastern North America	Overseas	2a04:4e42:61::313/128	Fastly	-	美国波士顿	-	65%	835ms
Southern China	BGP多线	199.232.161.57/32	Fastly	-	中国广州市	-	65%	4159ms
Southwestern China	中国电信	2a04:4e42:8c::313/128	Fastly	-	中国昆明市	-	65%	7163ms

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.

FastlyPrimary candidate

Confidence 65%