BuiltWith API for technology lookup and website lists

Check how legitimate one website looks before you buy from it: a legitimacy level, a written summary of what drove the verdict, and the signals behind it such as affiliate links or a missing live record. Every domain gets a verdict — an unknown website is assessed as unverified, which is an answer rather than a blank. One domain per request, not a batch of domains.

Count the websites running one named technology across the BuiltWith index: the live website total, the historical totals over time, and coverage among the highest-ranked websites. It answers how many, not which ones — the adopters themselves are a separate Endpoint. Free, one component name per request, and the same figures compare technologies against each other.

Count how many technologies a website runs in each stack group — framework, hosting, analytics, commerce and the rest — given its domain. Each group row carries a live count and a retired count, plus the dates the website was first and last indexed. Group counts only: the component names themselves never come back. Free.

Find the other domains sharing a tracking identifier with one website — the same analytics id, advertising id or hosting trace — together with the value that ties them together and the window each pairing was seen. This is evidence of common ownership or operation, not a redirect and not a link. Supply a domain, with a skip offset for the next page of identifiers.

Find candidate websites for a business name: each row carries the domain, the company name BuiltWith holds for it, estimated annual technology spend, page rank and any social profiles. Matching is fuzzy, so an unrecognised name comes back with the nearest companies rather than nothing — read the returned company name before trusting a row. It turns names into websites, never websites into companies.

Get the components BuiltWith suggests for one website, inferred from what comparable sites run: each row gives the suggested component, its category, a link and how established it is. These are suggestions to consider adding, not a reading of what the site already runs. Supply a domain; a site with no suggestions returns an empty list at no charge.

Get the recurring words one website uses about itself, collected off its own pages: every term comes from a page of the site, in the site's own wording. These are the terms the site chose — not search queries, not ranking data, and not the page bodies. Supply a domain; a site with nothing collected comes back empty and costs nothing.

List the websites seen at one network address, or carrying one BuiltWith tag, with the window each was observed. Supply the address in the provider's own form, such as IP-151.101.1.195, or a tag string — a domain is not a valid input here and comes back empty. These are the neighbours sharing an address, not a reading of what any one website runs. One address or tag per request, not a range of addresses.

List every website that currently runs one named technology, from the set of technologies BuiltWith tracks: supply the exact component name and get one row per website with the dates it was first and last detected, plus an opaque cursor for the next page. This is the reverse direction — technology in, websites out. An unknown component name is refused rather than guessed at, so resolve the canonical name first. Flat price per page.

Look up the canonical component names BuiltWith uses from a plain description of what a tool does: each candidate carries a similarity score, its category and a short description of the technology. This is the naming step that makes an adopter lookup possible when all you know is what the technology does — feed the name it returns to the adopter list. A meaningless phrase still comes back with the nearest names at low scores, so read the score.

Look up which technologies one website runs, given its domain: the CMS, hosting, ecommerce, analytics, advertising and other stack components BuiltWith detected, each with the dates it was first and last detected. The input is a website and the output is its technology list; this direction only. One domain per request.

Look up the forwarding around one website in both directions: which domains redirect to it, and where it redirects visitors on to. Each entry carries the other domain and the dates the forwarding was first and last observed. Supply a domain; a site involved in no forwarding comes back with two empty lists at no charge.