PSAP do-not-call registry: what it is and who it protects

Last updated 2026-07-09

What is a PSAP and why does it have its own DNC registry?

PSAP stands for Public Safety Answering Point. It is the official term for any facility that receives 911 calls and dispatches emergency responders. Every county sheriff's dispatch center, city police communications hub, and regional emergency operations center that answers 911 is a PSAP. Roughly 5,700 PSAPs operate in the United States ^[1].

When a telemarketing robocall or spam text hits a PSAP line, it does more than annoy a dispatcher. It can occupy a line that someone in cardiac arrest or a burning house is trying to reach. That is not hypothetical. The FCC documented robocalls tying up emergency communications systems when it built the case for stronger PSAP protections ^[2].

Because of that specific risk, PSAPs get their own layer of protection that sits on top of the standard do not call list. The FCC maintains a separate PSAP registry. The rules are stricter in one key way: there is no established business relationship exception and no consent carve-out. If a number belongs to a PSAP, you cannot call it for telemarketing. Full stop.

What law created the PSAP DNC registry?

Two laws did the work. The Telephone Robocall Abuse Criminal Enforcement and Deterrence Act (TRACED Act), signed December 30, 2019, directed the FCC to move harder against calls to emergency lines ^[3]. The Telephone Consumer Protection Act (47 U.S.C. § 227) had already banned autodialed calls to emergency lines since 1991. It is unlawful to "initiate any telephone call to any emergency telephone line, including any 911 line" using an automatic telephone dialing system, the statute reads ^[4].

What changed in the TRACED Act era is that the FCC formalized a registry specifically for PSAP numbers. Scrubbing obligations became explicit and the enforcement path got clearer. Before that, the TCPA prohibition existed but there was no central list to check. Callers could claim they did not know a number was a PSAP. The registry killed that defense.

The FCC's implementing rules sit in 47 C.F.R. Part 64. The agency updates the PSAP registry through its own administrative processes, and access runs through the same FCC systems that govern the national DNC registry ecosystem.

How is the PSAP registry different from the National DNC Registry?

The National Do Not Call Registry, run by the FTC under 16 C.F.R. Part 310, is a consumer list. Individuals register their personal and home numbers to opt out of most telemarketing. You can read more about how to get the do not call list and the FTC do not call list for the consumer side.

The PSAP registry is a different animal. Different purpose, different agency, different legal basis.

Feature	National DNC Registry	PSAP DNC Registry
Who registers	Individual consumers	911 emergency centers
Managed by	FTC	FCC
Consent exception	Yes, with prior express consent	No exception
EBR exception	Yes, 18-month rule	No exception
Statutory basis	47 U.S.C. § 227 + FTC Act	47 U.S.C. § 227(b)(1)(A)
Numbers on list	~249 million (2024 FTC data) [11]	~5,700 facilities [1]
Who must scrub	Telemarketers making outbound calls	Any caller using an autodialer or prerecorded message

The practical difference for a sales team comes down to one thing. The National DNC list has exceptions you might qualify for. The PSAP list has none. A PSAP number on your calling list is a hard block, regardless of how you got the number or what relationship you think you have.

Who is required to scrub against the PSAP DNC registry?

Anyone placing outbound calls with an automatic telephone dialing system or a prerecorded voice message is covered by 47 U.S.C. § 227(b)(1)(A) ^[4]. That sweeps in predictive dialers, progressive dialers, power dialers, ringless voicemail drops, and any tech that stores and dials numbers without a human entering each one before each call.

The obligation reaches third-party lead generators and dialing platforms that call on your behalf. If your vendor dials for you, you share the liability. The FCC and federal courts have held again and again that a company cannot outsource away its TCPA exposure by hiring a dialing partner ^[5].

Manual cold callers using a human-dialed phone with no automated component have narrower exposure under the PSAP rules specifically. The autodialer requirement of 227(b)(1)(A) does not apply to purely manual calls. But the reputational and practical risk of calling a 911 center is severe no matter how you dialed. Most compliance frameworks treat the PSAP list as a universal block.

If you use mobile phone do not call list scrubbing or any outbound compliance process, PSAP scrubbing should already be baked in. If it is not, fix that today.

What are the penalties for calling a PSAP number?

The TCPA sets a base statutory penalty of $500 per violating call ^[4]. Willful or knowing violations triple to $1,500 per call. The FCC has separate authority under the TRACED Act to impose forfeitures of up to $10,000 per call for calls to PSAPs specifically ^[3].

