- What should you do right now if you run a platform or marketplace?
- What exactly did the EU Commission do, and why now?
- Is phishing really that serious a problem for Italian platforms?
- What exactly does the DSA say about ad transparency?
- Three real-world scenarios: what changes for an e-commerce store, a B2B portal and a professional firm?
- What tools and measures are available to get compliant?
- What are the real risks of not complying?
- Why has the DSA become urgent right now?
- How do you actually get started with a DSA audit for your platform?
- What mistakes are most common when complying with the DSA?
- How can you tell if your platform is truly compliant?
- So, is the DSA a real problem for your platform?
- How we see it at SHM
- Frequently Asked Questions
- The EU Commission has opened an investigation into Booking.com for three DSA violations: fraudulent listings, phishing and failure to label paid ads.
- DSA fines can reach up to 6% of annual global turnover: X (formerly Twitter) already paid €120 million at the end of 2025.
- Every Italian platform or marketplace operating in the EU must immediately review three areas: content moderation, anti-phishing protection and advertising transparency.
- The most underestimated issue is technical: the DSA and GDPR overlap on ads, and marketing teams often don't realize it.
The European Commission has opened a formal investigation into Booking.com over paid ads not labeled as advertising, fraudulent listings and phishing. If you run a platform or marketplace, this case concerns you too.
What should you do right now if you run a platform or marketplace?
Start an audit on three fronts: content moderation, anti-phishing protection and ad transparency. Waiting for an investigation to arrive is already too late.
The Booking.com case isn't travel news. It's a clear signal for anyone running a digital platform with users in the European Union: the Digital Services Act (DSA, the EU regulation on digital services) is enforced through formal proceedings, not informal warnings.
The right question isn't "are we as big as Booking?" It's: "would our practices hold up in an audit?"
| Your situation | Urgency | why |
|---|---|---|
| Marketplace with third-party ads and paid listings | High | You're exposed on all three fronts of the investigation: fraud, phishing, ad transparency |
| Platform with user-generated content (UGC) | High | The DSA requires risk assessments and active reporting systems |
| E-commerce with unlabeled sponsored ranking | High | Art. 26 of the DSA requires clear, real-time labeling |
| Site with booking forms or customer contact data | Medium | Indirect phishing risk: your data can be used for scams |
| Small business under 50 employees and €10M turnover | Low | SMEs are exempt from the heaviest DSA obligations |
What exactly did the EU Commission do, and why now?
The Commission has opened formal proceedings against Booking.com for three possible DSA violations: fraudulent listings, phishing that exploits booking data and paid ads not identifiable as such.
The European Commission's official press release describes three specific areas of investigation. First: fraudulent or non-compliant ads and accommodations published on the platform. Second: phishing scams (attempts to steal data through fake emails or messages) that exploit users' booking data. Third: listings promoted through payment to appear higher in search results, without users knowing they were advertising.
The DSA has applied to all online platforms in the EU since February 17, 2024, with the exception of micro and small businesses. For platforms with more than 45 million monthly users in the EU, the so-called VLOPs (very large online platforms), it has been in force since August 2023, as clarified by the European Commission.
| Area of investigation | DSA article violated | What Booking.com is accused of |
|---|---|---|
| Fraudulent listings | Art. 16 and 28 | Failure to carry out due diligence and mitigate the risk of fake ads |
| Phishing on booking data | Art. 13 and 35 | Failure to protect users from scams that exploit their data |
| Unlabeled ads | Art. 26 | Paid promoted listings not identifiable as advertising |
This isn't the first time the DSA has had concrete consequences. In December 2025, X (formerly Twitter) received a €120 million fine for dark patterns (design practices that deceive users), shortcomings in its ad repository and obstacles to researcher access, as reported by Gli Stati Generali. The Booking.com case is the second major formal proceeding.

