A full-cohort source-check range is not summarized on this page. The dated package retains row-level source checks and historical publication limits. The package-check date records offline acceptance, not a source refresh.
100 reviewed Fastly company accounts. Evidence includes organization website http response plus fastly dns; current official supplier or service disclosure; published corporate asset get plus fastly dns. Claims apply only to the recorded property, product or workload.
Fastly source composition | Source class | Count | Scope |
|---|
| Organization website HTTP response plus Fastly DNS | 59 | Reviewed public evidence within the recorded property or workload; execution and payment remain unverified. |
|---|
| Current official supplier or service disclosure | 20 | Reviewed public evidence within the recorded property or workload; execution and payment remain unverified. |
|---|
| Published corporate asset GET plus Fastly DNS | 5 | Reviewed public evidence within the recorded property or workload; execution and payment remain unverified. |
|---|
| Service endpoint HTTP response plus Fastly DNS | 4 | Reviewed public evidence within the recorded property or workload; execution and payment remain unverified. |
|---|
| Accessible product or regional property plus Fastly DNS | 4 | Reviewed public evidence within the recorded property or workload; execution and payment remain unverified. |
|---|
| Current Fastly DNS configuration with access or routing limits | 6 | Reviewed public evidence within the recorded property or workload; execution and payment remain unverified. |
|---|
| Fastly delivery header indicating an upstream provider | 2 | Reviewed public evidence within the recorded property or workload; execution and payment remain unverified. |
|---|
Contexts in the Fastly research: Qualitative report examples of delivered resource and intermediary scope; no new company names in proposed copy. WhosBuilt review of the saved accepted report and approved examples; no source refresh.
Accepted report describes the retained list. Qualitative roles show presence, not prevalence. Counts refer only to the named recorded classifications; no source-by-context intersections are released. The displayed date is the package date. Source dates remain as recorded in the package; no source was refreshed for this analysis.
- Public sources do not verify paid subscriptions, organization-wide deployment or purchasing intent.
- Source retrieval dates record access; they do not make an older statement or historical deployment current.
- Published contact channels do not establish outreach permission, mailbox deliverability or purchasing authority.
- Supplier and historical disclosures retain their source and age limits; they are not proof of continued use.
- Published configuration does not establish browser execution or successful service operation.
- Domain DNS observations do not establish the organization’s wider hosting or procurement relationship.
Source access dates do not refresh historical statements. Static signals do not prove execution, payment or buying intent. Published contacts do not establish deliverability or outreach permission.