Applicability TestEU DSA

EU Digital Services Act Applicability Test

Classify whether a digital service is a DSA intermediary service, hosting service, online platform, marketplace, online search engine, VLOP or VLOSE before assigning obligations.

Use the test to capture EU-recipient facts, service functions, public dissemination, marketplace transactions, average monthly active recipients and micro or small enterprise evidence.

Author
Sorena AI
Published
May 9, 2026
Updated
May 9, 2026
Sections
5

Structured answer sets in this page tree.

Primary sources
6

Cited legal and guidance references.

Publication metadata
Sorena AI
Published May 9, 2026
Updated May 9, 2026
Overview

The DSA applicability question is not simply whether a company is online. The useful test is service-by-service: does the product offer an intermediary service in the Union, does it store user-provided information, does it disseminate that information to the public, does it let consumers conclude distance contracts with traders, and does it meet the average monthly active recipient threshold for very large services?

Section 1

Step 1: decide whether the service is a DSA intermediary service offered in the Union

Start with the specific service, not the corporate group. The DSA defines a recipient of the service as a natural or legal person using an intermediary service, including to seek information or make information accessible. A provider offers services in the Union when people in one or more Member States can use the intermediary service and the provider has a substantial connection to the Union.

Record the evidence for that connection. Establishment in the Union is one route. Other factual evidence can include a significant number of recipients in one or more Member States or targeting activities toward one or more Member States.

  • Name the service interface being tested, such as website, app, API, marketplace, cloud hosting service or search function.
  • Identify the EU Member States where recipients can use the service and the facts showing establishment, targeting or significant recipient volume.
  • Classify whether the service is mere conduit, caching or hosting before moving to platform-specific obligations.
  • Keep separate records for mixed products because one product can contain several services with different DSA roles.
Section 2

Step 2: classify the intermediary tier

The first classification branch is functional. A mere conduit service transmits user-provided information or provides access to a communication network. A caching service transmits user-provided information and stores it automatically, temporarily and intermediately to make onward transmission more efficient. A hosting service stores information provided by, and at the request of, a recipient.

Only after a hosting classification is plausible should the test ask whether the service is an online platform. Online platforms are hosting services that store and disseminate recipient-provided information to the public, unless public dissemination is only a minor, purely ancillary feature or a minor functionality of the main service that cannot be used independently for objective technical reasons.

  • Mere conduit evidence: access-provider or transmission role, no initiation of transmission, no selection of receiver and no selection or modification of transmitted information.
  • Caching evidence: automatic, intermediate and temporary storage used to make onward transmission more efficient or secure.
  • Hosting evidence: user-provided information is stored at the user's request, such as cloud storage, web hosting or stored listings.
  • Online platform evidence: the service makes stored user information available to a potentially unlimited number of third parties.
  • Ancillary-feature evidence: explain why public dissemination is minor, inseparable from the principal service and not a way to avoid platform rules.
Section 3

Step 3: identify marketplace, advertising, recommender and moderation consequences

A marketplace classification matters because some online platforms allow consumers to conclude distance contracts with traders. The DSA text and Commission materials connect that category to trader traceability and illegal-goods controls, so the applicability record should capture seller onboarding, product or service listings, checkout flows and consumer-facing seller information.

For any online platform, the applicability test should also note whether the service presents advertisements, uses recommender systems, is accessible to minors or moderates user-provided content. These facts do not replace the service classification, but they determine which platform obligations need follow-up.

  • Marketplace evidence: traders can offer goods or services and consumers can conclude distance contracts through the platform.
  • Trader evidence: collect identity, contact and verification fields used before a seller can offer goods or services.
  • Content moderation evidence: record removals, visibility restrictions, account restrictions, demonetisation and terms-based restrictions that may require statements of reasons.
  • Advertisement evidence: identify whether ads are presented on the platform interface and what parameters are available to recipients.
  • Recommender evidence: identify automated systems that suggest, prioritise or rank information for recipients.
Section 4

Step 4: test micro or small enterprise treatment before applying platform-section duties

The DSA contains an exclusion for providers of online platforms that qualify as micro or small enterprises under Recommendation 2003/361/EC. That exclusion applies to Section 3 platform obligations except Article 24(3), and it can continue for 12 months after losing micro or small status. It does not protect a service designated as a very large online platform.

The applicability test should therefore preserve the enterprise-size analysis separately from the service classification. A service can still be an online platform even if some platform-section obligations are excluded because the provider is micro or small.

  • Record the provider entity tested for micro or small enterprise status and whether group or consolidation facts affect that status.
  • Record whether the provider previously qualified as micro or small and, if so, when that status was lost.
  • Do not use the micro or small exclusion for a designated VLOP.
  • Keep Article 24(3) response readiness in scope because the exclusion does not remove the duty to provide active-recipient calculation information on request.
Section 5

Step 5: calculate active recipients and decide whether VLOP or VLOSE designation risk exists

For each online platform or online search engine, the DSA requires publication of average monthly active recipients of the service in the Union, calculated over the past six months, and updated at least every six months. This calculation is also the evidence base for very large online platform and very large online search engine designation.

