# WEB-157 — A changed domain must be updated on the brand record

> When the business moves to a new domain, the registered brand website must be updated to match.

- **Rule ID:** WEB-157
- **Layer:** Website (`WEBSITE`)
- **Checks:** `brand.website currency`
- **Severity:** MEDIUM — Usually survives review, but lowers your trust score or invites manual review.
- **When it bites:** Falls due after approval, once you are live and sending
- **How it is detected:** Not knowable before submission — reported with its deadline
- **Fix type:** Wait on an external system or a required interval
- **Required by:** TCR, EZ Texting
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/website/web-157/

## Why this rule exists

The brand record is re-checked long after approval, so a stale website field turns into a dead link on somebody else's schedule — and the consequence is not a request to update it but delivery problems and a re-vetting flag. Nobody thinks of the 10DLC record when a domain changes, because it is not part of any migration checklist.

## How to fix it

Update brand.website on the brand record as part of any domain migration, and keep the old domain redirecting until the change has been through vetting. Done when the registered URL is the one customers are being sent to.

## Check this yourself

**Is the 10DLC brand record on your domain-migration checklist, alongside DNS, email and analytics?**

1. Add brand.website to the checklist now — nothing will prompt you at migration time.
2. Update the brand record as part of the move, and keep the old domain redirecting until the change has been through vetting.

*What wrong looks like:* The brand record is re-checked months later against a dead link. The consequence is a re-vetting flag and delivery problems, not a request to update the field.

## Notes

Post-approval hygiene, invisible at submission. The user has to put the brand record on their own domain-migration checklist alongside DNS, email and analytics — nothing prompts them, and the failure surfaces as a delivery problem rather than as a registration one.