Bounces and stale contacts in podcast databases

Podcast hosting emails change with every show transfer, rebrand, or host turnover. A database entry verified in January can be dead by September. The decay is invisible until you send: the bounce arrives after the damage is done to your sending reputation.

This article expands one of the three verified gripes behind our Rephonic sentiment score of 3.0/5 (215 verified mentions, March-September 2026). The scoring method is on the methodology page; the pricing picture is on the pricing page.

How podcast contact data goes stale

What a bounce actually costs

Your email provider watches your bounce rate. Above roughly 2%, deliverability throttles begin; above 5%, your domain starts landing in spam - including your legitimate mail. A stale-database bounce rate of 10-20% (which verified customers report across podcast databases, this vendor included) can poison the inbox you also use for sales and clients.

What verified Rephonic customers report

Contact records that were right at signup going stale across months of use. The pattern is not unique to this vendor - every podcast database fights the same decay - but the complaint frequency puts it in our top two gripes for the tool.

Mitigations that work

Re-verify contacts before every campaign rather than trusting stored data, keep a suppression list of known-bounced addresses, and watch your bounce rate weekly rather than monthly. All three are standard practice; none are built into a database-only product.

The verdict

The fix for stale data is process, and the process belongs to the sending layer - which is another argument for tools that own both halves. Our sentiment score weights this as the second-ranked gripe for this vendor.

Compare across desks