Download websites that use Karma
1 live site using Karma right now
JavaScript libraries · by Google · since 2012 · open source
Preview Karma site datasets
Karma detection is a value inside the Technologies column. Two datasets carry it, switch between them to compare what's included.
| Domain | TLD suffix | TLD | Domain type | HTTP status | IP address | Country by IP | Social networks | Technologies last data checked | Technologies | PR value | Harmonic value | Domain creation date | Domain expiration date |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| themarthablog.com | com | com | ICANN | HTTP 200 | 141.193.213.20 | US | {"x-twitter":["http://twitter.com/marthastewart"]} | 2026-09-19 | Google Ads AW-1032511621 AW-664456688 +1, Google Analytics G-SE1J1S6B4V UA-27345479-6 +1, Google Tag Manager GTM-NCXMP7, PHP, RSS, Karma, MySQL, HTTP/3, jQuery, Favicon | 0.000000094407 | 14,272,160 | 2007-10-22 | 2026-10-22 |
| … | … | … | … | … | … | … | … | … | … | … | … | … | … |
| Domain | TLD suffix | TLD | Domain type | HTTP status | IP address | Country by IP | Social networks | Technologies last data checked | Technologies | DNS last data checked | DNS Status | DNS records | PR value | Harmonic value | RDAP/WHOIS last data checked | RDAP/WHOIS method | Domain creation date | Domain expiration date | Domain last changed | Registrar | RDAP/WHOIS Record | Response Status RDAP/WHOIS |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| themarthablog.com | com | com | ICANN | HTTP 200 | 141.193.213.20 | US | {"x-twitter":["http://twitter.com/marthastewart"]} | 2026-09-19 | Google Ads AW-1032511621 AW-664456688 +1, Google Analytics G-SE1J1S6B4V UA-27345479-6 +1, Google Tag Manager GTM-NCXMP7, PHP, RSS, Karma, MySQL, HTTP/3, jQuery, Favicon | 2026-09-21 | TRUE | {"A":["141.193.213.20","141.193.213.21"],"NS":["ns-1377.awsdns-44.org","ns-2031.awsdns-61.co.uk","ns-497.awsdns-62.com","ns-710.awsdns-24.net"],"CAA":[{"tag":"issue","flags":0,"value":"amazon.com"},{"tag":"issue","flags":0,"value":"amazonaws.com"},{"tag":"issue","flags":0,"value":"amazontrust.com"},{"tag":"issue","flags":0,"value":"awstrust.com"},{"tag":"issue","flags":0,"value":"comodoca.com"},{"tag":"issuewild","flags":0,"value":"letsencrypt.org"},{"tag":"issue","flags":0,"value":"letsencrypt.org"},{"tag":"issue","flags":0,"value":"pki.goog; cansignhttpexchanges=yes"},{"tag":"issuewild","flags":0,"value":"pki.goog; cansignhttpexchanges=yes"},{"tag":"issue","flags":0,"value":"sectigo.com"},{"tag":"issue","flags":0,"value":"ssl.com"},{"tag":"issuewild","flags":0,"value":"ssl.com"},{"tag":"issue","flags":0,"value":"trust-provider.com"},{"tag":"issue","flags":0,"value":"usertrust.com"}],"SOA":{"mname":"ns-2031.awsdns-61.co.uk","retry":900,"rname":"awsdns-hostmaster.amazon.com","expire":1209600,"serial":1,"minimum":86400,"refresh":7200}} | 0.000000094407 | 14,272,160 | 2025-10-25 | RDAP | 2007-10-22 | 2026-10-22 | 2025-10-25 | SafeNames Ltd. | {"raw_response":{"links":[{"rel":"self","href":"https://rdap.verisign.com/com/v1/domain/THEMARTHABLOG.COM","type":"application/rdap+json","value":"https://rdap.verisign.com/com/v1/domain/THEMARTHABLOG.COM"},{"rel":"related","href":"https://rdap.safenames.legal/rdap/domain/THEMARTHABLOG.COM","type":"application/rdap+json","value":"https://rdap.safenames.legal/rdap/domain/THEMARTHABLOG.COM"}],"events":[{"eventDate":"2007-10-22T21:20:54Z","eventAction":"registration"},{"eventDate":"2026-10-22T21:20:54Z","eventAction":"expiration"},{"eventDate":"2025-10-23T00:19:14Z","eventAction":"last changed"},{"eventDate":"2025-10-25T10:00:01Z","eventAction":"last update of RDAP database"}],"handle":"1291974670_DOMAIN_COM-VRSN","status":["client delete prohibited","client transfer prohibited","client update prohibited"],"ldhName":"THEMARTHABLOG.COM","notices":[{"links":[{"rel":"terms-of-service","href":"https://www.verisign.com/domain-names/registration-data-access-protocol/terms-service/index.xhtml","type":"text/html","value":"https://rdap.verisign.com/com/v1/domain/themarthablog.com"}],"title":"Terms of Service","description":["Service subject to Terms of Use."]},{"links":[{"href":"https://icann.org/epp","type":"text/html"}],"title":"Status Codes","description":["For more information on domain status codes, please visit https://icann.org/epp"]},{"links":[{"rel":"help","href":"https://icann.org/wicf","type":"text/html","value":"https://rdap.verisign.com/com/v1/domain/themarthablog.com"}],"title":"RDDS Inaccuracy Complaint Form","description":["URL of the ICANN RDDS Inaccuracy Complaint Form: https://icann.org/wicf"]}],"entities":[{"links":[{"rel":"about","href":"http://www.safenames.net","type":"text/html","value":"https://rdap.safenames.legal/rdap/"}],"roles":["registrar"],"handle":"447","entities":[{"roles":["abuse"],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text",""],["tel",{"type":"voice"},"uri","tel:+44.1908200022"],["email",{},"text","abuse@safenames.net"]]],"objectClassName":"entity"}],"publicIds":[{"type":"IANA Registrar ID","identifier":"447"}],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text","SafeNames Ltd."]]],"objectClassName":"entity"}],"secureDNS":{"delegationSigned":false},"nameservers":[{"ldhName":"NS-1377.AWSDNS-44.ORG","objectClassName":"nameserver"},{"ldhName":"NS-2031.AWSDNS-61.CO.UK","objectClassName":"nameserver"},{"ldhName":"NS-497.AWSDNS-62.COM","objectClassName":"nameserver"},{"ldhName":"NS-710.AWSDNS-24.NET","objectClassName":"nameserver"}],"objectClassName":"domain","rdapConformance":["rdap_level_0","icann_rdap_technical_implementation_guide_1","icann_rdap_response_profile_1"]}} | Domain is active |
| … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … | … |
The Karma dataset
Every site we've detected as running Karma, with version, hosting, country, TLD and traffic rank.
Karma lives inside 2 datasets
Karma detection is part of Technologies (€159/mo) and All data (€599/mo). Buy either to filter the full 1-site list, or grab a free preview first.
About Karma
A browser test runner has no job on a production website. Its purpose is to launch real browsers on a developer machine or a build server, run unit tests against application code, and report failures before anything is deployed. So when the fingerprint shows up on a live page, the interesting question is not what the tool does, it is why the tool is visible at all.
There are a few ordinary explanations. A build can ship its configuration or its test harness into the published directory. A repository can be served straight from a web root without a build step separating source from output. A vendored bundle can carry the adapter along with the library it was meant to test. Each of those is a finding worth having if you are auditing what a site exposes, because the same pipeline mistakes that publish a test runner also publish source maps, environment files and internal comments.
The other explanation is that the name is shared. Karma is a common word and more than one product has used it, so a fingerprint match confirms that a pattern matched, not that a specific vendor's software is present. Our classification records the JavaScript libraries category, which is itself a sign that the entry does not sit cleanly in a functional group.
What the structured facts do support is a specific piece of tooling, a JavaScript project released under the MIT licence, first appearing in 2012, with Google recorded as the originating vendor. A permissive licence and an origin inside a large framework team explain the shape of its adoption. The runner spread with the framework it was built alongside, became standard in enterprise front-end pipelines, and stayed there long after newer runners took over new projects. Codebases that still reference it tend to be maintained rather than new.
As of October 2026 we detect the fingerprint on 1 site. Anyone treating the count as a measure of how many teams use the runner will be misled, because the bulk of its real usage happens in continuous integration where no crawler can see it. Our figure measures public exposure of the artefact, which is a different and narrower thing.
Narrow is still useful. A researcher auditing deployment hygiene, or a security team looking for sites that publish their build directory, wants the list of domains where development tooling reached production. A per-domain lookup cannot produce that population. The downloadable dataset can, and it can be filtered by country and top-level domain to see whether the pattern clusters anywhere.
Frequently asked questions
How many websites use Karma?
webatla detects Karma on 1 website, refreshed daily, with its domain, DNS, WHOIS, IP, country and ranking.
Can I download the list of websites using Karma?
Yes, as structured JSONL. Grab a free sample first.
What's included for each site, and how fresh is it?
Domain, DNS, RDAP/WHOIS, the full technology stack, IP & country, PageRank and Harmonic, re-detected and re-exported daily.
How do I find the websites using Karma?
Buy the technology dataset, then download the complete list of domains we detect using Karma, re-exported every day.
What else is in the Karma technology data?
Each row places Karma next to the other technology on the same site, plus DNS, WHOIS, IP, country and ranking.
Can I download just the sites using Karma, or the whole database?
Both. Every site running Karma comes in the Technologies dataset, one downloadable file. Or buy All data for the entire database: technologies plus identity, ranking, DNS and RDAP/WHOIS for every domain, combined in one file. Daily fresh export.
How do I download the list of websites using Karma?
Three steps: (1) grab the free 10,000-row sample to inspect the schema, (2) buy the Technologies dataset, (3) download the full list of every domain we detect running Karma as a JSON Lines file. It is re-exported daily, so you can re-download the freshest list any time inside your access window. Each row carries the domain plus DNS, WHOIS, IP, hosting country and rank.
Get the full list of websites using Karma
Pick the dataset that covers what you need. Each one includes Karma and downloads as JSONL, rebuilt daily.
Full website tech stack per site: CMS, payments, analytics, frameworks.
Everything we have, in a single package. The full webatla universe.
Want to compare every dataset side by side? Visit the pricing page
Related technologies
