ads.txt Verification
Cross-reference every bid request against the publisher’s ads.txt file to confirm that the selling entity is an authorized reseller. Reject impressions from unauthorized sellers immediately.
Fraud Type Guide
Fraudsters misrepresent low-quality sites as premium publishers, tricking advertisers into paying premium CPMs for worthless placements.
Domain spoofing is an ad fraud technique in which bad actors falsify the domain information in programmatic bid requests, making low-quality or fraudulent websites appear to be premium publishers. Advertisers end up paying premium CPMs for inventory that is entirely worthless — their ads never appear on the sites they think they purchased.
The mechanism is straightforward: when an ad exchange receives a bid request, it includes the domain where the ad will supposedly be shown. Fraudsters manipulate this field, replacing the real (low-value) domain with a well-known publisher’s domain. Because the buying side trusts the declared domain, they bid aggressively — and the fraudster pockets the difference.
Step by Step
Fraudsters exploit multiple weak points in the programmatic supply chain to disguise low-value inventory as premium placements.
The fraudster modifies the domain field in the OpenRTB bid request, replacing the actual site URL with a premium publisher’s domain. DSPs see a reputable domain and bid accordingly.
Sophisticated fraudsters create counterfeit ads.txt files on spoofed domains or exploit misconfigured ads.txt records to appear as authorized sellers of premium inventory.
Using techniques like cross-domain iframes, URL masking, or server-side redirects, the fraudster ensures the ad request appears to originate from a legitimate publisher page.
Detection Methods
No single check is sufficient. Effective detection requires layering multiple verification methods across the supply chain.
Cross-reference every bid request against the publisher’s ads.txt file to confirm that the selling entity is an authorized reseller. Reject impressions from unauthorized sellers immediately.
Verify seller identities by checking the exchange’s sellers.json file. Confirm that the seller ID, domain, and entity name match the declared inventory source.
Map the full supply path from publisher to DSP. Eliminate unnecessary intermediaries and flag suspicious reseller chains that could be used to launder spoofed inventory.
Analyse individual placements for anomalies: mismatched content categories, unusual traffic patterns, impossible viewability metrics, and inconsistencies between declared and actual page content.
How Opticks Helps
Opticks automatically validates ads.txt and sellers.json records across every impression, flagging unauthorized sellers and mismatched domain declarations in real time.
Every placement is checked for domain-level anomalies: mismatched content signals, suspicious traffic fingerprints, and discrepancies between the declared URL and the actual rendering environment.
Machine learning models analyse traffic patterns at the placement level, identifying statistical anomalies that indicate spoofed domains — before budget is wasted.
Learn More
A deep dive into how domain spoofing works, real-world examples, and practical steps advertisers can take to protect their programmatic budgets.
Read the articleQuick-reference definition of domain spoofing and related ad fraud terminology, including bid request manipulation, ads.txt, and supply path optimization.
View glossaryDetect domain spoofing and other ad fraud techniques across your programmatic campaigns. Start your free trial or talk to our team.