Provider certification record
Black Hills Broadband LLC
Listed- RMD number
- RMD0041472
- FRN
- 0036735314
- OCN
- 487M
Identity
- Legal business name
- Black Hills Broadband LLC
- Doing-business-as
- Foreign Voice Service Provider
- No
- Business address
- 3213 W Main Street, 238, Rapid City SD 57702
- Filing contact
- Lucas Hoheisel
Managing Member · Legal
hello@blackhillsbroadband.com
(605) 206-9873
3213 W Main Street 238 Rapid City SD 57702
United States of America
Classification
- Provider role(s)
- Voice service provider
- STIR/SHAKEN implementation
Role Implementation Voice service provider None Overall None - Exemption rules
- Black Hills Broadband LLC is exempt from the requirements of 47 CFR § 64.6301 pursuant to 47 CFR § 64.6304(b), which exempts voice service providers that are incapable of obtaining an SPC token due to Governance Authority policy from those requirements until they are capable of obtaining one. STI-GA Policy Decision 001 (SPC Token Access Policy) requires that, to be cleared by the STI Policy Administrator for access to STI certificates, an entity must (1) have a current FCC Form 499-A on file with the Commission, (2) have been assigned an Operating Company Number, and (3) have certified with the Commission that it has implemented STIR/SHAKEN or complies with the Commission's robocall mitigation program requirements and be listed in the Robocall Mitigation Database. The filer satisfies the first two criteria: it has Form 499-A on file under Filer ID 838843 and holds OCN 487M. The filer cannot satisfy the third criterion until this filing is accepted and the filer is listed in the Robocall Mitigation Database. The filer is therefore presently incapable of obtaining an SPC token, and without an SPC token it cannot obtain an STI certificate from a Certification Authority or authenticate the calls it originates. The filer's downstream origination carrier applies STIR/SHAKEN attestation to the filer's traffic under that carrier's own certificate. The filer does not treat that arrangement as its own implementation, as those calls are not signed with a certificate issued to the filer and the filer holds no SPC token of its own. Immediately upon its listing in the Robocall Mitigation Database, the filer will register with the STI Policy Administrator, obtain its own SPC token and a certificate from an approved STI Certification Authority, authenticate the calls it originates on the IP portions of its network using its own certificate, and amend this certification accordingly. In the interim the filer complies with 47 CFR §§ 64.6303 and 64.6305(a) through the robocall mitigation program described in the accompanying program description.
Prior investigations / actions
- Description
Robocall mitigation plan
Declaration
- By
- Lucas Hoheisel
- Date
- 2026-08-27No Recertification Date
Listing history
| Date | Event | Detail / diff |
|---|---|---|
| 2026-08-27 | New | Initial certification filed and added to database. |