Provider certification record
Creatixdial LLC
Listed- RMD number
- RMD0040497
- FRN
- 0038552709
- OCN
Identity
- Legal business name
- Creatixdial LLC
- Doing-business-as
- CreatixReach
- Foreign Voice Service Provider
- No
- Business address
- 30 N Gould St Ste N, Sheridan WY 82801
- Filing contact
- mahmoud elhadad
Managing Member · Compliance
info@creatixdial.com
(914) 535-5885
30 N Gould St Ste N Sheridan WY 82801
United States of America - Principals, Affiliates, Subsidiaries, and Parent Companies
- Mahmoud Elhadad, sole member (100%); no parent companies, subsidiaries, or affiliates
Classification
- Provider role(s)
- Voice service provider
- STIR/SHAKEN implementation
Role Implementation Voice service provider None Overall None - Exemption rules
- The filer is exempt from the STIR/SHAKEN implementation requirement because it lacks control over the network infrastructure necessary to implement STIR/SHAKEN. The Commission recognized this exemption in the First Caller ID Authentication Report and Order, 35 FCC Rcd 3241, 3260, para. 40, and 47 CFR § 64.6305(d)(2)(i) permits a voice service provider to certify by explaining that it is unable to implement STIR/SHAKEN due to a lack of control over the necessary network infrastructure. The filer is a non-facilities-based reseller of voice services. It holds no Service Provider Code (SPC) token or STIR/SHAKEN signing certificate of its own, obtains all telephone numbers from its underlying carriers, and does not control the carrier networks over which its traffic is originated to the public switched telephone network. All call origination and caller ID authentication is performed by the filer's underlying carriers, each of which is registered in the FCC's Robocall Mitigation Database and authenticates calls under the STIR/SHAKEN framework on its own network. The filer verifies each underlying carrier's Robocall Mitigation Database registration and STIR/SHAKEN participation before routing traffic through it, and maintains a current internal register of all carriers in use. Because the filer has no signing infrastructure of its own, it cannot implement STIR/SHAKEN and instead complies through the robocall mitigation program described in its uploaded Robocall Mitigation Program Description, consistent with 47 CFR § 64.6305(a).
Prior investigations / actions
- Description
Robocall mitigation plan
Declaration
- By
- mahmoud elhadad
- Date
- 2026-07-03No Recertification Date
Listing history
| Date | Event | Detail / diff |
|---|---|---|
| 2026-07-08 | New | Initial certification filed and added to database. |