Provider certification record
KAYWRLD
Listed- RMD number
- RMD0029178
- FRN
- 0037368537
- OCN
Identity
- Legal business name
- KAYWRLD
- Doing-business-as
- Foreign Voice Service Provider
- No
- Business address
- 8300 Glen Myrtle Ave, Norfolk VA 23505
- Filing contact
- James Earl
Owner · Telecommunications
kayroyy@pm.me
(571) 456-6042
8300 Glen Myrtle Ave Norfolk VA 23505
United States of America - Principals, Affiliates, Subsidiaries, and Parent Companies
- This filing entity is solely owned and operated under KAYWRLD. It has no affiliates, subsidiaries, or parent companies.
Classification
- Provider role(s)
- Voice service provider
- Gateway provider
- STIR/SHAKEN implementation
Role Implementation Voice service provider None Gateway provider None Overall None - Exemption rules
- The filer is exempt from the STIR/SHAKEN implementation obligation under 47 CFR § 64.6304(f)(2). This exemption applies because the filer does not have the ability to obtain a Service Provider Code (SPC) token necessary for STIR/SHAKEN implementation and does not have access to the public telephone network through direct IP interconnection with a terminating provider. The filer is a small private voice service provider that originates calls solely for its own use or a small closed user group and does not provide services to the general public. As such, the filer cannot reasonably implement the STIR/SHAKEN authentication framework and instead relies on a robocall mitigation program in accordance with 47 CFR § 64.6305(a).; The filer is exempt from STIR/SHAKEN implementation under 47 CFR § 64.6304(f)(2). This exemption applies because the filer lacks the technical and operational capability to implement STIR/SHAKEN. Specifically, the filer does not have direct IP interconnection with downstream voice service providers, nor does it have access to the necessary Secure Telephone Identity (STI) tokens to participate in the authentication framework. The filer operates as a small, private voice/gateway provider that originates and processes calls exclusively through traditional TDM or non-IP-based systems. Therefore, the filer cannot reasonably implement STIR/SHAKEN and has instead adopted a robocall mitigation program compliant with 47 CFR § 64.6305(a)-(b), which includes traceback cooperation, traffic monitoring, and internal controls to prevent illegal robocalls. This exemption is consistent with the FCC’s rules for providers that do not have the ability to obtain SPC tokens or operate fully within the IP-based STIR/SHAKEN ecosystem.
Prior investigations / actions
- Description
Robocall mitigation plan
Declaration
- By
- James Earl
- Date
- 2025-08-07No Recertification Date
Listing history
| Date | Event | Detail / diff |
|---|---|---|
| 2025-08-13 | New | Initial certification filed and added to database. |