Those numbers compound fast. A single robocall campaign that blasts 50,000 numbers and hits even two PSAP lines could generate $20,000 in FCC exposure before private litigation even starts. TCPA claims are privately actionable, so the PSAP itself or parties harmed by blocked emergency service could sue.

The FCC has gone after robocallers who flooded emergency lines. In one widely cited matter, the agency moved against parties whose spam calls disrupted public safety communications, treating those violations as among the most serious in its robocall portfolio ^[2].

The dollar figure is only part of it. Calling a PSAP creates the kind of regulatory attention that lingers. The FCC coordinates with state attorneys general on robocall enforcement. A single complaint from a 911 center lands very differently than a consumer complaint does.

For how TCPA penalties scale across violation types, the do not call list report framework and enforcement trends are worth reading.

How do you get access to the PSAP DNC list to scrub against it?

The FCC administers the PSAP registry through its own systems, and access runs through the same portal infrastructure that supports its robocall enforcement programs. Compliance data vendors, including the major DNC scrubbing platforms, fold PSAP numbers into their suppression lists automatically.

Most outbound teams never pull the raw PSAP list straight from the FCC. They rely on a compliance vendor or dialing platform to keep an up-to-date suppression file that carries PSAP numbers alongside state and federal DNC data. For direct FCC access, start with the FCC's Consumer and Governmental Affairs Bureau, which oversees the registry ^[2].

If you are vetting a compliance vendor, ask them straight: does your suppression list include PSAP numbers from the FCC registry, and how often do you update it? A vendor that cannot confirm this on the spot and name an update cadence is a vendor worth replacing.

Run the do not call telemarketer list scrub and the PSAP scrub in the same pass, before any campaign launches. Separating them adds work and buys you nothing.

LeadCompliant's free DNC checker includes PSAP suppression in its lookup, which is one way to spot-check before a campaign goes live.

Do state do-not-call laws add additional PSAP protections?

Several states have telemarketing statutes that reference or independently protect emergency lines. Florida runs its own framework under the Florida Telemarketing Act, with emergency line protections alongside it ^[6]. Indiana and Pennsylvania have state-level telemarketing laws that sit next to the federal PSAP rules ^[7][8].

The federal framework under 47 U.S.C. § 227 preempts state law where the two conflict, but states can and do add extra requirements. A state might define "emergency line" more broadly than the FCC's PSAP definition, potentially covering non-911 dispatch lines like poison control centers or hospital emergency intake numbers.

Operate in Florida? Check the Florida do not call list rules. Dialing into Indiana or Pennsylvania? Same drill for the Indiana do not call list and do not call list PA. Each of those regimes may independently bar calls to in-state emergency lines in ways that reach past the federal PSAP registry.

The rule of thumb: check state law for the states where your called parties sit, more than where your company operates.

Can a PSAP number end up on your lead list by mistake?

Yes, and it happens more than people think. Here is why.

PSAP lines include administrative numbers tied to the 911 facility, more than the 911 trunk lines. Those administrative numbers sometimes surface in commercial databases, B2B prospecting lists, and data broker files. If you bought a list of government phone numbers or scraped a government directory, there is a real chance a PSAP administrative line rode along.

Number reassignment makes it worse. A PSAP can take over a number that used to belong to a commercial entity. Your list vendor may have verified that number as a legitimate business contact 18 months ago. It may now route to a 911 communications center ^[9].

That is exactly the scenario the FCC's Reassigned Numbers Database (RND) was built for. The RND, launched in 2021, lets callers check whether a number has been reassigned since they last had consent or contact ^[9]. PSAPs are among the entities whose numbers can show up there after reassignment.

The honest answer to "how do I avoid accidentally calling a PSAP" is layered scrubbing. Run your list against the PSAP registry directly. Run it against the RND for reassignment. Suppress any number that resolves to a government entity you cannot positively confirm as a legitimate commercial contact.

What should your compliance process look like for PSAP scrubbing?

A workable PSAP compliance process has four steps.

First, before any campaign launches, run your full dial list through a suppression file that includes FCC PSAP numbers. Make it automated and non-optional in your dialing platform, not a manual checkbox a campaign manager can skip on a busy morning.

Second, run a reassigned numbers database check in the same pass ^[9]. The RND check costs money (the FCC set per-query fees when it launched the service), but missing a reassigned PSAP number costs a lot more.

