REDAXO logo

Download websites that use REDAXO

1 live site using REDAXO right now

CMS · since 2003 · open source

1 site Dataset updated · 2026-10-04
Categories CMS
🔒 Get the list
Requires a dataset purchase
All figures here come from one snapshot of the webatla database, taken on this date (UTC). We usually refresh it every day.
1 Sites detected
0.0% Of all websites

Preview REDAXO site datasets

REDAXO detection is a value inside the Technologies column. Two datasets carry it, switch between them to compare what's included.

webatla-technologies-redaxo-2026-10-04.jsonl.zst · 1 row · 14 columns Daily fresh export
DomainTLD suffixTLDDomain typeHTTP statusIP addressCountry by IPSocial networksTechnologies last data checkedTechnologiesPR valueHarmonic valueDomain creation dateDomain expiration date
dreirad-marburg.orgorgorgICANNHTTP 200———2026-05-06PHP, PWA, HSTS, REDAXO, jQuery, Bootstrap, jQuery UI, jQuery-pjax, Apache HTTP Server0.00000000416599,729,1682020-05-072027-05-07
……………………………………
DomainTLD suffixTLDDomain typeHTTP statusIP addressCountry by IPSocial networksTechnologies last data checkedTechnologiesDNS last data checkedDNS StatusDNS recordsPR valueHarmonic valueRDAP/WHOIS last data checkedRDAP/WHOIS methodDomain creation dateDomain expiration dateDomain last changedRegistrarRDAP/WHOIS RecordResponse Status RDAP/WHOIS
dreirad-marburg.orgorgorgICANNHTTP 200———2026-05-06PHP, PWA, HSTS, REDAXO, jQuery, Bootstrap, jQuery UI, jQuery-pjax, Apache HTTP Server2026-09-28FALSE—0.00000000416599,729,1682026-05-14RDAP2020-05-072027-05-072026-05-07InterNetX GmbH{"raw_response":{"links":[{"rel":"related","href":"https://rdap.registrar.internetx.com/domain/dreirad-marburg.org","type":"application/rdap+json","value":"https://rdap.publicinterestregistry.org/rdap/domain/dreirad-marburg.org"},{"rel":"self","href":"https://rdap.publicinterestregistry.org/rdap/domain/dreirad-marburg.org","type":"application/rdap+json","value":"https://rdap.publicinterestregistry.org/rdap/domain/dreirad-marburg.org"}],"events":[{"eventDate":"2027-05-07T13:08:08.6Z","eventAction":"expiration"},{"eventDate":"2020-05-07T13:08:08.6Z","eventAction":"registration"},{"eventDate":"2026-05-07T13:08:22.518Z","eventAction":"last changed"},{"eventDate":"2026-05-14T13:59:02.051Z","eventAction":"last update of RDAP database"}],"status":["client hold","auto renew period"],"ldhName":"dreirad-marburg.org","notices":[{"links":[{"rel":"terms-of-service","href":"https://thenew.org/org-people/about-pir/policies/","type":"text/html","value":"https://rdap.publicinterestregistry.org/rdap/domain/dreirad-marburg.org"}],"title":"Terms of Service","description":["Public Interest Registry provides this RDAP service for informational purposes only, and to assist persons in obtaining information about or related to a domain name registration record. Public Interest Registry does not guarantee its accuracy. Users accessing the Public Interest Registry RDAP service agree to use the data only for lawful purposes, and under no circumstances may this data be used to: a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the registrar's own existing customers and b) enable high volume, automated, electronic processes that send queries or data to the systems of Public Interest Registry or any ICANN-accredited registrar, except as reasonably necessary to register domain names or modify existing registrations. When using the Public Interest Registry RDAP service, please consider the following: the RDAP service is not a replacement for standard EPP commands to the SRS service. RDAP is not considered authoritative for registered domain objects. The RDAP service may be scheduled for downtime during production or OT&E maintenance periods. Queries to the RDAP services are throttled. If too many queries are received from a single IP address within a specified time, the service will begin to reject further queries for a period of time to prevent disruption of RDAP service access. Abuse of the RDAP system through data mining is mitigated by detecting and limiting bulk query access from single sources. Where applicable, the presence of a [Non-Public Data] tag indicates that such data is not made publicly available due to applicable data privacy laws or requirements. Should you wish to contact the registrant, please refer to the RDAP records available through the registrar URL listed above. Access to non-public data may be provided, upon request, where it can be reasonably confirmed that the requester holds a specific legitimate interest and a proper legal basis for accessing the withheld data. Access to this data can be requested by submitting a request to WHOISrequest@pir.org. Public Interest Registry Inc. reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy."]},{"links":[{"rel":"glossary","href":"https://icann.org/epp","type":"application/rdap+json","value":"https://rdap.publicinterestregistry.org/rdap/domain/dreirad-marburg.org"}],"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":"application/rdap+json","value":"https://rdap.publicinterestregistry.org/rdap/domain/dreirad-marburg.org"}],"title":"RDDS Inaccuracy Complaint Form","description":["URL of the ICANN RDDS Inaccuracy Complaint Form: https://icann.org/wicf"]}],"entities":[{"links":[{"rel":"self","href":"https://rdap.publicinterestregistry.org/rdap/entity/151","type":"application/rdap+json","value":"https://rdap.publicinterestregistry.org/rdap/entity/151"},{"rel":"about","href":"https://rdap.registrar.internetx.com/","type":"application/rdap+json","value":"https://rdap.registrar.internetx.com/"}],"roles":["registrar"],"handle":"151","entities":[{"roles":["abuse"],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text",""],["tel",{"type":"voice"},"uri","tel:+49.941595590"],["email",{},"text","domain-abuse@internetx.com"]]],"objectClassName":"entity"}],"publicIds":[{"type":"IANA Registrar ID","identifier":"151"}],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text","InterNetX GmbH"]]],"objectClassName":"entity"}],"redacted":[{"name":{"type":"Registry Domain ID"},"method":"removal","prePath":"$.handle","pathLang":"jsonpath"}],"secureDNS":{"maxSigLife":1,"delegationSigned":false},"nameservers":[{"handle":"04d8a8fabc824bd9887fd04ddc80a32d-LROR","status":["associated"],"ldhName":"dns01.manitu.net","unicodeName":"dns01.manitu.net","objectClassName":"nameserver"},{"handle":"1aacd57636c741a8ae6c0989dbb359f1-LROR","status":["associated"],"ldhName":"dns02.manitu.net","unicodeName":"dns02.manitu.net","objectClassName":"nameserver"}],"unicodeName":"dreirad-marburg.org","objectClassName":"domain","rdapConformance":["rdap_level_0","icann_rdap_response_profile_1","icann_rdap_technical_implementation_guide_1","redacted"]}}Domain is active
……………………………………………………………
Showing 1 of 1 row · Technologies · Full website tech stack per site: CMS, payments, analytics, frameworks.

