Provider certification record
Protected Harbor Inc.
Listed- RMD number
- RMD0006759
- FRN
- 0031409170
- OCN
Identity
- Legal business name
- Protected Harbor Inc.
- Doing-business-as
- Foreign Voice Service Provider
- No
- Business address
- 60 Dutch Hill Road, Suite 1, Orangeburg New York 10956
- Filing contact
- Jeffrey Futterman
Chief Operating Officer · Operations
jeff@protectedharbor.com
(201) 957-1602
60 Dutch Hill Road Suite 1 Orangeburg New York 10956
United States of America - Principals, Affiliates, Subsidiaries, and Parent Companies
- Jeffrey Futterman
Classification
- Provider role(s)
- Voice service provider
- STIR/SHAKEN implementation
Role Implementation Voice service provider Partial Overall Partial - Exemption rules
- Protected Harbor, Inc. is a voice service provider that originates calls for its business customers and interconnects with upstream carriers for call termination. The Company does not currently implement STIR/SHAKEN authentication using its own SPC token or certificate. Protected Harbor obtains SIP trunking and Direct Inward Dialing (DID) services from its upstream carrier, which performs STIR/SHAKEN authentication where applicable. As a result, Protected Harbor is not currently directly authenticating calls with its own certificate. Consistent with 47 CFR § 64.6305, Protected Harbor maintains and certifies a robocall mitigation program for any traffic that is not authenticated under STIR/SHAKEN. The Company’s mitigation program includes customer vetting (Know Your Customer procedures), monitoring of outbound calling patterns for suspicious activity, cooperation with traceback requests from the FCC and the Industry Traceback Group, and enforcement measures against customers found to be originating illegal robocalls. Protected Harbor has initiated the process to obtain the necessary registrations required for direct STIR/SHAKEN authentication, including obtaining an Operating Company Number (OCN) and registering with the Secure Telephone Identity Policy Administrator (STI-PA). Until those registrations and technical integrations are completed, Protected Harbor will continue to operate under Partial STIR/SHAKEN implementation and rely on its robocall mitigation program as permitted under 47 CFR § 64.6305.
Prior investigations / actions
- Description
- Protected Harbor did not have a Robocall Mitigation Plan on file in the FCC Robocall Mitigation Database during 2025. Following the FCC’s adoption of the Robocall Mitigation Database requirements under 47 CFR § 64.6305, the Commission issued follow-up communications requesting submission of the required plan. Due to an internal administrative oversight, Protected Harbor did not respond within the required timeframe and missed the applicable deadline. As a result, the Enforcement Bureau removed Protected Harbor from the Robocall Mitigation Database pursuant to the In the Matter of Robocall Mitigation Database Filers, Order, DA 25-737 (August 25, 2025). These Orders found that Protected Harbor had failed to timely file a required Robocall Mitigation Plan in the Robocall Mitigation Database as required by 47 CFR § 64.6305 and therefore was subject to removal until compliance was demonstrated. Following removal, Protected Harbor immediately conducted an internal compliance review, developed and implemented a Robocall Mitigation Plan, and took corrective actions to align fully with the requirements of 47 CFR § 64.6305 on August 26, 2025. The Company submitted its Robocall Mitigation Plan and related remediation materials to the FCC and filed an appeal seeking reinstatement in the Robocall Mitigation Database on August 26, 2025. On August 29, 2025, the Enforcement Bureau provisionally reinstated Protected Harbor’s Robocall Mitigation Database filing, noting that Commission staff may contact the Company to request additional changes or clarifications. On November 19, 2025, the Enforcement Bureau identified deficiencies in the Company’s filing and requested corrective updates. Protected Harbor promptly addressed the identified deficiencies and submitted this updated filing to the Bureau on February 3, 2026. On March 3, 2026, the Enforcement Bureau identified deficiencies in the Company Filing and requested corrective updates. Upon review, we determined that our previous filing incorrectly indicated full STIR/SHAKEN implementation. Protected Harbor is not currently registered with the Secure Telephone Identity Policy Administrator (STI-PA) and does not yet have an Operating Company Number (OCN) or SPC token necessary to directly authenticate calls under STIR/SHAKEN. To ensure that our filing accurately reflects our current operational status, we have updated our certification on March 5, 2026 to reflect Partial STIR/SHAKEN implementation, with our upstream carrier performing call authentication where applicable. Our robocall mitigation program remains in place in compliance with 47 CFR § 64.6305. Protected Harbor has initiated the process to obtain the required registrations, including securing an OCN and registering with the STI-PA, with the goal of implementing full STIR/SHAKEN authentication through delegated signing with our upstream provider. Once these registrations and technical integrations are completed, we will update our RMD filing accordingly to reflect full STIR/SHAKEN implementation. The matter was administrative and procedural in nature and did not involve allegations or findings of illegal robocalling, spoofing, or unlawful traffic origination. Protected Harbor has not been subject to any FCC enforcement action, monetary forfeiture, or law enforcement action related to illegal robocalling within the past two years.
Robocall mitigation plan
Declaration
- By
- Jeffrey Futterman
- Date
- 2026-03-05Last Recertified 2026-02-02
Listing history
| Date | Event | Detail / diff |
|---|---|---|
| 2026-04-28 | New | Initial certification filed and added to database. |