Third, document the scrub. Keep a dated log showing which suppression files you used, their version or update date, and the record count before and after suppression. If the FCC or a plaintiff ever asks whether you checked the PSAP registry before a campaign, you want a file that answers in seconds.

Fourth, re-scrub before you recycle a list. A number that was clean six months ago may not be clean now. The FCC publishes no "PSAP numbers never change" assurance, because they do change. PSAPs add lines, reassign numbers, and expand coverage areas.

LeadCompliant's compliance kit includes a pre-campaign scrub checklist that covers this, useful if you want a documented procedure to hand a teammate or a regulator.

Newer to this? The broader government do not call list framework and the do not call list number registration process give useful context before you build the PSAP-specific workflow.

Are there any exemptions or safe harbors for PSAP calls?

Short answer: no, not for telemarketing or lead generation.

47 U.S.C. § 227(b)(1)(A) bans autodialed or prerecorded calls to emergency lines. The FCC has carved out no exemption for small businesses, political calls, nonprofit solicitations, or survey calls here. The emergency line prohibition stands independent of, and stricter than, the restrictions on calls to residential numbers.

Some calls to PSAP numbers are obviously legitimate. A vendor selling dispatch software calling the PSAP's purchasing department. A utility coordination call. An emergency alert integration service. But those calls come from a human rep dialing manually to a scheduled appointment, not from an autodialer campaign. The autodialer restriction is what creates the hard prohibition.

Got a genuine reason to contact a 911 center? Do it the old way. Have a human rep call the facility's published administrative line after researching the right contact. Do not let that number sit in an automated dialing campaign.

The established business relationship safe harbor under the FTC's rules at 16 C.F.R. § 310.4 does not override the TCPA's emergency line prohibition ^[10]. Separate legal regimes. The emergency line rule wins.

What if you receive a complaint from a PSAP?

Take it seriously right away. A complaint from a 911 center carries more regulatory weight than a standard consumer complaint. PSAPs are government entities. When one files with the FCC, it goes to enforcement staff with dedicated robocall prosecution mandates under the TRACED Act ^[3].

First step: pull your campaign records for that number. When it was dialed, how many times, from which campaign, using what list, and which suppression files ran before launch. You need this to respond to a regulator and to size your exposure.

Second, suppress the number immediately and audit every active campaign for related number ranges. If one PSAP number slipped through, check for others.

Third, if a formal FCC inquiry or letter arrives, respond through counsel. The FCC's Enforcement Bureau can issue subpoenas and impose forfeiture orders without going to court. You want a lawyer reviewing your response before it leaves the building.

Fourth, document your remediation. Regulators treat complaints very differently when the respondent shows a clean process, a prompt correction, and a credible account of how the gap happened, versus no records and continued violations.

Frequently asked questions

What does PSAP stand for in telemarketing compliance?

PSAP stands for Public Safety Answering Point. It is the formal term for any facility that receives 911 emergency calls and routes them to police, fire, or EMS. In telemarketing compliance, PSAPs have their own FCC-maintained registry of protected phone numbers that all autodialed callers must scrub against before dialing, with no exceptions.

Is calling a PSAP number illegal under the TCPA?

Yes. 47 U.S.C. § 227(b)(1)(A) prohibits using an automatic telephone dialing system or prerecorded voice to call any emergency telephone line, including any 911 line. This ban has existed since the TCPA was enacted in 1991. The TRACED Act of 2019 added a separate $10,000 per-call forfeiture penalty for PSAP violations enforced through the FCC.

How many PSAPs are in the United States?

Approximately 5,700 PSAPs operate across the United States, per National 911 Program data maintained by the Department of Transportation. Each facility may run multiple phone lines, so the total number of PSAP-protected telephone numbers in the FCC registry is higher than the facility count.

Does the National Do Not Call Registry cover PSAP lines?

No. The National DNC Registry managed by the FTC covers residential consumers. PSAP lines are government emergency facilities, not consumer registrants. They get protection through a separate FCC-maintained registry under the TCPA and TRACED Act rules. The two systems are legally and administratively distinct, and the PSAP prohibition is stricter because it has no consent or business relationship exceptions.

Can a PSAP number accidentally appear in a purchased lead list?

Yes. PSAP administrative lines sometimes appear in government directory databases or commercial data broker files. Number reassignment is also a risk: a number that was a legitimate business contact can be reassigned to a PSAP. This is why running both a PSAP registry scrub and an FCC reassigned numbers database check before any campaign is the right process.