The REDAXO dataset

Every site we've detected as running REDAXO, with version, hosting, country, TLD and traffic rank.

REDAXO lives inside 2 datasets

REDAXO 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.

Your REDAXO downloads

The datasets you own, sliced to REDAXO. Every button streams the latest daily export directly.

Format: JSONL (zstd) Dataset updated: 2026-10-04

API, columns & recipes → /account/api

About REDAXO

The people who choose REDAXO are almost never the people whose logo ends up on the finished homepage. A modular CMS built around templates and reusable code blocks is an agency decision, made by whoever will maintain the site for years afterwards, and it gets chosen for control over output rather than for an editing experience that demonstrates well in a sales meeting.

Written in PHP and released under the MIT license since 2003, the project has no vendor recorded in our data, which fits a community maintained system rather than a commercial product with a sales motion behind it. There is no license server, no billing record and no telemetry that anyone could query, so nobody holds an authoritative install count. Crawling is the only method available, and crawling has known limits.

Detection rests on traces the system leaves in delivered pages, meaning asset paths, generated markup patterns and occasionally a header or cookie name. A developer oriented CMS attracts exactly the kind of operator who strips those traces, either out of tidiness or on the theory that hiding the platform reduces exposure. Undercounting is therefore the expected error, and the direction of the error is worth stating rather than hiding.

As of October 2026 we detect REDAXO on 1 site. Our record carries no version breakdown for the project, so the dataset answers where the system runs and not which release each installation sits on. For a self hosted application the missing half is the half security researchers usually want, and pretending otherwise would help nobody.

The list is useful mainly to people already inside the ecosystem. AddOn developers and agencies want to know how large the deployed base really is before investing in extensions for it. Competing CMS vendors want sites running a system with a small maintainer pool, since a maintenance handover is an easier sale than a rebuild. Researchers tracking the long tail of self hosted publishing want a population that is not dominated by the handful of platforms everyone already measures.

A per domain lookup is the wrong tool for all of that, because the entire difficulty is not knowing which domains to check. An install base built by an agency network is scattered across unrelated brands with nothing in common but the builder. The export returns that scattered population as a single set, joined to country, TLD, hosting and the rest of each site's stack, which is how a pile of unrelated domains turns into something a researcher can reason about.

Frequently asked questions

How many websites use REDAXO?

webatla detects REDAXO on 1 website, refreshed daily, with its domain, DNS, WHOIS, IP, country and ranking.

Can I download the list of websites using REDAXO?

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 REDAXO?

Buy the technology dataset, then download the complete list of domains we detect using REDAXO, re-exported every day.

What else is in the REDAXO technology data?

Each row places REDAXO next to the other technology on the same site, plus DNS, WHOIS, IP, country and ranking.

Can I download just the sites using REDAXO, or the whole database?

Both. Every site running REDAXO 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 REDAXO?

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 REDAXO 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 REDAXO

Pick the dataset that covers what you need. Each one includes REDAXO and downloads as JSONL, rebuilt daily.

Technologies 14 columns

Full website tech stack per site: CMS, payments, analytics, frameworks.

€159 / mo
Buy and download Download preview dataset
All data 23 columns

Everything we have, in a single package. The full webatla universe.

€599 / mo
Buy and download Download preview dataset

Want to compare every dataset side by side? Visit the pricing page