Article 33 applies to online platforms and online search engines with average monthly active recipients in the Union equal to or higher than 45 million, once designated by the Commission. The Commission page explains the same threshold as more than 45 million users per month in the EU and notes that designated services have four months to comply with the DSA's very large service rules.

Does every hosting service become an online platform under the DSA?

No. A hosting service becomes an online platform only when it stores recipient-provided information and disseminates it to the public, unless that public dissemination is merely minor, purely ancillary and technically inseparable from another principal service.

What is the key DSA threshold for VLOP or VLOSE review?

The grounded threshold is 45 million average monthly active recipients of the service in the Union for an online platform or online search engine, followed by Commission designation as a VLOP or VLOSE.

What evidence should a DSA applicability test save?

Save the tested service interface, EU-recipient facts, intermediary tier, public-dissemination analysis, marketplace and search-engine facts, micro or small enterprise evidence, AMAR calculation method, source citations and the resulting obligation map.

  • Calculate AMAR separately for each online platform or online search engine service, not only for the provider as a whole.
  • Use EU recipients, not global users, registered accounts or raw traffic unless those measures are reconciled to active recipients.
  • Count recipients who engage with the platform by requesting hosting or being exposed to hosted information; for search, count recipients who submit a query and are exposed to indexed results.
  • Document deduplication across websites, apps, URLs or domain names where possible, and document any bot or scraper exclusions that do not require additional tracking of individuals.
  • Escalate for VLOP or VLOSE review at or near 45 million average monthly active recipients in the Union or when the Commission, a Digital Services Coordinator or public data indicates threshold risk.
Recommended next step

Turn the applicability test into a service-by-service evidence record

Sorena can help convert this DSA classification test into a cited scope record, AMAR evidence request and obligation map for each platform, marketplace, hosting service or search service.

Primary sources

References and citations

digital-strategy.ec.europa.eu
Referenced sections
  • Commission FAQ explains that hosting services must provide statements of reasons for certain moderation restrictions and online platforms submit them to the database.
"Article 17 of the Digital Services Act"
digital-strategy.ec.europa.eu
Referenced sections
  • Commission overview describes the DSA as proportionate, with lighter requirements for micro and small companies and more responsibilities for bigger platforms.
"Micro and small companies have lighter requirements"
eur-lex.europa.eu
Referenced sections
  • Articles 24 and 33 set publication, calculation, information-request and designation rules for average monthly active recipients and very large services.
"equal to or higher than 45 million"
Related guides

Explore more topics

