Age-restricted content on the site must sit behind a working age gate

The requirementstatement

Where the site or the campaign carries age-restricted content, the site must present a functioning age gate in front of it.

Severityseverity: BlockingBLOCKINGBreaking this rule gets the submission rejected. There is no partial credit.
When it bitesphase: Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
What is checkedobject: age-gate interstitial on the site
Where it liveslayer: WebsiteWEBSITE
How Ekas settles itdetectability: AI · crawlCRAWLHuman checkHUMAN; Needs your live site or policy page fetched and read. Ekas crawls it the way a reviewer would. Only someone holding the document or making the call can settle it. Ekas tells you exactly what to look at.
What the fix involvesfailureClass: Fix the websiteTERMINAL_WEBSITE; The fix lives on your site. No amount of rewording the form clears it.
Who requires itauthorities: T-MobileTwilioAWSCTIA
When it appliesapplicabilityText: Applies to every 10DLC registration.

Why this rule existsrationale

The gate is what keeps a minor from reaching alcohol, tobacco, firearms or adult material through a link in a text message, and carriers charge per-message violation fees rather than merely rejecting, so the cost of getting it wrong keeps accruing. Businesses that gate their checkout often leave the marketing pages open, which is the version of this a compliance-minded operator is most likely to trip.

How to fix itremediation

Put a date-of-birth gate in front of every page carrying restricted content, enforced server-side so a direct link cannot skip it. Done when opening a product URL in a private window shows the gate before the product.

Common mistakespitfalls

Gating the checkout and leaving the catalog open fails: the reviewer opens a product page directly and never sees the gate.

Provider rejection codescodes

The code you get back when this rule is what failed, and whether that provider lets you resubmit.

Provider	Code	Resubmit
Twiliogen2	30956	Yes
T-Mobile	706	Yes

Check this yourselfattestation

Ekas flags this from what you submit, but the fact that settles it sits somewhere only you can reach.

Opening a restricted product URL directly, in a fresh private window, are you stopped by the gate before you see the product?

1Copy a deep link to a restricted page — not the homepage — and open it in a private window.
2Confirm the gate appears before any restricted content is rendered.
3Repeat for the marketing and catalog pages, not just the checkout.

What wrong looks like: The checkout is gated and the catalog is open. The reviewer opens a product page directly, never sees the gate, and carriers charge per-message violation fees rather than merely rejecting.

Notesnotes

Absorbs MSG-176, which states the requirement from the message-copy side, and BRD-280 from the brand-eligibility side. The gate's form is WEB-108 (a full date of birth), its position WEB-109, its threshold WEB-112, and whether it survives a determined visitor WEB-110 — that last one is why HUMAN is declared alongside CRAWL here: a crawl can see a gate and cannot tell whether it holds. The user has to try to bypass their own gate, by opening a restricted URL directly in a fresh browser, and confirm they are stopped.

Rules you will hit next

Other website rules at the same severity. A registration is judged as a whole, not rule by rule.

WEB-001A brand website URL is requiredBlockingBLOCKING WEB-009The website must resolve and return contentBlockingBLOCKING WEB-012A parked or for-sale domain is not a websiteBlockingBLOCKING WEB-013A pre-launch placeholder is not a websiteBlockingBLOCKING WEB-014Staging, admin and internal hosts must not be the brand websiteBlockingBLOCKING WEB-016The website must be machine-crawlableBlockingBLOCKING

All website rules

WEB-107 is one of 93 website rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.