Tapper
AlertsPricing
Display & programmatic
Open exchange
Domain spoofing

Domain spoofing on open exchange programmatic campaigns

Domain spoofing is the defining invalid traffic risk of open exchange RTB, where invalid publishers misrepresent low-quality inventory as premium publisher placements in the bid stream your DSP buys against.

Trusted by leading brands worldwide

Tiffany & Co.
Adidas
Azadea
Punt Roma
Salsa Jeans
Sunglass Hut
Decathlon
Honda
Lexus
Mercedes-Benz
TOD
Toyota
Volvo
STC
Porsche
Almosafer
Infiniti
LEGOLAND
Cleveland Clinic
Nissan
Boggi Milano
Kiko Milano
Hyundai
Chevrolet
Aape
Kiabi
Maje Paris
Sandro
Ted Baker
ACE
Tawuniya
TOEFL
Regit
You.gr
Spitishop

Domain spoofing is structurally enabled by the open exchange RTB architecture

Domain spoofing is possible on the open exchange because the RTB bid request contains self-declared publisher information that the auction infrastructure cannot verify in the milliseconds available for auction processing. An invalid publisher declares a premium news domain in the bid request. Your DSP reads that declaration, runs it through brand safety filters, approves the bid, and pays a premium CPM. The impression is actually served on a bot farm with no relation to the declared publisher. Your campaign report shows delivery against premium inventory that your ads never actually reached.

Ads.txt was introduced specifically to address domain spoofing by establishing an authoritative list of sellers authorized to sell a domain's inventory. It has materially reduced the problem, but significant gaps remain. Many publishers maintain incomplete or outdated ads.txt files. Buyer enforcement at the impression level is inconsistent. Bad actors continuously adapt their techniques to exploit gaps between what ads.txt declares and what the bid stream actually enforces. Active impression-level monitoring remains essential for open exchange advertisers who want genuine protection rather than a false sense of security from ads.txt compliance.

How Tapper stops domain spoofing on Display open exchange

Three steps from connection to clean campaign data, no engineering required.

01

Connect your DSP to Tapper for impression-level monitoring

Tapper integrates with your demand-side platform and monitors every bid request and impression event in your open exchange buy, verifying declared publisher domains against authorized seller records.

02

Spoofed domains identified at the impression level before spend occurs

Declared publisher domains are cross-referenced against ads.txt records, known spoofing patterns, and traffic quality signals to identify misrepresented inventory before your budget is committed to invalid placements.

03

Spoofed inventory suppressed from your open exchange buying

Identified spoofed inventory sources are added to suppression lists applied to your ongoing open exchange buying, with campaign reports corrected to reflect delivery against genuine publisher inventory.

Domain spoofing on Display open exchange by the numbers

Data from Tapper's platform analysis and published industry research.

3,400+

Unique spoofed domains detected on the open exchange per month

$84B

Lost globally to invalid traffic annually

3x

Higher domain spoofing rate on open exchange vs private marketplace

20-40%

Average IVT rate on open exchange programmatic

Tapper vs standard brand safety tools

Capability
Tapper
Standard brand safety tools

Domain spoofing detection on open exchange

Tapper

Impression-level domain verification and real-time flagging

Standard brand safety tools

Post-bid analysis only, no pre-spend protection

Ads.txt gap coverage

Tapper

Active monitoring beyond ads.txt limitations

Standard brand safety tools

Relies on ads.txt enforcement alone

Spoofed inventory suppression

Tapper

Automated and instant per identified source

Standard brand safety tools

Manual blocklist updates required

Campaign report accuracy

Tapper

Corrects delivery data to reflect genuine publisher inventory

Standard brand safety tools

Reports reflect declared domain including spoofed entries

Case studies

Leading brands growing with Tapper

See how companies are protecting their ad budgets and improving ROI with Tapper.

Frequently asked questions

The open exchange bid stream processes self-declared publisher information with no real-time verification capability. Any publisher can declare any domain in a bid request, and the millisecond auction window means buyers must trust declared data rather than verify it independently. PMP and programmatic guaranteed deals involve direct publisher relationships that make domain spoofing attacks significantly harder to execute at scale.

Ads.txt significantly reduces domain spoofing by creating a public record of which sellers are authorized to sell a publisher's inventory, but it has real limitations. Not all publishers maintain current and complete ads.txt files. Buyer enforcement at the impression level is inconsistent. Bad actors continuously adapt to exploit gaps between ads.txt declarations and actual bid-stream enforcement. Active impression-level monitoring is necessary to catch what ads.txt misses.

Standard brand safety tools screen the declared publisher domain against content adjacency criteria and brand safety categories. When that declared domain is spoofed, the brand safety check passes for a publisher your ad never actually ran on. Your ad may be served adjacent to harmful content on the real serving domain while your reporting shows a brand-safe premium publisher placement, giving you a false sense of brand safety that does not reflect actual delivery.

Stop domain spoofing on your Display open exchange

Get a demo and we will show you exactly what Tapper would block on your account, before you commit to anything.