bunny.net CDN Detection: Possible Bunny.net Usage
CNAME, HTTP header, and ASN signals indicate that bunny.net may be using Bunny.net, with 85% confidence. Review the evidence and latest check time.
Confirmed use of Bunny.net
At least two real probes from different regions and multiple independent evidence types point to this provider.
Overall Confidence
Based on the independent evidence matched in this detection
Provider evidence strength
Current snapshotDetection Path
Complete · 5 stages
Complete · 6 addresses
Complete · 1 CNAME found
Complete · 6 IPs, 4 ASNs
Complete · response headers collected
Complete · 4 evidence types
Evidence Timeline
Observed facts ordered by collection time
Strong
Strong
Strong
Strong
Strong
Show 16 more evidence items
Strong
Strong
Strong
Strong
Strong
Strong
Strong
Strong
Strong
Strong
Strong
Strong
Strong
Strong
Strong
Strong
Score Explanation
Evidence strength breakdown
Response header name and value matches
IP range, ASN and regional ownership signals
Node and Routing Differences
Resolution results and access signals observed by region and carrier
| Region | Carrier | Resolved IP | CDN Provider | ASN | Location | TTL | Confidence | TTFB |
|---|---|---|---|---|---|---|---|---|
| Northern China | China Telecom | 138.199.9.104 | Bunny.net | AS60068 | 中国 北京市 | - | 85% | 482ms |
| Central node | Ansheng Network Technology Co., Limited | 185.111.111.155 | Bunny.net | AS212238 | - | 26s | 85% | - |
| East Asia | CTG Server Limited | 84.17.37.214 | Bunny.net | AS60068 | 中国香港特别行政区 香港 | - | 85% | 16ms |
| North America | IT7 Networks Inc | 143.244.49.177 | Bunny.net | AS60068 | 美国 洛杉矶 | - | 85% | 19ms |
| Eastern North America | Hostinger International Limited | 2a02:6ea0:f904::1163:1 | Bunny.net | AS60068 | 美国 波士顿 | - | 85% | 10ms |
| Southern China | Tencent | 143.244.49.178 | Bunny.net | AS60068 | 中国 广州市 | - | 85% | 893ms |
| Southwestern China | China Telecom | 2400:52e0:1a01::954:1 | Bunny.net | AS200325 | 中国 昆明市 | - | 85% | 944ms |
Confidence 85%
header: serverIP/CIDR: 138.199.9.104 in 138.199.9.104/32IP/CIDR: 2400:52e0:1a01::954:1 in 2400:52e0:1a01::954:1/128header: serverIP/CIDR: 185.111.111.155 in 185.111.111.155/32IP/CIDR: 2400:52e0:1e00:2::1332:1 in 2400:52e0:1e00:2::1332:1/128header: serverIP/CIDR: 2400:52e0:1502::1059:1 in 2400:52e0:1502::1059:1/128IP/CIDR: 84.17.37.214 in 84.17.37.214/32header: serverIP/CIDR: 143.244.49.177 in 143.244.49.177/32IP/CIDR: 2400:52e0:1a01::953:1 in 2400:52e0:1a01::953:1/128header: serverIP/CIDR: 109.61.86.193 in 109.61.86.193/32IP/CIDR: 2a02:6ea0:f904::1163:1 in 2a02:6ea0:f904::1163:1/128header: serverIP/CIDR: 143.244.49.178 in 143.244.49.178/32IP/CIDR: 2400:52e0:1a01::900:1 in 2400:52e0:1a01::900:1/128header: serverIP/CIDR: 143.244.49.177 in 143.244.49.177/32IP/CIDR: 2400:52e0:1a01::954:1 in 2400:52e0:1a01::954:1/128Methodology and limitations
The confirmation result is based on currently published rules, multiple real Agents, multiple regions, and at least two types of independent evidence.