Objective

Serving device intelligence from your own domain reduces interference from ad-blocker plugins and privacy browsers, which means fewer missed signals. This article shows you how to add a custom domain and start its verification.

Product

Fraud Risk Engine

Environment

Twilio Console

User Account Permission/Role(s) Required

Your user needs permission to add Fraud Risk Engine domains for this account. Without it, Add a domain is disabled and shows You do not have permission to add a domain.

Procedure

1. In the Twilio Console, select Identity & security in the left sidebar.
2. Select Fraud Risk Engine, then Domains.
3. Select Add a domain.
4. On the Add custom domain step, enter your domain in Domain, for example login.your-domain.com. Read the Load telemetry.js from your custom domain callout — you will need to point your client configuration at this domain as well.
5. Select Next.
6. On Choose DNS configuration method, select how you'll prove ownership:
7. Connect to your provider — sign in to your DNS provider and let it add the records for you. This option only appears when your provider is supported, and names the provider when it is known.
8. Manual — add the records yourself through your provider.
9. I'm not sure — Twilio gives you instructions you can hand to your administrator or IT team.
10. On Verify domain, follow the method you chose:
11. Manual shows the Type, Host, and Value for the A record, the CNAME record, and the CAA record. Use the copy control beside each one.
12. I'm not sure shows the same records as a message you can Copy message or Send these instructions to whoever manages your DNS.
13. Connect to your provider hands off to your provider and reports Provider connected when it succeeds.
14. Select Verify domain. The domain is registered and appears in the table with a status of Unverified until DNS propagates.

Additional Information

• Expect about 5 to 10 minutes to complete the setup, and up to 48 hours for the domain to verify.
• An account can hold up to three custom domains. At the cap, Add a domain no longer appears.
• Twilio also provisions a default domain for your account, shown as the first row in the table. That default domain must be fully verified before you can add a custom one, until then Add a domain is disabled with Your default domain is still provisioning. Try again in a moment.
• Add the CAA record alongside any CAA records you already have, rather than replacing them.
• Registering the domain is only half the job. Update your client configuration to load the detection script from this domain, or the signals keep going to the old host.
• Avoid terms like "telemetry" in the subdomain, ad-blockers commonly block them.
• If the connect-to-provider flow doesn't finish, Twilio reports Connection was not completed and suggests going back to try again or choosing a manual DNS setup instead.

This content was generated by AI and reviewed, edited, and verified by a human.