Is phishing really that serious a problem for Italian platforms?
Yes. Data from 2025 shows that over 9 million Italians fell victim to a scam while planning their vacations, and booking portals are scammers' preferred channel in 53% of cases.
Phishing tied to travel platforms isn't a theoretical risk. In summer 2025, over 9 million Italians experienced a scam or attempted fraud while planning their vacations, with estimated losses of around €560 million, according to Torino Cronaca.
In May 2025, Check Point Research detected a 55% increase in new travel-related domains compared with the previous year: out of more than 39,000 newly registered domains, 1 in 21 was malicious or suspicious, as documented by Hacker Journal. Many of these domains clone the interfaces of Booking.com and Airbnb to trick users.
The problem extends to the infrastructure level as well. Starting in February 2025, a Russian actor registered more than 4,300 domains to impersonate booking platforms, with a peak of 511 domains in a single day, according to Matrice Digitale / Netcraft.
DMARC is a technical protocol that stops fraudulent emails from appearing to come from your domain. According to BitMat / Proofpoint, as of July 2026, 30% of the main Italian travel sites have no DMARC measures in place, and only 45% use the highest level of protection. This means that more than half of Italian travelers are exposed to email fraud that appears to come from legitimate platforms.
What exactly does the DSA say about ad transparency?
Article 26 of the DSA requires platforms to clearly label every ad and to inform users in real time about who paid for it and why it is being shown to them.
The point about ads hits digital marketers most directly. Article 26 of the DSA states that every promotional content item must be immediately identifiable as such, indicating who paid for it and why that ad is being shown to that specific user. The European Commission's DSA Observatory explains this clearly.
In the Booking.com case, the problem is that listings paid to rank higher in the results were not recognizable as advertising. A user searching for a hotel couldn't tell whether the first result was the most relevant or simply the one that paid the most.
| DSA Art. 26 obligation | What this means in practice | Who must comply |
|---|---|---|
| Clear ad labeling | Every sponsored item must be visually distinguishable from organic results | All platforms with third-party ads |
| Advertiser identity | Users must know who paid for the ad | Marketplaces, comparison sites, internal search engines |
| Reason for display | The platform must explain why that ad is shown to that user | Platforms with behavioral targeting |
| Ad repository | VLOPs must maintain a public ad repository | Only platforms with over 45M monthly EU users |
There's another layer of complexity that marketing teams often overlook. In September 2025, the EDPB (European Data Protection Board) adopted Guidelines 3/2025, which clarify how the DSA and GDPR overlap: the DSA requires real-time information about ads, while the GDPR requires disclosure before data is collected. This creates a technical knot that calls for coordination between legal, marketing and development teams, as explained by PPC Land. The issue is similar to the one we already covered regarding default settings in AI-powered ad campaigns, where compliance is often ignored until a penalty arrives.