What is the fine for calling a 911 call center with a robocall?

The TCPA base penalty is $500 per call, tripling to $1,500 for willful violations. The TRACED Act added FCC forfeiture authority of up to $10,000 per call specifically for PSAP violations. A campaign that inadvertently reaches multiple PSAP lines can generate tens of thousands of dollars in exposure quickly, before any private litigation from the affected PSAP.

How often is the PSAP DNC registry updated?

The FCC updates the PSAP registry as 911 centers add, remove, or change phone numbers. There is no published fixed schedule equivalent to the FTC's 31-day National DNC refresh cycle. Best practice is to use a data vendor that syncs against FCC PSAP data at least monthly, and to re-scrub any list more than 30 days old before reuse.

Do political and nonprofit callers have to follow PSAP rules?

Yes. The TCPA's emergency line prohibition at 47 U.S.C. § 227(b)(1)(A) applies to any autodialed or prerecorded call to an emergency line. Political and nonprofit exemptions exist for other parts of the TCPA, like the residential DNC rules, but they do not override the emergency line prohibition. Political robocallers must scrub PSAP numbers too.

Does the PSAP registry cover text messages?

The TCPA's autodialer prohibition covers both voice calls and text messages sent by automated means. Most PSAPs now have text-to-911 capability, so PSAP numbers can receive SMS. Sending an automated marketing text to a PSAP number would likely trigger the same 47 U.S.C. § 227(b)(1)(A) liability as a robocall. Treat PSAP numbers as blocked for all automated outreach.

What is the FCC reassigned numbers database and how does it relate to PSAP scrubbing?

The FCC's Reassigned Numbers Database (RND), launched in 2021, lets callers check whether a phone number has been permanently disconnected and reassigned to a new subscriber since they last had contact. PSAPs can acquire previously commercial numbers. Running an RND check alongside a PSAP registry scrub catches numbers newly assigned to 911 centers that may not yet appear in all commercial suppression files.

Are ringless voicemail drops subject to PSAP restrictions?

This is contested legal territory. The FCC has treated ringless voicemail (direct-to-voicemail drops) as calls subject to TCPA rules in several guidance documents and proposed rules, though final definitive rulemaking has been debated. If your platform's ringless voicemail uses an automated process to deposit messages, treating PSAP numbers as hard blocks is the conservative and recommended approach.

Can a small business with fewer than 10 employees be liable for PSAP violations?

Yes. The TCPA has no small business exemption. The statute applies based on the method of the call, an autodialer or prerecorded message, not the size of the caller. The FCC has pursued enforcement against small operations. If you use a predictive dialer or any automated calling technology, PSAP scrubbing is a hard legal requirement regardless of your company size.

How is PSAP scrubbing different from scrubbing the federal DNC list?

Federal DNC scrubbing identifies consumer residential numbers that have opted out of telemarketing. PSAP scrubbing identifies government emergency facility numbers that are prohibited by statute. The legal basis, the managing agency (FTC versus FCC), the list size, and the available defenses all differ. You need both scrubs, run separately or through a vendor that combines them in one pass.

Sources

1. U.S. Department of Transportation, National 911 Program: Approximately 5,700 PSAPs operate across the United States
2. TRACED Act, Pub. L. 116-105 (2019): TRACED Act signed December 30, 2019, directed FCC to strengthen enforcement and imposed up to $10,000 per-call forfeiture for calls to PSAPs
3. 47 U.S.C. § 227, Telephone Consumer Protection Act: TCPA prohibits initiating any telephone call to any emergency telephone line including any 911 line using an automatic telephone dialing system; base penalty $500 per violation, $1,500 for willful violations
4. Florida Telemarketing Act, Fla. Stat. § 501.059: Florida has its own telemarketing statute with emergency line protections
5. Indiana Autodialer Law, Ind. Code § 24-5-14: Indiana has state-level telemarketing law complementing federal PSAP rules
6. Pennsylvania Telemarketer Registration Act, 73 P.S. § 2241: Pennsylvania has state-level telemarketing statute with provisions covering emergency lines
7. FTC Telemarketing Sales Rule, 16 C.F.R. Part 310: Established business relationship safe harbor under FTC TSR at 16 C.F.R. § 310.4 does not override the TCPA's emergency line prohibition
8. FTC, National Do Not Call Registry Data Book FY 2024: Approximately 249 million consumer numbers registered on the National DNC Registry as of 2024