DSA Ads and Recommender Systems: transparency duties, user choice, and evidence
A grounded DSA guide to ad labels, targeting restrictions, recommender parameter disclosure, non-profiling options for VLOPs and VLOSEs, ad repositories, and compliance evidence.
DSA Article 28 minors protection guide for online platforms
EU Digital Services Act guide to Article 28 minors protection: platform scope, child-safety measures, targeted ads limits, recommender controls, and grounded evidence.
DSA average monthly active recipients: what platforms must publish
A grounded FAQ on average monthly active recipients under the EU Digital Services Act, including publication, EU recipient scope, the 45 million VLOP/VLOSE threshold, and evidence records.
DSA Complaint and Dispute Workflows for Online Platforms
Build DSA complaint, appeal, statement-of-reasons, and out-of-court dispute workflows for online platform moderation decisions.
DSA crisis response for VLOPs and VLOSEs
EU Digital Services Act crisis response guide for VLOPs and VLOSEs: Article 36 Commission decisions, Article 48 crisis protocols, mitigation, governance, requests for information, and records.
DSA Dark Patterns: interface design checks for online platforms
Article 25 DSA guidance for reviewing online platform interfaces for deceptive, manipulative, or choice-distorting design patterns.
DSA Enforcement and Penalties in the EU
How Digital Services Act enforcement works: Commission and Digital Services Coordinator roles, VLOP and VLOSE investigations, fines, periodic penalty payments, and evidence readiness.
DSA illegal content notices: what must be included?
A grounded FAQ on EU Digital Services Act illegal-content notices: Article 16 notice elements, acknowledgement, decision notices, trusted flagger priority, statements of reasons, and records.
DSA Marketplace Trader Traceability FAQ
Answer to what EU Digital Services Act Article 30 requires online marketplaces to collect, verify, display, retain, and evidence for trader traceability.
DSA Marketplace Trader Traceability Guide
EU Digital Services Act guide for online marketplaces collecting, checking, displaying, storing, and evidencing trader traceability information.
DSA notice and action plus statements of reasons guide
A grounded Digital Services Act guide for notice intake, moderation decisions, statements of reasons, DSA Transparency Database submission, complaints, appeals, trusted flaggers, and records.
DSA Notice and Action Workflow for Hosting Services and Online Platforms
A grounded DSA notice-and-action workflow covering notice intake, completeness checks, trusted flaggers, decisions, user communications, statements of reasons, appeals, and records.
DSA recommender transparency FAQ: Article 27 and VLOP options
What EU Digital Services Act recommender transparency requires: main parameters, user options, VLOP/VLOSE non-profiling choices, and evidence to keep.
DSA researcher data access for VLOPs and VLOSEs
Article 40 DSA guide to vetted researcher data access for VLOPs and VLOSEs: DSC requests, eligibility checks, amendment grounds, confidentiality, security, and evidence records.
DSA service tier classifier for platforms, marketplaces, VLOPs and VLOSEs
Classify a digital service under the EU Digital Services Act as intermediary, hosting, online platform, marketplace, VLOP or VLOSE, with EU recipient-count evidence and obligation outputs.
DSA statement of reasons FAQ
When DSA statements of reasons are required, what they must contain, when online platforms submit them to the DSA Transparency Database, and what appeal records to keep.
DSA statement of reasons log workflow for online platforms
Build a DSA statement of reasons log for moderation decisions, Transparency Database submission, complaint links, retention, and QA controls.
DSA transparency report template fields and cadence
A source-grounded template outline for Digital Services Act transparency reports, covering applicable service tiers, reporting periods, CSV/XLSX format, retention, statement-of-reasons links, and required evidence tables.
DSA Transparency Reporting Obligations by Provider Tier
A grounded guide to EU Digital Services Act transparency reports, active-recipient publication, statements-of-reasons submissions, VLOP/VLOSE reports, templates, cadence, and evidence.
DSA VLOP and VLOSE Risk Assessments and Mitigation Guide
Grounded guide to Digital Services Act systemic risk assessments, mitigation measures, audits, transparency reports, data access, and governance evidence for VLOPs and VLOSEs.
DSA VLOP Audit Pack Workflow: Risk, Mitigation, Audit, and Transparency Records
Build a DSA VLOP or VLOSE audit pack covering Article 34 risk assessments, Article 35 mitigations, independent-audit evidence, transparency reports, data access, and compliance governance.
DSA VLOP Risk Assessment FAQ: Article 34, Mitigation, Audits
What VLOPs and VLOSEs must assess under the EU Digital Services Act, when to reassess, how Article 35 mitigation and annual audit evidence fit together, and what records to keep.
DSA vs DMA Platform Rules
Compare the EU Digital Services Act and Digital Markets Act by scope, designation thresholds, obligations, enforcement, evidence, and practical team ownership.
DSA vs GDPR: online-platform governance and personal-data obligations
Compare the EU Digital Services Act and EU GDPR by scope, ads, recommenders, minors, transparency, complaints, enforcement, and evidence.
DSA vs P2B Regulation: EU platform obligations compared
Compare the EU Digital Services Act with the Platform-to-Business Regulation for platform scope, business-user terms, content moderation, ranking transparency, complaints, enforcement, and evidence.
DSA vs Terrorist Content Online Regulation: notice-and-action vs removal orders
Compare DSA content-governance duties with the EU Terrorist Content Online Regulation removal-order workflow for scope, timing, evidence, authorities, and team ownership.
EU Digital Services Act checklist for platforms and hosting services
A grounded DSA checklist for classifying service tiers, notice-and-action, statements of reasons, complaints, transparency reports, ads, recommenders, trader traceability, VLOP/VLOSE duties, and evidence records.
EU Digital Services Act Compliance Guide
DSA compliance guide for intermediary services, hosting providers, online platforms, marketplaces, and VLOP/VLOSE teams: obligations, controls, and evidence to keep.
EU Digital Services Act FAQ: DSA scope, platform duties, VLOPs, reports, and penalties
Concise EU Digital Services Act FAQ covering intermediary-service scope, active-recipient thresholds, illegal-content notices, statements of reasons, trader traceability, recommender transparency, systemic-risk duties, reporting, penalties, and complaints.
EU Digital Services Act penalties and fines: caps and enforcement roles
DSA penalty caps and enforcement roles: Member State fines, Commission fines for VLOPs and VLOSEs, 1% procedural fines, and 5% periodic penalty payments.
EU Digital Services Act requirements by service tier
Overview of DSA obligations for intermediary services, hosting providers, online platforms, marketplaces, VLOPs and VLOSEs, including notices, complaints, ads, transparency reports, audits, data access and enforcement.
EU Digital Services Act service types and scope
Classify DSA service scope across mere conduit, caching, hosting, online platforms, marketplaces, online search engines, and VLOP/VLOSE threshold duties.
EU DSA deadlines and compliance calendar: application dates, reporting cycles, and VLOP clocks
Calendar view of grounded EU Digital Services Act dates: full application, user-number publication, VLOP/VLOSE designation clocks, statements of reasons, and transparency reporting cycles.
EU DSA Transparency Calendar: reporting, SoR database, AMAR updates
Build a DSA transparency calendar for annual reports, statement-of-reasons database submissions, active-recipient updates, and VLOP/VLOSE audit touchpoints.
EU DSA vs UK Online Safety Act: scope, duties, regulator, and evidence
Compare the EU Digital Services Act and UK Online Safety Act for platform scope, risk assessments, child protection, transparency, regulators, enforcement, and owners.