Three real-world scenarios: what changes for an e-commerce store, a B2B portal and a professional firm?
The impact of the DSA varies widely depending on the type of platform. Here are three illustrative cases to help you see where to act first.
Illustrative examples: the numbers and situations are meant to show the reasoning, they are not real customer data.
| Company type | Main risk | Priority action | Recommended timeline |
|---|---|---|---|
| E-commerce with third-party products (marketplace) | Fraudulent listings and unlabeled sponsored ads | Listing audit, reporting system, ad labeling | Within 30 days |
| B2B portal with paid ranking | Ads not identifiable as such (DSA Art. 26) | UI review for clear labeling, privacy policy update | Within 60 days |
| Professional firm with a contact form and newsletter | Indirect phishing: client data can be used by third parties | Enable DMARC 'reject', check SPF and DKIM | Within 15 days |
| Store chain with online booking | Booking data exposed to phishing | Two-factor authentication, monitoring of lookalike domains | Within 30 days |
The most underestimated case is that of the professional firm or small business with a contact form. You aren't directly subject to the heaviest DSA obligations, but your contact data can be used by scammers to build credible phishing campaigns. Protecting your email domain with DMARC is a simple technical measure that drastically reduces this risk.
What tools and measures are available to get compliant?
Measures fall into three categories: technical anti-phishing protection, content governance and advertising transparency. Each one requires different tools.
| Area | Tool / Measure | Who implements it | Indicative cost |
|---|---|---|---|
| Email anti-phishing | DMARC 'reject' + SPF + DKIM | Tech team / hosting provider | Low (DNS configuration) |
| Cloned domain monitoring | Brand protection services (e.g. Netcraft, Bolster) | Security team or agency | Medium-high (subscription) |
| Ad labeling | UI review with a visible 'Sponsored' label | Design + development team | Low-medium (one-time) |
| Ad repository | Ad database with public API | Development team | Medium (VLOPs only) |
| Content reporting system | Report form + internal review process | Legal + operations team | Low (internal process) |
| Periodic risk assessment | DSA audit with the official EU Commission checklist | Legal team or external consultant | Medium (consulting) |
The California law on streaming ads, analyzed in a dedicated article, shows how advertising transparency rules are converging globally. This isn't a European quirk: it's a direction the market is taking everywhere.
What are the real risks of not complying?
Penalties can reach up to 6% of annual global turnover. But the reputational risk and the loss of user trust can be even more costly.
The €120 million fine on X (formerly Twitter) showed that the EU Commission isn't stopping at big American platforms. The proceeding against Booking.com, a company based in the Netherlands, confirms that European platforms are in the crosshairs too.
The risk isn't just financial. A platform linked to fraud or phishing loses users' trust quickly, and rarely wins it back. For a marketplace or a booking portal, reputation is the product.
It's worth remembering that similar penalties for non-compliance have already been issued under the GDPR as well: the €8.6 million RTB fine and the €825 million Uber fine show that European regulators are enforcing the rules with growing consistency.
Why has the DSA become urgent right now?
The DSA has applied in full to all platforms since February 2024, but the first formal proceedings are only arriving now. The grace period is over.
For almost two years, the Commission worked mainly with the largest platforms, gathering data and opening informal dialogues. The proceeding against X in late 2025 and the one against Booking.com in October 2026 mark a change of pace: systematic enforcement has begun.
The context is made worse by the explosion of digital fraud. Check Point Research data shows a 55% rise in malicious travel domains in 2025 alone. Scammers adapt fast; platforms that don't keep up become unwitting tools for fraud.
How do you actually get started with a DSA audit for your platform?
Start by mapping the three risk areas identified in the Booking.com case, then set priorities based on your platform's actual exposure.
- 1 · Legal team or consultantCheck whether the DSA applies to youReview your company size and monthly EU users. Micro and small businesses are exempt from the heaviest obligations.
- 2 · Tech teamDomain anti-phishing auditCheck your DMARC, SPF and DKIM setup. If you're not at the 'reject' level, enable it within 15 days.
- 3 · Design + development teamAd labeling reviewEvery sponsored item must be visually distinguishable. Make sure the 'Sponsored' label is present and legible on all devices.
- 4 · Operations teamContent reporting systemThe DSA requires a mechanism for users to report illegal or fraudulent content. If you don't have one, build it.
- 5 · Legal teamDocumented risk assessmentPrepare a document describing the risks you've identified and the measures you've taken. In an investigation, it's the first thing they'll ask for.
- 6 · All teamsRegular updatesDSA compliance isn't a one-off fix. Plan quarterly reviews and keep an eye on the Commission's updated guidelines.
What mistakes do companies make most often when complying with the DSA?
The most common mistake is treating the DSA as a purely legal issue and handing it to the legal department without involving the tech and marketing teams.
The Booking.com case makes this clear: the alleged violations aren't errors in contracts or privacy policies. They're design problems (unlabeled ads), technical architecture problems (unblocked phishing) and operational process problems (fraudulent listings left up). These can only be solved with several teams working together.
| Common mistake | Why it's wrong | What to do instead |
|---|---|---|
| Leaving everything to the legal department | DSA violations are often technical or design-related, not contractual | Involve developers, designers and marketing |
| Assuming SMEs are completely excluded | SMEs are exempt from the heaviest obligations, but not all of them | Check case by case with a consultant |
| Updating the privacy policy and calling it done | The DSA requires operational action, not just documents | Implement real reporting and labeling systems |
| Ignoring the DSA-GDPR overlap on ads | The two regulations overlap and call for coordinated solutions | Align legal, marketing and development teams |
| Not monitoring cloned domains | Scammers use domains similar to yours to phish your customers | Set up a brand protection or DNS monitoring service |
How can you tell if your platform is truly compliant?
Each of the three risk areas has measurable indicators. Tracking them regularly is more useful than an annual audit.
| Area | Indicator | Alert threshold | Check frequency |
|---|---|---|---|
| Anti-phishing | Active DMARC level | Any level below 'reject' | Monthly |
| Anti-phishing | Fraudulent email reports from customers | More than 1 report per month | Weekly |
| Fraudulent listings | % of listings removed within 24 hours of a report | Below 90% | Monthly |
| Ad transparency | % of ads with a visible 'Sponsored' label | Any value below 100% | At every deploy |
| Governance | A documented, up-to-date risk assessment exists | Document older than 6 months | Quarterly |
So, is the DSA a real problem for your platform?
Worth it if you run a marketplace, a portal with third-party listings or a platform with paid ads, and you have users in the EU: the DSA applies to you, and the three areas of the Booking.com investigation are probably relevant. Start with the technical audit within 30 days.
Somewhere in between you have an e-commerce store with your own products and some form of sponsored ranking: the ad labeling requirement still applies. Check your UI and your anti-phishing email setup as a minimum priority.
Not yet if you're a micro or small business (under 50 employees and €10 million in revenue) with no third-party listings: the DSA's heaviest obligations don't apply. Still, protecting your email domain with DMARC is worth it regardless of the regulation.
How we see it at SHM
For us, the Booking.com case confirms something we often see in web architecture and digital integration projects: regulatory compliance gets treated as a legal problem, when it's almost always a design and process problem. Unlabeled ads aren't a contractual oversight; they're an interface problem. Unblocked phishing isn't a gap in the privacy policy; it's a technical configuration problem.
We believe that simplifying digital, making it transparent, safe and understandable for users, is the highest form of expertise. And here, it's also the smartest form of risk management.
If you run a platform or marketplace and want to know where you're exposed, we can help with a structured audit. Our strategic AI integration and web security services cover exactly the technical areas the DSA puts under scrutiny. If you need to train your team in-house on the topic, our business process automation training also covers content governance workflows. You can find more insights on digital regulation and technology in the Project management and technology section.
Frequently Asked Questions
Micro and small businesses (under 50 employees and €10 million in turnover) are exempt from the heaviest DSA obligations. However, if your site hosts third-party listings or ads, some basic obligations still apply. It's worth checking your specific situation with a legal advisor.
Fines can reach up to 6% of annual global turnover. For the largest platforms, in case of systematic violations, the Commission can also impose temporary measures or suspensions. The reputational risk of being associated with fraud or phishing can be even more costly than the fines.
Article 26 of the DSA requires every sponsored item to be visually distinguishable from organic results, showing who paid for it and why that ad is being shown to that user. A small gray line of text isn't enough: it must be clear and legible on every device.
DMARC is a technical protocol that stops fraudulent emails from appearing to come from your domain. It isn't an explicit DSA requirement, but it's the most effective technical measure for reducing phishing risk that exploits your brand. The 'reject' level offers maximum protection.
They are two separate regulations, but they overlap, especially on advertising. The GDPR governs the collection and processing of personal data; the DSA governs online platforms' responsibilities for content and transparency. For ads, the two regulations create obligations that must be met at the same time, which requires coordination between legal, marketing and development teams.
VLOPs (very large online platforms) are those with more than 45 million monthly users in the European Union. The official list is published by the European Commission. If you're not on that list, you're not a VLOP, but the DSA's baseline obligations still apply to every platform operating in the EU.
The DSA doesn't ask platforms to be perfect. It asks them to show they're genuinely trying, with documented systems and verifiable processes.
Related articles
Discover more articles exploring similar topics, selected to offer you a more complete and stimulating perspective. Each piece of content is carefully chosen to enrich your experience.