Country
—
ASN LANDING PAGE
AS-26496-GO-DADDY-COM-LLC - GoDaddy.com, LLC
Last updated · Jul 20, 2026
Country
—
Total prefixes
224
IPv4 prefixes
207
IPv6 prefixes
17
AS-26496-GO-DADDY-COM-LLC - GoDaddy.com, LLC currently reports 224 prefixes and 44 upstream, downstream, or peer relationships. These counts describe the current dataset; they do not by themselves prove network quality, reach, or service use.
An ASN page shows the public organization label, country or region, BGP prefixes, and available peer and upstream relationships. It adds network context but cannot confirm a website host, physical facility, security status, or service quality.
AS-26496-GO-DADDY-COM-LLC - GoDaddy.com, LLC is currently associated with an unknown region. These values come from public network sources and are useful lookup clues; an organization label, registration region, and actual service location may differ.
The page shows ASN data returned by the current upstream query; interpret it with the update time. Open representative IP pages from the same network and compare prefixes, source labels, and query times. Verify operator or service claims with the relevant registry or network operator.
Detailed data for this ASN is not available right now.
AS1299
AS1299
—
AS6453
AS6453
—
AS2914
AS2914
—
AS3320
AS3320
—
AS6939
AS6939
—
AS3303
AS3303
—
AS8220
AS8220
—
AS37468
AS37468
—
AS35280
AS35280
—
AS137409
AS137409
—
AS7195
AS7195
—
AS9002
AS9002
—
AS8359
AS8359
—
AS13786
AS13786
—
AS24482
AS24482
—
AS8966
AS8966
—
AS18106
AS18106
—
AS49544
AS49544
—
AS1828
AS1828
—
AS4230
AS4230
—
AS19151
AS19151
—
AS52320
AS52320
—
AS17639
AS17639
—
AS45489
AS45489
—
AS6057
AS6057
—
AS7575
AS7575
—
AS36236
AS36236
—
AS51185
AS51185
—
AS394256
AS394256
—
AS2518
AS2518
—
AS8529
AS8529
—
AS9304
AS9304
—
AS9498
AS9498
—
AS14907
AS14907
—
AS17557
AS17557
—
AS34927
AS34927
—
AS48237
AS48237
—
AS199524
AS199524
—
AS52025
AS52025
—
AS58952
AS58952
—
| Prefix | Name | Country |
|---|---|---|
| 103.44.220.0/24 | AS26496 | — |
| 103.87.189.0/24 | AS26496 | — |
| 103.87.190.0/23 | AS26496 | — |
| 104.238.110.0/23 | AS26496 | — |
| 104.238.64.0/18 | AS26496 | — |
| 104.238.64.0/19 | AS26496 | — |
| 104.238.64.0/22 | AS26496 | — |
| 104.238.64.0/23 | AS26496 | — |
| 107.180.0.0/17 | AS26496 | — |
| 118.139.160.0/19 | AS26496 | — |
| 118.139.160.0/21 | AS26496 | — |
| 118.139.176.0/21 | AS26496 | — |
| 132.148.0.0/16 | AS26496 | — |
| 132.148.54.0/24 | AS26496 | — |
| 148.66.128.0/19 | AS26496 | — |
| 148.66.128.0/22 | AS26496 | — |
| 148.66.132.0/23 | AS26496 | — |
| 148.66.134.0/23 | AS26496 | — |
| 148.66.136.0/22 | AS26496 | — |
| 148.66.140.0/22 | AS26496 | — |
| 148.66.142.0/23 | AS26496 | — |
| 148.66.144.0/21 | AS26496 | — |
| 148.66.152.0/21 | AS26496 | — |
| 148.66.152.0/24 | AS26496 | — |
| 148.72.0.0/17 | AS26496 | — |
| 148.72.192.0/22 | AS26496 | — |
| 148.72.204.0/22 | AS26496 | — |
| 148.72.204.0/24 | AS26496 | — |
| 148.72.206.0/23 | AS26496 | — |
| 148.72.208.0/21 | AS26496 | — |
| 148.72.220.0/22 | AS26496 | — |
| 148.72.224.0/19 | AS26496 | — |
| 148.72.238.0/23 | AS26496 | — |
| 148.72.244.0/22 | AS26496 | — |
| 148.72.248.0/21 | AS26496 | — |
| 148.72.32.0/21 | AS26496 | — |
| 148.72.32.0/23 | AS26496 | — |
| 148.72.34.0/24 | AS26496 | — |
| 148.72.36.0/24 | AS26496 | — |
| 148.72.37.0/24 | AS26496 | — |
Review OVHcloud network organization fields, prefixes, peers, upstreams, and downstreams.
Review Hetzner network organization fields, prefixes, peers, upstreams, and downstreams.
Review Vultr-related organization fields, prefixes, peers, upstreams, and downstreams.
Review Linode / Akamai organization fields, prefixes, peers, upstreams, and downstreams.
AS26496 is an autonomous system number. The current source associates it with AS-26496-GO-DADDY-COM-LLC - GoDaddy.com, LLC and the region field an unknown region; those values add network context but do not prove a specific service, physical location, or quality level.
They help explain the scale, interconnection depth, and route structure of AS26496. Richer peering and upstream data often indicate broader network reach, but they should still be interpreted together with prefixes and related IP landing pages.
Open a concrete IP page to check how the address maps into AS26496, then compare the prefix, source labels, and query time. Verify operator or service claims with the relevant registry or network operator.
Use real IP and ASN pages to understand ASNs, BGP prefixes, peers, upstreams, and downstreams, including the limits of each snapshot.
Build troubleshooting context from an IP, BGP prefix, ASN, and public network relationships without treating static route data as a packet path.
Compare representative cloud and edge networks by ASN, announced prefixes, peers, upstreams, and downstreams without inferring a specific host or customer workload.