<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[BounceProof Journal]]></title><description><![CDATA[Product, deliverability, and engineering notes from BounceProof.]]></description><link>https://blog.bounceproof.email</link><generator>GatsbyJS</generator><lastBuildDate>Mon, 24 Aug 2026 04:05:59 GMT</lastBuildDate><item><title><![CDATA[BounceProof makes plans available before signup]]></title><description><![CDATA[BounceProof makes plans available before signup Commit: 49ee78d · Date: 15 August 2026 /plans is now a public route. The new plans view…]]></description><link>https://blog.bounceproof.email/08-public-plans-page/</link><guid isPermaLink="false">https://blog.bounceproof.email/08-public-plans-page/</guid><pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate><content:encoded>&lt;h1&gt;BounceProof makes plans available before signup&lt;/h1&gt;
&lt;p&gt;&lt;strong&gt;Commit:&lt;/strong&gt; &lt;code&gt;49ee78d&lt;/code&gt; · &lt;strong&gt;Date:&lt;/strong&gt; 15 August 2026&lt;/p&gt;
&lt;p&gt;&lt;code&gt;/plans&lt;/code&gt; is now a public route. The new plans view loads tiers from &lt;code&gt;/api/billing/pricing/&lt;/code&gt; and displays prices, monthly verification allowances, seats, perks, a highlighted popular tier, loading/error states, and login, signup, and plan-selection actions.&lt;/p&gt;
&lt;h2&gt;Why users benefit&lt;/h2&gt;
&lt;p&gt;Prospective customers can compare capacity and features before creating an account, then start with the free option or choose a paid plan directly.&lt;/p&gt;
&lt;h2&gt;How this increases service value&lt;/h2&gt;
&lt;p&gt;Transparent pricing reduces purchase friction and makes recurring value easier to evaluate. Reading from the pricing API also keeps the public presentation aligned with billing configuration, supporting trust and conversion.&lt;/p&gt;</content:encoded></item><item><title><![CDATA[BounceProof keeps public pages usable when sessions expire]]></title><description><![CDATA[BounceProof keeps public pages usable when sessions expire Commit: 49ee78d · Date: 15 August 2026 The frontend API client and authentication…]]></description><link>https://blog.bounceproof.email/09-public-pages-survive-expired-sessions/</link><guid isPermaLink="false">https://blog.bounceproof.email/09-public-pages-survive-expired-sessions/</guid><pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate><content:encoded>&lt;h1&gt;BounceProof keeps public pages usable when sessions expire&lt;/h1&gt;
&lt;p&gt;&lt;strong&gt;Commit:&lt;/strong&gt; &lt;code&gt;49ee78d&lt;/code&gt; · &lt;strong&gt;Date:&lt;/strong&gt; 15 August 2026&lt;/p&gt;
&lt;p&gt;The frontend API client and authentication context now recognize public plans and legal routes. An expired token in local storage no longer redirects a visitor away from public content or blocks the plans page while background session checks run.&lt;/p&gt;
&lt;h2&gt;Why users benefit&lt;/h2&gt;
&lt;p&gt;Returning visitors can still read pricing and register even when an old login session has expired. Public information remains available without requiring a fresh login.&lt;/p&gt;
&lt;h2&gt;How this increases service value&lt;/h2&gt;
&lt;p&gt;This removes a subtle conversion barrier at the moment customers are evaluating BounceProof. It protects discovery and signup while preserving normal authentication behavior for protected areas.&lt;/p&gt;</content:encoded></item><item><title><![CDATA[BounceProof screens known spamtraps before SMTP checks]]></title><description><![CDATA[BounceProof screens known spamtraps before SMTP checks Commit: 49ee78d · Date: 15 August 2026 BounceProof adds verification/spamtraps.py…]]></description><link>https://blog.bounceproof.email/10-spamtrap-protection/</link><guid isPermaLink="false">https://blog.bounceproof.email/10-spamtrap-protection/</guid><pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate><content:encoded>&lt;h1&gt;BounceProof screens known spamtraps before SMTP checks&lt;/h1&gt;
&lt;p&gt;&lt;strong&gt;Commit:&lt;/strong&gt; &lt;code&gt;49ee78d&lt;/code&gt; · &lt;strong&gt;Date:&lt;/strong&gt; 15 August 2026&lt;/p&gt;
&lt;p&gt;BounceProof adds &lt;code&gt;verification/spamtraps.py&lt;/code&gt;, configurable CSV discovery, lowercase normalization, thread-safe caching, and a packaged list of approximately 1.2 million known trap addresses. The verification engine checks the list before disposable-domain and SMTP processing. Matches return &lt;code&gt;risky&lt;/code&gt;, reason &lt;code&gt;spamtrap&lt;/code&gt;, and &lt;code&gt;safe_to_send: false&lt;/code&gt;; SMTP is not attempted.&lt;/p&gt;
&lt;p&gt;Regression tests cover case-insensitive lookup, trap classification, and the normal non-trap path.&lt;/p&gt;
&lt;h2&gt;Why users benefit&lt;/h2&gt;
&lt;p&gt;Known honeypots become explicit exclusion signals instead of addresses that might be contacted. This can reduce sender-reputation damage, provider scrutiny, and misleading campaign results.&lt;/p&gt;
&lt;h2&gt;How this increases service value&lt;/h2&gt;
&lt;p&gt;BounceProof now answers a more valuable question than “does this mailbox respond?” It helps determine whether an address is prudent to send to, strengthening the service’s deliverability-safety promise.&lt;/p&gt;</content:encoded></item><item><title><![CDATA[BounceProof builds the frontend inside each deployment image]]></title><description><![CDATA[BounceProof builds the frontend inside each deployment image Commit: 49ee78d · Date: 15 August 2026 The root Dockerfile now uses a Node 2…]]></description><link>https://blog.bounceproof.email/11-reproducible-frontend-deployments/</link><guid isPermaLink="false">https://blog.bounceproof.email/11-reproducible-frontend-deployments/</guid><pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate><content:encoded>&lt;h1&gt;BounceProof builds the frontend inside each deployment image&lt;/h1&gt;
&lt;p&gt;&lt;strong&gt;Commit:&lt;/strong&gt; &lt;code&gt;49ee78d&lt;/code&gt; · &lt;strong&gt;Date:&lt;/strong&gt; 15 August 2026&lt;/p&gt;
&lt;p&gt;The root &lt;code&gt;Dockerfile&lt;/code&gt; now uses a Node 22 build stage to run &lt;code&gt;npm ci&lt;/code&gt; and &lt;code&gt;npm run build&lt;/code&gt;, then copies the generated frontend into the Python/Nginx runtime image. The same image also contains &lt;code&gt;spamtraps.csv&lt;/code&gt;.&lt;/p&gt;
&lt;h2&gt;Why users benefit&lt;/h2&gt;
&lt;p&gt;Customers receive the frontend compiled from the deployed source and the safety data required by the backend. Deployments no longer depend on a developer’s local or stale &lt;code&gt;frontend/dist&lt;/code&gt; directory.&lt;/p&gt;
&lt;h2&gt;How this increases service value&lt;/h2&gt;
&lt;p&gt;Builds become more repeatable across environments, reducing release surprises and ensuring new customer-facing features and safety protections arrive together. Consistency improves operational trust as BounceProof scales.&lt;/p&gt;</content:encoded></item><item><title><![CDATA[BounceProof adds explainable email verification]]></title><description><![CDATA[BounceProof adds explainable email verification Commit: 10414d5 · Date: 19 July 2026 BounceProof’s foundation combines syntax checks…]]></description><link>https://blog.bounceproof.email/01-explainable-email-verification/</link><guid isPermaLink="false">https://blog.bounceproof.email/01-explainable-email-verification/</guid><pubDate>Sun, 19 Jul 2026 00:00:00 GMT</pubDate><content:encoded>&lt;h1&gt;BounceProof adds explainable email verification&lt;/h1&gt;
&lt;p&gt;&lt;strong&gt;Commit:&lt;/strong&gt; &lt;code&gt;10414d5&lt;/code&gt; · &lt;strong&gt;Date:&lt;/strong&gt; 19 July 2026&lt;/p&gt;
&lt;p&gt;BounceProof’s foundation combines syntax checks, disposable-domain detection, role and free-provider classification, typo suggestions, DNS/MX discovery, SMTP mailbox probing, Reacher enrichment, and optional SMTP &lt;code&gt;VRFY&lt;/code&gt; checks.&lt;/p&gt;
&lt;p&gt;Results are categorized as valid, invalid, risky, unknown, disposable, catch-all, duplicate, or syntax error, with reasons, &lt;code&gt;safe_to_send&lt;/code&gt;, MX details, SMTP status, and suggestions.&lt;/p&gt;
&lt;h2&gt;Why users benefit&lt;/h2&gt;
&lt;p&gt;Users receive an actionable deliverability decision instead of a binary flag. They can remove obvious bad addresses, investigate risky records, correct likely typos, and choose quick or full verification modes. Better list quality reduces wasted sends and helps protect sender reputation.&lt;/p&gt;
&lt;h2&gt;How this increases service value&lt;/h2&gt;
&lt;p&gt;The engine turns BounceProof from a simple syntax checker into a deliverability intelligence service. Its explainable output supports both campaign decisions and automated workflows, making each verification credit more useful.&lt;/p&gt;</content:encoded></item><item><title><![CDATA[BounceProof makes large-list verification trackable]]></title><description><![CDATA[BounceProof makes large-list verification trackable Commit: 10414d5 · Date: 19 July 2026 VerificationJob, background tasks, progress…]]></description><link>https://blog.bounceproof.email/02-bulk-verification-jobs/</link><guid isPermaLink="false">https://blog.bounceproof.email/02-bulk-verification-jobs/</guid><pubDate>Sun, 19 Jul 2026 00:00:00 GMT</pubDate><content:encoded>&lt;h1&gt;BounceProof makes large-list verification trackable&lt;/h1&gt;
&lt;p&gt;&lt;strong&gt;Commit:&lt;/strong&gt; &lt;code&gt;10414d5&lt;/code&gt; · &lt;strong&gt;Date:&lt;/strong&gt; 19 July 2026&lt;/p&gt;
&lt;p&gt;&lt;code&gt;VerificationJob&lt;/code&gt;, background tasks, progress counters, duplicate detection, resumable checkpoints, indexed results, CSV export, and categorized totals establish bulk verification. The API also supports API-key single verification and credit balances.&lt;/p&gt;
&lt;h2&gt;Why users benefit&lt;/h2&gt;
&lt;p&gt;Customers can submit large lists without waiting for one long request. They can monitor progress, understand valid/invalid/risky totals, export results, and safely resume work after interruption. API access also enables signup, CRM, and campaign integrations.&lt;/p&gt;
&lt;h2&gt;How this increases service value&lt;/h2&gt;
&lt;p&gt;BounceProof becomes useful for both occasional list cleaning and repeatable production workflows. As volume grows, background processing and resumability reduce operational effort and make the service a dependable part of a customer’s data pipeline.&lt;/p&gt;</content:encoded></item><item><title><![CDATA[BounceProof introduces durable import audit trails]]></title><description><![CDATA[BounceProof introduces durable import audit trails Commit: 10414d5 · Date: 19 July 2026 ImportRun and ImportRecordLog preserve a permanent…]]></description><link>https://blog.bounceproof.email/03-import-audit-trails/</link><guid isPermaLink="false">https://blog.bounceproof.email/03-import-audit-trails/</guid><pubDate>Sun, 19 Jul 2026 00:00:00 GMT</pubDate><content:encoded>&lt;h1&gt;BounceProof introduces durable import audit trails&lt;/h1&gt;
&lt;p&gt;&lt;strong&gt;Commit:&lt;/strong&gt; &lt;code&gt;10414d5&lt;/code&gt; · &lt;strong&gt;Date:&lt;/strong&gt; 19 July 2026&lt;/p&gt;
&lt;p&gt;&lt;code&gt;ImportRun&lt;/code&gt; and &lt;code&gt;ImportRecordLog&lt;/code&gt; preserve a permanent record of every bulk-import row: lifecycle state, source identifier, sanitized raw and normalized data, action, changed fields, validation errors, exceptions, processing time, and linked verification result. Admin pages and failure queries support investigation.&lt;/p&gt;
&lt;p&gt;Audit records are created before target work, ordinary row failures do not stop later rows, and audit persistence failures are surfaced instead of silently losing evidence. Sensitive fields are redacted recursively.&lt;/p&gt;
&lt;h2&gt;Why users benefit&lt;/h2&gt;
&lt;p&gt;Teams can explain what happened to every source row, investigate disputed results, and distinguish validation failures from system errors. History remains available even if a result is later removed.&lt;/p&gt;
&lt;h2&gt;How this increases service value&lt;/h2&gt;
&lt;p&gt;Traceability makes BounceProof suitable for agencies and operational teams that need accountability and repeatability—not just an answer from an API. It also lowers support and debugging costs.&lt;/p&gt;</content:encoded></item><item><title><![CDATA[BounceProof establishes customer accounts and API access]]></title><description><![CDATA[BounceProof establishes customer accounts and API access Commit: 10414d5 · Date: 19 July 2026 The accounts application adds registration…]]></description><link>https://blog.bounceproof.email/04-accounts-and-access/</link><guid isPermaLink="false">https://blog.bounceproof.email/04-accounts-and-access/</guid><pubDate>Sun, 19 Jul 2026 00:00:00 GMT</pubDate><content:encoded>&lt;h1&gt;BounceProof establishes customer accounts and API access&lt;/h1&gt;
&lt;p&gt;&lt;strong&gt;Commit:&lt;/strong&gt; &lt;code&gt;10414d5&lt;/code&gt; · &lt;strong&gt;Date:&lt;/strong&gt; 19 July 2026&lt;/p&gt;
&lt;p&gt;The accounts application adds registration, login, email verification, password handling, account settings, API keys, demo-user tooling, and the supporting migrations. The React application provides the matching authentication and protected application flows.&lt;/p&gt;
&lt;h2&gt;Why users benefit&lt;/h2&gt;
&lt;p&gt;Customers have a clear path from signup to first verification, can retain history under an account, and can authenticate automated API requests securely.&lt;/p&gt;
&lt;h2&gt;How this increases service value&lt;/h2&gt;
&lt;p&gt;Identity, usage ownership, and API credentials turn verification into a persistent service relationship. They also provide the foundation for team access, usage controls, and paid plans.&lt;/p&gt;</content:encoded></item><item><title><![CDATA[BounceProof connects verification value to flexible billing]]></title><description><![CDATA[BounceProof connects verification value to flexible billing Commit: 10414d5 · Date: 19 July 2026 The billing system defines Free, Starter…]]></description><link>https://blog.bounceproof.email/05-credit-billing-and-plans/</link><guid isPermaLink="false">https://blog.bounceproof.email/05-credit-billing-and-plans/</guid><pubDate>Sun, 19 Jul 2026 00:00:00 GMT</pubDate><content:encoded>&lt;h1&gt;BounceProof connects verification value to flexible billing&lt;/h1&gt;
&lt;p&gt;&lt;strong&gt;Commit:&lt;/strong&gt; &lt;code&gt;10414d5&lt;/code&gt; · &lt;strong&gt;Date:&lt;/strong&gt; 19 July 2026&lt;/p&gt;
&lt;p&gt;The billing system defines Free, Starter, Growth, Pro, Agency, and Unlimited tiers with monthly and annual prices, seats, feature flags, top-up packs, and a founder lifetime deal. Credit accounts, transactions, invoices, subscription state, Square webhooks, bootstrap tooling, and billing tasks connect usage to payment.&lt;/p&gt;
&lt;h2&gt;Why users benefit&lt;/h2&gt;
&lt;p&gt;Customers pay according to measurable verification usage and can choose a plan that fits their volume. API access, priority processing, bulk dashboards, integrations, seats, and top-ups provide practical upgrade options without forcing every customer into the same model.&lt;/p&gt;
&lt;h2&gt;How this increases service value&lt;/h2&gt;
&lt;p&gt;The credit model makes cost predictable and the upgrade path understandable. Reliable transaction and webhook handling protect balances and payments, increasing trust in BounceProof as a business-critical service.&lt;/p&gt;</content:encoded></item><item><title><![CDATA[BounceProof delivers a complete customer web application]]></title><description><![CDATA[BounceProof delivers a complete customer web application Commit: 10414d5 · Date: 19 July 2026 The React frontend adds routing, protected…]]></description><link>https://blog.bounceproof.email/06-customer-web-application/</link><guid isPermaLink="false">https://blog.bounceproof.email/06-customer-web-application/</guid><pubDate>Sun, 19 Jul 2026 00:00:00 GMT</pubDate><content:encoded>&lt;h1&gt;BounceProof delivers a complete customer web application&lt;/h1&gt;
&lt;p&gt;&lt;strong&gt;Commit:&lt;/strong&gt; &lt;code&gt;10414d5&lt;/code&gt; · &lt;strong&gt;Date:&lt;/strong&gt; 19 July 2026&lt;/p&gt;
&lt;p&gt;The React frontend adds routing, protected layouts, navigation, dashboards, billing, documentation, legal pages, single verification, bulk jobs, result history, account management, authentication screens, and responsive product assets.&lt;/p&gt;
&lt;h2&gt;Why users benefit&lt;/h2&gt;
&lt;p&gt;Customers can discover the product, verify addresses, monitor jobs, review results, manage their account, and understand the API in one consistent interface.&lt;/p&gt;
&lt;h2&gt;How this increases service value&lt;/h2&gt;
&lt;p&gt;A guided workflow shortens time to first result and reduces the expertise required to use the verification engine. The same backend capability becomes accessible to both technical and non-technical users.&lt;/p&gt;</content:encoded></item><item><title><![CDATA[BounceProof adds a repeatable production foundation]]></title><description><![CDATA[BounceProof adds a repeatable production foundation Commit: 10414d5 · Date: 19 July 2026 The initial product import includes Docker…]]></description><link>https://blog.bounceproof.email/07-production-operations-foundation/</link><guid isPermaLink="false">https://blog.bounceproof.email/07-production-operations-foundation/</guid><pubDate>Sun, 19 Jul 2026 00:00:00 GMT</pubDate><content:encoded>&lt;h1&gt;BounceProof adds a repeatable production foundation&lt;/h1&gt;
&lt;p&gt;&lt;strong&gt;Commit:&lt;/strong&gt; &lt;code&gt;10414d5&lt;/code&gt; · &lt;strong&gt;Date:&lt;/strong&gt; 19 July 2026&lt;/p&gt;
&lt;p&gt;The initial product import includes Docker packaging, Nginx, Supervisor, Django entry points, environment examples, static-file handling, migration startup, Postgres/Redis/S3-compatible storage settings, deployment definitions, and SMTP source-IP rotation scripts.&lt;/p&gt;
&lt;h2&gt;Why users benefit&lt;/h2&gt;
&lt;p&gt;Customers benefit from reliable availability, consistent deployments, resilient worker processes, and greater capacity for SMTP verification. Most of these improvements are invisible when working correctly—which is exactly the point.&lt;/p&gt;
&lt;h2&gt;How this increases service value&lt;/h2&gt;
&lt;p&gt;Repeatable operations reduce deployment drift and service interruptions. SMTP rotation also supports deliverability capacity, helping BounceProof provide dependable results as customer volume grows.&lt;/p&gt;</content:encoded></item></channel></rss>