Improving the Effectiveness of the Robocall Mitigation Database; Amendment of CORES Registration System, Report and Order (FCC 24-135)

Publisher

Federal Communications Commission

URL

https://docs.fcc.gov/public/attachments/FCC-24-135A1.txt

Published

2025-01-08

Updated

unknown

Accessed

2026-09-16

HTTP status

200

License

US Government work; not subject to copyright in the United States (17 USC 105); public-domain; short excerpts and locators only

Source notes citing this source

• CORES registrants must update any information submitted to CORES within 10 business days of any change, and the Commission applies this requirement to all filers including those with individual FRNs. in context
• The Commission declined to adopt a PIN requirement, declined permissive blocking for facially deficient filings, and did not adopt specific data-validation tools, leaving the Bureau authority to implement them if benefits outweigh costs. in context
• The Commission directed the Wireline Competition Bureau to establish a dedicated reporting mechanism for deficient Robocall Mitigation Database filings. in context
• The Commission adopted a $100 application processing fee for initial Robocall Mitigation Database submissions and set the same filing fee of $100 per filing for the annual recertification requirement, revising 47 CFR 1.1105. in context
• Forfeitures for these RMD violations are assessed on a daily basis as continuing violations up to the statutory maximum. in context
• The Commission established a base forfeiture of $1,000 for failure to update information that has changed. in context
• The Commission established a base forfeiture of $10,000 for each violation for filers that submit false or inaccurate information to the Robocall Mitigation Database. in context
• The Commission directed the Wireline Competition Bureau and the Office of Managing Director to develop a two-factor or stronger authentication solution for accessing the Robocall Mitigation Database, and that solution must offer users the option of phishing-resistant authentication. in context
• Recertification of existing Robocall Mitigation Database filings for the first cycle fell due on March 1, 2026. inferred in context
• The Commission set an annual deadline of March 1 for recertification of existing Robocall Mitigation Database filings. in context
• Failure to fulfil the annual recertification requirement will result in referral to the Enforcement Bureau. in context

Cite this source record

APA

WarmTransfer. (2025, January 8). Improving the Effectiveness of the Robocall Mitigation Database; Amendment of CORES Registration System, Report and Order (FCC 24-135). WarmTransfer. https://warmtransfer.net/knowledge/sources/fcc-24-135-rmd-effectiveness-order

BibTeX

@misc{warmtransfer-fcc-24-135-rmd-effectiveness-order,
  title  = {Improving the Effectiveness of the Robocall Mitigation Database; Amendment of CORES Registration System, Report and Order (FCC 24-135)},
  author = {{WarmTransfer}},
  year   = {2025},
  url    = {https://warmtransfer.net/knowledge/sources/fcc-24-135-rmd-effectiveness-order},
  note   = {Federal Communications Commission, accessed 2026-09-16}
}